Batch Importer (Bib/Acq) (UXPROD-47)

[UXPROD-2661] Load Delimited or MARC records to create/update various record types, but do not store MARC Created: 16/Sep/20  Updated: 28/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: data-import, epam-folijet, loc, needs-t-shirt-size-BE
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
is defined by UIDATIMP-127 Load MARC Bib Record to create/updat... Open
Potential Workaround: Use the Q3 2020 functionality of only updating specific fields in the SRS MARC, instead of updating all fields
Release: Not Scheduled
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Small < 3 days
Development Team: Folijet
Kiwi Planning Points (DO NOT CHANGE): 2
PO Rank: 75
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: MO State (MVP June 2020): R3
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R3

 Description   

Split from UXPROD-2338 Closed to decrease scope; partial workaround: use new option to only update specific MARC fields in SRS

Purpose: To import data for Inventory or Acquisitions via a MARC record, but then do not save the MARC record in SRS

Sample use cases:

  • MARC Bib or Holdings creates related inventory record, but library does not want SRS (so Inventory Source = FOLIO, not MARC)
  • Brief MARC Bib supplies order or invoice data, but should not overlay a richer MARC SRS record

As a staff person working with imported files
I want to be able to specify whether an incoming MARC record should be saved in SRS or not
So that I can discard MARC records that are used for transport purposes only

From 9/23/20 Folijet grooming mtg:

  • In SRS, when try to use update or modify action in job profile; imported records saved in SRS, but no link to instance or original record
    • Job 1: modify, then create instance – all is fine
    • Job 2: Match MARC-MARC (so there is already an SRS), then update MARC – incoming record just has a few fields harvested to update the existing MARC, but does not have any links to an Instance; does it make sense to save to SRS?
    • Should we make explicit that the incoming record is saved or not?
    • Incoming record should not be linked to the instance
    • That’s how it’s working now
    • Revisit when we implement “Do not save MARC”


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 16/Sep/20 ]

Hi Oleksii Kuzminov and Ivan Kryzhanovskyi I split this feature from UXPROD-2338 Closed to pull it out of Q3 and reduce scope a little. This feature needs T-shirt sizes for UI and BE, plus we need a MOD story to correspond to the UI story. Thank you!

Comment by Ann-Marie Breaux (Inactive) [ 04/Feb/21 ]

Hi Karen Newbery, Christie Thomas, Raegan Wiechert I see that your libraries have ranked this as R1 - could you provide an example or two of the most urgent use cases from your library? I'm working on planning for the next round of Data Import work, and trying to understand how to weigh this against other pressing work. Thank you!

Comment by Christie Thomas [ 04/Feb/21 ]

Ann-Marie Breaux The first two use cases that come to mind are to create brief record for circulating objects that are not a part of the collection. (Such as laptops, power cords, etc.) We would not want to store the MARC for those, but we would have to load the data via a MARC file. The workaround for this is to create the files manually.

The second use case is for batch edits. If I want to add a statistical code or change the instance status for a batch of instance records, I must target the instance records with a MARC import file. If there is already a MARC record associated with the instance, then I can export the MARC record and re-import and overlay the MARC record without making any changes and tack on the batch changes that I need to make for the instance record. If there is no MARC record associated with the instance (such as for orders, circulating objects, etc.) then I would need to create a MARC record for the instance just to be able to make those updates in batch.

Comment by Raegan Wiechert [ 04/Feb/21 ]

We have lowered our ranking to R3. We believe the R1 was probably left over from before this was split off of 2338.

Generated at Fri Feb 09 00:25:48 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.