1. February 2006 Open Repository Meeting, Sydney Australia Integration: Knowing the Limits of a Repository MacKenzie Smith Associate Director for Technology MIT Libraries

2. February 2006Open Repository Meeting, Sydney Australia What is a Repository? Main Entry: 1re·pos·i·to·ry 1 : a place, room, or container where something is deposited or stored : depository 1 : a place, room, or container where something is deposited or stored : depository 2 : a side altar in a Roman Catholic church where the consecrated Host is reserved from Maundy Thursday until Good Friday 3 : one that contains or stores something nonmaterial 3 : one that contains or stores something nonmaterial 4 : a place or region richly supplied with a natural resource 5 : a person to whom something is confided or entrusted Merriam-Webster dictionary

3. February 2006Open Repository Meeting, Sydney Australia Institutional Repositories  Institution-based  Scholarly material in [all] digital formats  Cumulative and perpetual  Open and interoperable SPARC, 2002

4. February 2006Open Repository Meeting, Sydney Australia Digital Libraries  Digitized library material Special collections Special collections Archival collections Archival collections Non-print collections (images, multimedia, etc.) Non-print collections (images, multimedia, etc.)  Resembles publishing  Often requires specialized viewing tools or applications

5. February 2006Open Repository Meeting, Sydney Australia Learning Object Repositories  Discovery/reuse of discrete “Learning Objects” of teaching material  Must interoperate with Course Management Systems Course Management Systems Virtual Learning Environments Virtual Learning Environments Collaborative Learning Environments Collaborative Learning Environments  Standards from IEEE, IMS, ADL,OKI...

6. February 2006Open Repository Meeting, Sydney Australia Data Repositories  Typically specialized for one type of data, e.g. Statistical or geospatial datasetsStatistical or geospatial datasets Biological pathways or micro-array dataBiological pathways or micro-array data Genomics or proteomics dataGenomics or proteomics data Radio telescope or ocean sensor dataRadio telescope or ocean sensor data  Specialized requirements for deposit, search, viewing, manipulating data

7. February 2006Open Repository Meeting, Sydney Australia Non-academic Repositories  Back end for commercial Content Management Systems, other applications  Accessed by JSR 170, WebDAV, proprietary APIs  Next generation file systems which support versioning, rich metadata, security, etc.

8. February 2006Open Repository Meeting, Sydney Australia All of These are called “Repositories” DSpace DSpace Eprints Eprints Fedora Fedora SRB SRB Jackrabbit Jackrabbit Digital Commons Digital Commons Documentum Documentum Harvest Road Harvest Road Digitool Digitool i-Tor i-Tor ARNO ARNO CDSWare CDSWare  Function at different levels of the technical architecture  Have different features, functions  Support different (or many) service models

9. February 2006Open Repository Meeting, Sydney Australia DSpace Example: Core Functionality  Asset Capture Provide a workflow system that allows people (or their proxies) to deposit material directly into the archive  Description Provide tools for searching, browsing metadata and/or full- text of archived material  Redistribution Provide web-based access to archived material once found  Preservation Provide long-term access to archived materials by preserving the contents over archival time frames (i.e. by format migration, emulations tools, etc.)

10. February 2006Open Repository Meeting, Sydney Australia Not Core (for DSpace) Specialized functionality e.g. Traditional archives functionality Traditional archives functionality provenance, integrity, finding aids, etc. Records Management Records Management Publishing (e-journals or other) Publishing (e-journals or other) Classroom delivery Classroom delivery Tools for content manipulation Tools for content manipulation e.g. VDC for statistical datasets, ESRI for GIS, M:Media for annotated multimedia collections

11. February 2006Open Repository Meeting, Sydney Australia Interoperability  Solution for non-core functionality Make DSpace interoperate with other systems and tools that extend its functionality to support non-core services

12. February 2006Open Repository Meeting, Sydney Australia Interoperability Dimensions Systems and Tools interoperate at the protocol level OAI-PMHOAI-PMH Web ServicesWeb Services Z39.50Z39.50 CORBACORBA OKIOKI

13. February 2006Open Repository Meeting, Sydney Australia Interoperability Dimensions Applications interoperate at the functional level Institutional RepositoryInstitutional Repository Course Management (e.g. SAKAI, Blackboard, WebCT)Course Management (e.g. SAKAI, Blackboard, WebCT) Electronic Records ManagementElectronic Records Management E-PublishingE-Publishing E-Research (e.g. Grid)E-Research (e.g. Grid)

14. February 2006Open Repository Meeting, Sydney Australia Interoperability Dimensions Data interoperates at the semantic level DescriptiveDescriptive MODS, DC, MARC, VRA, LOM, FDGC, DDI…MODS, DC, MARC, VRA, LOM, FDGC, DDI… AdministrativeAdministrative ODRL, ODRL, TechnicalTechnical PREMIS, MPEG7PREMIS, MPEG7 StructuralStructural METS, IMS-CP, MPEG21METS, IMS-CP, MPEG21

15. February 2006Open Repository Meeting, Sydney Australia Interoperability is the Intersection of

16. February 2006Open Repository Meeting, Sydney Australia Defining Limits How do you define the limits of an IR? an IR? a library or an archive? a library or an archive? “academic computing”? “academic computing”? “content management” or “asset management”? “content management” or “asset management”?

17. February 2006Open Repository Meeting, Sydney Australia Defining Limits Focus on Mission Collection/asset management? Collection/asset management? Business layerBusiness layer Policies, description, long-term preservation, reporting, legal oversite, etc.Policies, description, long-term preservation, reporting, legal oversite, etc. Search? Search? Business layerBusiness layer But what about Google Scholar? Scirus? Thomsom Web Citation Index? Worldcat?But what about Google Scholar? Scirus? Thomsom Web Citation Index? Worldcat?

18. February 2006Open Repository Meeting, Sydney Australia Defining Limits Publishing? Publishing? User Interface or application layerUser Interface or application layer Manikin, other Cocoon-based UIsManikin, other Cocoon-based UIs Specialized content delivery toolsSpecialized content delivery tools e.g. classroom delivery, dataset manipulation Storage? Storage? Storage layerStorage layer SRB, data gridSRB, data grid Requires serious technical expertiseRequires serious technical expertise

19. February 2006Open Repository Meeting, Sydney Australia Conclusion  Start with a well-defined service model (business process, e.g. an IR)  Focus application development on that model  Accomplish other functionality through interoperation  Technical interoperation between component systems is easy…  Defining how those systems will work together functionally is harder… need a service framework  Achieving useful semantic interoperability is very hard… need fewer “standards” and better data models