Table of Contents | ||
---|---|---|
|
...
Batch heading correction operates by leveraging Alma's overnight linking and preferred term correction jobs to make changes to bib records. The procedure is straightforward, but care must be taken to ensure that it is executed correctly. A very big note: Alma login permissions are not granular. The new authorizations added to your login allow for other functionality, but we trust you will only perform actions for which you have received training.
Warning |
---|
A very big note: Alma login permissions are not granular. The new authorizations added to your login allow for other functionality, but we trust you will only perform these actions if you have been |
...
authorized to do so. Currently, |
...
only /wiki/spaces/ITSadmin/pages/41367219participants are |
...
eligible to use this function. |
...
Please see Amy Armitage and Mary Jane Cuneo for more information. |
Parameters of the Workaround
The workaround does not work on the following:
- Tag changes or on indicators. Norm rules are necessary for these functions; submit an Alma Support ticket for these jobs.
- Non-Latin scripts in AAP paired fields are not controlled at all because there is no official AAP for vernacular headings. A transliterated romanized 4XX in NACO name authorities is used to enhance search and discovery, and if a transliterated romanized field in a bibliographic record matches a 4XX in an authority record, it will flip through the normal means.
...
- Open the Metadata Editor and click on File
- Choose New and then Library of Congress name authority records
- A new authority record will open; note the 667 field: $$a THIS IS A TEMPORARY AUTHORITY RECORD FOR HEADING CORRECTION. THIS WILL BE DELETED.
- 4XX: enter the incorrect form of the heading, the one currently on the bibs in Alma. Use copy and paste, as described in 5a below.
- 1XX: enter the new form of the name that you are updating bib headings to.
Copy and paste the heading to ensure accuracy, particularly when changing headings that contain diacritics. Some tips:
- Do copy and paste from OCLC, Alma’s Community Zone, or LC
- Do not retain the double dagger subfield delimiter (ǂ). This must be changed to $$.
- Do not copy and paste headings from:
- the Alma Browse Bibliographic Headings list, because they won’t contain subfields
- the Internet, as we don't know their reliability for correct use of diacritics
- Do copy and paste from OCLC, Alma’s Community Zone, or LC
Do not add end punctuation. The bib headings will lack final punctuation but that is fine, as Alma is removing much of it anyway during controlpreferred term correction jobs.
- You may use zero spaces or one space between $$subfield and text content
- Click on Save and Release Record (or, click Save on the temporary authority and it will stay in the left pane as a reminder. It can be deleted when the records have been updated).
...
- If none of the records updated, remember, this indexing job can take several days.
- Otherwise, you will want to investigate why the record(s) didn't update with your batch job.
- First ensure that the job has actually run and isn't simply delayed; read more about Monitoring, Troubleshooting, and Checking Results of Jobs
- If the cause is input error, you can find the workaround authority record you created using the search type Authority in the persistent search bar to search, and run the job again.
- Some headings continue to display in the browse indexes even after they have been deleted or corrected in the bibliographic records; ExLibris says this will be resolved in October 2021.
eResource Portfolio
You may find that there are still records associated with the heading you changed. Investigation informs us that the record(s) is in the Community Zone, and it shows up in our list of records because we have a portfolio on this record. To determine whether a heading is from a CZ record, navigate to the bib record associated with the heading by following the three steps below to see the full record:
...