Ecoinformatics Redmine: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362009-10-22T19:17:09ZEcoinformatics Redmine
Redmine VegBank - 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> VegBank - 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> VegBank - 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> VegBank - Bug #4496 (New): search for plots based on 'communities similar to' a given typehttps://projects.ecoinformatics.org/ecoinfo/issues/44962009-10-22T19:16:25ZMichael Leemlee@nceas.ucsb.edu
<p>Not sure how this would look. Provide a community and VegBank thinks about which communities are similar and you get plots back from all communities. Not sure how this would work and if it's worth it. Maybe once 'suggest' a community is completed, this will be simpler.<br />But do we also want on-the-fly searching for similar types, e.g. by diagnostic species? Should only return types stored in the db as 'similar', which are at the same hierarchy level and based on composition or similarity in the field. This information is needed to develop proposals. Types can be queried by both scientific and common names.<br />Source is section 2.6.5 number 26b of requirements document, page 69</p> VegBank - Bug #4490 (New): expand plot searching to include various new criteriahttps://projects.ecoinformatics.org/ecoinfo/issues/44902009-10-22T19:15:37ZMichael Leemlee@nceas.ucsb.edu
<p>some of the new criteria are fairly simple. Some are more complex. Some are 'future' and may not need immediate work.</p>
<p>Source is section 2.6.5 number 26 of requirements document, page 69-72</p> VegBank - Bug #4489 (New): ensure VegBank documents plot type in the sense of 'classification' pl...https://projects.ecoinformatics.org/ecoinfo/issues/44892009-10-22T19:15:27ZMichael Leemlee@nceas.ucsb.edu
<p>Akin to CVS Plot Levels. May be catured in PlotValidationLevel, but I'm not sure. If we need to add a field, this will have broader implications, including VegBranch. There is a separate issue about typal plots here that is confusing. A plot is NEVER typal or not, it's the classification of the plot that is typal for a particular community.</p>
<p>Source is section 2.6.3 number 15 of requirements document, page 66</p> VegBank - Bug #4488 (New): Freeform entry of new taxonomic concepts.https://projects.ecoinformatics.org/ecoinfo/issues/44882009-10-22T19:15:13ZMichael Leemlee@nceas.ucsb.edu
<p>Particularly focused on communities, but might as well add plants while we are at it. We have some free form entry of people, for example, that would be a good template for how to do this.</p>
<p>Source is section 2.6.1 number 2b of requirements document, page 60</p> VegBank - Bug #4487 (New): Better support for typal plotshttps://projects.ecoinformatics.org/ecoinfo/issues/44872009-10-22T19:15:04ZMichael Leemlee@nceas.ucsb.edu
<p>add 'typal' to view of classifications and include in search fields.</p>
<p>Source is section 2.6.1 number 2c of requirements document, page 60</p> VegBank - 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> VegBank - 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> InfoVeg - Bug #3840 (New): Classification view/import/edit - CONTAINER BUGhttps://projects.ecoinformatics.org/ecoinfo/issues/38402009-02-25T20:26:00ZMichael Leemlee@nceas.ucsb.edu
<p>Bob, Forbes, and I just talked on the phone about classification and there are a few things we would like to do (the following points will all be made sub-bugs):</p>
<p>1) import a large amount of data from our excel spreadsheet tracking classification into the archive database.<br />Forbes will be adding 3 fields to it: 1) date classified, 2) classifiers, and 3) status (0=do not import into archive database, 1=DO import)</p>
<p>2) we need a framework for communities wherein we are placing a plot. This was thought originally to go into commClass and we'd mandate that only communities adhering to this framework could be linked from a classification event. However, we now believe it would be better to put this into commInterpretation, because we may need to classify to a different framework at a higher level (CVS higher levels) when CEGLs do not exist for a plot's community. Field: commInterpretation.cust_cvs_framework_id - reference which describes the classification system used, e.g. Braun-Blanquet, Forest Service Cover Types, US-NVC, or an idiosyncratic system.</p>
<p>3) We need a placeholder for "none of the above" when a plot does not fit into ANY community within a particular framework.</p>
<p>4) The viewer needs to be upgraded to both display and edit/annotate classification information. We want to be able to create a package of updates which can be shipped back and applied to the central archive. Initially this will just be classifications, but eventually it could also include flags of interesting, unlikely, or corrected values.</p>
<p>5) The viewer needs to eventually support building datasets, either selected one-by-one or through a search (all in one project, all with a CEGL, etc.) This dataset needs to be sortable according to one's whim and exportable to Excel.</p>
<p>Bob described a view that would have basic plot info on the left, a species list next to it, and a window to view/edit classification. Another window on the far right would list the dataset plots along with various/configurable data for those plots, which could be clicked and the data on the left updates to match it.</p> VegBank - Bug #919 (New): Advanced IP system, user-specific filtering of datahttps://projects.ecoinformatics.org/ecoinfo/issues/9192002-11-27T21:31:14ZMichael Leemlee@nceas.ucsb.edu
<p>Confidential plots (that is plot with plot.ConfidentialityStatus = 6) must not<br />be viewable in the system. Also not downloadable or queryable. They stay hidden.</p>
<p>The following are the rules for confientiality:<br />values valueDescription<br />0 Public <br />1 1 km radius<br />2 10 km radius<br />3 100 km radius<br />4 Location embargo<br />5 Public embargo on data<br />6 Full embargo on data</p>
<p>0 means that anyone can access all data belonging to the plot.<br />1-3 mean that latitude and longitude are "fuzzed" to some degree so that the<br />user doesn't know exactly where the plot is.<br />4 means that users can't access data from the place table for that plot, as well<br />as the lat/long. LocationNarrative and authorE, authorN, authorLocation in the<br />plot table should also be hidden.<br />5 and 6 mean that users can't access the plot at all - no attributes on any<br />tables.</p>
<p>RealLatitude and RealLongitude should ALWAYS be hidden from the user. Use<br />latitude and longitude instead.</p> VegBank - 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> VegBank - Bug #884 (New): Load database:NY-ESF-1500: DFhttps://projects.ecoinformatics.org/ecoinfo/issues/8842002-11-13T22:02:32ZMichael Leemlee@nceas.ucsb.edu
<p>DF-L?</p> VegBank - Bug #845 (New): Query manager - list of past querieshttps://projects.ecoinformatics.org/ecoinfo/issues/8452002-11-13T21:58:49ZMichael Leemlee@nceas.ucsb.edu
<p>"---"</p>