Hydra Connect lightening talk Jan14
•Download as POTX, PDF•
0 likes•1,313 views
A talk given to the Hydra Connect conference, January 2014, on the new version of the Hydra@Hull institutional repository
Hydra Connect lightening talk Jan14
- 2. Hydra@Hull - Background • Fedora repository since 2008 • Founder member of Hydra that same year • Implemented Hydra@Hull – End user interface, September 2011 – Staff create and edit interface, March 2012 – Hydra 6.1 upgrade, January 2014 • Hydra@Hull is a general purpose institutional repository – Aim to be able to offer some management capability for any digital collection on campus Hydra Connect | January 2014 | 2
- 3. Hydra@Hull design • Responsive design • Bootstrap Blacklight • Tile display • Role-dependent display Hydra Connect | January 2014 | 3
- 4. Hydra@Hull - diving in • Search / browse • Facets • Resource type ID Hydra Connect | January 2014 | 4
- 5. Part of a family • Library catalogue • Consistent UI • Common UI framework • Flexibility across material types Hydra Connect | January 2014 | 5
- 6. Differential display • All MODS based • Display by resource type • Single or multiple download • Combination of compound and complex modelling Hydra Connect | January 2014 | 6
- 7. Role-dependent access • Enables differential access • Solr-based gated discovery • Group based or • Individual access control • Permissions and sharing adapted from Scholarsphere Hydra Connect | January 2014 | 7
- 8. Managing stuff • Log in via campus ID and password (Shibbolised) • Functions available depend on role Hydra Connect | January 2014 | 8
- 9. Create and edit • Combination of resource type and generic templates • Configurable drop-down menu choices • Validation of record before creation (ActiveRecord helps with this) • Bootstrap design to break-up on screen workflow Hydra Connect | January 2014 | 9
- 10. Organising the content Structural sets • Internal organisation of content • Used to assign permissions – objects inherit set rights • User never sees these • All objects must be assigned a structural set Display sets • Ad hoc assignation to enable access to objects via their collection • Objects may belong to none, one or more display sets • Optional use • Informed by desire to generate time-bound collections, e.g., for online Archive exhibitions Hydra Connect | January 2014 | 10
- 11. Queue management • All objects go through a managed workflow • Using queue ‘sets’ • Objects created start in the proto-queue • All metadata and content added • When saved they move into the QA queue • Quality checks carried out and permissions added • If there is an issue with an item it gets moved to the Hidden queue • Admin users can move items to the Deleted queue • Though they are retained just in case • Managed using State Machine gem • Uses multiple ‘isMemberOf’ relationships Hydra Connect | January 2014 | 11
- 12. Looking ahead • Add image management workflow • Install, play and feed back on ArchiveSphere • Develop research data catalogue – And extend service for managing datasets • Feed repository into broader discovery environment – Including library catalogue and Summon • Implement Blacklight for archives catalogue • …plenty to talk about at next Hydra Connect! Hydra Connect | January 2014 | 12
- 13. Thank you Chris Awre, c.awre@hull.ac.uk Richard Green, r.green@hull.ac.uk http://hydra.hull.ac.uk http://libsearch.hull.ac.uk