Bug #3855
openCreate an EML Utilities module
0%
Description
For a while, it has been recognized that the EML schema should be developed independently from the xsl stylesheets. For the March release of EML/Metacat/Morpho, the following tag was created for these:
RELEASE_EML_UTILS_1_0_0_RC1
default.css
styles/*xsl
eml201to210.xsl
ascii-treeview.xsl
branding.js
default.js
This tag is probably adequate for Metacat and Morpho
In addition to the xsl stylesheets for displaying html, eml/styles/ includes subdirectories for converting between different versions of EML and between EML and other XML, like nbii and esri. So the structure of Utilities needs to be decided that can hold various material. One possible structure for utilities could be:
eml/utilities
eml/utilities/display
eml/utilities/display/styles
eml/utilities/conversions
eml/utilities/conversions/beta6toeml2
eml/utilities/conversions/eml20toeml210
Updated by Margaret O'Brien over 15 years ago
adding from Mike's email 2009-03-03, per use of /styles/ by metacat, and various skins.
-------
I had to make a few changes to the way the sbclter skin works, mostly because the style/shared/eml-2.0.0/eml.xsl file tries to import files from the skins directories. This worked when we used token replacement, but doesn't work with variables.
I will need to make similar changes to the pisco skin to make that work, so Chris, can you take a look at what I've done for sbclter and let me know if it's okay to make the same changes to pisco?
What I've done:
-- Created a style/shared/eml-2.1.0 directory that is a copy of the eml-2.0.0 directory (needs to be updated for 2.1.0)
-- Created style/skins/sbclter/templates/xsl/sbclter-eml-2.0.0.xsl and sbclter-eml-2.1.0.xsl which do local includes
and header template calls and import the shared eml.xsl files.
-- Pointed /style/skins/sbclter/sbclter.xml to the appropriate sbclter-eml-2.X.X.xsl file
What I propose for the new EML-UTIL module that we will create post release:
-- Rename the /style/shared directory to /style/common-css-layout
-- move the /style/common-css-layout code into the EML-UTIL module in svn (tag 2.0.0 code with old tags)
-- check out the common-css-layout from EML-UTIL at metacat build time (like we do now for common)
-- Rename the /style/common directory in EML-UTIL to /style/common-table-layout
-- If needed, extract any truly shared generic code from /style/common-X-layout directories into a shared directory.
Please let me know what you think.
Mike
Updated by Margaret O'Brien over 13 years ago
Just trying to keep this one on the radar!
I am currently at a DataONE workshop where we are writing descriptions for data management tools. We have an entry for the EML crosswalk stylesheets. In filling it out, I noticed:
1. the LTER has updated the esri2eml stylesheet, and has a link on their IM website.
2. The LTER has a copy of the bdp2eml.xsl in their SVN, (but apparently not the eml2bdp.xsl?)
So it seems that all of these tools could be part of the ERML utilities we talked about a while ago. But they would have to be synchronized first.