Activity
From 12/31/2007 to 01/29/2008
01/21/2008
- 05:46 PM Bug #2848: (migration) Ensure unique plot names b/t EEP and CVS plots
- this now works fine, entry tool, migration, and archive DB (See versions mentioned in an earlier comment today).
- 03:34 PM Bug #2848: (migration) Ensure unique plot names b/t EEP and CVS plots
- now in entry tool interface (CVS_EEP_DataEntryTool_v222p0121_mid2)
- 03:24 PM Bug #2848: (migration) Ensure unique plot names b/t EEP and CVS plots
- done in migration tool, too:
cvs_migration_vb13_p0121
Still needs more thorough test and integration into entry tool... - 03:10 PM Bug #2848: (migration) Ensure unique plot names b/t EEP and CVS plots
- archive database updated, version:
cvs-eep-archive_v1_0_9_COR_2008_01_21 - 03:07 PM Bug #2848: (migration) Ensure unique plot names b/t EEP and CVS plots
- entry tool has the new field in project: version CVS_EEP_DataEntryTool_v222p0121_post
- 02:48 PM Bug #2848: (migration) Ensure unique plot names b/t EEP and CVS plots
- I think solution 2a) is by far the simplest, which is to add a prefix to projects for one of CVS or EEP. CVS only us...
- 02:52 PM Bug #3025: improve reporting mechanism in entry tool
- We need to incorporate Steve's suggestions, which are (excerpts from Jan 10, 2008 email):
... tables pertaining to v... - 02:17 PM Bug #3025: improve reporting mechanism in entry tool
- this was sent out to Steve.
01/12/2008
- 12:26 PM Bug #3064 (Resolved): DBA: check that plot names match project code
- SQL to accomplish that:
SELECT project.projectName, project.entry_projectCode AS [project Code], observation.authorO...
Also available in: Atom