SMRE Simple Marc Record Editor, aka quickMARC (UXPROD-2263)

[UXPROD-2748] quickMARC Bib | Indicate when a MARC field is data import protected field Created: 13/Oct/20  Updated: 28/Jul/22  Resolved: 28/Jul/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Morning Glory (R2 2022)
Parent: SMRE Simple Marc Record Editor, aka quickMARC

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Khalilah Gambrell
Resolution: Done Votes: 0
Labels: quickmarc
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-2263 SMRE Simple Marc Record Editor, aka q... Closed
is defined by UIQM-53 Adjust the quickMARC edit UI to indic... Closed
Relates
relates to MODDICONV-137 Data Import setting for MARC field pr... Closed
relates to MODDICONV-138 Store MARC field protection settings Closed
relates to MODQM-58 Adjust the quickMarcJson payload to p... Closed
Epic Link: SMRE Simple Marc Record Editor, aka quickMARC
Development Team: Spitfire
PO Rank: 85
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R5
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R1

 Description   

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

In scope

  • quickMARC 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 quickMARC
  • 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 quickMARC 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 quickMARC, 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 quickMARC edit view that this is a protected field
  • quickMARC 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 quickMARC

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

Questions



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 19/Nov/20 ]

Hi Stephanie Buck - just checking - did this make the cut for R1 2021, or no?

Comment by Stephanie Buck [ 19/Nov/20 ]

Hi Ann-Marie Breaux. Capacity planning asked that Firebird limit our scope only to our main feature, remote storage, and UI only features when the FE devs are blocked.

Comment by Ann-Marie Breaux (Inactive) [ 19/Nov/20 ]

Stephanie Buck No worries! Good to know though, so thanks for the explanation

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