InfoVeg: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362007-08-08T17:26:37ZEcoinformatics Redmine
Redmine Bug #2901 (Resolved): Can't set new sampling level when resampling plotshttps://projects.ecoinformatics.org/ecoinfo/issues/29012007-08-08T17:26:37ZMichael Leemlee@nceas.ucsb.edu
<p>Need to be able to upgrade or downgrade plots to a new plot level when resampling.</p> Bug #2898 (Resolved): Type only team, plot or just plot in SelectPlot field and it finds ithttps://projects.ecoinformatics.org/ecoinfo/issues/28982007-07-24T05:27:31ZMichael Leemlee@nceas.ucsb.edu
<p>The picklist is full of the same information. Allow users just to type team-plot and it will figure out what you mean, limiting the list as the magic species picklists work. As soon as there is only one option, it should select that and move to that plot.</p>
<p>plot data, cover data, stem data, planted stem data: 4 forms.</p> Bug #2897 (Resolved): Allow users to change the year of their base plotshttps://projects.ecoinformatics.org/ecoinfo/issues/28972007-07-24T00:03:43ZMichael Leemlee@nceas.ucsb.edu
<p>Users often are entering plots that aren't year 0 into new entry tools. Thus, they will need to specify that their plots are really year 3, not 0. They'll need to be able to change the numbers later if they didn't do it properly the first time.</p> Bug #2894 (Resolved): Entry Forms should change record souce, not use filtershttps://projects.ecoinformatics.org/ecoinfo/issues/28942007-07-20T18:49:46ZMichael Leemlee@nceas.ucsb.edu
<p>Currently, entry tools display one plot at a time using filters. However, users can easily change or remove these filters. It would be better to alter the record source so that it isn't possible to show more than what's on the selected plot.</p> Bug #2893 (Resolved): VMD ordering should be flexible in forms: a few options and fall-backhttps://projects.ecoinformatics.org/ecoinfo/issues/28932007-07-13T21:29:02ZMichael Leemlee@nceas.ucsb.edu
<p>VMD should have versioning information printed on the datasheets. This may help sort out weird issues.</p>
<p>Ordering is important, so the entry tool should have several options that have historically been used (TreeLineID, stemIDCode, and NewOrder= nz(alternateOrder,treeLineID). If none of those work, a fall-back option could exist where you type the printed stemIDCode and then it finds that row and you type in the information.</p> Bug #2891 (Resolved): Strata should always be shown, but tab stops can be off if no headerhttps://projects.ecoinformatics.org/ecoinfo/issues/28912007-07-13T19:21:51ZMichael Leemlee@nceas.ucsb.edu
<p>This should function more like rows and header rows instead of showing only a certain number with the picklist.</p> Bug #2890 (Resolved): VMD improvementshttps://projects.ecoinformatics.org/ecoinfo/issues/28902007-07-13T18:15:58ZMichael Leemlee@nceas.ucsb.edu
<p>Lara Rozzell thinks a full page map of stems would make things a lot better.</p>
<p>should add a few blank lines to bottom of each plot for species that are new to the datasheets, but planted previously nonetheless.</p> Bug #2887 (Resolved): "Empty Mod" pseudo-species causes catch-22 errorshttps://projects.ecoinformatics.org/ecoinfo/issues/28872007-07-11T20:12:33ZMichael Leemlee@nceas.ucsb.edu
<p>When plots are sampled, but no trees are found on them, this causes a catch-22 of errors. Either the first is an error (no trees), or the emptyMod flag is an error because the row doesn't have valid data.</p> Bug #2886 (Resolved): Error checking flags null ddh for live-stakeshttps://projects.ecoinformatics.org/ecoinfo/issues/28862007-07-11T20:11:18ZMichael Leemlee@nceas.ucsb.edu
<p>Error checker should be smart enough to know that Live Stakes don't require ddh to be measured.</p> Bug #2882 (Resolved): Entry tool doesn't allow entry of source for "new" stems during monitoringhttps://projects.ecoinformatics.org/ecoinfo/issues/28822007-07-05T17:25:45ZMichael Leemlee@nceas.ucsb.edu
<p>When someone is monitoring, they may find stems that were new to the plot. They can enter these as new rows, but the source field is hidden. When a new row is added, source should reappear as an option. Might be difficult to manage, though we could use default values and a new field or something like that, so we'd know what was added in the baseline or later.</p> Bug #2881 (Resolved): Error checking flagged "[muliple]" as bad value.https://projects.ecoinformatics.org/ecoinfo/issues/28812007-07-02T20:14:02ZMichael Leemlee@nceas.ucsb.edu
<p>When users select more than one value, the list fills in [multiple] as the value. We need to allow this and ignore this when error checking.</p> Bug #2876 (Resolved): Error checker thinks that non-vascular genera shouldn't have "sp."https://projects.ecoinformatics.org/ecoinfo/issues/28762007-06-20T23:32:24ZMichael Leemlee@nceas.ucsb.edu
<p>But that's fine, generally. One could look at whether or not there was something in the species field of the carSpList for NC_std=7.</p> Bug #2871 (Resolved): stem mapping improvements neededhttps://projects.ecoinformatics.org/ecoinfo/issues/28712007-06-11T16:52:45ZMichael Leemlee@nceas.ucsb.edu
<p>There are some improvements needed to the stem mapping interface for VMD:</p>
<p>1) If stems have the same X,Y they should have the same letter on the map, perhaps we can add a note stating that multiple stems share the same coordinates, thus are marked with the same letter.</p>
<p>2) the borders of the plot overlap the letters on stems, making it hard to read. Should be reversed.</p> Bug #2866 (Resolved): Migrate data from OLD entry db to OLD archive (w/ SAS) (52,59,61)https://projects.ecoinformatics.org/ecoinfo/issues/28662007-06-07T18:38:35ZMichael Leemlee@nceas.ucsb.edu
<p>This includes projects 52,59,61.</p>
<p>OLD entry db -> SAS -> old entry db -> old archive db</p> Bug #2865 (Resolved): Datasheets & Protocol: Concrete soil (or similar) is problematic to our dat...https://projects.ecoinformatics.org/ecoinfo/issues/28652007-06-02T22:26:09ZMichael Leemlee@nceas.ucsb.edu
<p>Concrete. The question came up as to drainage category for<br />impermiable surfaces such as concrete, or more realistically hard-packed<br />clay. The Manual makes reference to a gley-horizon for poorly drained, yet<br />hard clay recently modified by construction equipment will not be gleyed.</p>
<p>Action Item: Forbes will research this in the USDA Soil Survey literature<br />and report back. Changes will be proposed to the group and ultimately<br />implemented by Michael.</p>