350 likes | 365 Views
Explore ADORA Digital Object Repository's history, concepts, extensibility mechanism, metadata registry, and operations. Learn about CNRI's rich repository project legacy and the standards set by ISO/IEC 11179 for metadata schema descriptions.
E N D
Active Digital Object Repository Architecture ADORA CNRI
Presentation Overview 1 Project History 2 ADORA Digital Object Concepts 3 ADORA Extensibility Mechanism 4 ADORA Metadata Registry CNRI
Presentation Overview 1 Project History 2 ADORA Digital Object Concepts 3 ADORA Extensibility Mechanism 4 ADORA Metadata Registry CNRI
CNRI’s Repository Project History • Repository, Handle and Digital Object notions elaborated by Kahn and Wilensky • Collaboration between CNRI and Cornell to further refine and elaborate the notions of digital objects and repositories. • Implementation of a prototype repository for the Library of Congress. • Implementation of a prototype repository for DTIC’s DVL. • Interoperability experiments between CNRI and Cornell funded by the Dlib test suite. CNRI
Presentation Overview 1 Project History 2 ADORA Digital Object Concepts 3 ADORA Extensibility Mechanism 4 ADORA Metadata Registry CNRI
Hamlet Get Page(42) Dissemination ADORA Digital Object CNRI
Identifier Operations Metadata Hamlet Data Operations Data ADORA Digital Object • Digital Objects are uniquely identified within a given domain name space. • Digital Objects can store or reference sets of sequences of typed bytes. • Digital Objects can associate their respective content with a set of extensible operations to reflect and enforce their creator’s assigned intended use. • Digital Objects are accessed through disseminations. CNRI
Repository • Clients can access any repository using the RAP protocol. RAP Deposit • To deposit new digital objects • To disseminate existing objects Disseminate Client ADORA Repository • Repositories provide storage for Digital Objects. • Repositories provide a secure environment in which all Digital Object disseminations are computed. CNRI
RAP Hamlet RAP Client Client RAP RAP Client Client Digital Objects are Statefull To be or not to be... 3rd edition 341 pages • Digital Objects are network accessible using the Repository Access Protocol (RAP). • Digital Objects maintain a unique sessions with each user. • User interactions are contextualized. CNRI
3 Connect to repository CNRI/TEST 4 1 Get Digital Object Resolve CNRI/TEST Handle System CNRI/Repository CNRI/TEST URN CNRI/Repository 2 CNRI/Repository DLS IOR:0001231. Resolve CNRI/Repository Digital Object Have Handles Get Digital Object CNRI/TEST Client CNRI
Presentation Overview 1 Project History 2 ADORA Digital Object Concepts 3 ADORA Extensibility Mechanism 4 ADORA Metadata Registry CNRI
Identifier Type Signature Definition Operations Stored Type Signature Data Operations Operations Data Implementation Servlet Servlet Stored Concepts of Extensible Operations CNRI
Identifier Identifier Operations Identifier Disseminator Type Signature Data Operations Data Servlet Attachments Disseminator Data Data Attachments Concepts of Extensible Operations Identifier • GetPage(page) • GetNextPage() • Getbibliography() • Translate(Language) Type Signature Servlet • How to GetPage(page) ? • How to GetNextPage() ? • How to Getbibliography() ? • How Translate(Language) ? • What Data to use ? CNRI
Identifier Client C Identifier Type Signature XYZ Repository Repository2 Disseminate Servlet XYZ-1 Data Attachments Client A XYX Data XYZ-1 Client B Deposit Extensible Operations Example CNRI
Presentation Overview 1 Project History 2 ADORA Digital Object Concepts 3 ADORA Extensibility Mechanism 4 ADORA Metadata Registry CNRI
ISO/IEC 11179 General Concepts ISO/IEC 11179 describes the standardizing and registering of metadata schemata to make them understandable and sharable. Provides a standard for formulating and maintaining metadata schemata element descriptions in a consistent manner. Provides guidance for establishing metadata description registries. CNRI
ISO/IEC 11179 Metadata Schema Description ISO 11179 defines a set of attributes for each element within any metadata schema. A Data Element’s attributes describe the metadata element in the following categories: Identifying Definitional Relational Representational Administrative CNRI
ISO/IEC 11179 Data Element Example: Part 1 D-LIB Magazine Metadata Schema Metadata element: Title Identifying: Name: Title Unique Identifier: Title Version: 0.1 Registration Authority: Corporation for National Research Initiatives Definitional: Definition: The title of the D-Lib Magazine item being described. CNRI
ISO/IEC 11179 Data Element Example: Part 2 Relational: Optional Fields Representational: Representation Category: ISO/IEC 10646 Form of Representation: text Data Type of Data element Value: character Maximum Size of Value: unlimited Minimum Size of Value: 0 Permissible Data Element Values: Administrative: Optional Fields CNRI
ISO/IEC 11179 Metadata Registry Promotes registration and acquisition of metadata schemata definitions. Enables the greater re-use of metadata schemata. Enhances the accuracy of new metadata. Enables for the interchange of metadata and data across computer systems and organizations. Facilitates the manipulation of metadata and data in software. CNRI
ADORA as a Metadata Registry • ADORA provides distributed access to its Digital Objects. • ADORA Digital Objects can have a wide range of content. • ADORA Digital Objects provide a high level of abstraction over the data that they contain. • ADORA Digital Objects provide a homogeneous interface to a heterogeneous set of contents. • Digital Objects have a high level of integrity and protect their content from unauthorized access. CNRI
Beyond ISO/IEC 11179 Functionality ADORA registries can be integrated with metadata and data collections. ADORA registries provide a set of operations that can convert metadata elements from one schema to another. ADORA registries are extensible allowing the addition of new conversion operations. ADORA registries are interoperable and can easily be aggregated. ADORA enhances the ability to automatically process metadata and data. CNRI
Describe using ISO 11179 Instance of Dublin Core Instance -Title -Creator -Subject and Keywords -Description etc... Metadata Schema Describe • -Element: Title • Name: Title • Identifier: Title • Definition: A name given to the resource. • Comment: Typically, a Title will be a name by which the resource is formally known. • -Element: Creator etc…. Metadata Schema Description Encode using XML Encode • <Element> • <Name>Title</Name> • <Identifier>Title</Identifier> • <Definition>A name given to the resource</Definition> • <Comment>Typically, a Title will be a name by which the resource is formally known.</Comment> • </Element> etc…. Encoded Metadata Schema Description Register in Registry Abstraction Register in Registry Digital Object Describing Metadata DC.Title="Kita Yama (Japan)" DC.Creator ="Kertesz, Andre” DC.Subject and Keywords="1968” DC.Definition = “Photograph” etc... Metadata CNRI
ISO11179 Type Signature: • Get Registration Authority • Get Submitting Organization • List Data Elements • Get Data Element(name) • …. • List Schema Conversion Types • ConvertTo(Input Schema, input metadata,Output Schema) DLIB Metadata Schema DLIB Schema ISO 11179 Type Signature ISO 11179 DLIB Attachment • ISO 11179 DLIB • Implements the method described in the ISO 11179 Type Signature given the particularities of the BLIB metadata schema. ISO11179 Metadata Schema Metadata Registry Digital Object • The Digital Object identifier and the disseminator ID are registered in the handle service CNRI
Interoperable Metadata Type Signature: • List Metadata Elements Names • Get Metadata (Element Name) • Get Metadata (Schema, Element Name) • …. • List Schema Conversion Types • ConvertTo(Input Schema, input metadata,Output Schema) DLIB Article #1 DLIBMetadata Interoperable Metadata DLIB Int. Meta. Attachment • DLIB Interoperable Metadata Servlet • Implements the functionality defined by the Interoperable Metadata Type Signature. • Reads DLIB Metadata. DLIB Metadata Metadata Digital Object • The DLIB Metadata is encoded in a format that the DLIB Interoperable Metadata Servlet can process CNRI
Client Interoperable Metadata Using Digital Object CNRI
Locate Registered Metadata Schema 2 DLIB Article Metadata DLIB Schema DLIB Metadata Schema Interoperable Metadata Type DLIB IM-V1 3 Attachments Get Conversion DLIB Metadata Schema Article 4 UCSB, DC DLIB Article Metadata DLIB Schema ISO 11179 Type Signature 6 Convert to UCSB ISO 11179 DLIB Attachment 1 GetConvertionTypes() 7 UCSB Encoded Metadata ISO11179 Metadata Schema 5 ConvertTo(UCSB Schema) Extensible Metadata Conversion -> UCSB, DC -> UCSB Encoded Metadata CNRI
Repository as a Collection of Collections Repository Carnegie Mellon Search Engine CMU Catalog Interface CMU Catalog Cornell CU Catalog Interface Cornell Catalog CMU Catalog Interface Carnegie Mellon UCSB Cornell Catalog Interface Cornell CNRI
Appendix • Handle system integration • Software Architecture • Software Release • ISO/IEC 11179 CNRI
Indexing Service Handle Protocol Handle Service RAP General System Overview Client RAP Repository 1 Repository 2 Indexing Service CNRI
Digital Object Processing Object Management Layer RAP Interface Layer Software Architectural Overview Store End Client Object Persistence Layer Store Interface API Object Management Layer Client Repository RAP Interface Layer RAP Requests RAP Replies Transport Protocol CNRI
Software Release CNRI
Software Components Client System Administration Tool Digital Object Browser Development Tools Client Library RAP RAP Definition Repository Repository Repository DBMS Legacy System CNRI