Requirements
User Story | Priority | Details | |
|---|---|---|---|
As a cataloger, allow me to automatically control all eligible unlinked/uncontrolled fields on TBD bib records in batch So that I do not have to automatically link one bib record at a time. | |||
As a cataloger allow me to run a job that automatically controls all eligible unlinked/uncontrolled bib fields on all bib records. | |||
As a cataloger allow me to run a job that automatically controls all eligible unlinked/uncontrolled bib fields based on a query | |||
As a cataloger do not allow the job to run on already linked/controlled bib fields | |||
As a FOLIO system administrator, I do not want data import to be the process for handling the batch authority linking as it may result in scalability/reliability issues as data import is used frequently and for critical workflows such as single record import, bulk-edit, and of course data import. | |||
As a cataloger, I want a report or stats on the success of automatic batch control. The success can be defined by the total number of bib fields + records linked to the authority heading. | |||
As a cataloger, I want a report or stats on the fields/records there were not linked. The number bib fields+records that were not linked. And or duplicate authority records? | |||
As a cataloger, I want the ability to export the results/stats in csv so I review and troubleshoot any issues. | |||
As a cataloger, I want the ability to view a list in FOLIO of the bib records that were included in the job and review the quality of the linking and/or why there was no link. | |||
As a cataloger, I want to specify what bib fields are run through the automated batch control process because I prefer not to have my 650s go through this process. | |||
As a cataloger, I want to decide how FOLIO matches authority headings to bib fields. I may elect to not match on $0 but instead match on a text string. Although $0 makes sense to be a value to link, we find adding it to our bib fields expensive and hard to manage/define with our third party provide of bib and/or authority records. | |||
As a cataloger, if I make batch authority control updates then the updates should be reflected on the MARC bib version history | |||
As a cataloger, once I have at least 50% of my bib records controlled by authority headings, ensure that any MARC bib updates via Data import does not result in significant performance decrease and scalability deterioration. | |||
As a cataloger, once I have at least 50% of my bib records controlled by authority headings, ensure that any MARC bib updates via Bulk edit does not result in significant performance decrease and scalability deterioration. | |||
As a cataloger, once I have at least 50% of my bib records controlled by authority headings, ensure that any MARC authority updates via Data import does not result in significant performance decrease and scalability deterioration. | |||
As a cataloger, once I have at least 50% of my bib records controlled by authority headings, ensure that any MARC authority updates via Bulk-edit does not result in significant performance decrease and scalability deterioration. | |||
As a cataloger, I should be able to run a query via the lists app that tells me if the bib field is controlled by an authority heading with details about the heading and last time the link was updated so I can review for troubleshooting purposes. | |||
As a cataloger, I do not need authority control to happen quickly if I am requesting TBD number of fields to controlled across TBD number of bib records. I like for the process to be run in the background and it does not impact daily and nightly workflows. | |||
As a cataloger, the batch authority control process can run for 8 hours if --- 16 hours if --- 24 hours if --- 48 hours if --- 72 hours if --- 144 hours if --- | |||
As a cataloger, I like to be able to schedule the running of this process | |||
As a cataloger, I am fine if FOLIO runs this process everyday starting at TBD time | |||
As a cataloger, I want the ability to cancel the process | |||
As a cataloger, I want the ability to get stats on the number of
| |||
As a cataloger, I want the ability to define a rule if using text string to match; to pick the right authority heading IF a duplicate authority heading is found. | |||
Process supports chunking? queue? |