Introduction
Multiple records with status "assigned" for the same identity are considered duplicates in the ISNI database. Such records should be merged when encountered.
...
The merge program acts on the basis of field 77A in records. It is run on the database twice a day at 11:00 and 16:00 GMT.
Merging in the WinIBW client
Merging records when one already has 77A
A search for records for John Carpenter yields a set of 31 hits.
...
Click on the Back arrow or press Ctrl+B to go back to list.
Select other possible matches from list and copy them to new windows. We found 3 records that look like they represent the filmmaker.
...
Twice a day the system runs a process to merge records based on field 77A.
Merging records when none has 77A
- Retrieve the record that has a duplicate.
- Right click in the record.
- Select Copy to New Window.
- Retrieve the other record that is a duplicate. This can be done by clicking the blue back arrow on the toolbar (or Ctrl+B) to return to the search history or by doing a new search.
- When the other record is found, right click in the record.
- Select Tile Windows Vertically.
- Click the Update button under one of the records to enter edit mode. It doesn't matter which one.
- Add field 77A to the record
- Person: 77A $aISNI#PERSON$bM$9[PPN of other record]
- Organization: 77A $aISNI#ORG$bM$9[PPN of other record]
- Copy the PPN from field 000 of the other record.
- Click Enter to save the record.”
77A field:
006 field:
The 006 field is used to flag changes by the ISNI Quality Team
Notes
- It doesn't matter which record gets the 77A field. The system will merge the records according to criteria outlined in the WinIBW manual. The cataloger cannot determine which record is retained.
- For more details, see section 4.1 of the WinIBW manual.
- Don't change the status of any of the records before merging.
- Merges are processed twice a day by the system.
- It is possible to have more than one 77A in a record to merge multiple records.When a merge is initiated in the client, the system adds field 006 with the logon ID of the individual in subfield $bAdd linking fields, such as related person or organization, only after the merge has completed. Otherwise, the links (which rely on the PPN) may be broken
...