How does column 8 in tab_loader-def work?

• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
We have a question about column 8 in tab_loader_def. This is a new feature for managing matches on more than on Bib record. We do use all those 3 tables (tab_loader, tab_loader_def, and tab_matching) to configure for the oclc_server and bib loaders. We have always left the tab_loader col. 8 at zero ‘0’ because we didn’t understand how to use it.

Could you explain more indepth what col. 8 can do if we place a value in it?

Resolution:
Let's assume that you currently have two records in your database which match an incoming record from OCLC, based on your tab_match configuration. If you have set column 8 to "1", a new, 3rd record will be created. You will see something like this in the loader log and the OCLC interface:

Multiple matching docs found in USM01 (000050123 000050125). Creating new record.
Create new bib - USM01.000050126

If you have column 8 set to "0", you will get a message about the two matching records, but the 3rd record won't be created. You will see something like this in the loader log and the OCLC interface:

Load record failed - Multiple matching docs found in USM01 (000050123 000050125)