EML: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362008-05-22T21:15:22ZEcoinformatics Redmine
Redmine Bug #3313 (Resolved): Edit EML documentation for access controlhttps://projects.ecoinformatics.org/ecoinfo/issues/33132008-05-22T21:15:22ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>The ability to restrict access is a common request. I think it would be good to add the following information regarding how to restrict access to a dataTable. I think this is the most common request.</p>
<p>The description at this location <a class="external" href="http://knb.ecoinformatics.org/software/eml/eml-2.0.1/index.html#N100A8">http://knb.ecoinformatics.org/software/eml/eml-2.0.1/index.html#N100A8</a></p>
<p>would be more helpful with the following addition.</p>
<p>---<br />An example for restricting a dataTable but not the metadata about the dataTable would require editing a specific distribution element. It is nested inside these elelments: <dataTable><physical><distribution><distribution/></physical></dataTable>. There will be other elements nested inside the dataTable element but the distribution element inside the physical element which is inside the dataTable element is the one that needs to be referenced by its ID. The ID needs to be added to the distribution element. <distribution id="999999">. The id needs to be a unique number within the eml file.<br />----</p>
<p>I think it would be good to add the text in the section two part of the second paragraph, after "... element by referencing its unique id."</p> Bug #3188 (Resolved): possible otherEntity and dataTable inconsistanceshttps://projects.ecoinformatics.org/ecoinfo/issues/31882008-03-26T19:00:47ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>The otherEntity element contains most of the same elements as the dataTable<br />element. For some reason the numberOfRecords is only contained in the dataTable<br />element. I think it would worth thinking about having it available but not<br />required in the otherEntity element. This way it would be easier to change a<br />dataTable element to an otherEntity element. It also seems like an<br />inconsistency. The main difference between the two elements is that a dataTable<br />requires that that the attributes are described and a otherEntity does not<br />require that. I think adding the numberOfRecords (not required though, 0 to many) to the otherEntity elements may help with converting dataTable entities to otherEntities when there is problems with listing the attributes.</p>