VegBank: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362002-08-16T22:01:31ZEcoinformatics Redmine
Redmine Bug #562 (Resolved): First Name and Last Name fields reversed on AutoFillhttps://projects.ecoinformatics.org/ecoinfo/issues/5622002-08-16T22:01:31ZMichael Leemikelee@unc.edu
<p>The First Name field for me comes up Lee and Last Name as Michael (unless the <br />error is in my record in the user database).</p> Bug #560 (Resolved): purchase and set up tape backup for vegbankhttps://projects.ecoinformatics.org/ecoinfo/issues/5602002-08-15T19:54:10ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to locate funds for a tape backup for vegbank and purchase. When completed,<br />either John, Mark, or Colby can set it up on the server.</p> Bug #559 (Resolved): manage vegbank.org domain at NCEAShttps://projects.ecoinformatics.org/ecoinfo/issues/5592002-08-15T19:42:04ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to move the vegbank,org DNS servers so that they are managed at NCEAS<br />rather than at the current ISP. Matt and Mark will start the setup for this at<br />NCEAS, and when the technical infrastructure is in place John will submit the<br />changes at Verisign to switch the name servers.</p> Bug #447 (Resolved): function to allow user to see the plots insert results via browserhttps://projects.ecoinformatics.org/ecoinfo/issues/4472002-03-21T22:07:01ZJohn Harrisharris@nceas.ucsb.edu
<p>right now when the user uploads files to the server and requests that they be <br />inserted there is no recipt showing the results of the database insertion <br />process. This funcrtion is critical b/c there is no application validation <br />layer and the user does not really know if the plot(s) has successfully be <br />inserted to the database</p> Bug #135 (Closed): Implement a prototype veg plots DBhttps://projects.ecoinformatics.org/ecoinfo/issues/1352000-09-22T16:04:03ZJohn Harrisharris@nceas.ucsb.edu
<p>Implement, using the design modifications made during the September 2000 <br />meetings, a veg plots database.</p> Bug #134 (Closed): Implement a prototype plant taxon DBhttps://projects.ecoinformatics.org/ecoinfo/issues/1342000-09-22T15:49:44ZJohn Harrisharris@nceas.ucsb.edu
<p>Develop a plant Taxon Database, using the plants 1996/2000 data and the <br />assumptions made by Peet, to interface with the plots database prototype. <br />Currently, Bob this seems to be a high priority job by Bob - I think that he <br />would like to have this implementation by the November meetings.</p> Bug #133 (Closed): Prepare a ERD for the taxon component NVC databasehttps://projects.ecoinformatics.org/ecoinfo/issues/1332000-09-22T15:44:51ZJohn Harrisharris@nceas.ucsb.edu
<p>This diagram should reflect the current thinking of: Taswell, Jones, Peet and <br />Harris and should allow for interaction with the plots database. This diagram <br />will be used in the taxonomy meetings in early November for discussion about how <br />to track changes in taxonomy.</p> Bug #132 (Closed): Prepare Tecnical Planning Document For October 15thhttps://projects.ecoinformatics.org/ecoinfo/issues/1322000-09-22T15:04:58ZJohn Harrisharris@nceas.ucsb.edu
<p>Write a technical report detailing the data model(s) for the plots database and <br />possibly the taxon database. This will include a web site as well as a more <br />printer friendly version.</p> Bug #108 (Closed): Design/develop a web site to support the Veg Plot Database Projecthttps://projects.ecoinformatics.org/ecoinfo/issues/1082000-08-30T17:33:57ZJohn Harrisharris@nceas.ucsb.edu
<p>Design a web site to support the development of the Veg Plot Database project. <br />This should include at the mimimum:</p>
<p>- General info about the project<br />- Documentation about the data model<br />- Database requirements<br />- Working examples</p> Bug #107 (Closed): Veg Plots Table Problems on Oracle (dev)https://projects.ecoinformatics.org/ecoinfo/issues/1072000-08-26T00:56:39ZJohn Harrisharris@nceas.ucsb.edu
<p>Currently having difficulty writing to Oracle DB on dev.nceas.ucsb.edu. The <br />java/JDBC app writes to the DB fine sometimes while other times stops for long <br />periods. The record that the app stops on is never constant.</p> Bug #106 (Closed): Loaders for prototype data into prototype DBhttps://projects.ecoinformatics.org/ecoinfo/issues/1062000-08-25T17:51:03ZJohn Harrisharris@nceas.ucsb.edu
<p>Write scripts to load data into the prototype database. The first script should <br />be for loading TNC PLOT DATA into the prototype database because this data is in <br />the most resaonably organized format.</p> Bug #105 (Closed): Obtain prototype data and explore data type and formatshttps://projects.ecoinformatics.org/ecoinfo/issues/1052000-08-25T17:28:30ZJohn Harrisharris@nceas.ucsb.edu
<p>Get prototype veg plot data from:<br /> TNC PLOTS DATABASE (contact: Jim Drake)<br /> USFS (contact: Jennings)<br /> individual plot data (contacts: M. Walker and B. Peet)</p>
<p>Also get some examples of 'split' and 'lumped' plant species as well as the USDA <br />plants database.</p> Bug #104 (Closed): Obtain Example Database Querieshttps://projects.ecoinformatics.org/ecoinfo/issues/1042000-08-25T17:18:59ZJohn Harrisharris@nceas.ucsb.edu
<p>Obtain, from the ecologists, possible example queries which will be sent to the <br />database. These will be used to test various aspects (including performance and <br />viability) of the prototype database.</p> Bug #103 (Closed): Convert the ER Model to a relational schemahttps://projects.ecoinformatics.org/ecoinfo/issues/1032000-08-25T17:13:10ZJohn Harrisharris@nceas.ucsb.edu
<p>Convert the updated ERD to SQL for prototype database implementation. This <br />will, of course, be an iterative process because the ERD will be a dynamic <br />document until this fall. Obtain Visio 2000, which has a direct translation <br />between the ERD and the SQL.</p> Bug #102 (Closed): Complete proposed ERD - for September meetinghttps://projects.ecoinformatics.org/ecoinfo/issues/1022000-08-25T16:21:29ZJohn Harrisharris@nceas.ucsb.edu
<p>Finish the ERD for the September Meeting for review by the visiting <br />technologists. This diagram should be in place before the arrival of the <br />ecologists, and then should be updated during the first part of the week (week <br />of September 11th) so that it remains consistent with the updated data <br />requirements and fields document (aka the Damman document). Keep in mind that <br />the data model is currently scheduled for October 15th.</p>