An overview of the state of the DRI pilot repository in October 2013 and a roadmap of forthcoming features

1. Pilot Repository Overview
Dermot Frost & Eoin Kilfeather

2. • Strand 3 is responsible for the technical delivery of DRI
• Four component Work Packages
 WP5 – Architecture
 WP6 – User Interfaces
 WP7 – Data Management
 WP8 – Storage

3. • Work carried out by a distributed team across three
institutions
 DIT – Eoin Kilfeather, Monica Harasimiuk, Anna Deegan
 NUIM – Damien Gallagher, Sinead Redmond, Ray Noonan
 TCD – Jimmy Tang, Stuart Kenny, Kathryn Cassidy, Peter
Tiernan, Kristina Bako
• Agile methodology
 Requirements driven
 Code sprints
 Daily “stand-up” calls

4. Technology Choices
• Cucumber (http://cukes.info/)
•
Domain Specific Language and executable specs
• Project Hydra (http://projecthydra.org/)
•
Blacklight (SOLR), Active Fedora (Fedora-Commons), Opinionated
Metadata, Hydra Access Controls, Sufia (next iteration)
• Ceph (needs further evaluation)
•
(http://ceph.com/)
S3 interface, Remote Block Devices
• Ansible (Dev/Test/Prod) (http://www.ansibleworks.com/)
• Vagrant (Dev) (http://www.vagrantup.com/)
• Open Nebula (Test/Prod) (http://opennebula.org/)
•
Cloud based infrastructure

5. Current Architecture

6. Current Architecture

7. Current Backend Features
• Ingest tools – web based and command line
for bulk ingest
• Data models
 File types – Audio, PDF
 Metadata – Dublin Core, EAD
• Surrogate generation
• Background processing using resque
• Antivirus and Malware scanning

8. Next Steps
•
•
•
•
•
•
•
•
Subcollection searching
User defined collections
Persistent identifiers
Audit trails
Preservation features
Additional authentication and authorization
Additional datatypes and metadata
Asset characterization