1. Building A Digital Asset Management System With And Around Fedora 4 Stefano Cossu, Director of Application Services, The Art Institute of Chicago DC Fedora User Group Meeting – Washington DC, USA – October 6 t, 2014

2. DAMS Project Goals Initially conceived as a document store Quickly grew out of its original scope Deeper integration with existing systems Provide a single source for storing and accessing shared data

3. LAKE – Linked Asset and Knowledge Ecosystem

7. DAMS Integrated Architecture Fedora 4 offers great integration capabilities Repository is surrounded by legacy and new systems Middleware for legacy systems is being developed Asynchronous and event-based architecture

8. AIC DAMS Main Players

9. Most Useful F4 Features Content modeling – flexible language at zero cost Sequencers – event-based automation Federation – integrating other data sources Triplestore and Solr indexing – search & query endpoints

10. F4 Features: Content Modeling Based on core JCR features Allows multiple inheritance and mix-in types Has been crafted as a foundation to our ontology Some limitations in expressiveness

11. F4 Features: Sequencers Extract metadata on ingestion Create/destroy derivatives based on node events Send messages to external systems

12. F4 Features: Federation Filesystem federation to access external source Custom JDBC connector (WIP) Federated content can be re-arranged via reference datastreams

13. F4 Features: Indexing Multiple indexing engines possible Powerful search/query tools: Triplestore, Solr... Current challenges: Test capability of default triplestores Adding RDFS/OWL statements in triplestore on top of indexed data

14. Thank you Check out our LAKE branch of fcrepo4: https://github.com/aic-collections/aicdams-lake Post on Google Groups: https://groups.google.com/forum/#!forum/fedora-tech E-mail me: scossu@artic.edu