EML: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362006-12-06T21:58:17ZEcoinformatics Redmine
Redmine Bug #2688 (New): embedded text format ignored by Metacathttps://projects.ecoinformatics.org/ecoinfo/issues/26882006-12-06T21:58:17ZInigo Gilisangil@lternet.edu
<p>When metacat displays metadata documents, the original format is often lost. Newlines, new paragraphs, bullets and the like are largely ignored by the metacat stylesheets, and all spaced is lumped together, creating undesired results.</p>
<p>A number of solutions are being considered and some are deployed in the development metacat at the LTER network office.</p>
<p>A broad approach would be to prepend an html <pre> tag wherever the user has specified within EML that the content should be treated as <literalLayout>.
Another broad approach is to plant <pre> tags in critical sections such as methodology descriptions (I.e: eml/dataset/methods/description/) or in inline data.
Other workarounds are to explore trimming white space in targeted locations (at beginning and end, not everywhere). There are a handful of different XSL treatments of whitespace, carriage returns, line feeds and new line characters discussed at http://www.dpawson.co.uk/xsl/sect2/N8321.html</p></pre> Bug #2212 (New): Several bug fixes for the eml2nbii.xsl stylesheet (transforming EML metadata to ...https://projects.ecoinformatics.org/ecoinfo/issues/22122005-09-30T15:42:26ZInigo Gilisangil@lternet.edu
<p>TARGET: EML 2.1.0</p>
<p>Several bug fixes improved the stylesheet eml2nbii.xsl. This stylesheet converts<br /> EML documents into the federal standard format BDP.</p>
<p>The stylesheet was delivered to eml-dev, and resides in the LNO CVS.</p>
<p>Here is a log of the changes/fixes</p>
*
<ul>
<li> There are about 50 issues (some critical metadata loss) solved in this<br />revision. Mostly are </li>
<li> metadata sections that were not completely mapped from the EML to the BDP<br />standard.</li>
<li> </li>
<li> Additionally, there are a few other improvements in the mapping. </li>
<li> This revision, 3000+ lines, previous 1600.
*
<ul>
<li>Itemized list of changes. NOTE, line numbers refer to the previous version<br />(revision 1.21) of "eml2nbii.xsl"
*</li>
</ul>
</li>
<li>line 51: Make all possible metadata transformations, that is, set the<br />variable $show_optional to true (1)</li>
<li>line 141: Loop over all entities in EML; Previosuly, only dataTable,<br />spatialRaster and spatialVector considered. "view", "storedProcedure" and<br />"otherEntity" added. </li>
<li> hard coded content values changed to english (dataTable to<br />tabular digital data, etc)</li>
<li>line 148: BDP "Sername" (series) contents not mapped. Added EML"series" <br />content, if populated in the EML instance.</li>
<li>line 158: BDP "pubPlace" contents not mapped. Added EML "pubPlace" content<br />when used.</li>
<li>line 161: BDP "publish" contents not mapped. Added EML "publisher" individual<br />and org. name when used.</li>
<li>line 172: BDP "onlink" contents not mapped. Added EML<br />"distribution/online/url" when used.</li>
<li>line 178: Odd hard coded value removed. It is possible that the author meant<br />some action. </li>
<li>line 196: BDP "purpose" contents not mapped. Added EML "purpose" </li>
<li>line 200: BDP "supplinf" contents not mapped. Added EML "additionalInfo" </li>
<li>line 243: Handling multiple single data time elements addressed (for each..),<br />gelogical Scale / Alternatetimescale, etc. About 300+ lines of code replace<br />about 120 of them</li>
<li>line 333: Currentness element hard coded to "as it was when data was compiled" <br />added</li>
<li>line 330: Comment change</li>
<li>line 335: Added all possible EML maintenance contents to map into BDP's update<br />field. Also, there was a bug in the conditional statement.</li>
<li>line 367: Added bounding altitudes mapping to the geographic coverage mapping<br />(Not considered before) </li>
<li>line 369: Added the G-poligon mapping.</li>
<li>line 539: Added taxonomic keywords, previously forced to NONE.</li>
<li>line 562: Added the case of optional classification system elements and other<br />taxonomic-related metadata groups (230 lines of code)</li>
<li>line 607, 620: Access element code group duplicated for use and access<br />constraints elements in BDP. Not quite accurate granularity. Removed duplicate code</li>
<li>line 607: Access element incomplete, the EML intellectual Rights section is<br />relevant here. Add code.</li>
<li>line 633: Added EML contact info. Need handle refs.</li>
<li>line 641: Added in "datacred" (credit) info from EML "associated parties" and<br />"funding" agency.</li>
<li>line 663: Addition of metadata: Attemting to use section 2 of BDP: Data<br />Quality Info. Some sections from EML methods can be used here. quite a bit of<br />code added</li>
<li>sections 3 and 4 of BDP skipped for now.</li>
<li>line 791: Misleading/Obsolete comments refined. </li>
<li>line 792: Include all EML dataset entities; add storedProcedure, view and<br />otherEntity types. </li>
<li>line 794: Not sure about the loop logic. Need testing.</li>
<li>line 886: Textdomain from attribute type nominal or ordinal mapped correctly<br />as is to "unrepresentable domain" </li>
<li>line 911: Unit type added to BDPs "range domain" from EML's attributes of type<br />interval or ratio.</li>
<li>line 915: EMLs date time attribute type mapped correctly to unrepresentable<br />domain.</li>
<li>line 921: THIS MAY NEED A CHANGE. accuracy missing. It is not exactly the<br />precision, but if EMLs attr. precision exists, it is mapped to BDPs attr.<br />accuracy for the sake of preserving metadata.</li>
<li>line 931: This conditional is out of place: there is no need of a EML physical<br />element to populate this element. All you need is a "publisher" or a "contact".<br />An distribution/online element helps.</li>
<li>line 936: Distribution element. The distributor should be the publisher. If<br />the publisher is not specified, it could default to the contact. Options included</li>
<li>line 960: Contact org mapped.</li>
<li>line 972: Contact person mapped</li>
<li>line 984: Contact person mapped</li>
<li>line 1058: Phone mapped better</li>
<li>line 1072: Fax mapped</li>
<li>line 1078: Email mapped</li>
<li>line 1102: In the previous version, the BDP element distribution info is only<br />mapped if the EML physical element is populated. We consider the case where the<br />EML "distribution" exists,</li>
<li> this opens a new case (lots of code)</li>
<li>line 1122: Sometimes the "data format " <del>geoform</del> is placed depending on the<br />entity we have in EML (data table, spatial vector, etc)</li>
<li>line 1257: Clarification added to the hard coded text.</li>
<li>line 1338: In practice, both metadata and data have the same publication date<br />(pubDate), therefore pubdate of EML data mapped to pub date of BDP metadata</li>
<li>line 1351: Try to map the metadataprovider as the metadta creator, otherwise<br />(metadata provider not present in EML) default to the EML contact</li>
<li>line 1386: add contact organization or contact person name even though we<br />placed already one or the other.</li>
<li>line 1475: map better the phone</li>
<li>line 1490: map the fax</li>
<li>line 1495: most importantly, map the email.
*</li>
</ul>