Open pvgenuchten opened 4 years ago
See:
This way to manage the templates implicates that if the custom schema has a template with same match element, will be executed the template from the schema with higher priority for both profiles.
Some alternatives:
1) Define in the template some check of any custom element only defined in the custom schema and with higher priority than the iso19139 template, that should cause that the custom schema uses this template and iso19139 uses it's own template. Example:
<xsl:template mode="csv"
match="gmd:MD_Metadata[count(gmd:contentInfo/gdpr:MD_ContentInfo) > 0]|
*[@gco:isoType='gmd:MD_Metadata' and count(gmd:contentInfo/gdpr:MD_ContentInfo) > 0]"
priority="10">
2) Change the csv generation to use saxon
to call a template with the schema name, instead of using mode
, something similar as done in the metadata editor code:
+1 for opt 2
CSV export seems to always use the tpl.csv from generic iso19139
In 3.0 this behaviour was still fine, and using the xsl from current schema