Hot Topics: The DuraSpace Community Webinar Series
Series 9: Early Advantage: Introducing New Fedora 4.0 Repositories
Curated by David Wilcox, Fedora Product Manager, DuraSpace
“Fedora 4.0 in Action at The Art Institute of Chicago and UCSD”
Wednesday, October 15, 1:00-2:00pm ET
Presented by:
David Wilcox, Fedora Product Manager, DuraSpace
Stefano Cossu, Data and Application Architect, Art Institute of Chicago
Nikhil Trivedi, Senior Application Developer, Art Institute of Chicago
Esmé Cowles, Software Engineer, University of California San Diego
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
10.15.14 Presentation Slides, “Fedora 4.0 in Action at The Art Institute of Chicago and UCSD”
1. October 15, 2014 Hot Topics: DuraSpace Community Webinar Series
Hot Topics: The DuraSpace Community Webinar Series
Series Nine:
“Early Advantage: Introducing New Fedora 4.0 Repositories”
Curated by David Wilcox,
Fedora Product Manager, DuraSpace
2. Sponsored by
Funding for this webinar series comes from our Members.
Join your fellow institutions by becoming a DuraSpace Member in support of
Visit http://duraspace.org/about_membership
3. October 15, 2014 Hot Topics: DuraSpace Community Webinar Series
Webinar 1: Fedora 4.0 in Action at The Art Institute of Chicago and UCSD
Presented by:
David Wilcox, Fedora Product Manager,
DuraSpace
Stefano Cossu, Data and Application Architect,
Art Institute of Chicago
Nikhil Trivedi, Senior Application Developer,
Art Institute of Chicago
Esmé Cowles, Software Engineer,
University of California San Diego
4. Fedora 4.0
•
Beta released in June 2014
•
Production release by end of year
•
4.0 focus on new installations
•
4.1 will support F3 to F4 migration
September 25, 2012 Hot Topics: DuraSpace Community Webinar Series
5. Getting to Fedora 4.0 Production
•
Beta pilot projects
•
Acceptance testing
•
Technical Working Group
•
Community feedback
•
Developer commitments
September 25, 2012 Hot Topics: DuraSpace Community Webinar Series
6. Beta Pilot Goals
•
Test 4.0 features in a production-like environment
•
Gather feedback for 4.0 release
•
Demonstrate diverse use cases
•
Encourage early adoption of Fedora 4
September 25, 2012 Hot Topics: DuraSpace Community Webinar Series
7. The Art Institute of Chicago Fedora 4 Beta Pilot Overview
Stefano Cossu, Director of Application Services, The Art Institute of Chicago Fedora Beta Pilot Webinar – October 14t, 2014
8. AIC DAMS Project Goals
•
Quickly grew out of original scope of storing assets
•
Long-term project goals:
•
Become a central source for storing and accessing shared knowledge
•
Integrate with existing systems
•
Federate and harmonize external resources
•
Provide different access levels to resources
•
Automate routine operations
•
Handle asynchronous operations
11. Most Useful F4 Features
•
Content modeling – flexible language at zero cost
•
Sequencers – event-based automation
•
Federation – integrating other data sources
•
Flexible access policies
•
External indexing – search & query endpoints
12. F4 Beta Pilot: Mutual Advantages
•
Providing early feedback about real-world use
•
Discovering common needs
•
Providing complex or less obvious scenarios and finding common solutions
•
Proposing features for merging in main codebase
•
Receiving fast, valuable feedback from the community
13. Where We Are At
Build single-node, custom Fedora instance
Create a content model
Create derivative and metadata automation
Build service provider / middleware
Write migration scripts
Set up initial asynchronous framework
Design front-end interface
Write custom federation connectors
Write access policies
Set up Fedora staging environment
Full-scale migration and load test
Purchase production hardware and set up systems
Build front-end on legacy CMS
14. Implementation Phases
Phase 1
•
Design initial content model (images only)
•
Build basic automation
•
Integrate with current CMS
Phase 2
•
Support all media types
•
Adjust content model to new media types
•
Extend front-end capabilities
Phase 3
•
Federate and link non-asset resources
•
Create aggregation entities
Phase 4
•
Federate external resources
•
LOD platform – provide public SPARQL endpoint
15. 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
32. Background
•
Homegrown repository
•
RDF metadata in a triplestore
•
Files on disk
•
Builtin derivatives, characterization, rights
33. Interest In Fedora
•
Wanted to stop doing everything ourselves
•
Loved the Hydra community
•
Fedora 3 didn't work the way we wanted it to
•
Implemented Fedora 3 API in our repository, with Hydra frontend application
34. Interest in Fedora 4
•
Wanted Fedora 4 to be different
•
Participating in Fedora 4 sprints since April 2013
35. Features
•
Native RDF support
•
Linked Data Platform
•
Transparent storage
•
Filesystem federation / serialization to disk
36. Beta Pilot
•
Map existing RDF to Fedora 4
•
Compare filesystem to Modeshape
•
Performance (ingest, read)
•
Functionality (transactions, versioning)
37. Federation Performance
•
Copying files is faster than REST API ingest
•
Updating metadata is much slower
•
On balance, Modeshape is slightly faster
•
Exploring Modeshape with external files
38. Federation Functionality
•
Transactions and versioning
•
Don't use these now, but interested
•
Easy access to files and serialized metadata
•
Message consumer can replicate this for Modeshape content
39. Ongoing Work
•
Full-scale ingest
•
With message consumer
•
Read performance
•
Hydra community working on shared metadata modeling for rights, works, etc.