Kingdom profiles
Animal and plant in one system
No product in the sector covers both. The ones that exist were built for one and carry that origin: asking a seed bank to record "donors" is as useless as asking a semen bank to record "accessions".
One core, two vocabularies
Akervo models once what both share — where material comes from, what is held, in which container, what has happened to it — and projects that core into each kingdom's language. A bank picks its own at sign-up and the whole application speaks it. No neutral vocabulary appears on any screen.
| Concept | Animal profile | Plant profile |
|---|---|---|
| Material source | Donor, with ear tag, microchip or tattoo | Source population, with its collecting site |
| Conserved unit | Sample: semen, embryo, oocyte, cell | Accession: seed, pollen, in vitro tissue |
| Classification | Species → breed → line | Species → variety, cultivar or landrace |
| Container and measure | Straw, vial, goblet → doses | Packet, jar, tube → seeds or grams |
| Intake | Collection, follicular aspiration | Harvest, collecting mission |
| Conditioning | Cryopreservation: technique, diluent, cryoprotectant | Drying and cleaning, then freezing |
| Testing | Health screening, one-off | Germination, recurring and scheduled |
| Replenishment | New collection from the same donor | Field regeneration |
Two things the plant profile needs and the animal one does not
Regeneration
A seed accession runs down, and every few years it has to be multiplied in the field before it is lost. It is a full cycle — sowing, harvest, new lot — producing a different container that keeps the identity of the same accession. Nothing in the animal domain has that shape, and a system built only for animal has nowhere to put it.
Scheduled testing
In animal, health status is established once and travels with the material. In plant, the germination test repeats on a cadence, and it is what triggers regeneration. That is why testing is scheduled against the container and not the accession: two packets of the same accession put away five years apart share neither viability nor calendar.
Hanging the test off the accession instead of the container is the shortcut that makes a plant profile unusable. It shows up late: when a collection has gone years without being checked and nobody finds out until it is needed.
Why one product rather than two
Mixed banks are rare, so the kingdom is chosen once per bank and stays fixed. What a shared core buys is not saved code: it is that the capabilities which do not depend on kingdom — inventory, requests, audit, reporting, deployment — are built and maintained once, and both communities get the same improvements.