Generate Metadata from OGC OWS sources

[samperd]

As a metadata manager I want to create "initial" or "stub" metadata records in ISO XML format using OGC Web Services (OWS) as the source for metadata So that I can reference these "stub" metadata records in my OWS (eg WMS Metadata URL) or import them into a catalogue (eg GeoNetwork)

Use case: An organization already has one or more OWS services. Data managers have already created services with minimum metadata. This organization wants to further its data governance maturity by adding a catalogue. Catalogue systems are able to harvest services and create MD (eg Geonetwork), however any edits made to the MD records are overwritten on each harvest. Creating stub records from the service will act as a starting point to import into such catalogues.

[emiliom]

:+1:

[samperd]

A bit more detail by way of sample workflow:

1. Get your data ready
2. Setup your OWS service
3. create a PyGeoMeta MCF referencing a single (or multiple) OWS service
4. Start up Pygeometa pointing to MCF file 4.5 PyGeoMeta makes an OWS call and pulls in "harvests" all avaialble MD from the service.
5. Resulting in one or more MD records (or I guess additional MCF Files) produced for each "layer" within the service
6. MD output in desired schema
7. MD output populated with any service or layer level MD provided in the service
8. the MD is considered a stub because it may not have all fields populated
9. Import stub MD record into a catalogue system
10. Leverage catalogue (or other tool) UI to enter human generated content (eg abstract, contact information, corporate MD)
11. Publish complete MD record

Alternatively the workflow could just generate additional MCF's that can then be converted to specific schemas in a another process (Batch processing?)

[tomkralidis]

Certainly a useful workflow. Given pygeometa is an enabler of workflows, suggest a contrib script to parse an OWS into 1..n MCF files (YAML objects).

[pvgenuchten]

I'm adding a similar workflow to pygeodatacrawler project (and using pygeometa internally).

• starting point is a csv with wms url's
• for each 'portal' (eg wms endpoint) a folder is created
• the crawler then goes through each of the folders to fetch the metadata records (as mcf.yml)
• an export goes through all the folders to create iso19139 for each of the mcf's
• the iso records are loaded on an instance of pycsw