EResource Management ERM Overview Duke University FOLIO Implementation
- Slides: 9
E-Resource Management (ERM) Overview Duke University FOLIO Implementation Planning Library Systems Platform Steering Group 1 | www. folio. org
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 2 | www. folio. org
Creating License Metadata in FOLIO Licenses App 3 | www. folio. org
Tools for Managing E-Resources E R M A c t i v i t i e s 1. Store license documents (over 1, 000) 2. Search for licenses and view terms 4 Current Tool Share. Point No tool available 3. Workflow management Trello 4. Manage orders and Invoices Aleph 5. E-resource holdings management Ex. Libris 360 Core 6. Discovery layer licensed content management Ex. Libris Summon | www. folio. org
Tools for Managing E-Resources ERM Activities Current Tool Summer 2020 Tool Sharepoint FOLIO Licenses No tool available FOLIO Licenses 3. Workflow management Trello 4. Orders and Invoices Aleph 5. E-resource holdings management Ex. Libris 360 Core 6. Discovery layer licensed content management Ex. Libris Summon 1. Store license documents 2. Search for licenses and view terms 5 | www. folio. org
FOLIO ERM Overview ERM Apps Supporting Apps Licenses Settings Agreements Organizations (Vendors) e. Usage Users e. Holdings* *e. Holdings is built for EBSCO KB institutions, Duke uses Ex. Libris 360/Serial Solutions 6 | www. folio. org
ERM Configuration and Data Migration Settings Organizations Users Manual data creation in FOLIO _______________________________________________________ Need to create an organization record for each vendor for which a license is created in FOLIO. Only users for ERM apps and users identified as “internal contacts” for a license are needed. ___________________________ 7 | www. folio. org • License: Terms and picklist order • Organizations: categories • Users: permissions, patron groups, address types • Would data migration from Aleph be useful exercise? • Who will enter these users and using what source? • Permissions structure?
ERM Configuration and Data Migration - continued Licenses Agreements Manual data creation in FOLIO 8 | www. folio. org Import package title lists (optional) e. Usage 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 Link between package and order not available until orders are in FOLIO. Minimal data required for each usage data provider. • Is importing package information worthwhile and feasible? • Will data import be ready?
Questions? 9 | www. folio. org
