1. www.monash.edu.au IMS 5010 - Evidence and Metadata 30 May 2006 Investigating metadata interoperability in the Clever Recordkeeping Metadata Project

2. www.monash.edu.au 2 Imagining automated metadata re-use Consumer Registry Finds service Service Descriptions Points to description Translation Service Describes service Locate service Exchange messages Source: Based on diagram from http://www.softstar-inc.com /

3. www.monash.edu.au 3 Clever Recordkeeping Metadata Project Chief Investigator Professor Sue McKemmish, Monash University Partner Investigators Professor Anne Gilliland-Swetland, UCLA Adrian Cunningham, National Archives of Australia Industry Partners and Collaborators National Archives of Australia State Records Authority of New South Wales Australia Society of Archivists, Committee on Descriptive Standards

4. www.monash.edu.au 4 Create once, use many times How to enable recordkeeping metadata interoperability? Practical Perspectives Overcome barriers to implementation of recordkeeping and resource discovery standards Demonstrate the business case for recordkeeping metadata Research Perspectives Explore role of recordkeeping metadata in support of business and recordkeeping processes Impact on recordkeeping and archiving functions Requirements for meta-tools for recordkeeping metadata management

5. www.monash.edu.au 5 Web Management System Traditional recordkeeping architectures Records Management Application Archival Management Application Subject Portals Community Archives Archival Gateways Business Systems Desktop Applications Email

6. www.monash.edu.au 6 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

7. www.monash.edu.au 7 Metadata broker as middleware (cont.) Records Management Application Archival Management Application Subject Portals Community Archives Web Management Systems Archival Gateways Email and Desktop Applications Metadata Broker Business Information Systems

8. www.monash.edu.au 8 Metadata broker as middleware - outcomes Observations –Standards not as interoperable as assumed –Complexity in recordkeeping metadata re-use –Limitations of current recordkeeping metadata standards Reflections on observations –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

9. www.monash.edu.au 9 Second iteration agenda 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

10. www.monash.edu.au 10 Service oriented architectures Open systemsOpen standards Open communication protocols Service Oriented Architecture StandardsMetadata

11. www.monash.edu.au 11 Web services technologies Consumer UDDI Registry Finds service WSDL Service Descriptions Points to description Service Describes service Locate service Exchange messages - SOAP Source: Based on diagram from http://www.softstar-inc.com /

12. www.monash.edu.au 12 Translation service CRKM Metadata Broker November 2005 Registry Authoritative 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 Repository Machine processable representations of metadata schemas and crosswalks Registry services Crosswalk compilation service

13. www.monash.edu.au 13 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/http://ebxmlrr.sourceforge.net/

14. www.monash.edu.au 14 CRKM Registry Metadata broker as web services cluster ebXML Registry CRKM Broker Schemas Crosswalks

15. www.monash.edu.au 15 UDDI Registry CRKM Registry Implementation Framework CRKM Registry ebXML Registry UDDI Registry WSDL service descriptions MADRAS Registry External links to entries for versions of standards Querying for schema and crosswalk objects

16. www.monash.edu.au 16 Metadata broker as web services cluster Translation Service Web Service Layer Metadata Registry Web Service Layer AGEMS Request to translate AGEMS to RKMSCA AGEMS – RKMSCA Crosswalk Service Web Service Layer Metadata Broker Client Request the AGEMS – RKMSCA crosswalk RKMSCA

17. www.monash.edu.au 17 CRKM Registry Information Model Layer 3 Abstract Layer 2 Representation Conceptual Model Metadata/Data Standard Metadata/Data Standard Metadata/Data Standard Version 1 Encoding 1 Version 2Version n Encoding 2Encoding n Version 1Version 2Version n Registry Objects

18. www.monash.edu.au 18 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

19. www.monash.edu.au 19 Realising sustainable interoperability APIEDIMiddlewareWeb services Service oriented architecture Prototype Conceptualisation

20. www.monash.edu.au 20 Service oriented architectures Recordkeeping Services

21. www.monash.edu.au 21 Recordkeeping services in SOA Metadata Broker

22. www.monash.edu.au 22 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

23. www.monash.edu.au 23 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

24. www.monash.edu.au 24 For more information See the Clever Recordkeeping Metadata Project web site at:- http://www.sims.monash.edu.au/ research/rcrg/research/crm/index.htmlhttp://www.sims.monash.edu.au/ research/rcrg/research/crm/index.html