Importing SFX data into Voyager Ray Delahunty Assistant Library Systems Manager University of the Arts London Voyager developer meets developer meeting 1-2 February 2010
The Environment Formerly the London Institute Six colleges each with a strong brand identity A university since 2004 Voyager Classic OPAC in use, Tomcat coming soon Budgetary limitations
What we have (1).
What we have (2).
OPAC features.
The XML data export.
Data conversion & cleanup. MarcEdit used, to convert the xml to MARC and to upgrade it as far as possible to MARC21. The conversion is simple MarcEdit work. Here is a sample record, fresh out from SFX’s XML:
After conversion. =LDR nas -a z = uuuuuuuuuxx-uu-|------u|----|eng-d =245 \4$aThe publishers weekly$h[electronic resource]. =210 \\$aPUBLISHERS WEEKLY =260 \\$bReed Business Information =022 \\$a =090 \\$a =856 \\$uhttp://e-library.arts.ac.uk:3210/sfxtst3?url_ver=Z &ctx_ver=Z &ctx_enc=info:ofi/enc:UTF- 8&rfr_id=info:sid/sfxit.com:opac_856&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&sfx.ignore_date_thres hold=1&rft.object_id= &svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc&svc.fulltext=yes& $yClick here to search this e-Journal. =866 \\$aAvailable from $s $t $xEBSCOhost Academic Search Elite:Full Text$z =866 \\$aAvailable from $s $t $xEBSCOhost Business Source Elite:Full Text$z =866 \\$aAvailable from 2001 volume: 248 issue: 10. $s $t $xFree E- Journals:Full Text$z =650 \4$aArts and Humanities$xLiterature
Data cleanup. Remove tags such as 210 Remove subfields i, s, t & z from tag 866, or if preferred all 866 tags Add punctuation and correct indicators Add tags such as a 506 and a 538 with suitable text Add tag 852 $b [e-journal location code]- (to create a mfhd on import) Optionally: change the leader06/07 to ms, swap the 022a and the 776x where there is a 776x (022$y is not used...).
Import data.
Mfhds- who wants to see them?
That view again:
For future overlays. 1.As part of the MarcEdit work rename 090$a (SFX control number) to 35$z. At the desired intervals do a new export from SFX comparing the data with the most immediately previous export. 2.The new import uses an overlay based on the Voyager 035$z index. New records are ADDED, existing (or changed) records are overlaid. 3.DELETED records currently have to be manually removed.
Warning. Check /m1/voyager/xxxxdb/data directory. Large batch edits upset the keyword indexing. If the size of the dynamic.dc file compared to the xxxxdb.1.dc is 50% or greater, then it is time for a keyword rebuild.
Last comments... Cheap, cheerful, and 2-3 hours work per load. A detailed step-by-step document is available.