University of Florida Digital Collections Home
UFDC Home   |   Help  |   RSS
<%BANNER%>
ARL Position Description Bank ( ARL PD Bank ) Presentation Slides, Webinar One
ALL VOLUMES CITATION DOWNLOADS PDF VIEWER
Full Citation
STANDARD VIEW MARC VIEW
Permanent Link: http://ufdc.ufl.edu/AA00011258/00001
 Material Information
Title: ARL Position Description Bank ( ARL PD Bank ) Presentation Slides, Webinar One
Physical Description: Presentation Slides (PPT)
Creator: Keith, Brian W.
Smith, Bonnie J.
Sullivan, Mark V.
Taylor, Laurie N.
Publisher: George A. Smathers Libraries
Place of Publication: Gainesville, FL
Publication Date: 5/8/2012
 Notes
Abstract: Presentation slides for the first webinar (May 8, 2012) on the ARL PD Bank. The ARL PD Bank will allow individual institutions to upload their position descriptions directly into the ARL PD bank. It will provide ease of collaboration between personnel officers from different academic libraries as well as provide each participating institution a sophisticated and customizable system for managing their own PDs.
 Record Information
Source Institution: University of Florida
Holding Location: University of Florida
Rights Management: All rights reserved by the source institution.
System ID: AA00011258:00001

Downloads

This item is only available as the following downloads:

PresentationWebinar1_05082012 ( PDF )

PresentationWebinar1_05082012 ( PPTX )


Full Text

PAGE 1

-ARL Position Description Bank -University of Florida George A. Smathers LibrariesMay 2012

PAGE 2

Agenda•Introductions •Background •Project Timeline •Design and Architecture •Discussion: •Assess user needs •System specifications

PAGE 3

Overall Goalan interactive discussion

PAGE 4

Project Team Brian W. KeithAssociate Dean, Administrative Services and Faculty Affairs Bonnie J. SmithAssistant Program Director, Human Resources Laurie N. TaylorDigital Humanities Librarian Mark V. SullivanHead, Digital Development and Web Services

PAGE 5

IntroductionsParticipant Introductions

PAGE 6

Basic Concepts•Position descriptions are an important element of HRM if: MaintainedOrganized Accessible •Our institutions expend effort managing them: ArchivingLocating/Retrieving MonitoringDistributing •Institutions frequently solicit example PD’s from other institutions and sharing this information has value

PAGE 7

AssumptionsAn 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

PAGE 8

PremiseInstitutional 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

PAGE 9

ProjectARL 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

PAGE 10

Project Timeline•Planning Phase (April –June 2012) •Implementation Phase (June 2012-January 2013) •Launch Phase (January-March 2013)

PAGE 11

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)

PAGE 12

Project Timeline•Implementation Phase (June 2012-January 2013) • Develop system and support documentation • Beta test • Evaluation of feedback • Finalize system and documentation

PAGE 13

Project Timeline•Launch Phase (January-March 2013) •System becomes available for all institutions •Marketing •User Support •Evaluation

PAGE 14

After the Active Project EndsSuccessful adoption of the system by institutions will result in the maintenance of the data

PAGE 15

Your Role•Planning Phase (April –June 2012) •Assess user needs •Develop and vet systems specifications •Implementation Phase (June 2012-January 2013) •Beta test •Feedback

PAGE 16

Design ElementsWeb 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

PAGE 17

ArchitectureStandard metadata fields• % FTE • FLSA status • Position type • Employment type • Institution type • Dates • Working title • Job type –borrowing from ARL salary survey

PAGE 18

ArchitectureA 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

PAGE 19

ArchitectureFeatures •Archives and access to previous versions of PD’s for a position •Support for the establishment of review schedules •Run internal only reports

PAGE 20

Today’s Discussion1.What documents do we currently use?

PAGE 21

Today’s Discussion2.How do we manage these?

PAGE 22

Today’s Discussion3.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

PAGE 23

Today’s Discussion4.Job types? Acquisitions Access Support Archivist/Curator Acquisitions AssessmentCommunications/Public Information Cataloger Digital Scholarship and Production Collection Development Digital Services Scholarly Communication/ Copyright Facilities Planning and Management Development/FundraisingILS Off site storage Rare Books/Manuscripts Reference/Research Instructional Services Document DeliveryExhibits Finance/Budget/AccountingHuman Resources Instructional TechnologyIT, Analyst IT, ProgrammerIT, Systems IT, Web DeveloperLibrary Storage Facility Media Specialist Preservation Public ServicesReference Subject SpecialistTechnical Services

PAGE 24

Today’s Discussion5.Features? Archive and access to previous versions of PD’s Supports establishment of review schedules Reporting

PAGE 25

Today’s Discussion6.What else –what are we missing or should we think about?

PAGE 26

-ARL Position Description Bank Thank you -Contact Information Bonnie Smith Email: ARLPDBank@uflib.ufl.edu Phone: 352-273-2603




TRACE ROUTE

Total Execution Time: 45 Milliseconds

MILLISECOND   CLASS.METHODMESSAGE
0sobekcm_page_globals.constructor
0sobekcm_page_globals.constructorApplication State validated or built
0sobekcm_database.verify_item_lookup_object
0sobekcm_page_globals.constructorNavigation Object created from URI query string
0sobekcm_database.verify_item_lookup_object
0sobekcm_page_globals.display_itemRetrieving item or group information
0sobekcm_page_globals.get_entire_collection_hierarchyRetrieving hierarchy information
0sobekcm_assistant.get_entire_collection_hierarchy
0cached_data_manager.retrieve_item_aggregation
0cached_data_manager.retrieve_item_aggregationFound item aggregation on local cache
0item_aggregation_builder.get_item_aggregationFound 'all' item aggregation in cache
0system.web.ui.page.page_load (ufdc.page_load)
0sobekcm_page_globals.constructor.on_page_load
0html_echo_mainwriter.add_style_referencesAdding style references to HTML
0html_echo_mainwriter.add_text_to_pageReading the text from the file and echoing back to the output stream
45html_echo_mainwriter.add_text_to_pageFinished reading and writing the file