Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Details: We need your help to finalize manually linking bib field and authority record requirements. 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. A MARC bib field's $0 will serve as a match point.
Scenarios
Scenario | Outcome Option | Outcome selection | Comments |
---|
Create new MARC bib record via data import app | A. No change. Nothing happens as far as linking. B. Something else. |
|
|
Create new MARC bib record via single record import functionality | A. No change. Nothing happens as far as linking. B. Something else |
|
|
Derive a new MARC bib record via quickMARC AND bib record has linked authorities | A. Allow a user to decide to keep links or remove them ONCE user hits the Derive action. B. Something else |
|
|
A MARC bib field linked to authority records Then user overlays the MARC bib record via single record import |
|
|
|
Update bib record via data import with NO change to the linked bib field - User updates a linked bib record via data import.
- The import file contains a bib record with a
- No change to authority linked MARC 100 bib field
- Indicators
- Controlled values
- Uncontrolled values
- Assume that the matched $0 is included in the import file
| No action required |
|
|
Update bib record via data import with A Change to linked bib field value(s) NOT controlled by authority - User updates a linked bib record via data import.
- The import file contains a bib record with a
- A linked 700 field has a change to uncontrolled $e. For example update $e from author to $e author $e narrator
- No change to controlled values
- No change to indicators
- Assume multiple 700s exist in file
- Assume that the matched $0 is included in the import file
|
|
|
|
Update bib record via data import With a Change to a linked bib field value Controlled by authority - User updates a linked bib record via data import.
- The import file contains a bib record with a
- Linked MARC bib 700 field has a change to $a
- File import has MARC bib 700 field $a Angeloo, Maya BUT the MARC bib 700 is linked to authority record 100 $a Angelou, Maya
- Assume multiple 700s exist in file.
- Assume that the matched $0 is included in the import file
- Assume that $9 is not included in the import file
| NR (ex. 100): This field does not get updated BUT there is some indication as to why the field was not updated and it can potentially be via R: (ex 700 - some of the 700s change) - a.) DI job log report b.) Separate - in-app report The report should include - Instance/HRID with link to the record
- Linked MARC field number that was not updated
- Date/time stamp of the update
- Reason the Linked MARC field number was not update.
- Controlled field value does not match
- Missing $0
- Changed $0
- possibly missing $9?
- Data import job ID?
|
|
|
Update bib record via DI AND Linked bib field has no $0 in an import file to be updated. - User updates a linked bib record via data import.
- The import file contains a bib record with a
- Linked 100 field does not include $0. No other change made to 100
- Assume that $9 is not included in the import file
|
|
|
|
Update bib record via DI AND Linked bib field has a different $0 value in an import file to be updated. - User updates a linked bib record via data import.
- The import file contains a bib record with a
- Linked 100 field includes a $0 but the value stored (ex. no234556) is not the same as what is in the import (ex. no234349). No other change made to 100
- Assume that $9 is not included in the import file
|
|
|
|
Update bib record via DI AND Linked bib field has a different $0 and change to a controlled value in an import file to be updated. - User updates a linked bib record via data import.
- The import file contains a bib record with a
- Linked 100 field includes a $0 but the value stored (ex. no234556) is not the same as what is in the import (ex. no234349).
- And subfield $d has changed from 1900 - 1998 to 1900 - 2000
- Assume that $9 is not included in the import file
|
|
|
|
Update bib record via DI and the bib field number is repeatable one of the bib field rows has been updated. - User updates a linked bib record via data import.
- The import file contains a bib record with a
- There are several 700 fields that are linked and some of are unlinked. One of the linked 700
- Includes a $0 but the value stored (ex. no234556) is not the same as what is in the import (ex. no234349).
- Another linked 700
- Has subfield $d has changed from 1900 - 1998 to 1900 - 2000
- A non-linked 700 has a change
- Assume that $9 is not included in the import file
|
|
|
|
Update bib record via DI and the bib field number is repeatable one of the bib field rows has been updated. (Has no $0) - User updates a linked bib record via data import.
- The import file contains a bib record with a
- There are several 700 fields that are linked and some of are unlinked. One of the linked 700
- Has no $0
- Assume that $9 is not included in the import file
|
|
|
|
Edit a MARC bib record (linked to an authority record) via quickMARC | - Cannot edit linked MARC bib fields
|
|
|
Create new MARC authority record (in batch) | No change. Nothing happens as far as linking. |
|
|
Edit MARC authority record via quickMARC | - If linked to a bib record AND authority 1XX OR 010$a has been updated then update all linked bib records with changed value(s).
- Bib updates should happen in a separate process.
- See below on options on how to communicate status/updates to users.
- Consider that multiple updates can happen concurrently.
Question(s): Expected time frame for changes to flow to all linked bib records. |
| Talk with Ann-Marie and Magda regarding statuses.
PS: expected time depends on amount of records and SRS and Inventory load in moment of update (for example a huge data-import is in progress). KG: Which service/module will handle the bib updates? |
Edit MARC authority records (in batch - DI) | - If authority 1XX or 010$a has been updated then update all linked bib records with changed value(s).
- Bib updates should happen in a separate process not as a part of MARC authority updates via data import.
- Once data import job is complete then a process should begin to update bib records
- Options to communicate to cataloging staff that updates are complete
- Possibly use Bulk-edit? Or Bulk-edit + schedule option?
- OR Create a log page that provides a query to all bib records updated based on authority record updates via MARC authority? Or dashboard widget that list log/jobs and current status to complete updates?
- Consider that multiple updates can happen concurrently.
Question(s): Expected time frame for changes to flow to all linked bib records. |
| " " KG: Any thoughts on Options to communicate to cataloging staff that updates are complete? KG: Which service/module will handle the bib updates?
|
Delete MARC authority record via quickMARC | - Allow for deletion to proceed
- Ask user to confirm that they want to delete the authority record. Ensure they understand impact of unlinking these records by providing # of records to be unlinked.
- Linked bib fields are no longer linked. No change to any bib subfield values.... only change is these fields can be edited.
|
|
|