1 / 23

Repositories: Disruptive Technology or Disrupted Technology? Sandy Payette, Executive Director DORSDL Workshop at ECDL

Repositories: Disruptive Technology or Disrupted Technology? Sandy Payette, Executive Director DORSDL Workshop at ECDL 2008 September 2008. What does this talk have to say about “applications” which is the theme of this track?. Social and Technical Forces 

minor
Download Presentation

Repositories: Disruptive Technology or Disrupted Technology? Sandy Payette, Executive Director DORSDL Workshop at ECDL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Repositories: Disruptive Technology or Disrupted Technology? Sandy Payette, Executive Director DORSDL Workshop at ECDL 2008 September 2008

  2. What does this talk have to say about “applications” which is the theme of this track?

  3. Social and Technical Forces  Waves of Repository-Enabled Applications • Institutional Repo and Digital Library Apps • IR: Scholars to deposit articles, etc. • DL: Digital library search and access; collections • Collaborative “Web 2.0” • collaborative filtering • annotate; discuss scholarly materials • E-Science, E-Research, Data-Intensive • Publications linked to data • Data aggregation from distributed sources • Fusion, simulation

  4. Implications for Repositories more open more collaborative more web-oriented more interoperable more distributed

  5. We can build amazing private islands Repository Island But should we?

  6. Infrastructure

  7. Emergence of Infrastructure Networks Systems Heterogeneous components Central control Closed, stable Dedicated/improvised gateways Heterogeneous systems Distributed control Coordination Generic gateways Open, reconfigurable Source: Understanding Infrastructure: Lessons for New Scientific Infrastructure, http://deepblue.lib.umich.edu/handle/2027.42/49353

  8. Repositories as components of networked information infrastructure

  9. Which are repositories? Google Data S3 Internet Archive E-Prints DSpace Fedora

  10. Repositories: Disruptive or Disrupted? • Where’s the multi-institutional perspective? • Where’s the Web? • What constraints do we impose by starting with the perspective of a single institution or “enterprise”? • What impact will “Cloud” storage and computing have? • What is the best path to real interoperability? • When do you need complex vs. simple and good enough? • How assert leadership in emerging value networks?

  11. Right Direction …Exposure and Re-Use of Digital Content

  12. Object Re-Use and Exchange (OAI-ORE) http://www.openarchives.org/ore/ Data model for describing bounded aggregations in Web graph

  13. E-Science Aggregations And in digital scholarly communication, the single container concept is obsolete. 2006 Astrophysics paper X-MM-Newton X-ray observation Vilspa, Spain Chandra X-ray observation Cambridge, MA A1795 Basic object information Strasbourg, France Hubble optical observation Baltimore, MD text

  14. Fedora objects can map to ORE Identified, bounded aggregations of related information units that form a logical whole. Components of a digital object may vary according to: Semantic type: book, article, software, dataset, simulation, … Media type: text, image, audio, video, mixed Media format: PDF, HTML, JPEG, MP3, … Network location Relationships: internal, external Identifier PDF HTML MP3 ore:describes ORE Resource Map Exposure

  15. Network of Digital Objects … aggregations related to aggregations ore:describes DC PID4 PID3 PID 1 hasPart hasPart HTML ore:describes DC DC ore:describes

  16. Another right direction…Repositories Embedded in Infrastructure(Fedora as case study)

  17. A History of Fedora Repository Project’s Technical Approaches to Interoperability • 1998: Interfaces • Generic interfaces to access and manage digital objects in a repository • Extensible interfaces on digital objects (“Disseminators”) to provide uniform service access points for heterogeneous underlying content • 2001: Web Services • APIs to access and manage digital objects in a repository • SOAP and REST over HTTP • 2002: XML-based digital object serialization formats • METS • FOXML (Fedora Object XML) • 2005: Semantic Technologies and RDF (RDF-based “Resource Index”)

  18. Now, make it fit better with Web in 2008+ • 2008: Atom Syndication Format • New with Fedora 3.0 via ingest/export operations • 2008: OAI-ORE • Experiments completed • Work in progress for Fedora 3.0/3.1 support • 2008-09: Adopt simple, common Web API(s) with wide appeal • Atom Publishing Protocol • SWORD • Other? • 2008-09: Connect backend storage to “Cloud”

  19. Fedora 2008-09: new Web exposures Atom (2008) OAI-ORE (2008) new formats New Web APIs: Atom Publishing SWORD Other TBD New Web APIs Fedora APIs Registry Search RDF Query Ingest Manage Access New: SPARQL/Mulgara Export Validate Disseminate LinkedData? Policy Store Registry RDF Index Triplestore File system RDBMS (Registry)

  20. Object serialization - Atom feed entry (1-n)

  21. New Akubra Project … backend abstraction Fedora Repository Service New Web APIs Fedora APIs Registry Search RDF Query Akubra Storage Abstraction Store registrydb Plug-in 1 Plug-in 2 Plug-in … • Cloud Storage: • Amazon S3 (now) • Google Data (next) • Other TBD Sun Honeycomb File System Other stores TBD…

  22. Repositories Not-Disrupted Expose repositories in a global networked environment; not just as local, closed systems Make it easier to access and re-use content that is stored in digital repositories, especially on the Web Make repositories conform to common protocols, formats, and standards that are being used in the Web; get repositories in the game of emerging value networks Provide transformations that enable content to be reusable in different contexts. Create repository connectors for common authoring applications to position repositories to capture content at beginning of its life, not at just end of it.

  23. More Info: http://fedora-commons.org/ http://fedora-commons.org/confluence Questions and Discussion

More Related