VegBank: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362011-09-19T22:12:03ZEcoinformatics Redmine
Redmine Bug #5493 (In Progress): tomcat crashes frequentlyhttps://projects.ecoinformatics.org/ecoinfo/issues/54932011-09-19T22:12:03ZNick Brandbrand@nceas.ucsb.edu
<p>Tomcat frequently gets into a state where it stops serving pages and needs to be restarted. This has been happening for a while now, first on the RHEL4 server (vegbank), and now on the new Ubuntu 10.04 virtual server (vegbankvm).</p>
<p>Most recently the tomcat service has been manually restarted on 7/30, 8/19, 8/21, 8/27, and 9/19.</p>
<p>I attempted to stop the frequent crashing by increasing the allocated memory in tomcat from 2GB to 4GB, but it crashed a couple days after the change, so I restored the 2GB setting.</p> Bug #5478 (New): after querying plants, communities, or plots, link back to searchhttps://projects.ecoinformatics.org/ecoinfo/issues/54782011-08-30T01:28:18ZMichael Leemlee@nceas.ucsb.edu
<p>When searching for something, web sites often want you to be able to modify your search terms easily and search again. We should do that. Now, you have to use the back button.</p>
<p>Seems like we could include part of the search page (fancy option) or at least offer a backlink to it, with the form filled out, ideally.</p> Bug #5391 (New): build process into war file does not generate faq.htmlhttps://projects.ecoinformatics.org/ecoinfo/issues/53912011-05-04T20:38:40ZMichael Leemlee@nceas.ucsb.edu
<p>the initial build process that generated the war file did not generate a faq.html file in web/general. This is handled in web/build.xml and needs to be called.</p> Bug #5211 (New): Colorado data not entered correctlyhttps://projects.ecoinformatics.org/ecoinfo/issues/52112010-10-20T13:17:10ZMichael Leemlee@nceas.ucsb.edu
<p>The taxonomy was not updated as originally requested, there are some problems with the cover values, there are some problems with the metadata, and the community names assigned are strangely rendered.</p>
<p>(from Peet email 10/20/2010)</p> Bug #4796 (New): receipt of plots with accession codes after loadinghttps://projects.ecoinformatics.org/ecoinfo/issues/47962010-02-16T16:49:37ZMichael Leemlee@nceas.ucsb.edu
<p>Don says: Would it be possible in the future, that whenever someone uploaded their data into VegBank, they could somehow be sent a table of their own plot codes and the VegBank accession code?</p>
<p>Michael: we could certainly add this to the receipt.</p> Bug #4502 (New): standardized online data entry form for plotshttps://projects.ecoinformatics.org/ecoinfo/issues/45022009-10-22T19:17:19ZMichael Leemlee@nceas.ucsb.edu
<p>This is vastly complex and difficult to assure that data are complete and things like network interruptions don't cause lost data. I think this is a poor use of time and will under the best circumstances result in poor data entry interface.</p>
<p>Source is section 2.6.2 number 9 of requirements document, page 60</p> Bug #4501 (New): map fields and upload data into the NVC Plot DBhttps://projects.ecoinformatics.org/ecoinfo/issues/45012009-10-22T19:17:09ZMichael Leemlee@nceas.ucsb.edu
<p>I have no idea how wide in scope this is. Without knowing something about the incoming data, it's impossible to start programming. This is very vauge. I think time would be better spent getting standard formats like VEGX working. We could also add TurboVeg or other specific formats, but other undefined formats can use VegBranch</p>
<p>Source is section 2.6.2 number 10 of requirements document, page 64</p> Bug #4500 (New): Implement a shared login between NVCRS and VegBankhttps://projects.ecoinformatics.org/ecoinfo/issues/45002009-10-22T19:17:01ZMichael Leemlee@nceas.ucsb.edu
<p>This is more complex than it seems and requires simultaneous coding on VegBank and NVCRS to accomodate. Questions:<br />1) when a user registers on NVCRS, do they register on VegBank simultaneously? <br /> a) What if they are already on VegBank? <br /> b) Provide a check box to also register on VegBank? <br /> c) Can two accounts be ''linked'' based on the same email address? What if someone registers with an alias on one system, but not the other? (e.g. <a class="email" href="mailto:jane_user@email.unc.edu">jane_user@email.unc.edu</a> vs. <a class="email" href="mailto:J_User@unc.edu">J_User@unc.edu</a>)<br />2) When a user updates his/her password, do both systems get updated? - security implications here<br />3) When a user logs into VegBank, does s/he get logged in to NVCRS automatically? or checkbox?<br />4) When a user logs into NVCRS, does s/he get logged into VegBank automically? Or checkbox to ''Also login to VegBank?''<br />5) The real can of worms: What about other fully compliant databases? Are we going to add these, too?</p>
<p>Source is section 2.1.3 number 12 of requirements document, page 16</p> Bug #4499 (New): Refresh VegBank from Public DBhttps://projects.ecoinformatics.org/ecoinfo/issues/44992009-10-22T19:16:50ZMichael Leemlee@nceas.ucsb.edu
<p>We will need to have VegBank query the NVCRS to get a list of updates. We need to define the scope of what's getting updated. Presumably, this means new community types, as well as their status, old types and new statuses, correlations of communities, and plot annotations to communities. Should not include plot data.</p>
<p>Source is section 2.3.5 number 21 of requirements document, page 48</p> Bug #4494 (New): Tracking and correlating multiple database GUIDs to entitieshttps://projects.ecoinformatics.org/ecoinfo/issues/44942009-10-22T19:16:08ZMichael Leemlee@nceas.ucsb.edu
<p>Some mechanism needed to track GUIDs from other dbs and how they relate to VB entities will eventually be needed. Need mechnism to discover identical plots in distributed databases, ideally, otherwise allow users to copy and paste lists of equivalent GUIDs</p>
<p>Source is section 2.6.10 number 39 of requirements document, page 76</p> Bug #4493 (New): terms of use revisionhttps://projects.ecoinformatics.org/ecoinfo/issues/44932009-10-22T19:16:00ZMichael Leemlee@nceas.ucsb.edu
<p>This is fairly doable. We could easily add a creative commons license to each plot, and allow users to specify such licenses when they upload data. Might include a new observation field to allow plot-by-plot changes of license. This would require a revision of VegBranch. Or, we could include this in the 'ownership/embargoes' of plots and could be edited from default after submission.</p>
<p>Source is section 2.6.2 number 14 of requirements document, page 65</p> Bug #4486 (New): large download supporthttps://projects.ecoinformatics.org/ecoinfo/issues/44862009-10-22T19:06:43ZMichael Leemlee@nceas.ucsb.edu
<p>An easier approach on our server would be to allow full database download for users wanting more than 3000 plots. Then they can filter the full list with a custom-provided list of plots.</p> Bug #4485 (New): Export VEGX formathttps://projects.ecoinformatics.org/ecoinfo/issues/44852009-10-22T19:06:33ZMichael Leemlee@nceas.ucsb.edu
<p>goes along with import of this format</p> Bug #4484 (New): Import VEGX plot data into VegBankhttps://projects.ecoinformatics.org/ecoinfo/issues/44842009-10-22T19:06:19ZMichael Leemlee@nceas.ucsb.edu
<p>Some work on this front has been completed in New Zealand on a database similar to VegBank. Should check with them before proceeding</p> Bug #1610 (Resolved): lift VA Heritage data embargohttps://projects.ecoinformatics.org/ecoinfo/issues/16102004-06-28T17:49:39ZMichael Leemlee@nceas.ucsb.edu
<p>Part of NatureServe/Heritage contract</p>