GDPDM pending issues as of April 25, 2005.
---------------------------------------------------


- How do we need to handle "phase determined"?  This was
  a field in the div_allele_assay table, but phase matters
  over mulitple assays.

- Need to evaluate the definition of field quality in
  table div_allele.  We may want to have a table
  that constrains quality_type?

- Do we need a parent_id field in the div_allele table?
  This would identify the raw data used to determine
  the allele.

- Need to make sure assignment of required/not required
  fields are appropriate.

- Do we need something to code crosses in the
  div_passport table?

- Should there be a way to keep track of "dominant
  allele_assays?"

- Should there be a way to record reference data?

- Consider having div_passport point directly to
  div_locality instead of going through
  div_accession_collecting.  This is in case there
  is no collection information.

- How do we handle synonyms with biological confidence
  at the passport level?

- How do we handle primer nomenclature?

- How do we store alleles to indicate not tested,
  no reaction, not detected, etc. ?

- Is foreign key div_locality_id required?  in div_obs_unit?
  in div_accession_collecting?

- rename cdv_marker to cdv_ref_genomic_sequence?
  many to many relationship between div_marker and
  div_map_feature?

- consider moving position and length to marker,
  and dropping the ref seq information from 
  allele_assay.

- for consistency and ease of use, should we convert
  all comments fields to "comments."
  (e.g. div_passport.remarks, div_stock.remarks,
  div_synonym.remarks, div_obs_unit.summary)

- Should field div_stock.seed_lot be required?

- Should div_experiment also group allele assays?

- Should div_passport.source be changed to required?

- Do we need fields to manage owner of records?