Setting up an interface with an e-citation vendor

KB article ID:4400

Last Modified

1/3/2023- Updated some testing code values due to a change in our test server's data

Required data format

e_citation_service_producer.xsd  - the XML schema for providing electronic citation data from a single traffic stop/incident.

e_citation_service_producer.html - a human-readable version of the same thing

Testing code values for court-specific data

Permalink

Use the following values (or let us know if if this isn't possible):

Testing code values for violator/litigant data

Use the following litigant for all citations except the CA/MX test (Test #4):

For Test #4, use the following, respectively:

Test scenarios

Permalink

BEFORE TESTING!  Goodin staff processing the test files shall verify that the client has signed a proposal for our e-citation services.

The e-cation vendor should create the following test citations,  while configured using the testing code values referenced above.  All test data should include the citation PDFs in-line as per the above-referenced schema. 

Revised 12/17/2021

A single test ticket should represent only one scenario

NOTE 1: The e-citation vendor has the option when submitting their tests to affirm that one or more tests aren't even possible with their system or in the given county being tested.

Production code values for court-specific configuration data

Permalink

The e-citation vendor should work with the court to configure their systems to match up with key data in the court's CMS:

Other configuration info for court systems

What tools are required to get the data to the court? This depend on which e-citation vendor you use:

Where should a vendor-provided tools such as DigiTicket's be installed?

It's the court's choice what PC should run a program which gets the data.

Where should the e-citation data be put? In the same location where the court keeps its Imaging files (since that is reliably available). Where is this?

For example: \\192.168.1.235\Imaging . The e-citation vendor may require a mapped drive in order to access this.  If the vendor's tool is beeing installed on a PC which also runs Imaging, there is a good chance that the PC already has an "I:" drive mapped this address/folder.  If you need help setting up a mapped drive, call us.

GAL moves this data into the PC JIMS Inbox about once a minute, so the XML doesn't stay on the Imaging share for long.