Skip to content
finwave Docs

Browsing Individuals

What you’ll learn

Section titled “What you’ll learn”
  • Where the individuals list lives
  • What each column shows and how sorting works
  • How the search filter behaves
  • What you can do from the row-actions menu

The list view

Section titled “The list view”

Every population has an Individuals page that lists every cataloged animal. Reach it from the population sidebar — Individuals → Browse in the standard navigation, or from any administrative drilldown into the population.

The page is a single sortable table with a search filter at the top right. It is intentionally simple; the deep stuff lives on each individual’s profile page.

Columns

Section titled “Columns”
ColumnWhat it shows
IdentifierThe primary identifier for the animal. Click to open the edit drawer.
Alternate IDsAny other identifiers this animal goes by, joined with ” / ”. Used by other research groups, legacy catalogs, or external databases.
SexA coloured badge — Male, Female, or ”—” for Unknown.
BirthThe recorded birth year, if known. The full date is editable on the profile but only the year shows in the list.
DeathRecorded year of death, if known. Same display rule as Birth.
(no header)The row-actions menu — see below.

Every column is sortable. The Identifier column uses natural sort — the kind of sort that puts CA2 before CA10 instead of treating them as strings — so identifier-prefix conventions like T049 / T049A / T049A2 come out in the right order.

Searching

Section titled “Searching”

A single free-text search box filters the list as you type. It does a case-insensitive substring match across:

  • Primary identifier
  • Every alternate identifier on the animal

So searching T049 matches any animal whose primary identifier or an alt ID contains T049. Searching Bigg matches anything mentioning that prefix in either field.

There are no quick-filter chips for sex, status, evidence tier, or cohort — those slice into the data via Workbench analyses rather than the list view.

Pagination

Section titled “Pagination”

The default page size is 25 rows. Options are 10, 25, 50, 100, and 500. Page size is remembered for the current session via the table component’s defaults.

Identifier validation

Section titled “Identifier validation”

If your population has the Pro identifier verifier enabled, the edit drawer’s identifier field shows a live validation indicator as you type — a ✓ check when the value matches your population’s identifier convention, or an error icon with the rule it violated. The list view itself doesn’t render the indicator; it surfaces only inside the edit form.

Row actions

Section titled “Row actions”

The more_vert icon at the end of each row opens a menu with these options. Availability depends on your role.

  • View Profile — navigates to /individuals/{id}, the profile page with sighting history, relationships, and image management.
  • Edit — opens the inline edit drawer for this animal. You can change identifier, sex, dates, alternate IDs, and notes. Changes propagate to the underlying catalog record.
  • Set Hero Image — pick which image represents this animal in catalog views. Only Professional and Administrator roles see this option.
  • Delete — permanently removes the individual record. Administrator-only. Annotations referencing this animal become orphaned; consider merging instead when two records turn out to be the same animal.

There are no bulk-select operations in the list. Every action is per-row.

Click-through to profile

Section titled “Click-through to profile”

Clicking the identifier text on a row opens the edit drawer (for in-line metadata changes). Clicking View Profile in the row-actions menu navigates to the full profile page. The two are deliberate — the inline edit is for quick fixes; the profile page is for review, sighting history, and management actions like merging and image curation.

Permission notes

Section titled “Permission notes”
  • Anyone with population membership can view the list.
  • Editing identifier / metadata is gated to Professional and Administrator on the API side; the drawer shows the controls regardless and the save will fail with a permission error if your role isn’t sufficient. Most teams configure roles so this isn’t ambiguous in practice.
  • Deleting an individual is Administrator-only.

For the full role matrix, see Roles & Permissions.

Section titled “Related”