Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 107, eHoldings Sprint 108
-
8
-
Spitfire
Description
Context: Primarily librarians will import MARC authority records thus our first phase of Authority work will be import functionality
Assumptions
- For initial release, we are not creating/updating an equivalent Inventory record type
- Import will generate an authority record that looks exactly like the quickMARC bibliographic record
Objectives
- Review all modules/services involved with importing authority records
- Define technical design for importing authority records
- Answer the following question (if applicable); is it best to build a new module or extend mod-quickmarc to support Authority records?
- Identify dependencies
- Identify questions/unknowns
Resources:
- Review linked JIRAs
- Please contact Ann-Marie and Oleksii K (Folijet). Taras is available until 2/15.
- Batch Loader 1-MARC intro: https://docs.google.com/presentation/d/1yI5RR_1TjSFy7Ka44aSHWUSIJJyjP0yjN8MKGV19tlI/edit?usp=sharing
- Data Import – Tips & Tricks: https://wiki.folio.org/display/FOLIOtips/Data+Import
- Loading MARC files for quickMARC: https://drive.google.com/file/d/11UH6kRm_NrVZAO-nSq2kQFj9C1CkoCNP/view?usp=sharing
PO questions
- Avg number of Authority records uploaded at one time
- Frequency of uploads
- What is an extremely high but realistic number of records uploaded at one time
Import requirements
- Supported file extensions/formats: All files with Data type = MARC. Go to Settings > Data Import > File extensions
- Honor Block import column actions selections
- Honor MARC Field protection entries. Go to Settings > Data import > MARC field protection
- Library staff member should be able to set up a mapping profile to populate authority records
- Library staff member should be able to setup a match profile that supports matching MARC authority records
- Library staff member should be able to setup job profiles to execute import requests
- Import actions to support: Create record and Update entire record
- Import actions not to support initially. Modify record and Delete record
- When a user imports then
- generate a HRID
- generate UUID
- store imported authority records in SRS
Deliverables
- Technical design/approach
- Review design/approach with this team, Oleksii K, Ann-Marie, and Taras (if available)
Stretch deliverable
- Create backend user stories
TestRail: Results
Attachments
Issue Links
- is required by
-
MODQM-75 Investigate | MARC Authority record | Implement sequence number generation mechanism for HRIDs
-
- Closed
-
- relates to
-
MODINVSTOR-170 Implement sequence number generation mechanism for HRIDs
-
- Closed
-
-
MODDATAIMP-368 Investigation: Update MARC Authority records during data import
-
- Closed
-
-
MODDICONV-174 Create default profile for importing new MARC Authority records
-
- Closed
-
-
MODSOURMAN-205 HRID handling in SRS for MARC authority records: Create
-
- Closed
-
-
MODSOURMAN-206 HRID handling in SRS for MARC bib records: Create
-
- Closed
-
-
MODSOURMAN-250 HRID handling in SRS for MARC authority records: Modify/Update
-
- Closed
-
-
MODSOURMAN-411 Dynamicaly define the payload of Data Import events depending on MARC Record type (Bib, Authority, Holding)
-
- Closed
-
-
MODSOURMAN-412 Restructure MARC related events to have common and type specific ones
-
- Closed
-
-
MODSOURMAN-462 HRID handling in MARC Auth App for MARC Authority records
-
- Closed
-
-
UXPROD-2322 Import MARC authority records - Create action (backend support only)
-
- Closed
-
- mentioned in
-
Page Loading...