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.
![[thumbnail of Presentation slides]](https://documents.el-una.org/style/images/fileicons/application_pdf.png) |
PDF (Presentation slides)
- Published Version
Restricted to Registered users only 451kB |
![[thumbnail of Supporting materials]](https://documents.el-una.org/style/images/fileicons/application_msword.png) |
Microsoft Word (Supporting materials)
- Published Version
Restricted to Registered users only 6MB |
Abstract
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.
| Item Type: | Conference or Workshop Item (Other) |
|---|---|
| Event Title: | ELUNA 2017 Annual Meeting |
| Subjects: | |
| Divisions: | ELUNA Conference Proceedings |
| ID Code: | 1528 |
| Deposited By: | Al Cornish |
| Deposited On: | 27 May 2017 00:03 |
| Last Modified: | 27 May 2017 00:03 |
Repository Staff Only: item control page