eprintid: 1528
rev_number: 9
eprint_status: archive
userid: 35
dir: disk0/00/00/15/28
datestamp: 2017-05-27 00:03:01
lastmod: 2017-05-27 00:03:01
status_changed: 2017-05-27 00:03:01
type: conference_item
metadata_visibility: show
creators_name: Curie, Carrie
creators_name: Kroon, Daniela
title: How did that number get there? That’s not an OCLC number…
ispublished: pub
subjects: Alma
divisions: eluna_conf
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.
date: 2017-05-10
full_text_status: restricted
pres_type: other
event_title: ELUNA 2017 Annual Meeting
event_location: Schaumburg, Illinois
event_dates: May 10-12, 2017
event_type: conference
refereed: TRUE
citation: 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.
document_url: https://beta-documents.el-una.org/id/eprint/1528/1/HowDidThatNumberGetThereThatsNotAnOclcNumber_051017_0230_Slides.pdf
document_url: https://beta-documents.el-una.org/id/eprint/1528/7/HowDidThatNumberGetThereThatsNotAnOclcNumber_051017_0230_ProcessDocumentation.docx