A Triage Method for Uncategorized Media Items
A reliable triage process confirms scope, source, item identity, relationships, required metadata, and destination before assigning a category.
In short: Process uncategorised items through six gates: collection scope, authorised source, item identity, work/version relationship, minimum metadata, and destination rule. Assign a category only when the evidence supports it. Send missing, conflicting, duplicate, or rights-related cases to named review queues rather than a permanent miscellaneous bucket.
An uncategorised item is a symptom. The cause may be a new media type, missing metadata, unclear source, duplicate relationship, or a category rule that no longer fits. Triage should reveal that cause before editing.
Gate 1: confirm collection scope
Ask whether the item belongs in the current phase by media type, source, household use, language, time boundary, and active/archive rule.
If out of scope, leave it unchanged or route it to a documented future review. Do not create a new category merely to absorb one exception.
Gate 2: confirm source and authorisation
Record the compatible source and verify that the user owns it or is legally authorised to use it. If source identity or authorisation is uncertain, stop classification and assign an owner to resolve it.
Never place credentials, tokens, or private source addresses in the triage sheet.
Gate 3: establish item identity
Record the title, media type, date or year where available, and a stable source identifier. Distinguish:
- film versus episode;
- work versus exact version;
- collection versus member;
- media item versus metadata-only card;
- available versus unavailable source version.
Do not infer identity from artwork alone.
Gate 4: check relationships and duplicates
Search the catalogue for matching identifiers, titles, dates, sources, versions, and languages. Use three states:
- confirmed relationship;
- possible relationship needing review;
- distinct item.
Matching titles alone do not prove a duplicate. Preserve both candidates until version and source evidence is sufficient.
Gate 5: verify minimum metadata
Apply the pre-import metadata rules. Required values should support a findability or maintenance task. Allow explicit unknown, absent, not applicable, and conflict states.
If a value is missing, do not guess. Route it to a metadata queue with the evidence needed and person responsible.
Gate 6: apply a destination rule
A category should have a stable definition that another maintainer can apply. Check:
- inclusion rule;
- exclusion rule;
- relationship to other categories;
- active or archive status;
- source dependency;
- household findability task served.
When no existing rule fits, record the item in “category design review.” Do not create a live category until several real items or a clear near-term need justify it.
Use separate exception queues
Keep distinct queues for:
- metadata missing;
- duplicate or version review;
- source or access review;
- rights or authorisation review;
- out of scope;
- category design;
- technical error.
One “miscellaneous” queue hides the action needed. Give every queue an owner, evidence requirement, and review cadence.
Original evidence: six-gate triage card
| Gate | Evidence | Result | Next action |
|---|---|---|---|
| Scope | Pass / Review | ||
| Source/authorisation | Pass / Review | ||
| Identity | Pass / Review | ||
| Relationships | Pass / Review | ||
| Minimum metadata | Pass / Review | ||
| Destination rule | Pass / Review |
Process ten representative items. Record how many pass directly, which queue receives each exception, and which rule causes repeated ambiguity. Feed the baseline from the pre-cleanup audit into this card.
Improve the rule, not just the queue
After one batch, review recurring causes. If several items fail the same gate:
- clarify scope;
- add a supported metadata mapping;
- define a version relationship;
- split an overloaded category;
- change intake rules;
- document a source limitation.
Update the complete cleanup plan before scaling. For categories that become empty after valid reclassification, use the empty category cleanup guide.
Common mistakes and limitations
- Creating a category for every exception.
- Guessing missing metadata.
- Treating matching titles as duplicates.
- Mixing rights review with ordinary categorisation.
- Keeping one permanent miscellaneous bucket.
- Processing large batches before validating the gates.
- Hiding unavailable items instead of preserving status.
Source metadata can be incomplete or inconsistent. Norva can organise and group variants from a compatible authorised source, but it cannot guarantee upstream data completeness.
Frequently asked questions
How many uncategorised items should I process at once?
Use a batch small enough to inspect and review, but varied enough to reveal common exception types. Ten to twenty may be a practical pilot, not a universal rule.
Is “Other” a valid category?
Only when it has a clear stable meaning and retrieval purpose. It should not become a substitute for unresolved triage.
What if no category fits one valid item?
Place it in category design review. Decide whether the item is out of scope, archival, or evidence that a new category serves a repeatable need.