VegBank: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362006-08-24T19:46:49ZEcoinformatics Redmine
Redmine Bug #2519 (In Progress): Tracking bug for upgrade of vegbankhttps://projects.ecoinformatics.org/ecoinfo/issues/25192006-08-24T19:46:49ZChad Berkleyberkley@nceas.ucsb.edu
<p>Tasks that need to be done on vegbank for the upgrade (in no particular order):</p>
<p>-modify backup procedures so that older backups get removed (2395)<br />-install new backup script (vegbank/bin/vbdump) which also runs the vacuum analyze on the db<br />-create cron job to automatically update the homepage data (2482) <br />--perhaps bug 2406 (updating the homepage map) could also be performed with a cron job<br />-upgrade postgres to version 8.1.4<br />-upgrade the vegbank schema to vegbank-changes-1.0.5<br />-update the amount of memory that tomcat on vegbank is using (it should be at least 1 GB) via the JAVA_OPTS=-Xmx1024m env var.<br />-make sure the properties in build.properties have the correct settings, including email server (should be mail.nceas.ucsb.edu)<br />-run the update password task in the build file to update the passwords in the db to the new format</p> Bug #2402 (New): Strategy to update denormalized data, cache, pageshttps://projects.ecoinformatics.org/ecoinfo/issues/24022006-04-07T00:44:43ZMichael Leemlee@nceas.ucsb.edu
<p>We have a series of items that are stored data, views, etc., that help with performance. These items need to be updated at various times when data changes or is added to the database. We need some strategy for how and when to update these denormalizations.</p> Bug #2394 (New): Make Search by person easier: filter by plots submitted and plots contributed tohttps://projects.ecoinformatics.org/ecoinfo/issues/23942006-04-05T17:32:45ZMichael Leemlee@nceas.ucsb.edu
<p>Allow searching by parties more easily. Filter to only data providers and project organizers, and perhaps plot PIs.</p>
<p>Have a list, make it searchable, then show the plots from those folks. Kind of have this with the "summary" info, but could be better.</p> Bug #2102 (New): IN JULY: Load Real Concepts that have been a major part of this granthttps://projects.ecoinformatics.org/ecoinfo/issues/21022005-06-08T19:44:31ZMichael Leemlee@nceas.ucsb.edu
<p>Make interact with extant USDA list.</p> Bug #1975 (New): Iteratively query to narrow or broaden query resultshttps://projects.ecoinformatics.org/ecoinfo/issues/19752005-02-10T22:14:33ZMichael Leemlee@nceas.ucsb.edu
<p>Use datasets ...</p> Bug #1956 (New): function to fuzz and unfuzz locations for adminhttps://projects.ecoinformatics.org/ecoinfo/issues/19562005-02-10T00:21:45ZMichael Leemlee@nceas.ucsb.eduBug #1955 (New): view my plots -- deposits, based on ownership + embargo chnghttps://projects.ecoinformatics.org/ecoinfo/issues/19552005-02-10T00:19:28ZMichael Leemlee@nceas.ucsb.edu
<p>allow user to update any embargoes to:</p>
<p>No embargo (drop embargo)<br />1 month<br />3 months<br />6 months<br />9 mo.<br />1 yr<br />2 yr<br />3 yr</p> Bug #1352 (New): choose which comms from commInterpretation - higher level obs summaryhttps://projects.ecoinformatics.org/ecoinfo/issues/13522004-02-24T23:47:22ZMichael Leemlee@nceas.ucsb.edu
<p>rules for showing picking what community from commInterpretation and plant<br />concept for each taxonObs need to be developed. See VegBranch for a first cut<br />of this, as this functionality exists there.</p>
<p>a default rule will be developed, for which caching of plot views and XML may be<br />used. If the user wishes to deviate from that, we will eventually allow that,<br />but views will be slower.</p> Bug #1022 (New): Eval: Form to calculate summary of multiple plotshttps://projects.ecoinformatics.org/ecoinfo/issues/10222003-03-27T10:09:46ZMichael Leemlee@nceas.ucsb.edu
<p>We need a form that shows a summary of multiple plots. Two uses will be when a<br />user gathers a "shopping cart" of plots and wants to see a summary of them (or<br />simply a summary of a query result). Also, we then need to be able to query<br />these plots with a URL. Given that URL's technically have a length restriction<br />(is this not so, Gabe?), though it is long, will this be possible for say, 15<br />plots? How about 150? 1500? You get the picture. Eventually, we will probably<br />need to add a table to VegBank that will store groups of plotAccessionNumbers<br />with a name so that the URL would be<br /><a class="external" href="http://vegbank/getplotgroup?plotgroup=VB.44.03-Mar-2008,01:23:56">http://vegbank/getplotgroup?plotgroup=VB.44.03-Mar-2008,01:23:56</a></p>
<p>As far as design of such a form, I (Michael) have some ideas from working with<br />Del Meidinger in the Ministry of Forests in Victoria, BC</p> Bug #890 (New): Load database:Peet _NCVS-4000: add in Fall 2006https://projects.ecoinformatics.org/ecoinfo/issues/8902002-11-13T22:02:53ZMichael Leemlee@nceas.ucsb.edu
<p>ML/RP</p> Bug #878 (New): PCord exporthttps://projects.ecoinformatics.org/ecoinfo/issues/8782002-11-13T22:01:47ZMichael Leemlee@nceas.ucsb.edu
<p>Roberts--Provide specs, Similar to two flat ascii</p> Bug #817 (New): Query for User-defined variableshttps://projects.ecoinformatics.org/ecoinfo/issues/8172002-11-13T21:56:11ZMichael Leemlee@nceas.ucsb.edu
<p>ML designs</p> Bug #704 (New): doubleCheck final DB: QA of plants and communitieshttps://projects.ecoinformatics.org/ecoinfo/issues/7042002-11-13T21:44:34ZMichael Leemlee@nceas.ucsb.edu
<p>DFL evaluate & test, conceptual (no pun intended) issues work.</p> Bug #681 (New): Website cleanup:Spelling and editing checkshttps://projects.ecoinformatics.org/ecoinfo/issues/6812002-11-13T21:41:37ZMichael Leemlee@nceas.ucsb.edu
<p>ML runs comprehensive spell check of website</p> Bug #675 (New): Evaluate Tutorialhttps://projects.ecoinformatics.org/ecoinfo/issues/6752002-11-13T21:41:05ZMichael Leemlee@nceas.ucsb.edu
<p>Allocate 1 week. ML will work on this in Oct & Nov. ML needs to expand and<br />import the help file from VegBranch to apply here. These must be evaluated by<br />PIs and staff. -First step is for ML to develop definition of scope via<br />discussion with RP & MJ</p>