1 / 9

Managing E-Resource Licenses in FOLIO: A Comprehensive Guide

Discover the benefits of FOLIO's ERM platform in license management at Duke University. Learn about manual data creation, organizations, users, and more. Explore data migration considerations and the essential tools available. Get insights on license terms, permissions, and metadata creation.

nuckols
Download Presentation

Managing E-Resource Licenses in FOLIO: A Comprehensive Guide

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. E-Resource Management (ERM) Overview Duke University FOLIO Implementation PlanningLibrary Systems Platform Steering Group

  2. Benefits of FOLIO ERM for Duke University The FOLIO License App stores both metadata about  e-resource licenses and full-text license documents • Enables library staff to quickly retrieve and interpret information about current vendor agreements • Supports changing collections priorities and the Libraries’ goal to have a greater influence on the scholarly communications environment

  3. Creating License Metadata in FOLIO Licenses App

  4. Tools for Managing E-Resources

  5. Tools for Managing E-Resources

  6. FOLIO ERM Overview ERM Apps Supporting Apps • Licenses • Agreements • eUsage • eHoldings* *eHoldings is built for EBSCO KB institutions, Duke uses ExLibris 360/Serial Solutions • Settings • Organizations (Vendors) • Users

  7. Settings Organizations Users Manual data creation in FOLIO _______________________________________________________ Only users for ERM apps and users identified as “internal contacts” for a license are needed. Who will enter these users and using what source? Permissions structure? Manual data creation in FOLIO _____________________________________________________ License: Terms and picklist order Organizations: categories Users: permissions, patron groups, address types Manual data creation in FOLIO _______________________________________________________ Need to create an organization record for each vendor for which a license is created in FOLIO. Would data migration from Aleph be useful exercise? ERMConfiguration and Data Migration

  8. Licenses Agreements eUsage Manual data creation in FOLIO ______________________________________________________ Data about each license will be entered manually into FOLIO. This metadata doesn’t exist in a system, so data migration isn’t an option Import package title lists (optional) _______________________________________________________ Link between package and order not available until orders are in FOLIO. Is importing package information worthwhile and feasible? Will data import be ready? Manual data creation in FOLIO  ______________________________________________________ Minimal data required for each usage data provider. ERMConfiguration and Data Migration - continued

  9. Questions?

More Related