Guide
How to record problems, hides, and alerts
How to record problems, hides, and alerts: on an open session, add a problem, then add one or more hide components. Each component picks a named source from the kit or names a new one; source tags live on that source.
Terrain, distraction, and negative tags plus notes are per hide. Indication and alert fields come from the problem indication/alert schema (neon/003_problem_indication_alert.sql).
Hide components and sources
Source material, placement, and terrain catalogs ship 10, 9, and 10 fixed options (src/lib/types.ts). Training focus prefs can highlight which of those you are working this week.
- Named sources (for example Becky or Blood Tin) persist on the account kit.
- Per-hide tags and notes stay on that component, not on the whole session.
Indication and alert outcomes
When the dog shows, record indication and alert fields on the problem. The product stores what you enter; it does not score or certify the find.
Limits
Outcomes are a log, not a judge.
- There is no automatic pass/fail against a certifying body.
- CalTopo live push is optional and separate from problem logging.
What is a problem in K9 SAR Log?
A problem is one activity on a session — usually one or more hide components with sources, tags, and optional indication or alert outcomes.
Where do source tags live?
On the named source in the kit. Terrain, distraction, and negative tags are per hide component.