Edit Shared MARC authority record, update Shared & Local Instances

Description

Purpose: In a consortium environment, authority control may be managed centrally and shared to member libraries. These authority records need to be discoverable by member libraries and available for linking. Libraries may need to update the headings (such as to add a death date) and these updates should be reflected in both linked shared Instances and linked local Instances/MARC bib SRS. 

Requirements

  • Allow user to edit a Shared MARC authority record with central tenant affiliation and permissions in the central tenant

    • Hide "Edit" option if users do not have permissions in the central tenant to edit MARC authority records

  • Upon save, present confirmation modal with the number of linked bibliographic records - any shared and local bib record to the specific tenant

  • Upon save, update MARC authority record, MARC bib record SRS, and Instance in central tenant

  • Upon update of the above records in the central tenant, trigger update to linked Shared/Local SRS MARC bibs and Shared/Local Instances

  • {*}Change the record updated message for all environments (consortia and non-consortia) to: {{*}}This record has successfully saved and is in process. Changes may not appear immediately{*}.

Scenarios:

  1. Scenario - edit:

    • Given the tenant is in a consortium environment and the user is viewing a Shared MARC authority record AND the user is affiliated with the central tenant AND the user has the "MARC Authority: Edit MARC authority record" permission in the central tenant

    • When the user selects "Edit" from the MARC authority app Actions menu

    • Then the quickMARC UI should appear

  2. Scenario - update MARC authority record in central tenant:

    • Given the tenant is in a consortium environment and the user has edited a Shared MARC authority record

    • When the user saves the record

    • Then the record should update the Shared MARC authority record in the central tenant

  3. Scenario - update central tenant MARC bib SRS and local MARC bibs/Instances

    • Given the tenant is in a consortium environment and the user has edited a Shared MARC authority record and changed a heading and the authority record is linked to any bib record (shared or local to tenant)

    • When the authority record is saved and updated in the central tenant

    • Then the update should trigger updates of the linked MARC bib SRS in the central tenant and of the linked Local SRS MARC bib/Instance in the member tenant(s)

  4. Scenario - confirmation modal - linked

    • Given the tenant is in a consortium environment and the user has edited a Shared MARC authority record and changed a heading and the authority record is linked to a bib record (shared or local to tenant)

    • When the user selects "Save & keep editing" or "Save & close" 

    • Then the "Are you sure" modal should appear with the number of linked bibliographic records (both Shared bibliographic records and any linked local records)

  5. Scenario - confirmation message - not linked:

    • Given the user has Saved a Shared the MARC authority record that is NOT linked to a MARC bibliographic record

    • When the central tenant MARC authority record is updated

    • Then the MARC authority app should appear AND the updated authority record should be open with a confirmation message that says "This record has successfully saved and is in process. Changes may not appear immediately."

  6. Scenario - confirmation message - linked:

    • Given the user has Saved a Shared the MARC authority record that IS linked to a MARC bibliographic record

    • When the central tenant MARC authority record is updated

    • Then the MARC authority app should appear AND the updated authority record should be open with a confirmation message that says ""{*}This record has successfully saved and is in process. [number of Shared and Local linked records] linked bibliographic record(s) updates have begun."{*}

  7. Scenario - hide edit option with no permissions

    • Given the tenant is in a consortium environment and the user does not have permissions to edit MARC authority records in the central tenant

    • When the user is viewing a Shared MARC authority record

    • Then the user should NOT see the "Edit" option in the actions menu

Environment

None

Potential Workaround

None

Attachments

3
  • 15 Sep 2023, 03:20 PM
  • 12 Sep 2023, 02:42 PM
  • 12 Sep 2023, 02:41 PM

is required by

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Yauhen ViazauSeptember 15, 2023 at 3:21 PM

Re-tested on https://folio-dev-spitfire-2nd-consortium.ci.folio.org/ - Issue 1 fixed Check Mark

Shared Authority record (linked and not linked) can be edited in Member tenant. See example:

Issue 2 remains and expected to be fixed when https://folio-org.atlassian.net/browse/MODELINKS-116#icft=MODELINKS-116 and https://folio-org.atlassian.net/browse/MODELINKS-118#icft=MODELINKS-118 are done

Denys BohdanSeptember 13, 2023 at 8:37 AM

Hey

issue 1 has the same root cause as issue in https://folio-org.atlassian.net/browse/UIMARCAUTH-284#icft=UIMARCAUTH-284 and will be fixed when back-end on environments is rebuilt.

issue 2 looks like an issue on back-end side or maybe some back-end work hasn't been implemented yet. could you take a look please?

Yauhen ViazauSeptember 12, 2023 at 2:45 PM

Tested on https://folio-dev-spitfire-2nd-consortium.ci.folio.org/ - issues found Warning

1) No Edit button for shared Authority on Member tenant (user with view/edit authority permissions in Central/Member) (not reproducible under admin user) - see:

2) Local Bib not updated when Shared linked Authority updated (when update in Central or Member) - see:

- please review

Christine Schultz-RichertAugust 20, 2023 at 2:37 PM

Hey - Yes, we should hide the Edit action. I updated the description and added another scenario, thanks!

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 18, 2023 at 3:19 PM
Updated October 3, 2023 at 3:28 PM
Resolved September 15, 2023 at 5:26 PM
TestRail: Cases
TestRail: Runs

Flag notifications