- ARL Position Description Bank - University of Florida George A. Smathers Libraries May 2012
Download ReportTranscript - ARL Position Description Bank - University of Florida George A. Smathers Libraries May 2012
- ARL Position Description Bank - University of Florida George A. Smathers Libraries May 2012 Agenda • Introductions • Background • Project Timeline • Design and Architecture • Discussion: • Assess user needs • System specifications Overall Goal an interactive discussion Project Team Brian W. Keith Associate Dean, Administrative Services and Faculty Affairs Bonnie J. Smith Assistant Program Director, Human Resources Laurie N. Taylor Digital Humanities Librarian Mark V. Sullivan Head, Digital Development and Web Services Introductions Participant Introductions Basic Concepts • Position descriptions are an important element of HRM if: Maintained Organized Accessible • Our institutions expend effort managing them: Archiving Locating/Retrieving Monitoring Distributing • Institutions frequently solicit example PD’s from other institutions and sharing this information has value Assumptions An effective, free system developed in partnership could enhance or ease the management of these documents and improve their usefulness to institutions A national-level, long-term digital archive of PD’s, if browsable and searchable, would improve the sharing of information about our industry Premise Institutional level value is provided in enhanced processing of PD’s through improved findability, access, and archiving which supports their use and maintenance This institutional value will lead to adoption and use of the system which results in an industry level resource of current and evolving description of duties and the work of libraries Project ARL has sponsored the development of this system It will be developed by a UF team, with broad input from other institutions, and hosted in perpetuity by UF Libraries Project Timeline • Planning Phase (April – June 2012) • Implementation Phase (June 2012-January 2013) • Launch Phase (January-March 2013) Project Timeline • Planning Phase (April – June 2012) • Assess user needs (Includes first series of webinars) • Develop and vet systems specifications (Includes next series of webinars) Project Timeline • Implementation Phase (June 2012-January 2013) • • • • Develop system and support documentation Beta test Evaluation of feedback Finalize system and documentation Project Timeline • Launch Phase (January-March 2013) • • • • System becomes available for all institutions Marketing User Support Evaluation After the Active Project Ends Successful adoption of the system by institutions will result in the maintenance of the data Your Role • Planning Phase (April – June 2012) • Assess user needs • Develop and vet systems specifications • Implementation Phase (June 2012-January 2013) • Beta test • Feedback Design Elements Web application Documents and metadata uploaded and updated by institutions Files could be text, PDF, or Word documents A simple, intuitive, easy to use interface Use of metadata or keywords to search Ability to customize and brand at the institutional level Secure digital preservation Architecture Standard metadata fields • • • • • • • • % FTE FLSA status Position type Employment type Institution type Dates Working title Job type – borrowing from ARL salary survey Architecture A series of fields not externally viewable Standard • • • • • • Employee name Supervisor name Position number Department/branch Date reviewed/modified Notes A number of customizable alpha/numeric fields Architecture Features • Archives and access to previous versions of PD’s for a position • Support for the establishment of review schedules • Run internal only reports Today’s Discussion 1. What documents do we currently use? Today’s Discussion 2. How do we manage these? Today’s Discussion 3. Does the proposed metadata make sense and are we missing anything? • • • • • • • • % FTE FLSA status Position type Employment type Institution type Dates Working title Job type – borrowing from ARL salary survey Today’s Discussion 4. Job types? Acquisitions Archivist/Curator Assessment Cataloger Collection Development Scholarly Communication/ Copyright Development/Fundraising Off-site storage Reference/Research Document Delivery Finance/Budget/Accounting Instructional Technology IT, Programmer IT, Web Developer Media Specialist Public Services Subject Specialist Access Support Acquisitions Communications/Public Information Digital Scholarship and Production Digital Services Facilities Planning and Management ILS Rare Books/Manuscripts Instructional Services Exhibits Human Resources IT, Analyst IT, Systems Library Storage Facility Preservation Reference Technical Services Today’s Discussion 5. Features? Archive and access to previous versions of PD’s Supports establishment of review schedules Reporting Today’s Discussion 6. What else – what are we missing or should we think about? - ARL Position Description Bank Thank you - Contact Information Bonnie Smith Email: [email protected] Phone: 352-273-2603