A Metadata System for Geomagnetism

Slides:



Advertisements
Similar presentations
IATI Technical Advisory Group Technical Proposals Simon Parrish IATI Technical Advisory Group, DIPR March 2010.
Advertisements

IRRA DSpace April 2006 Claire Knowles University of Edinburgh.
Business Development Suit Presented by Thomas Mathews.
With Folder HelpDesk for Outlook, support centres and other helpdesks can work efficiently with support cases inside Microsoft Outlook. The support tickets.
MEDIN Standards M. Charlesworth and the MEDIN Standards Working Group.
Introduction to Databases
Meta-Door 2.0 An online management tool for FGDC-compliant metadata, MarineXml, and SensorML.
Cornell University Library Instruction Statistics Reporting System Members: Patrick Chen (pyc7) Soo-Yung Cho (sc444) Gregg Herlacher (gah24) Wilson Muyenzi.
Progress Report 11/1/01 Matt Bridges. Overview Data collection and analysis tool for web site traffic Lets website administrators know who is on their.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
SWIS Digital Inspections Project (SWIS DIP) Chris Allen, Information Management Branch California Integrated Waste Management Board November 5, 2008 The.
MySQL + PHP.  Introduction Before you actually start building your database scripts, you must have a database to place information into and read it from.
Controlled Vocabularies (Term Lists). Controlled Vocabs Literally - A list of terms to choose from Aim is to promote the use of common vocabularies so.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Design central EMODnet portal Objectives, Technical Proposal and Consultation Process.
Options for Managing CARMA Databases Prepared by David Taylor Taylor Geomatics.
IS 325 Notes for Wednesday August 28, Data is the Core of the Enterprise.
Tweets Metadata May 4, 2015 CS Multimedia, Hypertext and Information Access Department of Computer Science Virginia Polytechnic Institute and State.
Comparison of CEN, FGDC and ISO standards for metadata Ing. Jan Ruzicka Institute of Economics and Control Systems VŠB – Technical university Ostrava 17.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
1 Meta-Door 2.0 An online management tool for FGDC-compliant metadata, MarineXml metadata, and SensorML.
Developing our Metadata: Technical Considerations & Approach Ray Plante NIST 4/14/16 NMI Registry Workshop BIPM, Paris 1 …don’t worry ;-) or How we concentrate.
Database Principles: Fundamentals of Design, Implementation, and Management Chapter 1 The Database Approach.
Code Simplicity: Software Design In Open Source Projects Max Kanat-Alexander
Online Submission and Management Information -- Authors
Advanced Higher Computing Science
MIKADO – Generation of ISO – SeaDataNet metadata files
VAdata Tools VAdata: Virginia’s Sexual and Domestic Violence Data Collection System.
Database and Cloud Security
The STEM Academy Data Solution
Getting Started on The Project Bank in Visual Studio
StudentTranscripts Service Overview
Programming Assignment #1
Software Documentation
Multi Rater Feedback Surveys FAQs for Participants
Multi Rater Feedback Surveys FAQs for Participants
StudentTranscripts Service Overview
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
StudentTranscripts Service Overview
Smoke and Mirrors Prototype
The Top 10 Reasons Why Federated Can’t Succeed
StudentTranscripts Service Overview
SDMX FROM NEEDS Kamel ABDELLAOUI Rafik Mahjoubi
MIKADO: Generation of CDI ISO19139 XML files
File Systems and Databases
Vanessa Tosello (IFREMER), Flavian Gheorghe (MARIS)
SDMX: A brief introduction
CLIENT RELATIONSHIP MANAGEMENT KEEPING TRACK OF REQUESTS THE EASY WAY
StudentTranscripts Service Overview
Chapter 13 Quality Management
Design central EMODnet portal Objectives and Technical description Initial draft prepared by the Flanders Marine Institute.
Data Model.
Student Introduction to CORE ELMS
StudentTranscripts Service Overview
Smoke and Mirrors Prototype
(acknowledgements to Mary Mowat, BGS)
WP 4 - Revision of Natura 2000 dataflow
StudentTranscripts Service Overview
ZTE Customer Request Self-Service Portal Operation Guide V1.0.5
MSDI training courses feedback MSDIWG10 March 2019 Busan
Open access in REF – Planning Workshop
What is an Internal Audit
Programming Assignment #1
Implementing DDI in a Survey Organisation
A metadata system for the global observatory community
Reportnet 3.0 Database Feasibility Study – Approach
Reporting your goals Sunday, July 21, 2019
My name is VL, I work at the EEA, on EA, and particularly on developing a platform of exchange which aims at facilitating the planning and development.
Information Retrieval
Contract Management Software 100% Cloud-Based ContraxAware provides you with a deep set of easy to use contract management features.
Presentation transcript:

A Metadata System for Geomagnetism Simon Flower Jürgen Matzka This work is being funded through EPOS – this is why it’s being presented at an EPOS meeting However the scope of the work covers the global geomagnetism community This work, now funded by EPOS, is the continuation of work in INTERMAGNET between BGS and GFZ over the past 2-3 years

Geomagnetic Observatory Metadata: What we record 180 active, 360 inactive observatories 200 contacts in 125 institutions Many instruments creating thousands of data sets Institutes Instruments People Data These figures are from the World Data Centre metadata database The data that we need to collect is sufficiently large and complex to need a data management tool, which we don’t have at the moment INTERMAGNET figures: 61 institutes, 132 active observatories, 17 former observatories Locations

Geomagnetic Observatory Metadata: How we record it World Data Centre: INTERMAGNET: World Data Centre – metadata is held in an Access databasend updated manually when contacts email us changes The Access database is well designed, but difficult to make accessible: It’s hard to add code that will allow the data to be distributed by web service It’s hard to design a system that will allow observatory operators to input metadata themselves INTERMAGNET – metadata for the annual DVD is compiled annually from text files metadata for the web site is in XML files which are updated when contacts email us Held in disparate ways: XML files on web site, unstructured text on DVD There are almost certainly other places where geomagnetic metadata is collected – metadata which could be merged into a central metadata system, provided it is suitably designed There’s a lot of manual work to get what we need. There are a lot of bits of metadata in different places, sometimes with conflicting contents Very little is easily accessible, particularly for use by computer ? Other bodies:

Geomagnetic Observatory Metadata: Problems with the current arrangements Difficult for data providers to update Data held in several unconnected systems -Inconsistent Difficult to use with computer programs -Unstructured Difficult to query – much of it not available publically

Geomagnetic Observatory Metadata: Design goals A single database for the whole community Easy for data providers to understand and update Easy for users to query and obtain data Contains information needed for the INTERMAGNET website, INTERMAGNET data DVD, World Data Centre web site (amongst others) Ideal: Be able to create a yearbook Conform to metadata standards (such as ISO 19115) to allow our data to be understood by users outside our community I think that the ‘gold standard’ for a geomagnetic metadata system is that we would have enough information to allow us to create the digital equivalent of a yearbook from the metadata for any of the digital data sets that we are collecting. We won’t get to this level with the first version of the system, but the idea of being able to recreate a yearbook from the metadata should continue to be an aspiration. ISO 19115 is a standard for geographic metadata. INSPIRE is a related standard that is mandatory in Europe We need to ensure both these things

Geomagnetic Observatory Metadata: Implementation Self service data entry Web services Tools to create DVD metadata Other clients Feed to INTERMAGNET web site Geomagnetic metadata database An easy to use data entry service will be provided. This will allow data providers to update entries for their own institutes and observatories Feeds will be provided to satisfy the specific requirements of a number of clients (INTERMAGNET and EPOS shown in the diagram – others expected to follow). The basic design will be flexible, allowing new clients to be added as needed. Tools will be available to allow the operators of the database to enter and delete data. The system will initially be implemented at the British Geological Survey. It will be designed to be flexible in it’s implementation, so that it could be moved to another institute, if required. Tools for database administration Feed to EPOS data portal

Geomagnetic Observatory Metadata: Implementation: The schema Designed to capture these things about an observatory: What institute or institutes does it belong to and is it supported by What is it’s location Who are the contacts for the observatory What instruments are / have been in operation at the observatory What data sets has the observatory produced Is the observatory a member of INTERMAGNET All these attributes may vary over time – the metadata allows for this This is a subset of the information held in the schema – for a more detailed description, contact me

Geomagnetic Observatory Metadata: Status First version of metadata schema designed and available to you (on request) to comment on Work progressing to ensure compliance with international metadata standards An easy to use data entry service will be provided. This will allow data providers to update entries for their own institutes and observatories Feeds will be provided to satisfy the specific requirements of a number of clients (INTERMAGNET and EPOS shown in the diagram – others expected to follow). The basic design will be flexible, allowing new clients to be added as needed. Tools will be available to allow the operators of the database to enter and delete data. The system will initially be implemented at the British Geological Survey. It will be designed to be flexible in it’s implementation, so that it could be moved to another institute, if required.

For more information, including details of the metadata schema Simon Flower: smf@bgs.ac.uk To be a success, this metadata system needs to be taken up by the community. Please help the design by requesting and commenting on the draft schema.