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.
Can We Build It? Yes We Can! Building an ERM Solution at the University of Notre Dame
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. What’s on tap for today?
• Background
» Our situation
• Do It Yourself
» Our approach
• ERM Components
» Modules
ER&L 2010
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
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. ERM System Development
Modular System Development
• One component at a time
• Each component specialized for
it’s own task
• Inter-connected, not inter-
dependent
ER&L 2010
13. The winding road
• Datamart
» Met reporting needs
• Usage Statistics
» Collection dev. priority
• Licensing
» Last hope for vended solution
• Acquisitions
ER&L 2010
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
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. 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
25. Publisher X Journal Collection
Publisher
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
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. 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
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. Next Steps
• Organizations - #1
• Acquisitions - #2
• CORAL Completion
» End of summer (fingers crossed)
• Why should you care?
» Sharing
» Development partner?
ER&L 2010
41. The End
Slides: http://www.library.nd.edu/eresources/downloads
• Robin Malott
» rmalott@nd.edu
• Benjamin Heet
» bheet1@nd.edu
ER&L 2010
Notas do Editor
Don’t put this slide in the version that I send in.