Dummy Records for On Order Bibs
We use dummy item records when some libraries on the server have a loan policy that does not allow for loans outside their library. The problem is that if the library with a more restrictive policy gets the first item on the bib, then that restrictive policy is set for everything on that bib. So we create a dummy item when we load the orders so we know that the first item will have the a loan rule allowing loans to other libraries. Then when the more restrictive item is added, only that item gets the restrictive policy.
These dummy items are created by the order loaders, including the quick click loader. This means that we will get a lot of these on popular bibs, but they are suppressed from public view, and staff can just ignore them.
We have a process to find these and delete them after three months. Libraries can delete them after they add items, but they don’t have to. They will get removed automatically.
Related Documentation
-
Acquisitions Process Outlines (Marmot Knowledge Base)
-
Eagle Valley Acquisitions Process (Marmot Knowledge Base)
-
Bud Werner Acquisitions Process (Marmot Knowledge Base)
-
OCLC Holdings Update Project (Marmot Knowledge Base)
-
Exporting MARC files (Marmot Knowledge Base)
-
(3) Load b & o records, match on 001 [acq3] (Marmot Knowledge Base)
-
(K) Load b & o, match on i - 020 & 001 [acq2] (Marmot Knowledge Base)
-
(X) Load file from Marquis macro 917 tag match [ing] (Marmot Knowledge Base)
-
(S) Load vendor file [ven] (Marmot Knowledge Base)
-
System Generated Review Files (Create Lists) (Marmot Knowledge Base)
-
(L) Load an OCLC MARC file [b] (Marmot Knowledge Base)
-
Dummy Records for On Order Bibs (Marmot Knowledge Base)
-
Marmot Cataloging Standards (Marmot Knowledge Base)
-
SkyRiver Install and Setup (Marmot Knowledge Base)
-
Z39.50 Cataloging (Marmot Knowledge Base)