Forcing a change into the Global Change Queue A strategy for handling heading changes when there is...

47
Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record

Transcript of Forcing a change into the Global Change Queue A strategy for handling heading changes when there is...

Page 1: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Forcing a change into the Global Change Queue

A strategy for handling heading changes when there is no matching authority record

Page 2: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Remember that the queue only changes headings for which there is an exactly matching authority record.

In cases where you have more bibliographicrecords with a particular heading than you want to change one at a time, you can forcethe heading change into the global change queue by locally creating a matching authority record.

Page 3: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Step by Step Outline

1. Call up bib. record that includes heading

you want to change

2. Begin to Save record. Stop at Authority

Validation screen

3. Highlight the heading you wish to create

4. Click the Create Auth button

5. Save the dummy authority record

6. Record the authority id number!

Page 4: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Step by Step continued7. Still on the dummy authority record, change the 1XX to the correct (new) form

of the heading8. Save the dummy authority record again. (This action puts the heading change into

the queue.)9. Select the change to be processed in the

queue10. After the change occurs, delete the

dummy authority record!

Page 5: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Example from Recent RDA Heading Changes

• Dept. changed to Department

“While abbreviating the word ‘Dept.’ was not AACR2 practice (but national practice under the LCRIs), the shift to RDA provides an opportunity to convert existing headings that contain the abbreviation ‘Dept.’ to represent the full form of the word in headings and appropriate references.”

(from: Summary of Programatic Changes to the LC/NACO Authority http://www.loc.gov/aba/rda/pdf/lcnaf_rdaphase.pdf)

Page 6: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.
Page 7: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Dept. of Agriculture - subordinatebodies with no exactly matching authority records

Page 8: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

1. Select a bibliographic record that uses the heading you wish to change

Page 9: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.
Page 10: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

2. Begin to save the record. Stop at the authority validation screen3. Highlight the heading you wish to create.4. Click the Create auth button

Page 11: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

5. Save the dummy authority record that you created.

Page 12: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

6. Write down the Auth number.

Page 13: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

7. Make the change to the heading

Page 14: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

8. Save the dummy record again.

Page 15: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Global Change Queue shows old heading only before running job 11.

Page 16: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

9. Select the change to be processed

Page 17: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Confirm that the bibliographic records have been processed by searching your catalog by the old and new headings. Did any not change?

Page 18: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Confirm that it is the dummy record (id# on your list? Question marks in 040?)

10. Delete the authority record

Page 19: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Cataloger’s Toolkit and

Correction Receiver

Programs you can use in conjunction with Voyager to facilitate global changes

Page 20: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

http://www.library.northwestern.edu/public

Page 21: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Program and documentation by Gary L. Strawn, Authorities librarian, etc., Northwestern University Library.

Page 22: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Help from Clayton State’s Adam Kubik - http://www.clayton.edu/library/documentsandinstructionsheets/installingctk

Page 23: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Important Points!• Powerful tools which can make large batch

changes. Understand what will happen. Read the documentation!

• Test on small changes first or in a test database.

• You have to do more than just install, you also have to work though a variety of special settings

• If you change versions of Voyager, you also have to change versions of Cataloger’s Toolkit and Correction Receiver.

Page 24: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

The toolkit contains lots of buttons which perform discrete functions. We use two buttons.

Page 25: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

The grey button is a dashboard, taking you to the full button array and the special settings tabs.

The big red plus button is the action button that we use for performing global changes. Looking at the authority record, it creates a small file that gets written to a folder. This file is used by Correction Receiver to find and modify a group of records.

Page 26: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Correction Receiver

• Works together with Cataloger’s Toolkit (Assign settings under Options)• Finds the ‘old’ heading in a bibliographic

record within the file and replaces it with the new heading defined by the authority record

Page 27: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

What do these two programs do to help with headings changes?

• Solve the big problems with the queue– Able to change both field tags and

indicators

– Able to make changes to base heading and base heading with additions or subdivisions

– Able to fix uniform titles

– Able to fix geographic subdivisions

Page 28: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Uniform Title Example

Here part of the uniform title is changing from arr. to arranged, and there are 15 bibliographic headings to be changed.

Page 29: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

A search of the current heading brings us to this browse list. Old and New headings show up here in this case. The important part is access to the authority record.

Page 30: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Once on the authority record, click on the red plus button. That activates the toolkit functionality

Page 31: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Cataloger’s Toolkit suggests corrections based on x-references in the authority record. In this case one heading is suggested for correction.

Page 32: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Correction Receiver changes from it’s normal “Active” state to “Working,” showing the heading and progress through the changes.

Page 33: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Searching again, you can see that the 15 headings have been corrected.

Page 34: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Correction Receiver creates a number of files as it works. One of those is a summary of activity. As you process each change, the program keeps a running tally of the total records changed. We record these in a special statistical category.

Page 35: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Example of changes to headings plus subdivisions

Page 36: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

If we search the Subject line, we find that there are two additional headings that would not be changed by the global change queue. They don’t exactly match the base heading which is the name alone. Headings with additions are not recognized for change.

Page 37: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Also, if we look at the second record, we can see that a uniform title is involved. And the queue will not change that either.

Page 38: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Retrieve the authority

record and click on the

red plus.

Page 39: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

In this case, Toolkit suggests three headings that could be changed. Sometimes these are very generic (no date at all, for instance) so examine carefully. You have to select each change. Toolkit only does one at a time.

Page 40: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Once again the Correction Receiver applies the changes.

Page 41: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

A search of the Name and then the Subject

file shows that all the needed changes were made in the catalog.

Page 42: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Send this to ‘special’ form feature

Page 43: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

If there was a suggestion on the first screen it will appear at the top. If not, the “Old heading” boxes will be blank. You can edit those.

Page 44: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Here is an example of a likely heading that might have existed in our catalog but not as a choice generated by the authority record. Click OK to process changes.

Page 45: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Geographic heading example

Page 46: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

Check out the Indirect subdivision form – Old and New. The New looks correct. But …

Page 47: Forcing a change into the Global Change Queue A strategy for handling heading changes when there is no matching authority record.

The entire form was filled out then this box was edited.