MARCcat: MARC Bibliographic records (UXPROD-786)

[UXPROD-2749] Have MARCcat honor the Data Import tenant-level field protection settings Created: 13/Oct/20  Updated: 19/Jan/21  Resolved: 19/Jan/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: MARCcat: MARC Bibliographic records

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Tiziana Possemato
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Data Import tenant-level field protections.PNG    
Issue links:
Defines
defines UXPROD-786 MARCcat: MARC Bibliographic records Closed
is defined by UICAT-116 Adjust the MARCcat edit UI to indicat... Closed
Relates
relates to MODDICONV-137 Data Import setting for MARC field pr... Closed
relates to MODDICONV-138 Store MARC field protection settings Closed
Epic Link: MARCcat: MARC Bibliographic records
Development Team: @cult
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R1
Rank: GBV (MVP Sum 2020): R5
Rank: MO State (MVP June 2020): R4

 Description   

Current situation or problem: In Honeysuckle, Data Import has implemented tenant-level settings for protecting MARC fields. Users editing a record via MARCcat should be able to tell when they are editing a protected field.

In scope

  • MARCcat can access the Data Import field protection settings and indicate that a particular field is protected, The user would be allowed to edit the field.

Out of scope

  • Disallowing the edit of protected fields via MARCcat
  • A separate permission (for now) that would allow a user to edit protected fields or not
  • A pop-up modal for each field indicating the user is trying to edit a protected field, and do they want to continue? SMEs agreed this would be too intrusive and cumbersome.
  • Editing of 001 and 999 ff fields is still disallowed, and the fields are greyed out on the MARCcat edit screen

Use case(s)

  • In standard practice, any MARC field with $5 BIGU is a protected field, and cannot be edited. However, sometimes users will need to edit those fields. In those cases, users should be allowed to edit the field via MARCcat, but should be able to tell that it is a protected field.

Proposed solution/stories

  • Need design from Kimie for some sort of indication in the MARCcat edit view that this is a protected field; nopefully can copy the design being used in UIQM-53 Closed
  • MARCcat needs to be able to access the Data Import field protection settings and use the same logic to indicate which fields are protected when editing a record via MARCcat

Links to additional info: See attached screenshot of field protection settings



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 19/Jan/21 ]

As of Jan 2021, development of MARCcat has ceased. Will incorporate some features into quickMARC.

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