|
Rank |
Problem |
Solution |
|
1 |
The interpretation of tree features may change; a given fire scar may
be determined to have occured in the spring by one researcher, and the
winter/dormant season by another for example. |
Link any analytical grouping to the feature, not the tree. Contradictions
will be eliminated by selecting one of the competing interpretations as
"preferred". |
|
2 |
The entire domain for certain attributes may be too "busy"
for certain researchers. For example, a researcher X is only interested
in tree species from Arizona. They would be overwhelmed by being given
a list of every species that have ever had dendrochronological research
performed on them. |
Create "profiles" that a user may join. Allow users to create
their own profiles. |
|
1 |
Researchers may want to enter their data to the system, but not make
it available to the general public while they are working with it. |
Provide a "publish" option for sample features, tree features
and events, grouped and referred to by a "reference". Implement
"Groups" whith different permissions to data. |
|
1 |
Researchers are interested in data assigned to "Sites" which
are indeterminant geographic areas. Sites may contain other sites and/or
overlap other sites. |
Group by features, and give the group the name of the "Site".
Provide note attribute to more fully describe site, allow group (s) to
be attributes of a reference. |
|
1 |
The terms "tree" and "sample" are sometimes used
interchangbly. Often, only one sample is taken from a tree, which is where
the ambiguity comes from. |
Provide separate tables for both, and require strict adherance to both.
Give options to automatically propagate entries in one from the other. |
|
|
1 |
Current names for samples & trees are not unique. The same tree/sample
may be renamed. |
Assign unique names, allow for alternate names of the tree/sample in
reference groups. |
|
2 |
People want to enter the location data for trees, and be able to map
it immidiately. |
ArcSDE, ArcGIS |
|
2 |
People will want to add additional layers (coverages, shapefiles, etc.)
to their view of the tree location data. |
ArcSDE, ArcGIS |
|
1 |
If more than one reference contain references to the same tree and event
features, and one of those features are updated, does the update get cascaded? |
Implement a "preferred" attribute for tree features, sample
features and events. Don't cascade, but allow people the option of selecting
the original or most current version of the data to use in the reference. |
|
1 |
FHX files abound. Many are duplicates, or at least contain duplicate
information. How do you discover what is original, and what is duplicated? |
Copy all the files to a single CD. Create a program to process different
levels of similarity between files, and generate reports. Go through and
pitch or import the files. |
|
1 |
Future reanlysis of wood may look at different features. |
Allow tree features to be expanded. |
|
1 |
Researchers may find a measure of interpretation "confidence"
helpul while they are first working with their data. |
Add "confidence" attribute to tree features, sample features
and events. |
|
2 |
In the case of some features for sequoia, there will be a desire to
automatically identify inconsistencies between samples from the same tree,
and to automatically generate events. |
Create a tool to aid in data entry. |
|
1 |
Some researchers may ultimately be interested in "events",
others will be interested in the underlying tree features used as proxies
of the event. |
Allow researchers the option of searching for both events and features. |
|
1 |
More than one programmer will be working on similar projects. |
Create code repository (SourceForge). |
|
2 |
The location of trees will need to be entered in multiple projections. |
Use software to reproject before entering into database. See GeoTransform |
|
2 |
User groups (and hence users) must have different permissions (r/r&w/0)
for References. Permissions should cascade to feature groupings, and group
tree features and group events. |
Implement UserGroup tables for tracking permissions and membership. |
|
2 |
User groups (and hence users) must have different permissions (r/r&w/0)
for Events. Permissions should cascade to Event evidence. |
Implement UserGroup tables for tracking permissions and membership. |
|
2 |
User groups (and hence users) must have different permissions (r/r&w/0)
for Tree. |
Implement UserGroup tables for tracking permissions and membership. |
|
2 |
User groups (and hence users) must have different permissions (r/r&w/0)
for Tree features. Permissions should cascade to Tree Feature evidence. |
Implement UserGroup tables for tracking permissions and membership. |
|
2 |
User groups (and hence users) must have different permissions (r/r&w/0)
for Samples. |
Implement UserGroup tables for tracking permissions and membership. |
|
2 |
User groups (and hence users) must have different permissions (r/r&w/0)
for Sample features.. |
Implement UserGroup tables for tracking permissions and membership. |
|
2 |
The same tree may be referred to by different names in different references. |
Use reference specific names in References that track to the unique
database name. |
|
2 |
A species may be taxonomically lumped, and then re-split. |
Keep the original (author supplied) name. Map to a 'preferred' name.
As names change, just change the mapping. |
|
2 |
More than one coding convention exists for species. |
Associate codes with a coding system as well as species. |
|
2 |
|
|
|
2 |
|
|
|
2 |
|
|