1 / 13

SeaDataNet

SeaDataNet Harmonizing and optimizing the metadatabases and controlled vocabularies, incl maintenance & retrieval systems. Present metadatabases. Present set-up. ICES. Map. Cross matrix. Print. Map. Print. Data online. XML. Web. Print. Web. Print. Web. Print. Map. Print. Web.

ulla
Download Presentation

SeaDataNet

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. SeaDataNet Harmonizing and optimizing the metadatabases and controlled vocabularies, incl maintenance & retrieval systems

  2. Present metadatabases

  3. Present set-up ICES Map Cross matrix Print Map Print Data online XML Web Print Web Print Web Print Map Print Web Data online Web Web EDMED EDMERP CSR EDIOS ORG CDI BODC MARIS BSH BODC MARIS MARIS Ascii Access XML Access Ascii Online XML Ascii Online Master CMS XML Java Tools Java Tools National collation by NODCs Java Tools Research Institutes, Data Holding Centres, Monitoring agencies, .. All over EUROPE

  4. SeaDataNet objectives • Up to date maintenance of each Directory • More cohesion between Directories and Vocabularies • Provide users with cross searching functionality • Discard redundancy to avoid asking for the same info • Thereby: • Safeguarding backward compatibility to legacy metadata (where required!) • Establishing governance arrangements • Ensuring continuity while developing

  5. Considerations for maintenance • The system must engage all NODCs and for CDI all partners • The volume of entries and frequency of updating of each of the directories differs considerably between each directory and per NODC • The maintenance of each directory is performed by different classes of staff from institutes • The directories make more or less use of vocabularies, which differ for comparable topics • For each directory a central coordinator is required to safeguard momentum and quality

  6. Conclusions for maintenance • the maintenance system must support a number of modalities to cope with all NODCs AND the different metadirectories in practice • one integrated data model is not feasable in practice, but better cohesion between the different formats and schemas (with ISO19115 as basis) • each format has to be reconsidered for optimization, better use of controlled and common vocabularies and EDMO for organisations • for each metadirectory a central master database must be continued under governance of the object manager (next to and linked to local databases, if available)

  7. Proposed Set-up for maintenance • derive a range of controlled vocabularies with technical and content governance • updating and maintenance of the metadirectories by: • online maintenance by NODCs via CMS (incl master editing options) • XML export from local system in a semi-automatic way, with exchange initiated by NODCs at regular intervals • XML export from local system in automatic and continuous proces (harvesting system) • Note: per metadatabase NODCs can have a different choice!

  8. Actions maintenance system • optimize and document each format (tune to use of common controlled vocabularies, ISO19115 schema and GML) • define controlled vocabularies and organize technical and content governance (BODC with committee of BODC, IFREMER, BSH, RIKZ, ..) • each directory coordinator (BODC, BSH, MARIS) modifies its central metadatabase configuration (entry, import and management) to the modified formats, use of controlled vocabularies and support of 3 maintenance modalities. • NODCs choose their preferred modality per metadatabase and adapt to the new configuration

  9. Actions maintenance system • continue the updating of metadatabases with the present set-up • develop the new set-up in parallel, including conversion routine at coordinators (BODC, BSH, MARIS) for conversion from old to new format • switch systems as soon as also the new front-end is ready

  10. Considerations for retrieval & presentation • Each metadatabase coordinator continues to provide an end user interface and develops in parallel an upgraded version for the new format (thereby considering more geographical functionalities (OGC)) • NODCs must have access to the central metadatabases and controlled vocabularies to enable them to develop their own end-user interfaces at local, national, regional and thematic levels • Next to the individual SeaDataNet metadatabase end-user interfaces the SeaDataNet portal must provide a cross searching end-user interface over all metadatabases

  11. Proposed use of Web Services • Install Web Services for the controlled vocabularies (BODC is volunteering) • Install a Web Service for each Directory by BODC, BSH and MARIS to support intermediate users • NODCs use these intermediate Web Services to develop their own local, regional, thematic end user interfaces • SeaDataNet uses these intermediate Web Services to develop its cross searching end user interface at the SeaDataNet portal

  12. End-users End-User Interface SeaDataNet Cross search End user interface CSR Web Service NODCs and institutes End-User Interface EDMED SeaDataNet Web Service End-User Interface Local/ National/ Regional End user interfaces EDMERP Local/ National/ Regional End user interfaces Web Service Local/ National/ Regional End user interfaces Local/ National/ Regional End user interfaces End-User Interface Local/ National/ Regional End user interfaces CDI Web Service End-User Interface EDIOS Web Service End-User Interface EDMO NODCs Web Service Web Service Vocab

  13. Actions for retrieval and presentation • Formulate specifications for the required functionality of the intermediate Web Services • Develop Web Services for Controlled Vocabularies (BODC) • Develop Web Services for each Directory (BODC, BSH, MARIS) in mutual coordination • Formulate specifications for the cross searching SeaDataNet end user interface • Upgrade existing end user interfaces for each directory (BODC, BSH, MARIS) • ….

More Related