Transcript Advisory Group Meeting 25 May 2006

Advisory Group Meeting
25 May 2006
Clever Recordkeeping Metadata Project
Advisory Group Meeting
25 May 2006
CRKM Research Team
www.monash.edu.au
A quick recap
• Sustainability requires moving
beyond hand crafting crosswalks and
hard wiring applications
First Iteration
• Establish and instantiate a scenario in
which to explore metadata re-use
• Constraints of records management
and archival processes, technologies
and tools developed for paper
recordkeeping and in applicationcentric IT environments
• 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
• Use XML and XSL technologies to
instantiate schemas and crosswalks
• Limitations of current recordkeeping
metadata standards
Second Iteration
Today’s meeting:-
• Develop metadata broker as a cluster of web
services
• Discuss actions, observations and
reflections
• Revise scenario processes in line with
continuum and SOA view
Source: Kemmis and McTaggert 1988
• Test use of broker within such a framework
• Develop business case for recordkeeping
www.monash.edu.au
metadata in such a framework
2
CRKM Metadata Broker November 2005
Validation service
Source metadata
Translation service
Target metadata
Crosswalk compilation service
Registration
Registry services
Registry
Request for Schema
Authoritative information on metadata
schemas, metadata elements and
crosswalks in human readable and
machine processable forms
Repository
Schema information
Machine processable
representations of metadata
schemas and crosswalks
www.monash.edu.au
3
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
4
CRKM Metadata Broker Implementation
CRKM Registry
ebXML Registry
Schemas
Crosswalks
Metadata
Broker
www.monash.edu.au
5
CRKM Descriptive Requirements
Layer 3
Conceptual Model
Abstract
Metadata/Data
Standard
Version 1
Metadata/Data
Standard
Version 2
Metadata/Data
Standard
Version n
Layer 2
Representation
Encoding 1
Encoding 2
Encoding n
Version 1
Version 2
Version n
www.monash.edu.au
6
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
7
Realising sustainable interoperability
API EDI
Middleware
Web
services
Service
oriented
architecture
Prototype
Conceptualisation
www.monash.edu.au
8
Metadata broker as middleware
Records
Management
Application
Email and
Desktop
Applications
Web
Management
Systems
Metadata
Broker
Business
Information
Systems
Archival
Management
Application
Archival
Gateways
Subject
Portals
Community
Archives
www.monash.edu.au
9
Metadata broker as web services cluster
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
Source
instance
Target
instance
Metadata Broker Client
www.monash.edu.au
10
Service oriented architectures
Recordkeeping Services
Data/Information/Object Stores
Business
Services
Infrastructure
Services
Utility
Services
Service Bus
Business
Process Engines
Business Logic/
Rule Bases
Service
Registries
Metadata
Registries
www.monash.edu.au
11
Recordkeeping services in SOA
Metadata Broker
Data/Information/Object Stores
Recordkeeping
Business
Services
Infrastructure
Services
Utility
Services
Service Bus
Recordkeeping
Business Process
Engines
Recordkeeping
Business Logic/Rule
Bases
Recordkeeping Service
Registries
Recordkeeping
Metadata Registries
www.monash.edu.au
12
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
13
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
www.monash.edu.au
14