EML: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362009-01-17T00:48:20ZEcoinformatics Redmine
Redmine 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 #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 #2079 (In Progress): Move project element to top-levelhttps://projects.ecoinformatics.org/ecoinfo/issues/20792005-05-12T23:27:36ZShaun Walbridgewalbridge@nceas.ucsb.edu
<p>This is a request to move the <project> element to the root-level of the EML<br />schema. Currently, the <project> element (type="proj:ResearchProjectType") is<br />embedded within the <dataset> element.</p>
<p>The NCEAS Ecosystem-Based Management (EBM) program is creating a registry of EBM<br />projects. Projects in the EBM program relate a project to the products<br />generated, which include citations, URI references, and datasets. No products<br />are required to have a valid project (since projects may be in early stages of<br />development or lack publications). Ideally, this could be stored in EML as one<br />main EML document for the project, citations, URIs, and then additional EML<br />documents for each dataset.</p>