1. DuraSpace, Fedora and DuraCloud Triangle Research Libraries Network September, 2009

2. DuraSpace, Inc. Combined Fedora Commons, Inc. and DSpace Foundation 501-(c)3 private, non-profit company 4-year project funded by Moore Foundation to become self-sustaining Continuing software development Moving towards community-based software development Ensuring durability for a web in the clouds!

3. Scholarly and Scientific Collections Preservation and Archiving Education, Knowledge Spaces The world we work in… Data Curation, Linking, Publishing blog and wiki and more …

4. DuraSpace Products Fedora Dspace Akubra – storage plug-in module with transactional file system Mulgara – RDF indexing engine Topaz – core semantic knowledgebase components DuraCloud

5. Solution Communities Community group that creates and maintains the vision for software solutions in an area Trying to create the conditions for collaboration Gather resources to create software for solution Coordinates development with DuraSpace technical staff

6. Solution Areas Data Curation Open Access Publishing Preservation and Archiving Small Archives Scholars Workbench

7. The Flexible Extensible Digital Object Repository Architecture A set of abstractions that can be used to represent different kinds of data A repository management system A foundation for many information management applications Designed to make data durable over the long term

8. 165 Current Known Users Broadcasting and media – 1 Consortia – 9 Corporations – 14 Government agencies – 8 IT- Related Institutions – 10 Medical Centers and Libraries – 4 Museums and Cultural Organizations – 5 National Libraries and Archives – 16 Professional Societies – 2 Publishing - 4 Research Groups and Projects – 18 Semantic and Virtual Library Projects - 6 University Libraries and Archives - 68

9. Making complex digital information durable is a very hard problem The existence and meaning of content needs to be verifiable as technologies change A history of the changes to the encoding and state of content must be reliably provided A meaningful context for any unit of content may be one of many and must be sustained Complex resources will increasingly be dispersed across institutional boundaries.

10. The Fedora abstractions provide a durability framework. Content is unitized as information objects that combine data, metadata, policies, relationships and the history of the object. Complex digital resources are formally defined graphs of related objects. The public view of the content is presented as abstract behaviors. The web services orientation of Fedora provides the basis for repository federation.

12. DC Persistent ID RELS-EXT AUDIT 1 1 2 2 n n Reserved Datastreams Custom Datastreams (any type, any number) A data object is one unit of content POLICY

13. Object Properties Data or Service Definition orService Deployment A, I, or D (Active, Inactive, Deleted) Any string 2007-04-30T19:59:03.000Z (UTC, ISO8601 format) Any string System generates value Either way Client provides value LEGEND namespace:name PID Object Type State Label Content Model Created Date Last Modified Date Owner ID PID

14. Datastream Properties Version Any XML NCName unique within the object X, M, E, or R (Inline XML, Managed, Externally Referenced, or Redirected) A, I, or D (Active, Inactive, Deleted) true or false 1 or more System generates value Either way Client provides value LEGEND Datastream Datastream ID State Control Group Versionable

15. Policies Machine enforceable expressions of rules, what they are applied to and who they affect. Who is affected can be defined in different authorization sources, such as LDAP services Rules can be as simple as allow or deny. Rules are applied to objects as a whole, any datastream, or a dissemination, as well as each API call and more.

16. Relationships Among Objects Describes adjacency relationships among objects, among units of content RDF data of the form: PID – typeOfRelationship – relatedObjectPID Can used to assemble aggregations of objects Can build graphs of relationships to feed into user interfaces

17. Optional Object Behaviors Data objects can have different views or transformations Sets of abstract behaviors that different kinds of objects can subscribe to Corresponding sets of services that specific objects can execute The business logic is hidden behind an abstraction

18. Content Access Content Management

20. Content Models Create classes of data objects Expressed as Cmodel objects A Cmodel object defines the number and types of data streams for objects of that class A Cmodel object binds to service objects to enable appropriate behaviors to be inherited by data objects

21. Persistent ID (PID) Service Definition Metadata SystemMetadata Datastreams Cmodel Object Persistent ID (PID) Service Binding Metadata (WSDL) SystemMetadata Datastreams Web Service service contract service subscription data contract Persistent ID (PID) RDF data Datastreams System Metadata Service Mechanism Object Service Definition Object Persistent ID (PID ) System Metadata Datastreams Data Objects

22. Other components include: - Parameter values used by the method - Datetime stamp for earlier version A behavior call has the form : Object PID + SDef Name + Method Name

23. Objects Representing Aggregations Creating parent objects for complex resources Representing explicit collections Representing implicit collections Creating digital surrogates for physical entities

24. Text Collections

25. The Rossetti Archive

26. A Research Project

27. Fedora Repository Service GSearch OAI Ingest Simple JMS Simple JMS Fedora Framework Service Integration More… repository publishes events services listen and consume events or other messages

28. DuraCloud Trusted management of and access to durable digital assets in the cloud DuraSpace Mediating Service Microsoft

29. DuraCloud - basics Replicate to multiple storage providers Replicate to multiple geographic areas Monitor and audit digital assets Compute services in cloud next to content Hosted by DuraSpace not-for-profit org Partnerships with cloud providers Pay for use for services and storage Available to run internally- open source

30. Use Cases: DuraCloud with Cloud Storage Online backup for text, images, datasets, video, audio Enable preservation via multiple copies, geographies, administrations Elastic provisioning of temporary or permanent storage for projects or jobs

31. Use Cases: DuraCloud with Cloud Compute Streaming service for video Hosting JPEG2000 image engine Indexing and other processing heavy jobs Repositories in cloud Data and text mining over open data Optional aggregation of open data

32. Partners and Pilots Selected initial cloud providers Selected 2 initial pilot partners

33. Pilot use cases Ingest large quantity of material Replicate to multiple cloud platforms Manage replication and monitoring Run services

34. DuraCloud Timeline Initial open source release– summer 2009 Begin pilots – September 2009 Pilot data loading and testing – Fall 2009 Plug-ins for repository platforms – Q4 2009 Beta for repository community - Q1 2010 Pilot testing with compute services Q1 2010 Report pilot results – Q1 2010 Launch production service Q2 2010

35. http://www.duraspace.org/ http://www.fedora-commons.org/