Activity
From 06/01/2004 to 06/30/2004
06/28/2004
- 10:50 AM Bug #1612 (Resolved): add new comms for CO plots and link
- Part of NatureServe/Heritage contract
- 10:49 AM Bug #1611 (Resolved): Data Ready: Load plots: NS/Hrtg:New York: 250 : Tim Howard
- Part of NatureServe/Heritage contract
- 10:49 AM Bug #1610 (Resolved): lift VA Heritage data embargo
- Part of NatureServe/Heritage contract
- 10:49 AM Bug #1609 (Resolved): Data Ready: Load plots: NS/Hrtg:Minnesota: 250
- Part of NatureServe/Heritage contract
- 10:48 AM Bug #1608 (New): Load plots: NS/Hrtg: Nebraska: 1500
- part of NatureServe/Heritage Contract
- 10:46 AM Bug #1607: Load Plots: Arctic releves
- Need to ask permission, which shouldn't be hard to get
- 09:02 AM Bug #1607 (New): Load Plots: Arctic releves
- Mike Jennings found this pile of plots which is currently available online. Do
we have to ask these folks before we... - 10:45 AM Bug #903: Data ready: Load database:Walker - LTER-300
- Michael needs to email Joy and Marilyn and check status
- 10:37 AM Bug #900: Load database:Cal range monitoring - USFS-700
- decided we didn't know what these plots were in June 14,15 meeting in Chapel Hill
- 10:37 AM Bug #899: Load database:Nevada range monitoring USFS-800
- decided we didn't know what these plots were in June 14,15 meeting in Chapel Hill
- 10:37 AM Bug #898: Load database:Oregon range monitoring USFS-400
- decided we didn't know what these plots were in June 14,15 meeting in Chapel Hill
- 10:37 AM Bug #897: Load database:CAL serpentine - USFS-?
- decided we didn't know what these plots were in June 14,15 meeting in Chapel Hill
- 10:37 AM Bug #896: Load database:Cal ecology - USFS-?
- decided we didn't know what these plots were in June 14,15 meeting in Chapel Hill
- 10:37 AM Bug #894: Load database:OR - Heritage-1000
- decided we didn't know what these plots were in June 14,15 meeting in Chapel Hill
06/15/2004
- 01:20 PM Bug #1222: Develop Mock-up of Prosal-Peer Review machine
- done, and handed to Xianhua, who is working on it
06/11/2004
- 04:28 PM Bug #764: Develop a system to export Vegbranch compatible data
- The zipped UTF-16 encoded CSV import file which contains plots selected from the
plot query display page can now be d...
06/05/2004
- 04:27 PM Bug #1220: Need systematic approach to viewing all data in database
- Apache's powerful URL rewriting capabilities gives us lots of options here. For one, I'd prefer to keep
the script ...
06/03/2004
- 10:20 AM Bug #780: Email and show online deposit receipt; (option of long or short format?)
- need to also provide user with file that updates his/her VegBranch
accessionCodes with new VegBank accession codes so... - 09:10 AM Bug #807: Interpret taxon in extant plot
- This can be done without CRUD, but eventually we will need to add it for weird
interpretations. This can be a 2 step... - 07:48 AM Bug #1220: Need systematic approach to viewing all data in database
- Perhaps this bug is unclear. We need a way to view any data in the database by
simply calling a URL and perhaps a se... - 07:43 AM Bug #804: Interpret community in extant plot
- depends on CRUD
see example: http://tekka.nceas.ucsb.edu/~lee/forms/interpPlotToComm.html
There must be a link to th... - 07:04 AM Bug #1374: Get adding plant and adding community forms working with new model
- depends on CRUD
see example here:
http://tekka.nceas.ucsb.edu/~lee/forms/addNewPlant.html - 07:03 AM Bug #764: Develop a system to export Vegbranch compatible data
- In order for this bug to be closed, we need to have the XML output styled and a
new option for downloading plots: as ...
06/02/2004
- 06:29 PM Bug #807: Interpret taxon in extant plot
- not really Nov1, but sooner than other bugs
- 06:29 PM Bug #764: Develop a system to export Vegbranch compatible data
- not really Nov1, but sooner than other bugs
- 06:29 PM Bug #1374: Get adding plant and adding community forms working with new model
- not really Nov1, but sooner than other bugs
- 06:29 PM Bug #804: Interpret community in extant plot
- not really Nov1, but sooner than other bugs
06/01/2004
- 11:22 AM Bug #1220: Need systematic approach to viewing all data in database
- Per the initial request, I'd say this bug can be closed. We have the
GenericDispatch action which works well, labele...
Also available in: Atom