Migration of Physical to Electronic (P2E) Resources in Alma

Slides:



Advertisements
Similar presentations
SHARED COLLECTIONS, SHARED RECORDS? RESOURCE SHARING AT THE META-LEVEL Charley Pennell, NCSU - Natalie Sommerville, Duke TRLN Annual Meeting, 13 July 2012.
Advertisements

ALEPH version 19.01/20.01 Cataloging & Acquisitions/Serials Updates South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD
South Dakota Library Network ALEPH Acquisitions Overview South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD © South.
ALEPH 500 Union Catalogue Overview Judy Levi Senior Product Analyst Ex Libris Ltd. November 2004.
Acquisitions and Serials in 2005 and beyond Georgia Fujikawa Manager, Training Programs.
Tutorial Holdings Management Adding, Editing, and Assigning Full Text Finder Links support.ebsco.com.
ALEPH version Course Reading & Reserves Course Documents South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD
WILIUG 1. June 2, 2005 Using Review Files with Millennium Rapid & Global Update jenny schmidt SWITCH Library Consortium.
Electronic Serials Invoicing with Innovative Presenter: Kathy Peters Accounts Payable, Acquisitions University of Missouri.
Vended Authority Control --Procedures and issues.
Alma 1 year after STP: implementing batch services IGeLU Budapest Sep 2, 2015 Bart Peeters Head Operations LIBIS.
©2004 Deloitte Drop Shipment and Back to Back Order Processes in Oracle 11i July 19, 2004.
WPM What’s behind the icon? Work Programme Management.
South Dakota Library Network Remote ILL Workflow Creating Borrowing Requests South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD
South Dakota Library Network ALEPH Serials Overview South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD © South Dakota.
ALEPH version 19.01/20.01 Interlibrary Loan Updates South Dakota Library Network 1200 University, Unit 9672 Spearfish, SD © South Dakota.
YBP and Innovative: Making the connection Diane Carroll, Audrey Wilson and Jenny Yoshikawa WSU Libraries October 15, 2008.
MARCIt records for e-journals project to implement MARCIt service McGill University Library Feb
Data Migration Preparation
1 Resource Management: Resource Management Fundamentals.
How to transfer 85x prediction patterns from ADM library to HOL library Presenter: Yoel Kortick.
1 Alma Migration Form How to fill in the Non-Ex Libris Migration Form.
1 Orientation and concepts: Alma concepts. 2 Copyright Statement All of the information and material inclusive of text, images, logos, product names is.
Items Version 18 Upgrade Training. Items: Version 18 Upgrade Training 2 All of the information in this document is the property of Ex Libris Ltd. It may.
1 E-Acquisitions Workflows and Management in Alma Network Zone.
1 Acquisition Models Asaf Kline Director, Alma Product Management  Ex Libris Ltd., Internal and Confidential.
Mastering Inspections in WebTMA Jenny Pino TMA Systems.
In the Zone! Working in the NZ Lori Robare, University of Oregon Alliance Summer Meeting July 9, 2014.
1 Voyager to Alma Data Migration Chen Marckfeld January 14, 2016.
Delivers local and global resources in a single search The first, easy step toward the first cooperative library service on the Web WorldCat Local “quick.
© 2015 Ex Libris | Confidential & Proprietary Yoel Kortick Senior Librarian Cataloging introductory flow.
1 Yoel Kortick Senior Librarian Adding a local Electronic Collection.
1 What Do You Find in Verde? Largest KnowledgeBase in the market Focal point for e-resource management in library Trials and evaluations Lifecycle workflows.
1 Yoel Kortick Senior Librarian Working with the Alma Community Zone and Electronic Resources.
1 Yoel Kortick | Senior Librarian Serials automation tasks for summary holdings.
Kate Cabe Western Washington University Jesse Thomas University of Idaho TROUBLESHOOTING SUMMIT REQUESTS IN ALMA.
© 2015 Ex Libris | Confidential & Proprietary Using the shelf-ready process Yoel Kortick | Senior Librarian.
Licenses & Prevailing Terms Updated: 18-Jun-2006.
Moshe Shechter | Alma Product Manager
Introduction to Import Profiles July 2016
British Library Document Supply Service (BLDSS) API
Some Alma Basics GUGM June 15, 2017.
New and emerging acquisitions workflows Purchase requests
Resource Management / Acquisitions
Joanna Bailey, Western Washington University
Update SFX from Verde - Availability
Patron Driven Acquisition (PDA) Demand Driven Acquisition (DDA)
Fundamentals Acquisitions 02 – Workflow Rules Administration
Publishing to OCLC Yoel Kortick Senior Librarian.
Cleaning up the catalog: getting your data in order
Connection changes in Scribe Starting with version 7.9.0
Standing Orders in Alma
Alma – OASIS Real-Time Acquisition Integration Overview
Resource Sharing Locate
ALEPH Version 22 Beginning Cataloging
Importing and exporting records in Alma
Alma E-Resources Management and Workflows Boot Camp
(Includes setup) FAQ ON DOCUMENTS (Includes setup)
E-Resource Management and Workflows in the Network Zone
New Alma Customer Onboarding Preparation and Best Practices
Journal separation anxiety
Electronic Resource Workflows
Introduction to Alma Network Zone Topology
CSU Millennium to Alma migration
E-Resources in Prospector
From Local Catalog to World Wide Web
Evaluations and Trials in Alma
Yoel Kortick. Senior Librarian
Prediction Patterns and Summary Holdings
Presentation transcript:

Migration of Physical to Electronic (P2E) Resources in Alma

Overview Legacy ILS’s had one structure for storing and handling resources – the physical resource Electronic resources were added as physical because older ILS’s weren’t intended to handle anything else. Each institution managed their electronic resources in whatever way they chose. In Alma, a physical resource is quite different from an electronic resource and the workflows and structures are not the same Alma determines how to migrate Electronic inventory based on how it was setup in the legacy ILS During migration, all inventory is assumed to be physical unless specified otherwise in P2E file

Alma Records Physical Records in Alma Electronic Records in Alma Should show local E-records only. P2E creates only local ones. [SM] New screenshot of local resources only Electronic Records in Alma

Electronic Resource In Alma This is how electronic resource packages look in Alma after the P2E process has been completed Indicates that the package is an active local record. When greyed out, it indicates an inactive local record. Indicates the e-resource is global and linked to the Community Zone. P2E records will not be in this category.

Physical Resource in Alma

Alma Orders Physical Electronic Electronic only Electronic and Physical Maybe better to take the screenshot from April release (il-urm08) and remove the bullet

Normal Conversion Process Convert physical inventory from legacy ILS to Alma with the normal conversion process

Institution Resources The institution is requested to provide a list of bibliographic identifiers that actually represent electronic resources with their corresponding resource type. Resource Types: Portfolio: single title, purchased online in full-text Electronic Collection Package: group of portfolio’s sold together DB: for searching article/title info Note: There will remain an attribute difference between the DB’s and the Packages even after they are both generically called electronic collections.

Electronic Locations The institution will typically provide indication of libraries or locations that represent electronic inventory in the migration form. The institution may have a single bibliographic record in multiple formats, so we must know to retrieve only the holding/item information for the electronic location and not the physical location. All ILS’s except Aleph (as two-level lib/loc is migrated automatically) ILSs with Item-level material types All ILS’s Maybe also a screenshot from Aleph form

Records with multiple URL’s/Notes Behavior When there is one URL found in the 856u holding or bib (or whatever field specified by the institution as electronic link – it is matched on a 1 to 1 basis to the electronic resource.) When there are multiple URL’s found connected to the record (856u or other), we create separate inventory for each URL (ex: multiple packages) If we find that the there are identical provider name information and public notes in the (ex: 856u$z [$z - public note], we will match them to their corresponding 856u’s in sequential order.)

Records with multiple URL’s/Notes Behavior - Example If the Institution provided this in the migration setup for a specific holding or bib: URL source: 856 |u Note source: 856 |z Vendor provider source: 856 |3 We expect 3 e-portfolios with these attributes:

Conversion Process The system processes Institution input by Determining if the bib record exists Determining resource level of the record – bib, item, or holding (it looks for the lowest level) Checking if there is an associated order record for the resource (assuming acquisitions are in the scope of migration for institution) BIB Holding Item Highest Middle Lowest

BIBS If a bibliographic record provided by the institution has no attached electronic holdings or items, we create a portfolio, package or DB and associate it with that Bib (that is, there is no e-holding/item to convert, but only new e-inventory to add/associate with that Bib) In this case, there may be physical holdings/items. However, they will remain untouched.

Associated order record For each record, Alma checks for an associated order record by using the Bib, Holding, or Item ID to find the location from the corresponding inventory list supplied Alma allows one order per inventory record. When there are more than one associated order for the same resource (e.g. ordered from one vendor, then cancelled and ordered from a different vendor), migration processing will use an open/recent order first . Other orders will relate to the e-order, but may remain categorized as physical. The Ex Libris roadmap has plans to handle non-primary orders as well in the future.

Associated Order Workflow (Inventory) During P2E conversion, the system uses the following workflow for associated orders. When the criteria is met, the system takes the action and stops. Active Order Use latest send date Single order with no electronic location found Select the single order even if the order is not in an electronic location Multiple orders not in an e-location Don't link any order System Action Order Status “any order with this location?” Maybe the inactive should be under the active tree logically? Inactive Order Use any order associated with this e-location with any status using latest sent date If no inactive order with e-location found, apply logic from above

ILS Electronic Records Duplicated from Link Resolver system Since Alma intends to store both ILS and link resolver records in one system, the default migration pattern is to identify and eliminate duplicate link resolver records stored in the ILS and presume that the link resolver records will serve as the master. Via migration, it is possible to recognize the link resolver records as specified in the migration form based on the text specified in 035|a Exception 1: Another record with linked ILS orders, in which case the link resolver record is transferred as a suppressed record to retain data integrity. Exception 2: The ILS record has no order, but is still migrated in case the Bib record also has physical inventory. “eliminate other records”? Skip Suppress Handle

Handling Duplication Alma Migration Process tries to: Ensure that the end-user discovery experience is not affected by any duplication. This is achieved by: Primo setup de-dupe to ensure search results are combined where possible Preferring link resolver versions of e-resources via “ViewIT” end-user service menu over ILS-versions Ensure that there is no data loss by making sure that the relevant order/back-office information managed in the ILS remains. This results in the SFX or other link resolver system version serving as the master for linking/delivery/discovery and the ILS version as the back-office tracking and management master. Alma offers ongoing optional and manual back-office cleanup. For back-office duplication elimination – the following manual steps can be optionally undertaken by the institution: Associate LR/CZ inventory with ILS-originated order * Un-associate ILS-originated e-record with ILS-originated order* Re-link the ILS-originated order to LR/CZ Bib instead of ILS-originated Bib (this is currently planned to be possible from Jun 2014 release) Delete ILS-originated Bib/inventory (via MD editor or building a set of records for deletion/withdrawal) Preferring SFX or other link resolver system versions via “ViewIT” end-user service menu * and license, (if relevant), via search and resource editor

Use Case 1 Legacy ILS and Link Resolver ALMA Bibliographic Record SFX package Open Order 1 Open Order 2 Bibliographic Record Order 2 (Not Migrated) Order 1 (Migrated) SFX Package P2E package Manual de-duplication options exist for this case

Use Case 1 Example Stub Bibliographic Record in Alma before P2E Process 2 open orders are associated with the stub bibliographic record This slide is before P2E…it is never seen by the Institution. I suggest we change this slide to text indicating that the orders would be physical if not included in P2E….

Use Case 1 – Orders associated with BIB The 2 open orders are associated with the bibliographic record Bib is also in the LR/Community Zone

Use Case 1 (Post P2E) Active Order Even though there were 2 open orders, only one is migrated based on system logic specified earlier The BIB linked to the CZ is also migrated, however, a future ALMA release will allow for manual de-duplication of ILS/LR records relinking of the migrated order to Link Resolver record. Active Order Use latest send date

Use Case 2 Bibliographic Record included in P2E Bib not included in LR/CZ Physical item in electronic location Physical item in physical location Electronic portfolio made from the electronic location item Bibliographic Record included in P2E Physical item in physical location remains

Use Case 2 (Example) cont… 2 physical copies, although one of them is identified as being in a physical location based on Institution input in the migration form (for all ILS’s except for Aleph)

Use Case 2 Example (post P2E) After the P2E process has been completed – the item which had been associated with an electronic location has been converted to electronic, while the physical resource has remained physical. Add 2-3 slides about ERM overlay methods

Use Case 3 (Aleph) Bibliographic Record Bibliographic Record Physical Item in a lib/location with e-material type – EBOOK Physical Item in a lib/location with non e-material type. Migration Form: Material type = EBOOK is electronic Electronic items created for material type: EBOOK Bibliographic Record Physical Holdings/Item remains for non-EBOOK material type

Use Case 3 In the P2E-Libs_Cols Tab in Migration Form, they have specified material type EBOOK as being electronic Institution has indicated the library MAIN in the migration form as being an electronic location

Use Case 3 Physical title in Alma Contains 1 holding 3 different items

Use Case 3 cont… Once you drill down to the item level, you can see that there are different material types, even though they are all linked to the same location = MAIN Library

Use Case 3 (post P2E) After P2E process, the item specified as material type = EBOOK has been converted to electronic, while the other 2 have remained physical.

Thank You!