Adjust links suggestion for consortium
Description
Environment
Potential Workaround
CSP Request Details
CSP Rejection Details
Attachments
defines
is blocked by
is required by
relates to
Checklist
hideTestRail: Results
Activity

Valery_PilkoOctober 10, 2023 at 1:06 PM
Re-tested on https://folio-dev-spitfire-2nd-consortium.ci.folio.org/
Now we can use only one request to link Local/Shared MARC bibs with Local/Shared MARC authority records.
1) For linking Local MARC bib use "<Member>" x-okapi-tenant header
2) For linking Shared MARC bib use "<Central>" x-okapi-tenant header
See attached screencasts:
Issue 1 - looks like it fixed, but sometimes request don't return MARC authority records
See attached screencast:
Issue 1 probably will be fixed in the scope of and

Valery_PilkoOctober 10, 2023 at 8:16 AM
According to discussion on sync-up Issue 2 - will be fixed in the scope of **

Valery_PilkoOctober 9, 2023 at 4:06 PM
According to the notes from , the following scenario was re-tested, and it still reproduces:
Issue 2 - "Local linked MARC Bib is not updated after update of Shared MARC authority (which is linked to Shared and Local Instances) from Central tenant"
Expected result: Linked field in Local "Instance" record is updated according to the updates in Shared linked "MARC authority" record.
Actual result: Linked field in Local "Instance" record is not updated according to updates in Shared linked "MARC authority" record.
See attached screencast:
Note: The same issue reproduces when linked Shared MARC authority was edited on UI in Central/Member tenant.
Steps to reproduce could be found in this test case: https://foliotest.testrail.io/index.php?/cases/view/407641

Valery_PilkoOctober 9, 2023 at 1:29 PM
Hi
During testing on https://folio-dev-spitfire-2nd-consortium.ci.folio.org/ following Issue 01 is found: ""500" and "403" errors are returned to POST "/records-editor/links/suggestion" requests for member and central tenants"
Note: Issue reproduces not each try. See details on screencast.
Preconditions:
1) Authorized user has assigned following permissions in Central tenant:
Inventory: All permissions
MARC Authority: View MARC authority record
User has assigned following permissions in Member 1 tenant:
Inventory: All permissions
MARC Authority: View MARC authority record
quickMARC: View, edit MARC bibliographic record
quickMARC: Can Link/unlink authority records to bib records
2) Member 1 tenant has local "MARC bibliographic" record (
) with "$0" value corresponding to imported shared "MARC Authority"'s (
) naturalId in a linkable field.
Steps:
1. Log in into Member 1 tenant of https://folio-dev-spitfire-2nd-consortium.ci.folio.org/ as user from preconditions.
2. User is on the detail view pane of local "Instance" record opened in the "Inventory" app, ex. of search query: "C405922 Instance Local M1"
3. Click on the "Actions" at the third pane >> Select "Edit MARC bibliographic record" option.
4. Click on the "Link headings" button in the upper right corner of the pane
Expected result: Field eligible for linking with subfield "$0" was linked to "MARC authority" record from the Preconditions, e.g. "100" field is linked.
Actual result:
On UI: Error toast notification is displayed
DevTools:
1) POST "/records-editor/links/suggestion" for College tenant is returned with "500" error and following message:
2) POST "/records-editor/links/suggestion" for consortium tenant is returned with "403" error and following message: "Access for user 'northc1' (d4b48727-1e98-4c55-9c28-180e8ee801a2) requires permission: marc-records-editor.links.suggestion.post"
See attached screencast:

Valery_PilkoSeptember 15, 2023 at 1:48 PMEdited
QA note:
1) The whole story UIPFAUTH-76 should be retested in scope of current issue.
2) Scenario from MODDATAIMP-901
should be re-tested in scope of current issue:
Update of Shared MARC authority that is linked to instances from central tenant - the user should be able to update shared authorities from the central tenant that are linked to local records
Details
Assignee
Mukhiddin YusupovMukhiddin YusupovReporter
Pavlo SmahinPavlo SmahinLabels
Priority
P2Story Points
5Sprint
NoneDevelopment Team
SpitfireFix versions
Release
Poppy (R2 2023)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee

Overview:
The purpose of this story is to enhance the links suggestion process in a consortium environment. Currently, authorities are propagated to member tenants from the central tenant. During the suggestion process, when searching for authorities to provide suggestions, the search results may include both shadow copies and local records. Shadow copies are distinguished by having the prefix "CONSORTIUM-" in the source field. To ensure the accuracy of suggestions and maintain data integrity, requests to the source-record-storage should be made in the scope of the central tenant when dealing with shadow copies.
Requirements/Scope:
Modify the links suggestion process to differentiate between shadow copies (CONSORTIUM-) and local records in the search results.
Enhance the search mechanism to route requests to source-record-storage in the context of the central tenant when dealing with shadow copies.
Ensure that shadow copies are correctly identified and utilized in the links suggestion process.
Approach:
Review the existing links suggestion process to understand how authorities are currently propagated and utilized in the consortium.
Implement logic to distinguish between shadow copies and local records based on the source field prefix (CONSORTIUM-).
Enhance the search component to route requests for shadow copies to source-record-storage in the context of the central tenant.
Update the links suggestion process to consider both shadow copies and local records as potential suggestions.
Conduct thorough testing to validate that the modifications accurately differentiate between shadow copies and local records and that suggestions are provided correctly.
Acceptance Criteria:
Meets requirements
Unit tests are written