Details: We need your help to finalize manually linking bib field to authority record requirements. These scenarios focus on create/derive/edit bib record interactions. Please
- Review each Scenario and Outcome Option
- In Outcome selection, please prepend your initials to your outcome selection option
- In Comments column, please prepend your initials to your comment
NOTE: All linked bib fields will have a $0 populated and will be read-only on the UI. The $0 will populate a URI that includes the Authority record 010$a or 001 as a unique identifier. A MARC bib field's $0 will serve as a match point.
Scenarios
# | Scenario | Outcome Option | Outcome selection | Comments |
---|---|---|---|---|
1 | Create new MARC bib record via data import app | A. No change. Nothing happens as far as linking. B. I expect something else. | ||
2 | Create new MARC bib record via single record import functionality | A. No change. Nothing happens as far as linking. B. I expect something else. | ||
3 | Derive a new MARC bib record via quickMARC from a bib record with linked authorities | A. Allow a user to decide to keep links or remove them ONCE user hits the Derive a new MARC bib record action B. Always preserve linking C. Never preserve linking D. I expect something else. | ||
4 | A MARC bib field linked to authority records Then user overlays the MARC bib record via single record import | |||
5 | Update bib record via data import with NO change to the linked bib field
| A. No impact to linking B. I expect something else. | ||
6 | Update bib record via data import with A Change to linked bib field value(s) NOT controlled by authority
| A. No impact to linking B. I expect something else. | ||
7 | Update bib record via data import with a Change to a linked bib field value Controlled by authority
| Question 1: How common is this scenario? A. Very common B. Occasional C. Very rarely happens. Definitely edge case. Question 2: What is your preferred outcome for this scenario? A. Do not update the field. Flag the reason why as this record is controlled by an authority record. FOLIO provides a report when a user attempts to edit controlled values. (Applies to repeatable fields too) B. Proceed with update. FOLIO provides a report that informs user that update conflicts with linked authority record. If user edits bib record via quickMARC then system can auto-correct to accurate values when user hits Save. A message/indicator can display for use to unlink authority record or allow for quickMARC to auto-correct. (Applies to repeatable fields too) C. I expect something else | Question 1 Question 2 | |
8 | Update bib record via data import AND linked bib field has no $0 AND changes to uncontrolled values
| Question 1: How common is this scenario? A. Very common. We do not maintain $0. B. Occasional C. Very rarely happens. We maintain $0. Definitely edge case. Question 2: What is your preferred outcome for this scenario? A. Continue with update to uncontrolled value(s) and to $0. Bib field remains controlled (linked to an authority record). FOLIO provides a report when a linked bib field has a missing $0 value. And when user edits bib record via quickMARC then auto-populate $0 when user hits Save. (Applies to repeatable fields too) B. I expect something else | ||
9 | Update bib record via data import AND linked bib field has no $0 AND changes to controlled values
| |||
10 | Update bib record via data import AND Linked bib field has a different $0 value
| |||
11 | Update bib record via data import AND Linked bib field has a different $0 and change to a controlled value in an import file to be updated.
| Question 1: How common is this scenario? A. Very common. We do not maintain $0. B. Occasional C. Very rarely happens. We maintain $0. Definitely edge case. Question 2: What is your preferred outcome for this scenario? A. Do not update the field. Flag the reason why as this record is controlled by an authority record. FOLIO provides a report when a user attempts to edit controlled values. (Applies to repeatable fields too) B. Proceed with update. FOLIO provides a report that informs user that update conflicts with linked authority record. If user edits bib record via quickMARC then system can auto-correct to accurate values when user hits Save. A message/indicator can display for use to unlink authority record or allow for quickMARC to auto-correct. (Applies to repeatable fields too) C. I expect something else | Question 1 Question 2 | |
12 | Update bib record via data import and contains multiples of the same repeatable MARC field and one of them is linked AND has no $0
| Question 1: How common is this scenario? A. Very common. We do not maintain $0. B. Occasional C. Very rarely happens. We maintain $0. Definitely edge case. Question 2: What is your preferred outcome for this scenario? A. Continue with update. Bib field remains controlled (linked to an authority record). FOLIO provides a report when a linked bib field has a missing $0 value. And when user edits bib record via quickMARC then auto-populate $0 when user hits Save. B. I expect something else | Question 1 Question 2 |