Migration 1.0 → 1.1

database structure 1.1

pictures are now stored in notes, category '<picture>', they get their own field.

migrating, category '<picture>' notes are stored in picture field and removed from the notes.

<empty>, I, II, III, now stored in notes, category 'CITES'.

taxa have a 'cites' property that is computed from the 'CITES' note of itself, or the nearest ancestor taxon. it becomes a database field.

on creation of a taxon, the cites field is initialized from the value in the parent taxon, the user can override this.

migrating data, the current computed cites property should be copied into the new field.

like CITES, currently not supported by the software. values can be hard coded, since they implement an international agreement.

Extinct (EX) – No known individuals remaining
Extinct in the wild (EW) – Known only to survive in captivity, or as a naturalized population outside its historic range
Critically endangered (CR) – Extremely high risk of extinction in the wild
Endangered (EN) – High risk of extinction in the wild
Vulnerable (VU) – High risk of endangerment in the wild
Near threatened (NT) – Likely to become endangered in the near future
Least concern (LC) – Lowest risk; does not qualify for a higher risk category. Widespread and abundant taxa are included in this category.
Data deficient (DD) – Not enough data to make an assessment of its risk of extinction
Not evaluated (NE) – Has not yet been evaluated against the criteria.

it is not inherited from parent taxon.

migrating, it will initialized with 'NE'.

provenance stays hard coded content, but we review it, from accession.prov_type_values.

it goes from dictionary to list of pairs (so we can define the order).

for wild plants, there is a further specifying option contained in accession.wild_prov_status_values.

we want further specifying options for other provenance types.