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
Charles Sturt University (CSU)
•
Multi-campus Australian regional university
•
~30,000 students including many distance education students
•
~1000 active research staff
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
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
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
CRO Primo view
Migration issues
Major issues:
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
CRO DigiTool collections
e.g. Faculty/School – 2011 – Arts – School of Theology
CRO DigiTool collections
CRO DigiTool collections
CRO DigiTool collections
Migration issues
Major issues:
DigiTool publication types vs Primo resource types
1. Primo distinguishes Book and eBook whereas DigiTool does not
DigiTool publication types
CSU Library Primo/PCI resource types
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Book
Book chapter
Conference paper
Creative works
Journal article
Report
Audio
Book
Conference paper
eBook
eVideo
Image
Journal article
Thesis
+ others
DigiTool publication types vs Primo resource types
Normalisation rule logic:
DigiTool
publication
type
Attached DigiTool UNLOCKED object Primo resource
and/or external link exists (856 40
type
URL)?
Book
Y
eBook
Book
N
Book
DigiTool publication types vs Primo resource types
2. Additional resource types required
DigiTool publication types
CSU Library Primo/PCI resource types
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Book
Book chapter
Conference paper
Creative works
Journal article
Report
Audio
eBook chapter
Book
Conference paper
eBook
eVideo
Images
Journal article
Thesis
+ others
Migration issues
Major issues:
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:
Locked CRO resources
Solution:
Where the record only has locked DigiTool digital
objects and no external eResource link (descriptive
MD 856 40 $u):
1.
Set the Primo delivery category to "physical item"
2.
Set "may be available" availability text to "Citation
only"
Locked CRO resources
Normalisation rules adjusted:
Attached UNLOCKED
DigiTool object and/or
external link exists (856
40 URL)?
Primo delivery
category
View online
tab
displays?
Availability
text
Yes
Online resource
Yes
Online
access
No
Physical item
No
Citation only
Locked CRO resources
Migration issues
Major issues:
Additional Primo Facets
Additional facets: author’s faculty, school and research
centre - issues:
1.
Facet values dirty due to human interaction with
adding/editing data
2.
Facet values should not be generated for certain legitimate
names, e.g. Office of DVC
3.
CRO includes superseded faculty, school and research
centre names:
e.g.
Current faculty name = Science
Old faculty name
= Science and Agriculture
Additional Primo Facets
Strategies:
1.
Dirty data tidied in DigiTool by making global
changes (p_manage_21) and by making manual
changes in Meditor
2.
Undesirable facet values, e.g. Office of the DVC,
suppressed via the normalisation rules
3.
Decided that old faculty, school and research
centre names would not be retrospectively
changed
Migration issues
Major issues:
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
Migration issues
Major issues:
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
researchoutput.csu.edu.au alias
Trialled in test DigiTool and staging Primo
environments:
1.
CSU’s Division of Information Technology setup a
new CSU alias called cro.csu.edu.au
2.
cro.csu.edu.au was then pointed to the Primo test
server (quinto.unilinc.edu.au)
3.
Primo main menu and tile links updated from
quinto.unilinc.edu.au to cro.csu.edu.au
researchoutput.csu.edu.au alias
Test results:
1.
The CRO link works:
e.g.
http://cro.csu.edu.au/primo_library/libweb/action/search.do?v
id=CSU2&mode=Advanced
2.
The alias persists regardless of the searches carried out or
the links clicked within the CRO Primo view
Migration Issues
Major issues:
DigiTool redirections to the CRO Primo view
Categories of required redirections:
•
RD collections
•
RD author publications deep link
•
RD permalinks
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-advancedgo&file_format_code=WEX&local_base=GEN01CSU01&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=fal
se&query=lsr19,contains,<staff ID>
Other issues
•
Author publications link generator
•
Addition of new search types
•
Primo bibliographic display tweaking
•
Permalinks display
•
Duplicates
•
Broken DigiTool descriptive MD links