1 / 24

Building Your ERM Knowledge Base

Building Your ERM Knowledge Base. Bigger Isn’t Necessarily Better Or Is It? NISO E-Resources Forum Denver, CO September 24-25, 2007. Session Outline. Reference sources Project goals and objectives Reality check Sources of data Record structure Outputs. Session Outline. Workflow

hewitt
Download Presentation

Building Your ERM Knowledge Base

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building Your ERM Knowledge Base Bigger Isn’t Necessarily Better Or Is It? NISO E-Resources Forum Denver, CO September 24-25, 2007

  2. Session Outline • Reference sources • Project goals and objectives • Reality check • Sources of data • Record structure • Outputs

  3. Session Outline • Workflow • Staffing • Training • Ongoing maintenance • Discussion/Examples/Questions

  4. Where would I be without my coffee?

  5. Reference sources • Digital Library Federation • Electronic Resource Management Initiative Deliverables (aka the Web hub) http://www.library.cornell.edu/elicensestudy/dlfdeliverables/home.htm • Appendix D (Data Dictionary) • Appendix E (ERM System Data Structure)

  6. Reference sources cont. • NISO activities • SERU • http://www.niso.org/committees/SERU/ • License Expression • http://www.niso.org/committees/License_Expression/LicenseEx_comm.html

  7. What do I want to accomplish? • Track trials • Track administrative details • Collect use statistics • Display better information to users • Gain control over licenses • Reports

  8. Who decides? • E-Resources Librarian • Technical Services • Library administration • Collection development • ILL • The ERM vendor!

  9. Where’s my information? • Paper files • ILS • Subscription agent • Other knowledge bases (SFX, Serials Soltuions, TDNet) • Local solutions (spreadsheets, databases) • Institutional memory

  10. Record Structure • What do you want to track and why? • DLF has a 40 page data element dictionary • Where is the data and who controls it? • Specific ERM design limitations • Consider public display and reports

  11. Outputs • Who is your audience? • OPAC • A-Z lists • Reports • Spreadsheets • SQL • Searchable web page

  12. Workflow • What can be automated? • Manual input • Assembly line approach possible? • Documentation!!!

  13. Staffing • Analyze number and skill set • License work is more time consuming • Roles and responsibilities

  14. Training • Develop a data dictionary • Templates • User Groups/online discussion lists • Vendor manuals • Practical realities • Priorities • Revise, revise

  15. Ongoing Maintenance • Whose responsibility? • Quality control • Schedule for updates • Problem reporting • Evaluation/Assessment

  16. Discussion • Buffalo examples • Data dictionary • Records • Reports • Questions

  17. Thank you! Susan Davis Head, Electronic Periodicals Management University at Buffalo UNLSDB@buffalo.edu 716-645-2784

  18. Ongoing Maintenance • Who’s responsible? • How do they know when to update? • Quality control • Reports • Are you happy with your choices?

  19. Discussion • Sample records and reports • Future developments • Questions • Answers (maybe) • Advice from others?

More Related