Dura Space Fedora and Dura Cloud Thorny Staples

Dura. Space, Fedora and Dura. Cloud Thorny Staples Director, Community Strategy and Alliances ESIP Meeting, July 8, 2009

Dura. Space, 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 • Misson-driven, products evolve to follow community needs • Moving towards community-based software development

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

Dura. Space Products • Fedora • Dspace • Akubra – storage plug-in module with tranactional file system • Mulgara – RDF indexing engine • Topaz – core semantic knowledgebase components • Dura. Clould

Solution Communities • Community group that creates and maintains the vision for solution bundle in an area • Gathers resources to create software for solution • Coordinates development with Dura. Space technical staff • Smaller group that gets things done will emerge

Solution Areas • • • Data Curation Open Access Publishing Integration Services Preservation and Archiving Small Archives Scholars’ Workbench

Other Possible Community Groups • Other software development groups • News and Publications Outreach group that works with our Communications Director • Issue/advocacy groups that work on standards important to the community

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

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

Community-built Applications • • Fez Muradora Islandora (Drupal-based) Arrow VITAL (vendor software from VTLS) e. Sci. Doc Hydra

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.

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.

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

PID Object Properties LEGEND Client provides value System generates value Either way PID “namespace: name Object Type “Data Created Date “ 2007 -04 -30 T 19: 59: 03. 000 Z” (UTC, ISO 8601 format) Last Modified Date “ 2007 -04 -30 T 19: 59: 03. 000 Z” (UTC, ISO 8601 format) or Service Definition or Service Deployment State “A”, “I”, or “D” (Active, Inactive, Deleted) Label “Any string” Content Model “Any string” Owner ID “Any string”

Datastreams hold or represent the content Managed Fedora stores and manages the content bytestream. Content located via internal ID External Fedora stores a reference (URL) to the content and mediates access to the content External Redirected Inline XML Fedora stores a reference (URL) to the content, but will not mediate access to content. Fedora stores a name-spaced block of XML content within the Fedora digital object XML wrapper file.

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

Relationships Among Objects • Describes adjacency relationships among objects, among units of content • RDF data of the form: PID – type. Of. Relationship – related. Object. PID • Can used to assemble aggregations of objects • Can build graphs of relationships to feed into user interfaces

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

Content Access Content Management

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

Service Definition Object Cmodel Object ce n i v o r se ripti sc b su Persistent ID (PID) System Metadata Datastreams Service Definition Metadata Persistent ID (PID) RDF data System Metadata Datastreams da t a co service contract nt Data Objects Persistent ID (PID) ra ct Persistent ID (PID) System Metadata Datastreams System Metadata Service Binding Metadata (WSDL) Datastreams Service Mechanism Object Web Service

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

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

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

Current Work… early seeds for Dura. Cloud concept Shared Storage Abstraction Plug-in 1 Amazon Plug-in 2 Local Storage Plug-in … University SAN/Fabric

Dura. Cloud - 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 Dura. Space not-for-profit org • Partnerships with cloud providers • “Pay for use” for services and storage

Dura. Cloud Trusted management of and access to durable digital assets in the cloud Dura. Space Mediating Service Amazon EMC Sun Microsoft

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

Examples • • Text, images only Art and Architecture Quantitative data Aggregation objects