Metadata Record Export (UXPROD-652)

[UXPROD-4146] Data export - Removing fields from SRS before export Created: 21/Mar/23  Updated: 18/Dec/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: Trillium (R1 2025)
Parent: Metadata Record Export

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: LC5, firebird-po-share, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-4585 Enhancements to Instance local fields... Draft
Potential Workaround: Manual edits after records are exported
Release: Ramsons (R2 2024)
Epic Link: Metadata Record Export
Analysis Estimate: Medium < 5 days
Front End Estimate: Large < 10 days
Front-End Confidence factor: 20%
Back End Estimate: XXL < 30 days
Back-End Confidence factor: 20%
Development Team: Firebird
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem:
The existing implementation allows users to select fields from the records to be exported but does not allow suppress fields that should not be included in the export.

In scope

  • Mapping profile provides option for suppressing fields:
    • from SRS record (if present)
    • from simplified MARC record (if SRS is not present)

Out of scope
tbd

Use case(s)
The library does not want the local fields to be included in the export

Questions

  1. Should we discuss also suppression of FOLIO record fields that user might need to suppress?
  2. Are other than local fields (9xx) also suppressed?


 Comments   
Comment by Magda Zacharska [ 23/May/23 ]

The prioritization might depend on the architectural decisions related to storing local fields.

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