InfoVeg: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362008-07-14T22:08:25ZEcoinformatics Redmine
Redmine Bug #3452 (In Progress): evaluate beta PDA version of the reference listshttps://projects.ecoinformatics.org/ecoinfo/issues/34522008-07-14T22:08:25ZMichael Leemlee@nceas.ucsb.edu
<p>I think it would be really helpful to create a webpage that could be downloaded onto a mobile device (smart phone or PDA) and this could be consulted in the field. Especially for contractors, as I'd think the likelihood is they'd have such devices on them when sampling. Probably likely for Pulse, too.</p>
<p>All the glossary terms in the protocol would be desirable to include, and it would still be fairly small for a device, using javascript to show/hide what's of interest. Users would first select which list/field they are interested in, then be shown the field definition, optionally a list of values that are options, then optionally also a series of definitions for each value (or one at a time).</p> Bug #3430 (In Progress): Create 1-pager instructions for each level (workshop '08)https://projects.ecoinformatics.org/ecoinfo/issues/34302008-06-25T22:48:52ZMichael Leemlee@nceas.ucsb.edu
<p>We would like to create a one-page instruction set for each CVS Level so that people can refresh their memories without consulting the entire Protocol Document.</p> Bug #3420 (New): Preprint "plot datasheet" when upgrading to level 3 (workshop '08)https://projects.ecoinformatics.org/ecoinfo/issues/34202008-06-25T22:41:50ZMichael Leemlee@nceas.ucsb.edu
<p>If plots are revised to upgrade to level 3, the plot sheet should be pre-populated with those data previously reported during level 1 or 2 monitoring. We have placed this on our list of desirable features, but have not yet given it a high priority owing to the infrequency of upgrading to level 3.</p> Bug #3006 (New): Add LSID+GUID to data rowshttps://projects.ecoinformatics.org/ecoinfo/issues/30062007-11-16T19:04:43ZMichael Leemlee@nceas.ucsb.edu
<p>The best way of tracking duplicates is unfortunately not our current system, but rather a GUID that is an LSID that has a GUID in it:<br />format: urn:lsid:cvs.bio.unc.edu:[tableName]:PK-[GUID]<br />length should be at least 150, probably go to full 255.</p>
<p>This would have to be override-able as sometimes newly created entities should map onto existing ones. This would enable each client entry tool to create unique IDs for data- without the need to update each client after adding to archive db.</p>
<p>This is far better than our current PK+bln_new flag. It would be a new series of fields (or one table?) that would create GUIDs and assign them to entities.</p> Bug #2904 (New): Allow editing of default stratum method and cover methodhttps://projects.ecoinformatics.org/ecoinfo/issues/29042007-08-10T23:13:48ZMichael Leemlee@nceas.ucsb.edu
<p>These values are currently stored in X_otherOptions as names "stratumMethodAccessionCode" and "coverMethodAccessionCode". The accession codes could be changed to switch to a different method. But each would require types/indexes that have only a single character for the cover forms to work properly, and the default strata.</p>