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

[UXPROD-2802] NFR: Handle implicit/explicit actions in job profiles Created: 05/Nov/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: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: NFR, cataloging, data-import, epam-folijet, needs-t-shirt-size-BE, needs-t-shirt-size-FE
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 MODSOURCE-196 Add pre-processing handler for MARC u... Draft
is defined by MODSOURCE-197 DRAFT Ensure all the actions on entit... Draft
is defined by UIDATIMP-748 Add info callouts for implied actions... Draft
Relates
relates to UXPROD-2200 Create interactive log-summary of bat... Draft
relates to UXPROD-3502 Enhancements to the Data Import log (... Closed
relates to UXPROD-3695 Additional Changes to the Data Import... Draft
Release: Not Scheduled
Epic Link: Batch Importer (Bib/Acq)
Front End Estimator: Ivan Kryzhanovskyi
Back End Estimator: Ann-Marie Breaux (Inactive)
Development Team: Folijet
PO Rank: 105
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: Grand Valley (Full Sum 2021): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R2

 Description   

Right now, any imported MARC Bib will update the existing MARC record stored in SRS. If the import is only meant to update an item record, the user does not expect the SRS ARC (and the corresponding instance) to be updated by that imported MARC Bib. The only thing that would cause part of the SRS MARC to be updated is if the user includes a MARC Update action that only acts on specific fields. The SRS MARC update is implicit right now.

On the other hand, to impose the MARC record field protections, a user must include an explicit Update MARC action in the job profile, even if they are not overriding any of the field protections.

These are not ideal or expected behaviors. We need to talk through the user expectations and figure out how to make the job profiles behave as expected. In some cases, it may just be a UI change to make the implicit actions more explicit. In other cases, it may be a behavior change for Data Import

Also consider reviewing and refining Field protections, Override of field protections, and Updating individual fields as part of this feature



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 18/May/21 ]

Marked as Juniper at-risk due to no stories yet, and backend work for stability/reliability taking more time than expected. See if we can define this with better documentation on which profiles to use, and with possibly only UI changes

Comment by Ann-Marie Breaux (Inactive) [ 03/Jun/21 ]

Moved to R2/Kiwi

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