advisory group meeting 25 may 2006
DESCRIPTION
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 - PowerPoint PPT PresentationTRANSCRIPT
www.monash.edu.au
Advisory Group Meeting25 May 2006
Clever Recordkeeping Metadata Project
Advisory Group Meeting
25 May 2006
CRKM Research Team
www.monash.edu.au
2
A quick recap
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
• Use XML and XSL technologies to instantiate schemas and crosswalks
• 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
• Standards not as interoperable as assumed
• Complexity in recordkeeping metadata re-use
• Limitations of current recordkeeping metadata standards
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
Source: Kemmis and McTaggert 1988
Today’s meeting:-
• Discuss actions, observations and reflections
www.monash.edu.au
3
Translation service
CRKM Metadata Broker November 2005
RegistryAuthoritative information on metadata
schemas, metadata elements and crosswalks in human readable and
machine processable forms
Target metadata
Request for Schema
Schema information
Registration
Source metadata
Validation service
Crosswalk compilation service
RepositoryMachine processable
representations of metadata schemas and crosswalks
Registry services
Crosswalk compilation service
www.monash.edu.au
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/
www.monash.edu.au
5
CRKM Registry
CRKM Metadata Broker Implementation
ebXML Registry
Metadata Broker
Schemas
Crosswalks
www.monash.edu.au
6
CRKM Descriptive Requirements
Layer 3
Abstract
Layer 2
Representation
Conceptual Model
Metadata/Data Standard
Metadata/Data Standard
Metadata/Data Standard
Version 1
Encoding 1
Version 2 Version n
Encoding 2 Encoding n
Version 1 Version 2 Version n
www.monash.edu.au
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
www.monash.edu.au
8
Realising sustainable interoperability
API EDI Middleware Web services
Service oriented
architecture
Prototype
Conceptualisation
www.monash.edu.au
9
Metadata broker as middleware
Records Management Application
Archival Management Application
Subject Portals
Community Archives
Web Management
Systems Archival Gateways
Email and Desktop
Applications
Metadata Broker
Business Information
Systems
www.monash.edu.au
10
Metadata broker as web services cluster
Translation Service
Web Service Layer
Metadata Registry
Web Service Layer
Request to translate
from source to target
Source –Target Crosswalk Service
Web Service Layer
Metadata Broker Client
Request the source – target crosswalk
Source instance
Target instance
www.monash.edu.au
11
Service oriented architectures
Data/Information/Object Stores
Business Process Engines
Infrastructure Services
Utility Services
Business Services
Service Bus
Service Registries
Metadata Registries
Business Logic/Rule Bases
Recordkeeping Services
www.monash.edu.au
12
Recordkeeping services in SOA
Data/Information/Object Stores
Recordkeeping Business Process
Engines
Infrastructure Services
Utility Services
Recordkeeping Business Services
Service Bus
Recordkeeping Service Registries
Recordkeeping Metadata Registries
Recordkeeping Business Logic/Rule
Bases
Metadata Broker
www.monash.edu.au
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
www.monash.edu.au
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