1 / 14

AIHW Knowledgebase Redevelopment project

AIHW Knowledgebase Redevelopment project. Trish Ryan Head, National Data Development Unit Australian Institute of Health and Welfare 02 6244 1054 trish.ryan@aihw.gov.au Nigel Mercer Consultant 0412 063 024 nigel@littleoak.com.au. Metadata registry.

quinn-hicks
Download Presentation

AIHW Knowledgebase Redevelopment project

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. AIHW Knowledgebase Redevelopment project Trish Ryan • Head, National Data Development UnitAustralian Institute of Health and Welfare • 02 6244 1054 • trish.ryan@aihw.gov.au Nigel Mercer • Consultant • 0412 063 024 • nigel@littleoak.com.au

  2. Metadata registry • Australian Health, Community Services and Housing metadata registry • ‘The Knowledgebase’ – developed 1997 • Implementation using 11179 • www.aihw.gov.au • Look for ‘Knowledgebase’

  3. Project status • Redevelopment project begun March 2003 • Scope and issues paper prepared • Stakeholder and user consultation process • Two main outcomes / opportunities • Considerable upgrade to website, including significant help and assistance for metadata users and developers • Metadata redevelopment, including incorporation of new version of ISO/IEC 11179

  4. Functional requirements for website • Identification of types of users • Support for: • Metadata users • Metadata developers • Metadata registrar (maintainers) • Metadata approvers

  5. Functional requirements for website • Education and guides for users and developers • About metadata • How to access and download metadata • How to develop and obtain approval/endorsement • ‘Good’ metadata examples

  6. Additional requirements • Record users (optional) • Support users recording their interest in individual metadata items • Direct links (urls) to metadata items • Can store ‘rich’ text e.g. formatting, tables, diagrams etc.

  7. Additional requirements • Track changes for candidate items i.e. how is this version different from the current one? • Publish different dictionaries and reports from the metadata content (ability to specify templates for extraction and formatting)

  8. Metadata item Metadata item candidate Metadata item update history Metadata user Record interest in metadata item Interest in metadata item Maintain metadata items Registrar KB user interface Extract for publications www user Create metadataUpload candidates Software tool Metadata developer Main KB functions

  9. Opportunity for metadata redevelopment • Realisation of benefits obtainable from considerable metadata reorganisation • Include metadata structures from new 11179 • Expected to address a number of issues facing national data development committees

  10. Current status • Considering metadata structures (architecture) • Assessing workload and process to redevelop metadata content • Building examples to show national data committees impact of proposed structures

  11. Registration status Metadata set Object class Property Value domain Data Element Concept Data Element Classification system

  12. Project timetable • February 2004 - Sign-off on new structures • Includes agreement on redevelopment process • February-June - Develop protocol (business rules) for metadata registry • March-September - Redevelop content • August-November - Develop software

  13. Current issues • Object classes and properties • Classification systems for • Existing ontologies • Number of moving parts • Versioning of all metadata item types • XML integration • Existing content redevelopment process

More Related