Shared library
One laboratory's coverage becomes every laboratory's.
A mapping validated in one service is useful in every service that later meets the same application. The library is how that happens, and it holds parsing definitions rather than evidence.
- Self-hosted, offline
- Parsing definitions only, never case data
- You decide who it is shared with, including nobody
How it works
Validated once, applied everywhere it fits.
When an examiner accepts a generated mapping, that mapping can be contributed to a shared library. Contributions are versioned, scored and moderated, and validated entries are proposed for automatic application when another laboratory opens a seal containing the same application.
Query expansion rules travel the same way, so the vocabulary one unit builds up around a particular kind of case becomes available to the others.
-
Versioned
A mapping has a history, and a laboratory can see what changed and when.
-
Moderated
Entries are reviewed before they are proposed for automatic application.
-
Applied on import
A matching entry populates the viewer when the seal is opened, with no examiner action.
The question everyone asks first
Case data never goes into the library.
The library holds parsing definitions, which describe how to read a given application's data structure. It never holds evidence, never holds records recovered from a device, and never holds anything that identifies a case, a device or a person.
It is self-hosted on your infrastructure and runs offline. You decide who it is shared with, and that decision can be nobody.
The library holds definitions of how to read a structure. It does not hold the data that structure contained.
Why it matters
Expertise stops leaving with the person who had it.
An examiner who works out how to read an unfamiliar application usually holds that knowledge personally, and it leaves the service when they retire or transfer. A validated mapping is that knowledge in a form the service keeps.
Across a group of cooperating laboratories the effect compounds. Each service stops rebuilding what another has already validated, and coverage grows from use rather than from anybody's product roadmap.
What is working today, and what is not
Working today
- Contribution of validated mappings to a self-hosted library.
- Versioning, scoring and moderation of entries.
- Matching against the library at seal import, with automatic application.
- Sharing of query expansion rules alongside mappings.
In development
- Deduplication and linking across seals.
- Cross-laboratory reporting on coverage growth.
See it running on a real extraction
Thirty minutes, on fictitious data, with time for your questions. If VERA does not fit what your service needs, that is a useful answer too.
Every request is reviewed before access is granted.