EML: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-11-28T07:49:12ZEcoinformatics Redmine
Redmine Bug #5751 (New): EML stylesheet problem for i18n texthttps://projects.ecoinformatics.org/ecoinfo/issues/57512012-11-28T07:49:12ZMAITA Eiichimaita.eiichi@nies.go.jp
<p>eml-resource.xsl:284<br /> <xsl:value-of select="$i18nElement/."/><br />is wrong because this command extracts not only<br />the primary language text but also the additional<br />translation text.</p>
<p>For extracting only the primary language text,<br />the command should be modified as the following line:<br /> <xsl:value-of select="$i18nElement/text()"/></p> Bug #5615 (New): Examine HTML skins for EMLhttps://projects.ecoinformatics.org/ecoinfo/issues/56152012-06-05T18:43:45ZMargaret O'Brienmob@msi.ucsb.edu
<p>examine EML default HTML-skins to make sure that they reflect good EML practice, and that labels and layout are intuitive to non-developers. This is especially important so that EML will reflect positively on applications which present it, like Metacat.</p> Bug #5255 (New): missing template for method/methodStep/software/implementation/distribution/inlinehttps://projects.ecoinformatics.org/ecoinfo/issues/52552010-12-13T23:15:46Zgastil gastilmarygastil@yahoo.com
<p>See <br /><a class="external" href="http://dev.nceas.ucsb.edu/knb/metacat?action=read&qformat=lter&docid=gastil_test.1.1">http://dev.nceas.ucsb.edu/knb/metacat?action=read&qformat=lter&docid=gastil_test.1.1</a><br />and<br /><a class="external" href="http://dev.nceas.ucsb.edu/knb/metacat?action=read&qformat=lter&docid=gastil_test.1.2">http://dev.nceas.ucsb.edu/knb/metacat?action=read&qformat=lter&docid=gastil_test.1.2</a></p>
<p>Example EML doc knb-lter-vcr.89.5 has a SAS script included in the EML. John has it under <br />eml/dataset/additionalInfo/section/section/para/literalLayout</p>
<p>That appears in the metacat skin, although the display does not respect the literalLayout. (does not display like <pre>). That is not today's bug.
Looking at the eml spec, it seemed a more appropriate place to put code would be using the eml software tag. gastil_test.1.1 is in the dev metacat as an example. This is valid EML (according to oXygen) yet this does not properly display in the (dev) metacat skin. I put the SAS code under
method/methodStep/software/implementation/distribution/inline/CDATA
I tried that method section at the whole-dataset level gastil_test.1.1
and at the entity level gastil_test.1.2
The xslt template does not seem to handle either of these. Click on the "Inline Data" link and get this error:
<error>
the requested docid '' does not exist
</error></p></pre> Bug #4683 (New): The knb xslt stylesheet display is squished over to the lefthttps://projects.ecoinformatics.org/ecoinfo/issues/46832010-01-21T01:15:15ZMargaret O'Brienmob@msi.ucsb.edu
<p>For a long time we have noticed that for some EML datasets, the HTML rendered by the knb or lter XSLT stylesheets (from metacat) is squashed over to the left side. It appears to be something about the column-width. Just now we found 2 consecutive revisions of a dataset where the earlier one does not squish, but the second one does. Those ids are:<br />knb-lter-mcr.9.4 (not squished)<br />knb-lter-mcr.9.5 (squished)<br />the difference between the 2 EML docs might help identify the XSLT problem. Both are EML2.1. The main difference between the 2 files is that the second one includes a methods tree. There might be a bug for this already -- if so sorry, I had no luck finding one.</p> Bug #4265 (New): texttype stylesheet does not correctly handle mixed contenthttps://projects.ecoinformatics.org/ecoinfo/issues/42652009-07-27T18:11:37ZMargaret O'Brienmob@msi.ucsb.edu
<p>Mixed content is allowed in paragraphs. But the stylesheet does not correctly display content like this (from knb-lter-mcr.8.6)<br /><para><br />The abundance of taxa are estimated to the following levels: <br /> <itemizedlist><br /> <listitem><br /> <para>Corals: Order;</para><br /> </listitem><br /> <listitem><br /> <para>Macroalgae: Genus, sometimes Species;</para><br /> </listitem><br /> <listitem><br /> <para>Algal Turfs: Functional Group of many Species;</para><br /> </listitem><br /></itemizedlist><br /></para></p> Bug #4117 (New): squished rendering of some EML datasetshttps://projects.ecoinformatics.org/ecoinfo/issues/41172009-05-28T20:03:50ZJing Taotao@nceas.ucsb.edu
<p>Margaret reported this issue:</p>
<p>Hi Duane and Jing -<br />I'm working with MCR to update a couple of their datasets. I noticed that this eml doc has a problem with the lter and knb skins where all the content if<br />shoved over to the left in a narrow column. It is slightly wider in MSIE than in Firefox.</p>
<p><a class="external" href="http://metacat.lternet.edu/knb/metacat?action=read&qformat=lter&docid=knb-lter-mcr.10">http://metacat.lternet.edu/knb/metacat?action=read&qformat=lter&docid=knb-lter-mcr.10</a><br /><a class="external" href="http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=default&docid=knb-lter-mcr.10">http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=default&docid=knb-lter-mcr.10</a> <br />This also happens to some SBC datasets, but not all -- for example, knb-lter-mcr.1 renders just fine. I'm pretty sure I've seen this in docs from other lter<br />sites as well, but I dont seem to be able to drum up any at the moment (i.e., by randomly choosing docids...)</p>
<p>Can you tell me what is going on?<br />thanks -<br />Margaret</p> Bug #3754 (New): Provide metadata docid along with data docid in download URLhttps://projects.ecoinformatics.org/ecoinfo/issues/37542009-01-17T00:48:20ZShaun Walbridgewalbridge@nceas.ucsb.edu
<p>Until Metadata has a column connecting documents to metadata documents, we should provide the metadata docid using the stylesheets. It's a straightforward change to the link, and allows us to meet all the requirements laid out in [1].</p>
<p>1. <a class="external" href="http://help.nceas.ucsb.edu/Informatics_tools_deployment#sensible_names">http://help.nceas.ucsb.edu/Informatics_tools_deployment#sensible_names</a></p> Bug #3508 (New): create a stylesheet for EML2.0.x to EML 2.1.0https://projects.ecoinformatics.org/ecoinfo/issues/35082008-10-06T23:33:43ZMargaret O'Brienmob@msi.ucsb.edu
<p>there are 4 changes in EML 2.1.0 which need to be addressed in a transformation stylesheet. Summarized:<br />1. datetime -> dateTime (bug <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: datetime element does not use consistent naming (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1152">#1152</a>)<br />2. new additionalMetadata/metadata element (bug <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: use of <any> in additionalMetadata is invalid (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/2054">#2054</a>)<br />3. method -> methods (bug <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: Inconsistent naming of "method"(s) element (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/2568">#2568</a>)<br />4. access trees moved (bug <a class="issue tracker-1 status-3 priority-5 priority-highest closed" title="Bug: fix access control rule ambiguities (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1132">#1132</a>)</p>
<p>Detailed:<br />1. xpath in instance docs: <br />/eml/dataset/dataTable/attributeList/attribute/measurementScale/datetime <br />becomes .../dateTime</p>
<p>2. xpath in instance docs (* neq <describes>): <br />/eml/additionalMetadata/* becomes /eml/additionalMetadata/metadata/*</p>
<p>3. method was declared in entity group, so all these paths become "methods":<br />eml/dataset/dataTable/method <br />eml/dataset/spatialRaster/method <br />eml/dataset/spatialReference/method <br />eml/dataset/spatialVector/method <br />eml/dataset/view/method <br />eml/dataset/storedProcedure/method</p>
<p>4. access trees moved:<br />case 1: access tree at resource level:<br />/eml/dataset/access and /eml/software/access moved to eml/access</p>
<p>case 2: access tree(s) in additionalMetadata sections:<br />Current behavior:<br />Do not recognize <access> siblings of additionalMetadata/describes that reference <br />/eml/dataset/distribution <br />/eml/software/distribution</p>
<p>Recognize <access> siblings of additionalMetadata/describes that reference<br />/eml/dataset/dataTable/physical/distribution<br />/eml/software/implementation/distribution</p>
<p>recognizable cases:<br />4.2.1.one additionalMetadata/describes element pointing a recognized node, with one sibling access tree<br />action: move the access tree, remove additionalMetadata section</p>
<p>4.2.2. two (or more) additionalMetadata/describes elements pointing to recognized nodes, with one sibling access tree<br />action: copy the access tree to both locations, remove additionalMetadata</p>
<p>4.2.3 two (or more) additonalMetadata/describes<br />4.2.3.1 references a distribution node<br />action: remove the <describes>, copy the access tree to the referenced node<br />4.2.3.2 references some other non-recognized node<br />action: leave the <describes>, <br /> additionalMetadata/access -> additionalMetadata/metadata/access</p>
<p>4.3. one additionalMetadata/describes element pointing to a recognized node, <br />with multiple sibling access trees (in eml 2.0.x, these will need to have been wrapped in another element in order to be valid)<br />action: move nothing. can't deal with elements that arent 2.0.1 [aside: addtionalMetadata section will have <metadata> tag added per item 2. above ]</p>
<p>4.4 the eml-author created access trees in additionalMetadata that contain non-eml material. we cannot move these to other parts of the EML instance document. [aside: If metacat has encountered additional not-eml elements alongside access elements, it would have ignored them.]</p>
<p>To be sure output is valid EML, a script should include the parser to check the doc against the schema. Can the stylesheet do this alone? Jing and margaret not sure.</p>
<p>4.1. assuming stylesheet finds the non-eml material (ie, it can parse), possible actions include: <br /> a? ignore access tree, but wrap it in <metadata> </metadata><br /> or b? reject document, tell use that the resulting eml will be invalid<br /> or c? rebuild access tree in the new location (ie, try to interpret what author wanted)</p> Bug #3492 (In Progress): Unit should be pluralized by defaulthttps://projects.ecoinformatics.org/ecoinfo/issues/34922008-09-23T17:49:18ZShaun Walbridgewalbridge@nceas.ucsb.edu
<p>In eml-physical.xsl, the template 'physicalsize' should see if the unit is greater than one, and pluralize accordingly. Currently, it just reads:<br /> <xsl:value-of select="./@unit"/></p>
<p>Perhaps instead, it could read:<br /> <xsl:value-of select="./@unit"/><br /> <xsl:if test="@unit > '1'"><br /> s<br /> </xsl:if></p>
<p>Mostly annoying because most EML documents with entities have a byte count, and it displays as '145902 byte' currently.</p> Bug #2226 (New): EML2 style sheet double the number of complex delimited format in physical modualhttps://projects.ecoinformatics.org/ecoinfo/issues/22262005-10-10T22:15:34ZJing Taotao@nceas.ucsb.edu
<p>If a eml2 document has a complex delimited format. The dispaly will double the<br />number of elements. For example, if a document has 10 textFixed elements. But<br />the display will have both 10 textFixed elments and 10 textDelimited elements.</p> Bug #2147 (In Progress): EML Stylesheet problem with web address URL'shttps://projects.ecoinformatics.org/ecoinfo/issues/21472005-07-11T23:12:03ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>Data Set Description on the web for ID's like knb-lter-gce.77.8 to not link<br />correctly to the Web Address such as listed under Metadata Provider(s). Is this<br />a known problem - that the Data Set Descriptions Web Addresses do not direct<br />right because the address reads an additional http into the URL? here is an<br />example record from the KNB site knb-lter-gce.77.8 <br /><sid> Callie - the links are adding the <a class="external" href="http:// in">http:// in</a> front of the urls<br /><sid> which alreadt have http in them<br /><sid> same is not true for Online Distribution Info<br /><Callie> anyway with the online Data Set Descriptions the Web links do not work<br />for some of the records and this one in particular knb-lter-gce.77.8 <br /><Callie> an example is where the Metadata Provider(s): Web Address reads as<br /><a class="external" href="http://gce-lter.marsci.uga.edu/lter">http://gce-lter.marsci.uga.edu/lter</a> but when you click on the link it tries to<br />go to <a class="external" href="http://http//gce-lter.marsci.uga.edu/lter/">http://http//gce-lter.marsci.uga.edu/lter/</a><br /><sid> yep<br /><sid> i will have to check the xml stylesheets<br /><sid> eml stylesheets<br />--- vero_lunch is now known as vero<br /><sid> Callie - the extra http is hard coded each time into web addresses - i<br />think the problem was that is we dont add <a class="external" href="http:// then">http:// then</a> it messes up the urls<br />which dont have http in from <br /><sid> e.g. a link like this <a class="external" href="http://www.google.com">www.google.com</a><br /><sid> will show up as <a class="external" href="http://knb.ecoinformatics.org/www.google.com">http://knb.ecoinformatics.org/www.google.com</a><br /><Callie> yes, I've also seen problems with linking when just www is at the start<br />of an address rathern than <a class="external" href="http://www">http://www</a><br /><Callie> The only thing I was thinking was insisting that when people enter in<br />an address that it includes the <a class="external" href="http:// or">http:// or</a> other type of http2//: ect Maybe then<br />we wouldn't need the <a class="external" href="http:// to">http:// to</a> be added??<br />--- jinglunch is now known as jing<br /><sid> yes<br /><sid> example of that would be <a class="external" href="https:// or">https:// or</a> <a class="external" href="ftp:// ">ftp:// </a><br /><sid> maybe you can add a bug regarding this in the eml bugzilla...<br /><sid> if you do, specify that the bug is in eml stylesheets rather than in eml<br />schema</p> Bug #2085 (New): Access Control not shown by EML stylesheetshttps://projects.ecoinformatics.org/ecoinfo/issues/20852005-05-21T01:35:04ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>The access control information is not shown by XSLTs if no public read access <br />is specified. So if we have access control as:<br /><access> <br /> <allow> <br /> <principal>public</principal><br /> <permission>read</permission><br /> </allow><br /> <allow> <br /> <principal>uid=sgarg,o=NCEAS,dc=ecoinformatics,dc=org</principal><br /> <permission>read</permission><br /> </allow><br /></access></p>
<p>or</p>
<p><access> <br /> <deny> <br /> <principal>public</principal><br /> <permission>read</permission><br /> </deny><br /> <allow> <br /> <principal>uid=sgarg,o=NCEAS,dc=ecoinformatics,dc=org</principal><br /> <permission>read</permission><br /> </allow><br /></access></p>
<p>then the XSLTs will show access rule for uid=sgarg</p>
<p>But if we have this:<br /><access> <br /> <allow> <br /> <principal>uid=sgarg,o=NCEAS,dc=ecoinformatics,dc=org</principal><br /> <permission>read</permission><br /> </allow><br /></access></p>
<p>then nothing is shown by XSLTs.</p> Bug #2048 (New): param attributeindex defined twice in eml-settings.xslhttps://projects.ecoinformatics.org/ecoinfo/issues/20482005-03-19T00:15:03ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Johnoel reported this. attributeindex is defined twice in eml-settings.xsl.<br />Seems like a typo.</p>