1 / 21

Implementation of ISO/IEC 11179 in METeOR

Implementation of ISO/IEC 11179 in METeOR. Robyn Kingham Edwards. Overview. Introduce AIHW and METeOR Discuss structures and functionality of METeOR. Including private work spaces, multiple registration authorities and use of XML.

vilina
Download Presentation

Implementation of ISO/IEC 11179 in METeOR

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. Implementation of ISO/IEC 11179 in METeOR Robyn Kingham Edwards

  2. Overview • Introduce AIHW and METeOR • Discuss structures and functionality of METeOR. Including private work spaces, multiple registration authorities and use of XML. • Review the implementation of ISO/IEC 11179 2nd edition in METeOR with a focus on differences and extensions. • Online demonstration of METeOR • Questions

  3. The Australian Institute of Health and Welfare • Better information and statistics for better health and wellbeing. • Data standards underpin the data reported in the 100+ reports produced each year.

  4. An online metadata registry for Health, Community Services and Housing. • An implementation of ISO/IEC 11179 version 2

  5. Features of METeOR • System for creation, review, endorsement, publication and maintenance of metadata • Customised content management system • xml • version control & editing features • role-based views • Hosted online externally

  6. Metadata functions • Discovery and access to metadata an export in XML • Creation of new metadata • Review (quality assurance) • Submission to registration authority • Processing through registration lifecycle • Maintenance and management

  7. Data element Data element concept Value domain Classification scheme Object class Property ISO 11179-based building blocks

  8. Person–height, total centimetres NNN Person–height Total centimetres NNN An example of 11179 in a METeOR data element Person Height

  9. About the database • Customised XML-based content management system • Metadata item requirements are represented as a number of XML components • Not a relational database

  10. Underlying Extensible Mark-up Language (XML)

  11. 1..1 property registry.propertyConcept 1..1 0..* 1..1 0..* objectClass dataElementConcept dataElement registry.objectClassConcept registry.conceptDataElement 0..* registry.valueDomainDataElement 1..1 0..1 0..* valueDomain registry.classificationScheme The functional METeOR model 0..* classificationScheme

  12. Other relationships 0..1 0..1 0..* 0..* stewardOrganisation stewardOrganisation dataElement registry.steward registry.steward 0..* 0..* 0..* 0..* 0..* registry.relatedSeeAlso registry.relatedSupersedes 0..* 0..* registry.relatedFormedFrom metadataitem dataElement2 0..* dataElement3

  13. Developer Visible to developers only Undefined Proposed Visible to developers & registrars only Recorded Registrar Candidate Visible to all users Standardisation pending Standard Retired Superseded Registration Lifecycle

  14. Reg status Sector

  15. Divergence from 11179 • Designed and built with the long-term goal of being a conforming application. • User functional requirements specified a number of significant differences and extensions to the metadata registry model provided by 11179.

  16. Differences • Conceptual domain not implemented but under consideration for future development • Classification scheme implemented differently (as a related metadata item which provides the conceptual basis for some value domains) • Metadata item relationships (more extended than 11179 to accommodate navigation links such as supersession)

  17. Differences cont. • Registration status values needed to match national data committee processes • Some ‘administered items’ not implemented as separate metadata items to ensure simplicity for registration authorities: • Context is an attribute of all metadata items • Representation class is an attribute of value domains

  18. Extensions • Multiple registration authorities (capacity for a metadata item to be registered, optionally, by > 1 Registration Authority) • Data set specifications for grouping metadata items with additional info (sequence number, optionality etc.) • Object class mandatory (as building block for data element concept)

  19. Extensions cont. • Properties mandatory (as building blocks for data element concept) • Glossary needed to define terms which did not form data elements (potential need for glossary documented in 11179 but very significant demand in METeOR)

  20. Questions

More Related