Project

General

Profile

Bug #3528

Add EML 2.1.0 namespace mapping to "qformat.xml" files

Added by ben leinfelder about 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Normal
Category:
metacat
Target version:
Start date:
10/13/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3528

Description

You can add EML 2.1.0 documents to Metacat, but viewing them with a skin only gives you the ASCII tree view.
All the eml*.xsd files are packaged in the war and ready to be referenced, all we need to do is add a mapping to the qformat.xml files in each skin.

the entry should look like:

<doctype publicid="eml://ecoinformatics.org/eml-2.1.0">
<target publicid="-//W3C//HTML//EN">/style/common/eml-2.1.0/eml.xsl</target>
</doctype>

History

#1 Updated by ben leinfelder about 12 years ago

added 2.1 entries for all skins except:
-nceas
-pisco
-sbclter

The NCEAS skin uses a custom style sheet for eml documents, and the sbclter and pisco skins use a stylesheet that is in the /style/shared/...directory rather than style/common.
These will need to be addressed - either they can use the common 2.1 xsl or they will need to have custom xsl files made for them.

#2 Updated by ben leinfelder about 12 years ago

for NCEAS:
-split the "common" templates into nceas-common.xsl. nceas.xsl and nceas-eml-2.1.0.xsl include the nceas-common.xsl and use the templates within it while still importing and calling the appropriate common eml stylesheet for the version being displayed. Both nceas.xsl and nceas-eml-2.1.0.xsl support displaying the fgdc and resultset documents, though they will currently only use the original (2.0.1) nceas.xsl to do that.

#3 Updated by ben leinfelder almost 12 years ago

Sounds like SBCLTER and PISCO skins are on their own in terms of adding EML 2.1.0 support

#4 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 3528

Also available in: Atom PDF