Data Model - Administration

---

Program

Strategy

Sampling scheme

Sampling strata (denormalized)

User expertise area

Users

---

Details

Program

• Program is the entity that holds a data collection project (e.g. a scientific project, a UE project, ...).

• A Program describe the project (label, name, description);

  • Each program has one or more strategies;

• A program manages access rights by users (ProgramPerson) or departments (ProgramDepartment), and can declare monitored locations (Program2Location).

Strategy

• A Strategy holds one data collection protocol. Typically, it define all parameters (PSFMU) that should be collected.

  • Each collected parameters is collected inside a acquisition level (e.g. on Trip, on Operation, on Landing, ...)

• Forthcoming:

  • A strategy is applied on one or more period and on one or more locations.

This concept of program / strategies allow us to generate all the fields that user can fill in screens, and also all applied controls (min/max, type). This is part the generic aspect of SUMARiS tools.

Strategy application

An AppliedStrategy is a Strategy applied on locations and periods (AppliedPeriod). It refines the sampling plan through AppliedSamplingStrata, and details the collected parameters via PmfmStrategy and PmfmAppliedStrategy (acquisition level, mandatory flag...). Restrictions to taxa and taxon groups are expressed by ReferenceTaxonStrategy, TaxonGroupStrategy and TaxonGroupSamplingStrata. A strategy is also applied by departments (StrategyDepartment).

Sampling scheme

A SamplingScheme organizes the sampling operations of a program (e.g. survey, observer program).

Sampling strata (SamplingStrata) can carry their own measurements (SamplingStrataMeasurement) and validity periods (SamplingStrataAppliedPeriod). AcquisitionLevel identifies the level (e.g. Trip, Operation, Landing) on which parameters are collected.

Sampling strata (denormalized)

DenormalizedSamplingStrata is a flat, pre-computed copy of the sampling strata, used for fast reporting.

User expertise area

The expertise areas define the users' activity zones. The local language translation of the repository lists (species, profession, equipment, etc.). Combined with regionalization, it is then possible to restrict the repository lists to display only the relevant elements for the user's region.

Users

Users belong to a department (Department); user profiles (ADMIN, USER, SUPERVISOR, GUEST) control program access.

• Each user has persistent settings (locale, map preferences) and authentication tokens (pubkey, expiration date), as children of Person.
  • The user profile itself is stored in UserProfile (ADMIN, USER, SUPERVISOR, GUEST).

Besides authentication tokens (UserToken), each person owns persistent settings (UserSettings): locale, map preferences, table settings, etc.

A ProgramPrivilege grants a program-specific privilege (e.g. observer, recorder) to a person.