The Docket Read as Part of the Work
This connector is not prebuilt. It would be built to your requirement on the REST API path the platform already uses, with scope and effort agreed per engagement. Tyler Odyssey is the court case management system of record in many US state and county courts, holding the docket, filings, parties and hearing calendar. Its distinguishing feature for this purpose is the calendar: a court's work is driven by dates, and evidence that cannot be found before a date is evidence that failed.
How it connects
Evidence would transfer with the case identifiers that make it findable later, so an exhibit and the media behind it stay connected instead of being re-keyed by a clerk. A workflow could then read the docket, which is where the value concentrates: assembling what a hearing needs, checking whether a filing deadline has passed, or finding every case a party appears in, which is a question the docket can answer and a folder structure cannot.
An engagement would settle who may see what. A court's records are public in part and sealed in part, and the boundary runs through individual documents rather than whole cases, so an integration that keys only on case number will eventually expose something sealed. That mapping is the work.
Odyssey stays the case system of record. The docket, filings and calendar stay there, and nothing is written back unless a step is scoped for it. Whether a disposition changes retention on attached media is agreed rather than assumed.
What you can do together
- Keep an exhibit attached to its case through identifiers rather than through re-keying.
- Read the docket from a workflow to assemble what a hearing needs.
- Find every case a party appears in, which the docket can answer and a folder cannot.
- Map sealed and public status at the document level, not the case level.
A scenario
- ScopingThe engagement would map public and sealed status at document level and settle retention on disposition.
- SetupThe connection is configured once against the Odyssey API with case identifiers mapped to attributes.
- FilingAn exhibit and its media attach to the case under the agreed access mapping.
- A hearing weekA workflow reads the calendar and assembles what each listed matter needs, flagging one where a deadline has passed.
- A sealed documentIt is reachable only by those entitled, because the mapping was at document level rather than case level.
What stays where
Odyssey remains the case system of record
Docket, filings, parties and calendar stay there.
Sealed status runs through documents, not cases
Keying access on case number alone is what eventually exposes something sealed.
Retention on disposition is decided
A court schedule and an evidence schedule are rarely the same document.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud, on premises, or air-gapped.
Products and solutions
Not a Folder Named After an Officer
This connector is not prebuilt. It would be built to your requirement on the REST API and ingestion path the platform already uses, with scope and effort agreed per engagement. Tyler Records is the law enforcement records management system holding incident reports, arrests and case files. Where the Odyssey connection answers what a court needs from a docket, this one answers the question upstream of it: which case a piece of evidence belongs to, before anything reaches a court.
How it connects
Report and case records would come across over the API, and the case number would arrive as a custom attribute on the media, so evidence files against the case rather than sitting in a folder named after the officer who uploaded it. That is the failure this removes, and it is a filing problem rather than a storage one.
Because an agency on the Tyler stack often runs Tyler Records alongside Tyler Enterprise CAD, an engagement would establish which identifier is authoritative for what. The incident number answers which call a recording came from; the case number answers which case it files against; and they are not the same field. Building against one and labelling it the other is how an agency ends up with evidence that is technically filed and practically unfindable.
Tyler Records stays the authoritative record. Report writing does not change, nothing is written back unless scoped, and whether a closed case changes retention on attached evidence is agreed rather than assumed.
What you can do together
- File evidence against the Tyler Records case number, so nothing depends on who uploaded it.
- Keep the case number and the incident number distinct, each answering its own question.
- Assemble what a case file needs with a workflow reading the record.
- Find cited items that are absent before a deadline does.
A scenario
- ScopingThe engagement would establish which identifier is authoritative for which question, and settle retention on closure.
- SetupThe connection is configured once against the Tyler Records API with the case number mapped to an attribute.
- FilingInterviews and body camera video attach to the case, under the library's access control and custody record.
- Case preparationA workflow gathers the attached media and lists what the report cites but the library does not hold.
- HandoverThe file goes to the prosecutor with the case number on every item.
What stays where
Tyler Records remains the authoritative record
Reports, arrests and case files stay there, and report writing is unchanged.
Case number and incident number are different fields
One answers which case, the other which call, and conflating them is the usual mistake on this stack.
Retention on closure is decided
Whether a closed case changes evidence retention is agreed rather than assumed.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud, on premises, or air-gapped.
Products and solutions
Next step
See it on your own Tyler Technologies instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/tyler-technologies