An Introduction to the MEDIN Discovery Metadata Standard October 2016 NOC Liverpool An Introduction to the MEDIN Discovery Metadata Standard Good morning. This presentation will give you introduction to the ‘MEDIN metadata standard’

What is metadata & what should I do with it? October 2016 NOC Liverpool What is metadata & what should I do with it? Essentially, metadata is: Information about a dataset Discovery Metadata is: Information used to describe datasets (or series or services) so that a user can easily find them using a portal and determine the details of where they can be accessed A documented record of datasets managed within an organisation or an application Discovery Metadata contains: What I' ‘Metadata’ is data about data. Metadata tells you about the dataset so that you know what that dataset is about without actually having to delve into the dataset and work it out yourself. This makes searching for data a lot easier. It is called ‘discovery metadata’ because you can search for datasets by searching for their metadata. This makes it easily discoverable to someone outside your organisation. Once you have discovered the metadata, you can either decide not to go any further (if you have found out about it and decided it is not the right dataset you are looking for) or you can decide to seek out the data. This you can do through the MEDIN portal either by downloading the data directly through the portal or by contacting the data provider/ originator (if such restrictions to downloading the data freely apply). Title Abstract Temporal coverage Geographic coverage Ownership of record Access conditions Location of dataset (amongst others)

What is a dataset? October 2016 NOC Liverpool The correct level for a dataset is a cruise, survey or a set of repeat observations with a common purpose   A dataset usually constitutes a specifically-funded piece of work The dataset should be easily extractable from a database for a 3rd party (Best Practice) Searchable using an online interface e.g. MEDIN portal (Best Practice)

Discovery Metadata Standard October 2016 NOC Liverpool MEDIN have developed a Discovery Metadata Standard to enable online discovery of datasets 3 components make up the Standard Defined metadata content, specified as elements and detailed in a guidance document Software tools (online and offline) to create metadata records A validation language (schematron) to check the records created using the software tools XML is the ‘language’ used to encode the record so that it becomes machine readable. The MEDIN standard which makes up a metadata record is composed of parts called elements. These make up the metadata record and together give you a ‘picture’ of what the data is comprised of. XML stands for Extensible Markup Language. This is used to encode the metadata record so that it is computer readable. MEDIN has guidance documents to help you through creating metadata records, a validation tool to make sure that you have all the right information in your record so that it complies with the standard, and tools which create and also validate/test your records so that it adheres to the standards.

Discovery Metadata Standard - Guidance October 2016 NOC Liverpool Available on website Compliant with: ISO19115 (Geographic information – Metadata) INSPIRE UK GEMINI2 ISO 19139 schema set for encoding xml This is a part of the guidance document which helps you to comply with the geographic information, INSPIRE and UK GEMINI. This uses the ISO19139 schema set to which xml can be written. There is also a short simple version available which avoids the need to understand xml INSPIRE is the EU standard for geographic-based data which requires metadata to be discoverable and comparable across the EU. GEMINI2 is the UK version of the standard of which MEDIN is tasked to look after the marine side of the standard and which meets all current requirements up to the EU level. We use the ISO coding to ensure compliance with EU and UK legislation. There are 2 levels of checks (schema and the schematron) which test the structure and content of the xml. The schema is the basic global test which asks yes/no questions and which is case and order sensitive. This requires exact answers. The schematron is written by MEDIN and includes additional questions that are medin specific, e.g. If one question is answers, are the conditional questions that are linked also answered. These are some screenshots of the metadata standard. Example of the contents, element and subelement example and example of that element within the xml. Of course there is also the simpler version. However, there is a shorter, simpler version available!

Discovery Metadata Standard - Introduction October 2016 NOC Liverpool http://www.oceannet.org/submit_metadata/creating.html http://www.oceannet.org/marine_data_standards/medin_disc_stnd.html This screenshot shows the MEDIN website page which tells you which methods/tools you can use to create metadata. There are two main ones, these are the online tool and the Metadata Maestro. To the right, in the quick links box, there is a 99 page detailed document (code for more technical people) and 15 page simplified guidance notes on the main page.

Tools On-line metadata generation and editing tool October 2016 NOC Liverpool On-line metadata generation and editing tool 2. Desktop tool Metadata Maestro. Can work in stand alone mode. Now I will go through the types of tools that you can use to create validator. The first one is the most simple to use to create metadata through a form-based tool. This is the easiest beginner level tool and does quite a lot of background work that you dont need to worry about. The second is the desktop tool – the metadata Maestro tool. This tool enables you to create xml directly using a template. It is standalone and so therefore can be used offline.. This tool is more versatile but requires the user to be more familiar with xml. It is useful for when working with larger quantities of metadata

Other tools October 2016 NOC Liverpool Also a tool which assists in transforming already populated metadata databases into MEDIN format XML metadata. Designed so that organisations who hold their own metadata can transfer their data into this structure from which a tool can be applied to produce xml records 4. Specific tools for GIS users: Stylesheets for transforming ArcCat ESRI ISO standard metadata to MEDIN standard. Arc 9 stylesheet no longer supported. Arc 10 stylesheets now available (This to be explained in detail later) The third option is for tailor made systems if your organisation already has its own metadata database and pulls al the information into the correct part of the xml. We wont cover this today so contact medin helpdesk.... The last option is for creating metadata using ArcGIS. MEDIN have downloadable stylesheets to generate metadata as you create datasets. Medin helpdesk on hand

Validation October 2016 NOC Liverpool ► Testing the structure and content of the xml records to ensure that they comply with the standard Schematron (compliant with ISO 19757 (Part 3) Information technology -- Document Schema Definition Languages (DSDL) -- Part 3: Rule-based validation – Schematron). ►Used in many different circumstances and tools so that if the standard changes it only requires one update rather than various validation methods for different applications The schematron ‘sits’ in the metadata editor tools in a validation step. Can be used by organisations to test transfer between metadata holdings We have to validate our structure to comply with the standards. This ensure the correct order, language and contact, conditional elements are entered. This also makes sure that the xml reflects changes made to the standard

The Schematron Technical guidance document on the schematron October 2016 NOC Liverpool Technical guidance document on the schematron This screenshot is the page on the MEDIN website that gives you more guidance on the schematron should you require to look into this further or if your org wants to create a schematron in your own tool.. MEDIN has developed the software to translate metadata databases into MEDIN formatted XML for inclusion on the MEDIN portal. This tool can only be applied to an existing relational database (such as in Oracle). Contact enquiries@oceannet.org for further details. Gives you a link to the xslt file that the schematron is written in plus the guidance doc

Summary of dataset discovery October 2016 NOC Liverpool Important that the portal is not inundated with records or not rich enough to be useful to the user All metadata records can be harvested (and produced primarily for) by the portal. MEDIN guidance on website plus FAQs: Once the records are exported to the MEDIN portal, they are ready to be searched using the discovery tool. There are frequently asked questions on the portal (bottom right hand side). This screenshot is of one of the FAQs – what is a dataset

Updating the MEDIN discovery standard October 2016 NOC Liverpool Standards evolve! Therefore: MEDIN has placed itself to be engaged in and contribute to any changes in national and international standards that could influence our own Members of the MEDIN standards Working Group also are represented on various groups such as the UK Location Programme, INSPIRE and BSI groups Sign up to the e-mail list to be kept up-to-date on changes UK gemini and inspire are fairly stable now. Relevant changes are made as necessary, but Most often they are just to to relax elements, i.e. Mandatory to conditional.... i.e. Publication date. rather than restrict.. British Standards Institution If interested in changes you can sign up to the email on the portal

‘Conformity / Specification’ October 2016 NOC Liverpool Element 25 – Conformity Used to specify if the dataset being described conforms to specified guides for data collection/re-use Covers INSPIRE data specifications (http://inspire.ec.europa.eu/document-tags/data-specifications) EU Guidelines drawn up with aim of aiding interoperability of spatial datasets and services. Legal requirement for public bodies to be INSPIRE compliant Covers whether dataset has usage metadata as defined by MEDIN Data Guidelines

‘Conformity / Specification’ October 2016 NOC Liverpool How to populate Conformity? Three sub-elements: Specification. Detail the name of the guide that the dataset conforms to e.g. MEDIN Data Guideline X and the document date Degree of conformity. A binary response of true or false indicating whether the data conform to the specified guide or not. Explanation. A free text field allowing the metadata creator to explain why the dataset is/is not conformant.

MEDIN discovery metadata in action October 2016 NOC Liverpool Log onto the MEDIN portal www.oceannet.org Look at the ‘quick links’ on the right hand side. Have a short play with the Data Discovery Portal to see how the discovery metadata gets used. Practical to follow!

MEDIN Metadata Editor Practical October 2016 NOC Liverpool Open Internet Browser (Chrome or Firefox) www.dassh.ac.uk/medin_metadata Log-in: Username: medin.metadata@mba.ac.uka Password: medinmetadata