1 / 14

Advisory Group Meeting 25 May 2006

Advisory Group Meeting 25 May 2006. ‘Create once, use many times’. Clever Recordkeeping Metadata Project Advisory Group Meeting 25 May 2006. CRKM Research Team. A quick recap. Sustainability requires moving beyond hand crafting crosswalks and hard wiring applications

ayita
Download Presentation

Advisory Group Meeting 25 May 2006

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. Advisory Group Meeting25 May 2006 ‘Create once, use many times’ Clever Recordkeeping Metadata Project Advisory Group Meeting 25 May 2006 CRKM Research Team

  2. A quick recap • Sustainability requires moving beyond hand crafting crosswalks and hard wiring applications • Constraints of records management and archival processes, technologies and tools developed for paper recordkeeping and in application-centric IT environments • First Iteration • Establish and instantiate a scenario in which to explore metadata re-use • Conceptualise application independent metadata translation as a metadata broker, i.e. middleware • Determine technical environment for the prototyping • Standards not as interoperable as assumed • Complexity in recordkeeping metadata re-use • Limitations of current recordkeeping metadata standards • Use XML and XSL technologies to instantiate schemas and crosswalks • Second Iteration • Develop metadata broker as a cluster of web services • Revise scenario processes in line with continuum and SOA view • Test use of broker within such a framework • Develop business case for recordkeeping metadata in such a framework • Today’s meeting:- • Discuss actions, observations and reflections Source: Kemmis and McTaggert 1988

  3. CRKM Metadata Broker November 2005 Validation service Target metadata Source metadata Translation service Crosswalk compilation service Crosswalk compilation service Registration Registry services Schema information Repository Machine processable representations of metadata schemas and crosswalks Registry Authoritative information on metadata schemas, metadata elements and crosswalks in human readable and machine processable forms Request for Schema

  4. ebXML Registry • Two part specification of requirements for object repository and associated registry • ebXML Registry Information Model • ebXML Registry Services and Protocols • Availability of freeBXML Registry - open source reference implementation of an ebXML Registry • see http://ebxmlrr.sourceforge.net/

  5. CRKM Metadata Broker Implementation CRKM Registry ebXML Registry Metadata Broker Schemas Crosswalks

  6. Layer 3 Abstract Layer 2 Representation CRKM Descriptive Requirements Conceptual Model Metadata/Data Standard Metadata/Data Standard Metadata/Data Standard Version 1 Version 2 Version n Encoding 1 Encoding 2 Encoding n Version 1 Version 2 Version n

  7. CRKM Recordkeeping Requirements • Need to respect SOA design principles of loose coupling and minimal dependencies • Each component keeps records of its transactions • ebXML Registry Event Information Model • AuditableEvent class allows for the event to be located in time (timestamp), linked to the agent responsible for generating the event (user), and the transaction that generated the event (requestId). • Stamp target instance with translation details • Implications for schema design in incorporating metadata about the metadata

  8. Realising sustainable interoperability API EDI Middleware Web services Service oriented architecture Prototype Conceptualisation

  9. Metadata broker as middleware Records Management Application Web Management Systems Archival Gateways Email and Desktop Applications Metadata Broker Subject Portals Community Archives Archival Management Application Business Information Systems

  10. Request the source – target crosswalk Translation Service Metadata Registry Web Service Layer Web Service Layer Request to translate from source to target Source –Target Crosswalk Service Web Service Layer Metadata broker as web services cluster Source instance Target instance Metadata Broker Client

  11. Service oriented architectures Recordkeeping Services

  12. Recordkeeping services in SOA Metadata Broker

  13. Conclusions • Extent to which paper paradigms still dominate recordkeeping practice • Why the service oriented paradigm is desirable for recordkeeping • Point to the degree of re-thinking required in the profession to make recordkeeping in such environments a reality • Highlight the infrastructure required to support clever metadata, particularly the role of registries at different levels of operation and granularity

  14. Conclusions (continued) • For schema and standard developers • Moving from compliance to interoperability requires rigorous conceptual modelling translatable into unambiguous and precise representations for machine processing • Need for identification and descriptive frameworks for schemas to facilitate their use

More Related