eprintid: 1039
rev_number: 10
eprint_status: archive
userid: 23
dir: disk0/00/00/10/39
datestamp: 2013-07-12 11:08:53
lastmod: 2016-05-27 21:06:45
status_changed: 2013-07-12 11:08:53
type: conference_item
metadata_visibility: show
item_issues_count: 0
creators_name: Deck, Larry
title: Error-mining In Your Aleph-Oracle Database
ispublished: pub
subjects: aleph
divisions: eluna_conf
abstract: Errors and inconsistencies  can creep into your Aleph data through the initial conversion process,  staff inattention,  and  other  routes.  Many  are innocuous,  but some can cause problems with retrieval or even with functionality.  We will look at ways to use SQL to discover and list errors and  inconsistencies  in order  to correct  them before  they cause  trouble.  Simple  queries on both administrative   records  (items,  orders,  patrons)  and  bibliographic  records  can  identify  potential errors.  More  complex  queries  can find inconsistencies  and  create  input for Aleph batch services like manage-62  and the patron loader, to correct errors once they’re found. I present a rapid tour of such techniques with a focus on practical problem-solving.
date: 2013-05-03
date_type: published
full_text_status: restricted
pres_type: lecture
event_title: ELUNA 2013
event_location: Athens, GA
event_dates: April 30 - May 3, 2013
event_type: conference
refereed: FALSE
citation: Deck, Larry (2013) Error-mining In Your Aleph-Oracle Database. In: ELUNA 2013, April 30 - May 3, 2013, Athens, GA.
document_url: https://beta-documents.el-una.org/id/eprint/1039/1/ELUNA_2013_final_Lawrence_Deck.pdf