Investigating the transfer from DigiTool Resource Discovery to Primo - lessons learned

1. Investigating the transfer from DigiTool Resource Discovery to Primo- lessons learned Karin Smith Charles Sturt University kasmith@csu.edu.au Bronwyn King UNILINC bronwyn.king@unilinc.edu.au

2. Charles Sturt University (CSU) • Multi-campus Australian regional university • ~30,000 students including many distance education students • ~1000 active research staff

3. UNILINC • Provides hosting and software support services to a consortium of libraries (mostly Ex Libris products) • DigiTool, Primo, Aleph and SFX services provided to CSU

4. CSU Research Output (CRO) • CRO is CSU’s institutional repository • Showcasing CSU’s research output • Used for government reporting - metadata • Open access publications harvested to Google and Trove • DigiTool software • Resource Discovery has been the main UI

5. Why migrate to Primo? • Modern/user friendly discovery interface • CSU Library already uses Primo as their main UI: PrimoSEARCH • Open access DigiTool records are loaded to PrimoSEARCH • Separate CRO user interface is still required: • Allows display of locked and unlocked records • CRO view is tailored to researchers at CSU

6. CRO Primo view

7. Migration issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

8. CRO DigiTool collections How do we replicate the DigiTool hierarchical structure? Solution: • Develop Primo deep links for each collection permutation • Embed links in service_csu2.html using a jQuery accordion dropdown menu

9. CRO DigiTool collections e.g. Faculty/School – 2011 – Arts – School of Theology

10. CRO DigiTool collections

11. CRO DigiTool collections

12. CRO DigiTool collections

13. Migration issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

14. DigiTool publication types vs Primo resource types Primo distinguishes Book and eBook whereas DigiTool does not DigiTool publication types • Book • Book chapter • Conference paper • Creative works • Journal article • Report CSU Library Primo/PCI resource types • Audio • Book • Conference paper • eBook • eVideo • Image • Journal article • Thesis • + others

15. DigiTool publication types vs Primo resource types Normalisation rule logic:

16. DigiTool publication types vs Primo resource types Additional resource types required DigiTool publication types • Book • Book chapter • Conference paper • Creative works • Journal article • Report CSU Library Primo/PCI resource types • Audio • eBook chapter • Book • Conference paper • eBook • eVideo • Images • Journal article • Thesis • + others

17. Migration issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

18. Locked CRO resources Initial problem: • View online tab displayed for locked and unlocked resources • Frustrating for the end user as even when logged in, the object would not be available to them:

19. Locked CRO resources Solution: Where the record only has locked DigiTool digital objects and no external eResource link (descriptive MD 856 40 $u): • Set the Primo delivery category to "physical item" • Set "may be available" availability text to "Citation only"

20. Locked CRO resources Normalisation rules adjusted:

21. Locked CRO resources

22. Migration issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

23. Additional Primo Facets Additional facets: author’s faculty, school and research centre - issues: • Facet values dirty due to human interaction with adding/editing data • Facet values should not be generated for certain legitimate names, e.g. Office of DVC • CRO includes superseded faculty, school and research centre names: e.g. Current faculty name = Science Old faculty name = Science and Agriculture

24. Additional Primo Facets Strategies: • Dirty data tidied in DigiTool by making global changes (p_manage_21) and by making manual changes in Meditor • Undesirable facet values, e.g. Office of the DVC, suppressed via the normalisation rules • Decided that old faculty, school and research centre names would not be retrospectively changed

25. Migration issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

26. Authentication • Previously PDS SSO and Shibboleth had been configured for Primo and Aleph • Usually SSO is configured for all relevant products • Only CRO staff are permitted to access locked DigiTool objects Conclusion: SSO for DigiTool not needed

27. Migration issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

28. researchoutput.csu.edu.au alias • CRO badging is important including the DigiTool/Resource Discovery links • researchoutput.csu.edu.au is the link for CRO’s Resource Discovery • The researchoutput.csu.edu.au alias points to the DigiTool server: bilby.unilinc.edu.au • researchoutput.csu.edu.au should be redirected to the Primo server at the STP stage

29. researchoutput.csu.edu.au alias Trialled in test DigiTool and staging Primo environments: • CSU’s Division of Information Technology setup a new CSU alias called cro.csu.edu.au • cro.csu.edu.au was then pointed to the Primo test server (quinto.unilinc.edu.au) • Primo main menu and tile links updated from quinto.unilinc.edu.au to cro.csu.edu.au

30. researchoutput.csu.edu.au alias Test results: • The CRO link works: e.g. http://cro.csu.edu.au/primo_library/libweb/action/search.do?vid=CSU2&mode=Advanced • The alias persists regardless of the searches carried out or the links clicked within the CRO Primo view

31. Migration Issues Major issues: • CRO DigiTool collections • DigiTool publication types vs Primo resource types • Locked CRO resources • Additional Primo facets • Authentication • researchoutput.csu.edu.au alias • DigiTool redirections to the CRO Primo view

32. DigiTool redirections to the CRO Primo view Categories of required redirections: • RD collections • RD author publications deep link • RD permalinks

33. DigiTool redirections to the CRO Primo view Solution: Addition of rewrites to Apache httpd.conf e.g. RD author publications redirection: This rewrite redirects: http://researchoutput.csu.edu.au/R?func=search-advanced-go&file_format_code=WEX&local_base=GEN01-CSU01&mode=1&find_code1=WID&request1=<staff ID> To the equivalent Primo deep link: http://cro.csu.edu.au/primo_library/libweb/action/dlSearch.do?&institution=CSU&vid=CSU2&group=GUEST&onCampus=false&query=lsr19,contains,<staff ID>

34. Other issues • Author publications link generator • Addition of new search types • Primo bibliographic display tweaking • Permalinks display • Duplicates • Broken DigiTool descriptive MD links