User:Kenirwin/ERM
 | This is not a Wikipedia article: It is an individual user's work-in-progress page, and may be incomplete and/or unreliable. For guidance on developing this draft, see Wikipedia:So you made a userspace draft. Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Electronic Resource Management (ERM) refers to practices and software systems used by libraries to keep track of important information about electronic information resources, especially internet-based resources. The development of ERM became necessary in the early 2000s as it became clear that traditional library catalogs and integrated library systems were not designed to handle metadata for resources as mutable as many online products are.
History[edit]
The idea of developing Electronic Resource Management systems emerged in 2001-2002, growing out of research by Tim Jewell at the University of Washington. The Digital Library Federation and NISO began work in May 2002 to develop standards for ERM data.[1] These standards were published in the 2004 as Electronic Resource Management: Report of the DLF ERM Initiative. [2] Since the publication of the report, several vendors of integrated library systems have released ERM products.
Examples of Commercial Products[edit]
Several library automation companies have developed ERM products, including several with generic-sounding names for specific commercial products. Some commercial systems include:
- ERM from Innovative Interfaces, Inc.
- ERMS from Sirsi Dynix, developed by Serials Solutions
- Meridian from Endeavor (now owned by Ex Libris)
- Verde from Ex Libris
- Verify from VTLS
Some open source ERM systems also exist, including:
- CUFTS from Simon Fraser University
- HERMES (Hopkins Electronic Resources ManagEment System) from Johns Hopkins University
Features of ERM systems[edit]
Features of some ERM systems include[3]:
- Supporting acquisition and management of licensed e-resources
- May be integrated into other library system modules or may be a standalone system
- May have a public interface, either separate or integrated into the OPAC
- Providing descriptions of resources at the package (database) level and relate package contents (e.g. e-journals) to the package record
- Encoding and perhaps publicly displaying licensed rights such as e-reserves, coursepacks, and interlibrary loan
- Tracking electronic resources from point of order through licensing and final access
- Contain information about the data providers, consortial arrangements, access platform
- Providing contact information for all content providers
- Logging problems with resources and providers
- Providing customizable e-mail alerting systems (e.g. notices to managers when actions are expected or required)
- Linking license documents to resource records
- Enabling access to SUSHI usage statistics
References[edit]
- ^ "DLF Electronic Resource Management Initiative". Digital Library Federation. 2004. Retrieved 2008-11-11.
{{cite web}}: Cite has empty unknown parameter:|coauthors=(help) - ^ Jewell,, Tim; et al. (2004). "Electronic Resource Management: Report of the DLF ERM Initiative". Digital Library Federation. Retrieved 2008-11-11.
{{cite web}}: Cite has empty unknown parameter:|coauthors=(help); Explicit use of et al. in:|first=(help)CS1 maint: extra punctuation (link) - ^ Feather, Celeste (2007-03-22). ERM Systems: What Are They and What Do They Do?. Columbus Metropolitan Library, Columbus, OH: OhioNET.
{{cite conference}}: Cite has empty unknown parameters:|booktitle=and|coauthors=(help)
Further Reading[edit]
Yu, Holly & Breivold, Scott (Eds.) (2008) Electronic Resource Management in Libraries: Research and Practice. Hershey, PA : Information Science Reference. ISBN 1599048914
Category:Library_and_information_science