Define Traits and record Measurements

Traits are shared variable definitions; Measurements are their values recorded for Locations, Taxons, Individuals, Vouchers, or Media. Define the Trait before collection, because changing its meaning after others use it can invalidate data. For ownership, curator permissions, duplicate consolidation, statuses, and translation tools, see Trait governance and curation.

Before creating a Trait

Search name, export_name, unit, and definition; select the measured object; describe method, instrument, position, precision, and protocol; reuse a unit with the same meaning; cite the protocol when applicable; and define validation rules. Similar names and units do not guarantee equivalent methods. The unique export_name should be stable, short, and contain no spaces or accents.

Choose the type

• Quantitative real: decimal measurements, normally with unit and range.
• Quantitative integer: counts and other integers.
• Categorical: one unordered category.
• Categorical multiple: several simultaneous categories.
• Ordinal: one category whose rank represents order.
• Text: observations that should not be categories.
• Color: a validated hexadecimal color.
• Link: a Taxon or Voucher, optionally with an associated count.
• Spectral: a value vector with a defined expected length.
• GenBank: a molecular accession linked to an Individual or Voucher.

Categories need stable meanings, descriptions when necessary, and consistent translations. Rank is part of an ordinal Trait’s definition. Do not encode a genuinely quantitative measurement as numbered categories.

Record and review Measurements

Every Measurement identifies its Trait, measured object, responsible Person, date, and access-controlling Dataset. Add a Reference for values extracted from publications. Before a bulk import, create one Measurement in the interface, test validation and object type, submit pilot rows, review the UserJob, reconcile returned IDs, and GET the result to verify value, date, Person, and object.

See importing Traits with R and importing Measurements with R.

Use forms

Web forms arrange Traits and required fields. A Form Task applies the protocol to target objects and tracks what remains unmeasured. Mobile forms supply OpenDataBio Collect with protocols, Taxons, objects, geolocation, photographs, and offline measurement fields. Define Dataset, Traits, units, and categories first; assign users; test a few objects; synchronize; and review Measurements, coordinates, Media, and logs before full deployment.

Changes after use

The creator can edit a valid Trait while it is unused or used only in Datasets where the creator is an administrator. Trait curators can maintain the public library globally. Categories already used in Measurements require a curator to redefine or reorder them. Coordinate cross-user corrections through the governance workflow instead of silently changing a shared concept.