roomthily / gstore-elseweb Goto Github PK

Now that the proof of concept is in place, revise the XSLT to handle the MI/MD metadata elements as one set for the entity definitions. And not make assumptions about that final entity object.

Other than running into the limitations of XSLT, what are the limitations on the MI lineages as in could we pack another round or two of the lineage/md-as-source widgets into a file and create "understandable" metadata and functional prov?

This might be a bug in the schema.

If the info is there (i.e. we can easily identify the URL), include any actual URLs as dcat:distribution/dcat:Distribution/dcat:accessURL elements for the Dataset entities.

Uses "Local Geotiff" for the srcused in Publish. Needs to be "Local WGS84 Geotiff" (and change in the as yet to be committed iso example).

The xslts only handle the most basic prov trace - it is a dataset or an activity with no characteristics. But there's no real, valid way to handle the ontologies for the step sources well.

Unless we move to ISO DS records where the granules are the sources of the steps. We would have access to the more complete documentation schema, but it's probably not the best use of DS.

More to the point, one would need to resolve the DS, the granules and potentially any external 19110 or 19119 records to generate the full trace.

Pretty much just what it says on the tin. Except maybe have some default structure?