https://beta-documents.el-una.org/id/eprint/1528 2017-05-27T00:03:01Z info:eu-repo/semantics/descriptiveMetadata https://beta-documents.el-una.org/id/eprint/1528/ How did that number get there? That’s not an OCLC number… Curie, Carrie Kroon, Daniela The OCLC number is a standard number used by many automated services. What happens if a non-OCLC number somehow made it into the MARC record styled as an OCLC number? What can it mess up? This is an issue our Consortium faced, as we were preparing data for an upcoming migration and encouraging member libraries to complete the OCLC Reclamation/Data Sync process. Our Consortium developed a process using OCLC Collection Manager (Query Collections), MarcEdit, Excel, and Access to identify potentially affected records where the Aleph bibliographic record’s OCLC number and title and the OCLC record's OCLC number and title did not match. 2017-05-10 Conference or Workshop Item PeerReviewed application/pdf en https://beta-documents.el-una.org/id/eprint/1528/1/HowDidThatNumberGetThereThatsNotAnOclcNumber_051017_0230_Slides.pdf application/msword en https://beta-documents.el-una.org/id/eprint/1528/7/HowDidThatNumberGetThereThatsNotAnOclcNumber_051017_0230_ProcessDocumentation.docx Curie, Carrie and Kroon, Daniela (2017) How did that number get there? That’s not an OCLC number…. In: ELUNA 2017 Annual Meeting, May 10-12, 2017, Schaumburg, Illinois. info:eu-repo/semantics/objectFile info:eu-repo/semantics/objectFile info:eu-repo/semantics/humanStartPage