jen-thomas/wildlife-observations

Django project for recording observations of wildlife at different sites

wildlife-observations's Issues

Reports

Identifications and observations

• Number of each species
• Total number of observations
• Total number of observations of each suborder
• Total number of identifications, perhaps split by multiple identifications of observations
• Total number of observations identified to species and confirmed in some way (confidence = confirmed or yes)
• Total number of observations identified to species and still to check or confirm in some way (confidence = redo, check, in progress, review)
• List of the observations that do not have an identification (have the list with a direct link to the observation / create the ID easily)

Add notes field to visit model

Make observation and photograph a many to many

Initially, the photograph model had a foreign key to an observation but there are some photographs which show more than one observation, therefore this needs changing to a many-to-many relationship.

Correct unique constraints in models

Set up database backups

• backup database to local computer (daily)
• backup database to remote location (daily)
• have command to be able to backup database manually

Add habitat model and foreign key to this model from Site model

The habitat of each site should be classified using a source.

Model:

• habitat type
• source

Add documentation for each model

Correct importer for test data

Whilst building the data importers, several models were changed or improved slightly. The importer of test data needs correcting to be able to work, still.

Deal with foreign keys in admin

Add validation that the specimen ID contains the same details as the visit and survey from which it was obtained

The specimen ID is formed of the following parts:

• site name (in the format area0X where X is the number, with all of this together forming a unique site name)
• date of visit (in the format yyyymmdd)
• method and repeat of survey (N for net, H for hand and 1 or 2 for the repeat)
• suborder of specimen (C for Caelifera, E for Ensifera)
• number of specimen within the suborder for that survey (in the format XXX where a number is padded with zeros to make it three digits)

An example would be: TOR01 20210915 N1 C001

It would be helpful if there could be some kind of validation that the name of the specimen ID meets the same details as the visit and the survey, as well as being unique. Alternatively, the specimen ID could be constructed from the metadata (although this would perhaps then require that all of the specimens are created before adding a random identification).

Add notes field to survey model

Create importer for data already in spreadsheets

• Sites
• Visits
• Surveys
• Observations
• Identifications

Change display format of date in admin view of visit

Display date in yyyy-mm-dd format, instead of

Add latin name of species in taxonomy species table to species name model automatically

All species should have a latin name, but will not necessarily have an English name or such in another language. It would be helpful to populate this automatically such that the species can be chosen from the list of species for an identification.

Import existing data

• Sites
• Visits
• Surveys
• Observations
• Identifications

Add species to database

Add validation to sum percentage covers to 100 in vegetation structure

There are some measures of ground cover which should add up to 100 within the one set of measurements for a row in the vegetation structure model.

Add validation to make sure this number is always reached if there is a value entered into one of these variables:
percentage_vegetation_cover
percentage_ground_cover
percentage_bare_rock

Set up project in Pycharm

Changes to identification model

• allow date of identification to be nullable
• add notebook field

Constraint for repeat number

A survey can be done using different methods. Sometimes, this method is used more than once at a particular site. In this database, this is referred to as a repeat (although in statistical terms, it is not strictly so). The first time a method is used at a site during a particular visit, this is called repeat 1. The second time it is used during a visit, it would be repeat 2.

Add constraints to the database to ensure that a repeat 2 cannot be entered if a repeat 1 has not yet been entered for a particular visit.

Change display format of start and end time of a survey in admin view

Display date in hh:mm:ss format rather than

Create script to import example database

Sometimes when testing it is useful to be able to have a database with some data in that can be reimported after dropping the current database, rather than having to enter everything again from scratch.

Show only surveys that have not had met conditions entered, in the dropdown in admin view

When a survey has already had met conditions entered, do not include it in the drop-down list that is presented to the user when adding a new set of met conditions (this would save time for the user to avoid them entering it, only then to be presented with an error message saying it has already been done).