XREF Reports were returned from OCLC for the records matched during reclamation. \u00a0The CBB schools were able to receive a 4 column report that included bib number, original oclc number, matched oclc number and action performed (e.g. holdings set, record added, etc.) \u00a0For URSUS, which is a multi institution catalog, the only report available contained bib number and OCLC number matched. \u00a0 This report was compared to original records sent to determine which records required updates to the 001.<\/p>\n
Using the resulting spreadsheets, containing bib number and new OCLC number, were used to generate tiny marc records (using Marc Edit for some schools and Marc Perl for others, both worked fine) in the following format (Leader, 001 containing the new OCLC number, and the bib number for matching.)<\/p>\n
LDR 00073 2200049 4500
\n001 4546677
\n907 |a .b12232944<\/p>\n
These records were then loaded into the system using this III Load Table<\/a>*. \u00a0 Note that this results in the overwriting of the existing 001. \u00a0This was not considered a problem, though the Orbis-Cascade Alliance has information on how to avoid this on their Reclamation-Loading OCLC numbers or records page<\/a>.<\/p>\n *Reloading the records was not without problems. This table is the one eventually used by most schools and worked reasonably well, though\u00a0occasionally\u00a0a record leader would be corrupted. \u00a0 These leaders where identified in Create Lists by searching Marc Leader 21, Impl Len (c5) != 0. \u00a0III was contacted and they “deleted” the leaders on these records, which forced the system to regenerate a corrected leader. \u00a0 \u00a0The problem was sent to programming at III.<\/p>\n \u00a0<\/span><\/p>\n XREF Reports were returned from OCLC for the records matched during reclamation. \u00a0The CBB schools were able to receive a 4 column report that included bib…<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":202,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"footnotes":""},"class_list":["post-894","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/pages\/894","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/comments?post=894"}],"version-history":[{"count":18,"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/pages\/894\/revisions"}],"predecessor-version":[{"id":2834,"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/pages\/894\/revisions\/2834"}],"up":[{"embeddable":true,"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/pages\/202"}],"wp:attachment":[{"href":"https:\/\/www.maineinfonet.org\/mscs\/wp-json\/wp\/v2\/media?parent=894"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}MSCS<\/a> >> People<\/a> >> Technical Services Subcommittee<\/a><\/h6>\n","protected":false},"excerpt":{"rendered":"