InfoVeg: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362008-05-16T01:18:55ZEcoinformatics Redmine
Redmine Bug #3298 (Resolved): Entry fields overlapping on level 1 plots, if level 3 plots are added firsthttps://projects.ecoinformatics.org/ecoinfo/issues/32982008-05-16T01:18:55ZMichael Leemlee@nceas.ucsb.edu
<p>This is the strangest error I've seen that I've been able to fix on a database. If you added a level 3 plot first in a list of plots, when you go to the level 1 plot, some fields on the plot data form overlap, where the size and modules of a plot are specified.</p>
<p>It turns out that some SQL was executing that used a field that was in the main form currently active rather than the correct field. It was accidentally mistyped in the SQL but found a place to read from.</p>
<p>Incorrect SQL:<br /> DoCmd.RunSQL "update observation set entry_plotLayoutType=IIf([cvs_Level]<3,1,3) where entry_plotLayoutType is null;"</p>
<p>correct SQL:<br /> DoCmd.RunSQL "update observation set entry_plotLayoutType=IIf([cust_cvs_samplingLevel]<3,1,3) where entry_plotLayoutType is null;"</p> Bug #2922 (Resolved): Use non-modal messages when adding new partieshttps://projects.ecoinformatics.org/ecoinfo/issues/29222007-09-01T16:17:30ZMichael Leemlee@nceas.ucsb.edu
<p>Currently, you can add parties in plotContrib subform, but it asks you "do you have more info about [person] and you have to select yes, no or cancel." It should be more streamlined, I think. The advantage to it as it is now is that you can't add duplicate parties as easily, but it should be less modal.</p>
<p>Perhaps Gmail-ish, where it says "you have added party X" and there would be an "undo" link at the same place.</p> Bug #2917 (Resolved): Entry DB is getting larger and larger - allow downloads of data to decrease...https://projects.ecoinformatics.org/ecoinfo/issues/29172007-08-29T19:33:02ZMichael Leemlee@nceas.ucsb.edu
<p>We could post data online for people and distribute a smaller set of data.</p>
<p>Community data could certainly be removed from most posts, but clean integration with download of new data would be necessary. Could perhaps do without soilTaxa, too.</p> Bug #2776 (Resolved): Need some queries to help us summarize issues for contractorshttps://projects.ecoinformatics.org/ecoinfo/issues/27762007-02-14T22:33:06ZMichael Leemlee@nceas.ucsb.edu
<p>Need a naming scheme (qa_quick)?</p>
<p>A simple summary by project:<br />SELECT project.projectName, project.entry_projectCode AS code, Count(observation.OBSERVATION_ID) AS plots<br />FROM project INNER JOIN observation ON project.PROJECT_ID = observation.PROJECT_ID<br />GROUP BY project.projectName, project.entry_projectCode;</p> Bug #2667 (Resolved): Test Entry Tool processing of data vs. SAShttps://projects.ecoinformatics.org/ecoinfo/issues/26672006-11-13T17:51:04ZMichael Leemlee@nceas.ucsb.edu
<p>SAS can process data (the old way) and we should take some new data, export it to old style CVS text files, run them through SAS, then see if SAS and Access come up with the same data at the end of the process.</p>
<p>This will require that Forbes run the data through SAS, Michael run the data through Access (noting carefully any fixes that were human fixes, like fixing logical errors).</p>
<p>Then Michael will compare the results to see if the data are the same (the focus here, is obviously on the tree and herb data).</p> Bug #2659 (Resolved): StratumPlot not linked to HerbDatahttps://projects.ecoinformatics.org/ecoinfo/issues/26592006-11-11T00:29:30ZMichael Leemlee@nceas.ucsb.edu
<p>The stratum plot records are not properly linked in from the data sources for recent projects. StratumPlot.StratumPlotHerbIDNum is the field in question. We need to ideally get the entry databases for projects 47 and higher, and for the new Roanoke plots. If we can't get them, it will be somewhat easy to piece back together based on taxa.</p>