EML: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362013-04-10T21:34:07ZEcoinformatics Redmine
Redmine Bug #5903 (Resolved): Replace "Owner" with "Creator" in EML stylesheetshttps://projects.ecoinformatics.org/ecoinfo/issues/59032013-04-10T21:34:07Zben leinfelderleinfelder@nceas.ucsb.edu
<p>"Data Set Owners:" should be "Data Set Creators:" etc...</p> Bug #5734 (Resolved): Attribute Domain info not rendered by stylesheetshttps://projects.ecoinformatics.org/ecoinfo/issues/57342012-11-14T18:21:18Zben leinfelderleinfelder@nceas.ucsb.edu
<p>For example.</p>
<p><a class="external" href="http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=default&sessionid=0&docid=nceas.997.2&displaymodule=attributedomain&entitytype=dataTable&entityindex=1&attributeindex=1">http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=default&sessionid=0&docid=nceas.997.2&displaymodule=attributedomain&entitytype=dataTable&entityindex=1&attributeindex=1</a></p> Bug #5705 (Resolved): Contact showing multiple people/orgs when EML file does nothttps://projects.ecoinformatics.org/ecoinfo/issues/57052012-09-06T22:03:22Zben leinfelderleinfelder@nceas.ucsb.edu
<p>When styling in Metacat (and presumably elsewhere) we see many entries in contact that don't make much sense.<br />see examples:<br />nceas.973<br />nceas.931.8</p> Bug #3166 (Resolved): remove extra "attributeindex" parameter in eml-settings.xslhttps://projects.ecoinformatics.org/ecoinfo/issues/31662008-02-27T00:01:02Zben leinfelderleinfelder@nceas.ucsb.edu
<p>The "attributeindex" parameter is multiply defined in the eml-settings.xsl file. This came up when trying to view metadata from within Kepler. The XSLT parser did not like this double definition.<br />Neither Jing not Dan could recreate the problem on their systems.<br />But declaring parameters twice is not correct, and since it breaks the style sheet for me, why no remove it?</p>
<p>Not sure what this means in terms of packaging and tagging as a new release (use RELEASE_EML_2_0_1_UPDATE_6?).</p>
<p>I've tried including this change in the kepler style jar and can successfully view the metadata there.</p> Bug #3151 (Resolved): Package datamanager.jar without including classes from supporting jarshttps://projects.ecoinformatics.org/ecoinfo/issues/31512008-02-14T23:44:27Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Currently the datamanager distribution <em>unjars</em> all the supporting jars it uses and packages them with the datamanager classes as a single datamanager.jar file.</p>
<p>Only datamanager classes should be included in this jar. Gathering the necessary supporting jars should be the responsibility of the application making use of the datamanager api.</p>
<p>This should make it easier to include in metacat and kepler and prevents version clashes with supporting jars.</p> Bug #3096 (Resolved): Date data type (domain) need be handled correctlyhttps://projects.ecoinformatics.org/ecoinfo/issues/30962008-01-23T19:18:11ZJing Taotao@nceas.ucsb.edu
<p>Currently, Date data type (domain) in EML document is treated as string in database system. This will cause some limitation in query operation to date data type.</p> Bug #3051 (Resolved): standardUnit restriction doesnt match eml-unitDictionary.xmlhttps://projects.ecoinformatics.org/ecoinfo/issues/30512008-01-02T23:13:36ZMargaret O'Brienmob@msi.ucsb.edu
<p>Entered on behalf of James Conners (@CCE/PAL LTERs)</p>
<p>paraphrased from his email:<br />In the current EML-2.0.1 schema (eml-attribute.xsd) the restricted set of values allowed for a standardUnit doesn't exactly match up with what's in the unit definitions document shipped with eml2.0.1(eml-unitDictionary.xml). There are two <unit> definitions (numberPerLiter and numberPerMilliliter) in eml-unitDictionary.xml that aren't listed as allowable for the <standardUnit> element in eml-attribute.xsd (Otherwise these lists match up correctly).</p> Bug #2979 (Resolved): create Union query to concatenate results from multiple entitieshttps://projects.ecoinformatics.org/ecoinfo/issues/29792007-10-09T22:24:42Zben leinfelderleinfelder@nceas.ucsb.edu
<p>The motivation for this enhancement came from both Kepler (wanting to merge data from like-structured datatables in an EMLDataSource actor) and from the FIRST project where a similar function is desired (but across many different packages).<br />Implementation is intended to be a straightforward SQL union/union all between two or more Query objects.</p> Bug #2775 (Resolved): DataManager cuts last row off data_tablehttps://projects.ecoinformatics.org/ecoinfo/issues/27752007-02-13T23:28:23ZChad Burtcburt@msi.ucsb.edu
<p>Had a problem putting this data into a database:<br /><a class="external" href="http://data.piscoweb.org/catalog/metacat?action=read&docid=cburt.5.2&qformat=pisco">http://data.piscoweb.org/catalog/metacat?action=read&docid=cburt.5.2&qformat=pisco</a></p>
<p>It looks like the last row,<br />(2006-02-01,3,10,"test fixtures are fun")<br />is getting cut off.</p>
<p>I haven't tested a dataset without a header file. I suspect either the header is being counted against it in a loop or there is a < where a <= would be more appropriate.</p> Bug #2083 (Resolved): dimension 'current' is wrongly entered as 'charge'https://projects.ecoinformatics.org/ecoinfo/issues/20832005-05-20T18:58:40ZMatt Jonesjones@nceas.ucsb.edu
<p>Somehow the base dimension list for EML has 'charge' as a fundamental dimension<br />instead of 'current'. THis is wrong, and should be fixed. See the NIST site<br />for details. <a class="external" href="http://physics.nist.gov/cuu/Units/units.html">http://physics.nist.gov/cuu/Units/units.html</a></p>
<p>'Charge' should be a derived unit that is equal to ampere*second which is the<br />definition of a coulomb.</p>