1 / 21

Reportnet standards and next steps

Reportnet standards and next steps. Søren Roug, Information and Data Services (IDS). Use of Standards. Historically, Reportnet has been targeted towards the webbrowser. It is a standard called REST You can upload any file to CDR Communication between sites is done with XML-RPC

ursula-moreno
Download Presentation

Reportnet standards and next steps

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. Reportnet standards and next steps Søren Roug, Information and Data Services (IDS)

  2. Use of Standards • Historically, Reportnet has been targeted towards the webbrowser. • It is a standard called REST • You can upload any file to CDR • Communication between sites is done with XML-RPC • Transfer of metadata uses RDF (Semantic Web) • Reportnet does not use • Service Oriented Architecture (SOA) • SOAP • INSPIRE

  3. Introduction of XML(A standard for file formats) • In 2004 Reportnet started to give preferential treatment to XML • One single requirement: • That the XML file has a schema identifier • From this we can: • Run QA scripts using the XQuery language • Convert to other formats using XSL-T • Edit the XML content using XForms standard for webforms

  4. 2008 focus • Integration of national repositories into Reportnet • Guidelines on How to implement a Reportnet/SEIS node • Use of QA service from national node • Use of conversion service from national node • Registration of datasets • Via a manifest file • Via manual registration at website

  5. 2009 focus (next steps) • How to register the datasets • How to search for the datasets • How to track updates to the datasets • How to bookmark found datasets • How to merge datasets • How to trust the dataset • How to trust the trust

  6. Registering a SEIS dataset Discovered via manifest files and manual registration

  7. Adding metadata

  8. Bookmarking and searching the dataset

  9. Working with files vs. records • Now we know where the files are in the SEIS universe • But we can do more: • We can read the content of XML files • Example of an XML snippet: <stations xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:noNamespaceSchemaLocation="http://water.eionet.europa.eu/stations.xsd"> <station> <local_code>32301</local_code> <name>St. Pölten</name> <longitude_decimal>15.63166</longitude_decimal> <latitude_decimal>48.21139</latitude_decimal> <altitude>270</altitude> <station_type_eoi>Industrial</station_type_eoi> <area_type_eoi>urban</area_type_eoi> </station> ... </stations>

  10. Merging principles Station structure as a table Identifier local_code name ... #32301 32301 St. Pölten ... #32302 32302 Linz ... Quadruples Subject Predicate Object Source #32301 type River Station austria.xml #32301 local_code 32301 austria.xml #32301 name St. Pölten austria.xml #32302 type River Station austria.xml #32302 local_code 32302 austria.xml #32302 name Linz austria.xml

  11. Merging the datasets Austria Stations .xml Belgium Stations .xml Germany Stations .xml XSL Transformation to quadruples Aggregation Database

  12. Merging the datasets (with later updates) Austria Stations .xml Austria update1 .xml XSL Transformation Aggregation Database

  13. Searching • To find all river stations in Europe you search for subjects with the type=”River Station” • The query will format it as a table for you • Obviously you get duplicates because 32301 has been updated

  14. QA work • Let’s first colour the cells by their source

  15. QA work • Then we merge by letting the newer sources overwrite the older:

  16. QA work • Don’t trust one source? • Turn it off before you merge

  17. QA work • Then we merge

  18. QA work • Gapfilling? • Add your own source as a layer • The layer is stored on QAW Hermann’s gapfilling layer created 2008-11-27

  19. QA work • Then we merge • And we export to our working database for production...

  20. Trusting the dataset and trusting trust • Datasets and values can be evaluated by looking at the source • Is the source URL from a reliable organisation/person? • Is the methodology described? • Are there reviews on QAW? • Who wrote the reviews? • Are there others who have used the data? • Who are they?

  21. Summary These new tools intend to solve the use of the Reportnet deliveries: • Aggregation/Merging • Manual QA and gap-filling • Traceability to the sources • Noticing when the source has been updated/deleted • Review of the source for inclusion • That was no problem before because only authorised parties could upload to CDR • With SEIS anyone can participate

More Related