Can We Build It? Yes We Can! Building an ERM Solution at the University of Notre Dame

766 views

Published on

The Hesburgh Libraries at the University of Notre Dame have committed to building a custom ERM system after several years of investigating vended solutions. This presentation will include the reasons for our decision, the approach we are taking to building a custom solution, and why we think this is the best option available.

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
766
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Don’t put this slide in the version that I send in.
  • Can We Build It? Yes We Can! Building an ERM Solution at the University of Notre Dame

    1. 1. Can We Build It? Yes, We Can!Building an ERM solution at the University of Notre Dame Robin Malott, Benjamin Heet ER&L 2010 University of Notre Dame
    2. 2. What’s on tap for today?• Background » Our situation• Do It Yourself » Our approach• ERM Components » Modules ER&L 2010
    3. 3. About Us• What we’ve got » CEP (checklist for electronic products) database• What we want » What everybody wants…to be loved? » No, a working ERM• Where we’ve looked » Here, there, everywhere » What we found… ER&L 2010
    4. 4. TheCrowded ERM ER&L 2010
    5. 5. If you build it…• Why build it? » Not our first choice » Meeting priorities • Flexibility, workflows, selector initiation, and more » Modular units, modular system • “Just show me the information I need to do my job” ER&L 2010
    6. 6. ERM System DevelopmentModular System Development• One component at a time• Each component specialized for it’s own task• Inter-connected, not inter- dependent ER&L 2010
    7. 7. ERM System DevelopmentAdvantages• Promotes collaboration• End users see progress quicker• Easier implementation ER&L 2010
    8. 8. ERM System DevelopmentDisadvantages• Important to have a strong framework and standards• Needs programmer on staff ER&L 2010
    9. 9. ERM System DevelopmentOur Approach• PHP and MySQL• Focus on workflow• Simplified interface design ER&L 2010
    10. 10. “Out of intense complexities, intense ”simplicities emerge.Winston Churchill ER&L 2010
    11. 11. Centralized Online Resources Acquisitions and CORALLicensing Data Mart Reporting Tool Usage Statistics Acquisitions Licensing Organization s Cancellation ER&L 2010
    12. 12. Data Mart Reporting Tool ER&L2010
    13. 13. The winding road• Datamart » Met reporting needs• Usage Statistics » Collection dev. priority• Licensing » Last hope for vended solution• Acquisitions ER&L 2010
    14. 14. Usage Statistics Module• Need a better way to manage » Pay someone else » Build our own• What is important to us? » Less time gathering stats » Find out what the numbers mean ER&L 2010
    15. 15. Override bad data…itIncludes archivehappens!reports ER&L 2010
    16. 16. - Logfile of uploadactivity- Link to original file ER&L 2010
    17. 17. ER&L 2010
    18. 18. ER&L 2010
    19. 19. Statistics Highlights• Avoiding junk in, junk out » HTML vs PDF • Springer vs ScienceDirect » Outliers • Use spikes, fair or personal archiving » General bad data • Missing/incorrect issn, duplicate data ER&L 2010
    20. 20. Licensing Module• Datamart, Statistics – Done• Still looking for vendor ERM » Licensing as last straw• Opportunity knocks » Law student with programming skills• OK, let’s build this one too » Final commitment to local development made ER&L 2010
    21. 21. Queue showing licenses with activestatus ER&L 2010
    22. 22. Search against license, document andprovider names ER&L 2010
    23. 23. Showing scanned license, viewChildren child amendment to primaryOpen thedocuments associated to parentlicenseterms/expressions ER&L 2010
    24. 24. ER&L 2010
    25. 25. Publisher X Journal CollectionPublisher X Un-named License Agreement ForAdd terms delivered to users via SFX Display many expressions as us, as Notes for external you’d like menu use ER&L 2010
    26. 26. Confidential License Agreement Compare expressions across all documents! ER&L 2010
    27. 27. Licensing Highlights• Keyword search• Expression comparison• Delivery of terms to users » ILL, Coursepacks, eReserves• Flexibility http://closedstacks.files.wordpress.com/2009/01/thumbs-up.jpg » Customize fields » Track expressions of your choice ER&L 2010
    28. 28. Cancellation Module• Datamart, Usage, Licensing – Done• The Nitty-Gritty » Needs assessment » Focus Groups• Wow, that’s a big project! » Start small » Redesign cancellation system as proof of concept ER&L 2010
    29. 29. my folderin progress current queue ER&L 2010
    30. 30. personal queue mark complete ER&L 2010
    31. 31. Simplified View for Collection Managers ER&L 2010
    32. 32. Detailed View for Staff and Administrators ER&L 2010
    33. 33. Routing View ER&L 2010
    34. 34. send emailnotificationsthrough tool everyone involved in process ER&L 2010
    35. 35. Search ER&L 2010
    36. 36. Cancellation Highlights• Selector Initiation » Save to My Folder (for later)• Routing » Workflow queue » Notification alerts » In process status• Functionality / Infrastructure ER&L 2010
    37. 37. Acquisitions Module• Re-purpose, expand Cancellation » Product » Cost » Licensing » Routing » Organizations • Contacts, Account numbers, Support ER&L 2010
    38. 38. InProgress ER&L 2010
    39. 39. Organizations Module• Organizations Module?? » Organizations exist in each module • Publishers, providers, platforms, vendors, e tc • A logical link between systems » Parent / Child Organizations » Contact names for each organization• How do we organize that data? ER&L 2010
    40. 40. Next Steps• Organizations - #1• Acquisitions - #2• CORAL Completion » End of summer (fingers crossed)• Why should you care? » Sharing » Development partner? ER&L 2010
    41. 41. The End Slides: http://www.library.nd.edu/eresources/downloads• Robin Malott » rmalott@nd.edu• Benjamin Heet » bheet1@nd.edu ER&L 2010

    ×