Download
data migration process n.
Skip this Video
Loading SlideShow in 5 Seconds..
Data Migration Process PowerPoint Presentation
Download Presentation
Data Migration Process

Data Migration Process

180 Views Download Presentation
Download Presentation

Data Migration Process

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Data Migration Process

  2. Two Major Types of data • MARC • Bibliographic, holdings, authority data • Non-MARC • items, loans, patrons, vendors, circulation, acquisition data

  3. MARC Data • Supplied in ISO2709 format • Processing: • Convert to ALEPH sequential format (with the help of ALEPH standard routines) • Character conversion (ex. ANSEL to UTF-8) • Data massaging if necessary (ex. add a field indicating which library owns the record) • Load

  4. ALEPH Sequential record • 000000001 LDR L 00533cas--22001577a-4500 • 000000001 001 L AAA-8375 • 000000001 008 L 950330s 000000001 035 L $$a510214168 • 000000001 092 L $$a378(941)$$b20705 • 000000001 1102 L $$aUNSW Alumni. • 000000001 24500 L $$aNewsletter /$$cUNSW Alumni. • 000000001 78000 L $$tAlumni Association newsletter$$w510210510 • 000000001 78504 L $$tUNSW News$$w510239942 • 000000001 94910 L $$aNewsletter (UNSW Alumni Association) • 000000001 995 L $$aM$$hP$$j378(941)$$n20705$$pNov 1987 - Jun 1992 • 000000001 FMT L SE

  5. Non-MARC Data1. Data format • 01 Z303. • 02 Z303-REC-KEY. K • 03 Z303-ID PICTURE X(12). • 02 Z303-ID-1 PICTURE X(20). S • 02 Z303-ID-2 PICTURE X(20). S • 02 Z303-PROXY-ID PICTURE X(12). • 02 Z303-PRIMARY-ID PICTURE X(12). • 02 Z303-NAME-KEY PICTURE X(50). S • 02 Z303-VERIFICATION-1 PICTURE X(15). • 02 Z303-VERIFICATION-2 PICTURE X(15). • 02 Z303-VERIFICATION-3 PICTURE X(15). • 02 Z303-OPEN-DATE PICTURE 9(8). • 02 Z303-UPDATE-DATE PICTURE 9(8). • 02 Z303-CON-LNG PICTURE X(3). • 02 Z303-ALPHA PICTURE X(1). • 02 Z303-NAME PICTURE X(200). • 02 Z303-TITLE PICTURE X(10). • 02 Z303-DELINQ-1 PICTURE 9(2). • 02 Z303-DELINQ-N-1 PICTURE X(200). • 02 Z303-DELINQ-2 PICTURE 9(2). • 02 Z303-DELINQ-N-2 PICTURE X(200). • 02 Z303-DELINQ-3 PICTURE 9(2). • 02 Z303-DELINQ-N-3 PICTURE X(200).

  6. Documentation on Data StructureData description • 02 Z303-REC-KEY. • Z303-ID M X(12) • DESC: User’s identification key - cannot be changed. • CONV: Must be unique. • Z303-ID-1 O X(20) • DESC: alternative user identification key • CONV: Must be unique. Usually used for user barcode. • Z303-ID-2 O X(20) • DESC: alternative user identification key. • CONV: Must be unique.

  7. Conversion Specifications • ALEPH Z303 fields Local system Comment • corresponding field • Z303-ID Create sequential numbers • Z303-PROXY-ID blank • Z303-PRIMARY-ID blank • z303_name_key 06 name This field is a normalized “lower case” variant the of “06 name”. • !Z303-ID-VERIFICATION-1 20 what kind of card, 19 barcode 1. ex. • 1900305918 • 20LPAS • should be converted as • LPAS-19003059182. if 19 barcode =’0’, create ‘dummy’ barcodes (for example, sequential numbers may be used). • it’s necessary to create report of the users with the dummy barcodes. • Z303-ID-VERIFICATION-2 01 identification • Z303-OPEN-DATE 17 registration date ALEPH date format is YYYYMMDD. • Z303-UPDATE-DATE 31 date of last update ALEPH date format is YYYYMMDD.

  8. Aleph display of SEQUENTIALfile • 01 z303 \ • 02 z303_rec_key \ • 03 id ....................100 • 02 z303_id_1 ...............903054595 • 02 z303_id_2 ............... • 02 z303_name_key ...........blok f f • 02 z303_verification_1 ..... • 02 z303_verification_2 ..... • 02 z303_verification_3 ..... • 02 z303_open_date ..........19881118 • 02 z303_update_date ........19971017 • 02 z303_con_lng ............DUT • 02 z303_alpha ..............L • 02 z303_name ...............BLOK, F.F. • 02 z303_title .............. • 02 z303_delinq_1 ...........00 • 02 z303_delinq_n_1 ......... • 02 z303_delinq_2 ...........00 • 02 z303_delinq_n_2 ......... • 02 z303_delinq_3 ...........00 • 02 z303_profile_id ......... • 02 z303_ill_library ........UBU50 • 02 z303_home_library ....... • 02 z303_field_2 ............ • 02 z303_field_3 ............AFRUU,m • 02 z303_ill_total_limit ....0000 • 02 z303_ill_active_limit ...0000 • 02 z303_dispatch_library ... • 02 z303_birth_date .........19130926

  9. Checking and testing • Check data validity • At this stage data problems are discovered (duplicate records, corrupted data) • The problems are reported to a customer for handling • Load data the ALEPH • Basic testing by Exlibris • Overall testing by ODIN • ODIN submits problems report • Ex Libris corrects problems and reruns conversion

  10. Conversion Adjustment & Loading • As early as possible,all the data is used for the tests, as samples might not reflect the complexity of the data. • The loading of the data and the calibration of the Oracle database are interlocked, hence modifications of the basic configuration are done accordingly. • The system is tested after each iteration of data upload. • Adjustments to the conversion programs are done correspondingly to ensure the validity and integrity of the system.

  11. Conversion before STP • We need to run the whole conversion process at least twice in order to make sure that everything works properly • Each run of conversion is followed by extensive testing (customer)

  12. Conversion Decisions to be Taken • What data to convert • Conversion schedule • Library/ies participating in the first round of conversion