Primo and Omeka : turning local databases into harvestable repositories

1. Primo and Omeka : turning local databases into harvestable repositories Alexander J. Jerabek Bibliothécaire Technologies de l’information Service des bibliothèques jerabek.alexander_j@uqam.ca 2014-05-01

2. Goal Makespecialperipheric collections more accessible and more visible by integratingtheminto Primo

3. The Pouchet collection • Donation of 36 000 print documents and 20 050 vinyl records to the Music library • Primarilypedagogic or popular documents • Cataloguedapartfrom main catalogue, searchable in a local database (Access, .asp) • Ongoingwork to catalogue all items

4. The Pouchet collection

5. The Pouchet collection

6. The Pouchet collection

7. The Pouchet collection

8. Problem • How to getexisting records into Primo? • How to get new or modified records into Primo?

9. Local database ‘Palmaro’

10. Local database ‘Palmaro’

11. Omeka • “Omekais a free, flexible, and open source web-publishing platform for the display of library, museum, archives, and scholarly collections and exhibitions. Its “five-minute setup” makes launching an online exhibition as easy as launching a blog.” • http://omeka.org/about • Omekais a project of the Roy Rosenzweig Center for History and New Media, George Mason University.

12. Advantages of Omeka • Easy set up and maintainance • French interface • Doesexactlywhatweneed : create and update records and allowharvest via by Primo • Useful plugins • Create multiple users • Long range plans for possible digitization

13. Disadvantages of Omeka • Not possible to make global changes to records • Dublin Core not always best fit for data • Not alwayseasy to define default values • Not possible to export data

14. Omeka plugins • CSV Import • OAI-PMH Repository • Simple Vocab • Dublin CoreExtended • HideElements • Collection Tree

15. Prepare the staff • Createusers • Write up procedures for creating records • Re-iterativeprocess • Test runs in staging to findsnags

16. Omekaadmin

17. Omekaadmin

18. Omekaadmin

19. A few bugs • Dropping initial diacritic • Cannotsearch on threeletterwords

20. Import data into Excel • Tidy data as much possible • Filters in Excel • Search and replace in Textpad • Corrections usingOpenRefine (http://openrefine.org/) • Addcolumns, constants (e.g. Format) • Crosswalk, column headers to DC elements • Save as csv UTF-8

21. Excel to CSV

22. Dataset import intoOmeka

23. Dataset import intoOmeka Omeka CVS import defaults ChooseColumnDelimiteris : ; Choose Tag Delimiteris : | Choose File Delimiter : , ChooseElementDelimiter : /

24. Data set import intoOmeka

25. Data set import intoOmeka

26. Data set import intoOmeka

27. Setting up Primo • Set up a datasource • Set up a scope • Set up a pipe • Create new local fields • Create new set of normalizationrules • Tweak Primo interface

28. 1. Set up a data source

29. 2. Set up a scope

30. 3. Set up a pipe

31. 4. Create new local fields • lds08 : Parolier (lyricist) • lds09 : Compositeur (composer) • lds10 : Interprète (performer) • (see notes below for steps)

32. 4. Rules for new local fields • Ex. new field for lyricistbased on ‘ (par.) ’

33. 5. Create new normalizationrules • Strip out parenthetical notes for display

34. 5. Create new normalizationrules • Strip out parenthetical notes for display

35. 5.(record modified in Omeka)

36. 5. Create new normalizationrules • Addcomplementary information • not: • Dublin Core:Publisher Dublin Core:Description • Bibliothèque de Musique Disponible au comptoir de prêt • Insteadadded : • <display> • <ispartof>Musique en feuille no.10599, voir au comptoir de prêt de la Bibliothèque de Musique</ispartof>

37. 5. Create new normalizationrules • Added or modified a few elements to conformwithour Aleph records • <display/type> = score • <search/general> = Musique en feuille • <search/searchscope> = ubibmusique • <facets/toplevel> = uqam_inst • <facets/library> = M

38. 6. Tweak Primo interface • No use for location/request tab or for more (sfx) tab.Hidethemwith CSS using the datasourceprefix : • ul.EXLResultTabsli.EXLRequestTab a[href*="BIBMUSIQUE"], • ul.EXLResultTabsli.EXLMoreTab a[href*="BIBMUSIQUE"] {display:none;} • Html: • <ul class="EXLResultTabs…"> • <li class="EXLRequestTab…"> • <a href="display.do?tabs=requestTab….doc=BIBMUSIQUE10478..."> • <a href="display.do?tabs=moreTab...&doc=BIBMUSIQUE10478...">

39. A few problems, questions remain • Aznavour and Coulonges • The problem of Aznavour as (comp.), (interp.), (par.) – leave in parenthicalelements or removethem • Vs

40. Aznavour and Coulonges • Aznavour • (include all facets)

41. Aznavour and Coulonges • Aznavour • (include all facets)

42. Aznavour and Coulonges • The example of Georges Coulonges as (comp.), (par.) – leave in parenthicalelements or removethem • Vs

43. A few problems, questions remain • Strip out parenthetical notes for facets and suggested new searches • In addtion to ‘(par.)’ etc. wealso have ‘(par. Fr.)’ and others. To getthem all weused:

44. A few problems, questions remain • Currently no way to limit or prefilter to ‘Musique en feuille’, searchable elements are incompatible with visible elements • Resource type vs Format • Library vs Collection • Not a visible searchable scope option

45. Outcomes • Collection is available via Primo • Records are modified, added, harvested nightly into Primo • Circulation stats increase dramatically

46. Future plans • Phase 2 of Pouchet collection, ~10k vinylrecordings • Horus : Law libraryannual reports database, 1500 records • Gestio: Management documentation centre collection of greyliterature, technicalpapers, etc. 6000 records • Possibility of adding digital objects if sheet music isscanned, documents are digitized

47. Questions?jerabek.alexander_j@uqam.ca