1 / 15

Voyager developer meets developer meeting 1-2 February 2010

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

aine
Download Presentation

Voyager developer meets developer meeting 1-2 February 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Importing SFX data into Voyager Ray DelahuntyAssistant Library Systems ManagerUniversity of the Arts London Voyager developer meets developer meeting 1-2 February 2010

  2. The Environment • Formerly the London Institute • Six colleges each with a strong brand identity • A university since 2004 • Voyager 7.0.4 • Classic OPAC in use, Tomcat coming soon • Budgetary limitations

  3. What we have (1).

  4. What we have (2).

  5. OPAC features. Location limit groups issue- we must have holdings records, as “All Colleges” is only 70% of records. Note also e-book and e-journal limit groups available for limiting.

  6. The XML data export.

  7. Data conversion& cleanup. MarcEdit used, to convert the xml to MARC and to upgrade it as far as possible to MARC21. http://oregonstate.edu/~reeset/marcedit/html/index.php The conversion is simple MarcEdit work. Here is a sample record, fresh out from SFX’s XML:

  8. After conversion. =LDR 01074nas-a2200157z--4500 =008 081027uuuuuuuuuxx-uu-|------u|----|eng-d =245 \4$aThe publishers weekly$h[electronic resource]. =210 \\$aPUBLISHERS WEEKLY =260 \\$bReed Business Information =022 \\$a0000-0019 =090 \\$a954921332001 =856 \\$uhttp://e-library.arts.ac.uk:3210/sfxtst3?url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&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_threshold=1&rft.object_id=954921332001&svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc&svc.fulltext=yes&$yClick here to search this e-Journal. =866 \\$aAvailable from 1997. $s110975424179894$t110975424179893$xEBSCOhost Academic Search Elite:Full Text$z111030372947000 =866 \\$aAvailable from 1997. $s110975592608364$t110975592608362$xEBSCOhost Business Source Elite:Full Text$z110976729154818 =866 \\$aAvailable from 2001 volume: 248 issue: 10. $s110976638852341$t110976638852340$xFree E- Journals:Full Text$z1000000000485631 =650 \4$aArts and Humanities$xLiterature

  9. 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...).

  10. Import data.

  11. Mfhds- who wants to see them?

  12. That view again:

  13. For future overlays. • 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. • The new import uses an overlay based on the Voyager 035$z index. New records are ADDED, existing (or changed) records are overlaid. • DELETED records currently have to be manually removed.

  14. 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.

  15. Last comments... Cheap, cheerful, and 2-3 hours work per load. A detailed step-by-step document is available.

More Related