Setting up an interface with an e-citation vendor


Required data format

The e-citation producer schema, and an html representation of it, can be found at http://www.goodinassociates.com/schema/Drafts/

Testing code values for court-specific data

Permalink

Use the following values (or let us know if if this isn't possible):
  • Court ORI: IL068015J (Montgomery County).  It isn't absolutely necessary to set this, since our e-citation ticket import presumes that the e-citation vendor didn't provide the wrong court's data.
  • Agency ORI: IL0030100 (Greenville)- changed this code on 11/28/2016 to one which isn't County (due to FB15477)
  • Officer badge number/name: 1/SMITH, JOSEPH
    • Some test scenario tickets can use other badge numbers and names
  • Hearing courtroom (<Event>/Location)- if the court expects the officer to indicate this, it has be in PC JIMS
  • TownshipCode/TownshipName: 9/Panama

Test scenarios

Permalink

Clerk should use a test environment to create the following test scenarios, to ensure that the vendor is handling them correctly (all test data should include the citation PDFs in-line as per the above schema).  A single test ticket can certainly represent more than one scenario:

  1. Multiple offenses on the same incident
    1. One with a CM charge and a TR charge
    2. One with two TR charges
  2. DUI- this should use both "flavors" of DUI offense typically charged (offense codes 14721 and 14722).
  3. Local ordinance violations, both for ordinance violations based on ILCS offenses such as for squealing tires (using a <Charge>Code from the AOIC offense table) and non-ILCS violations such as for weed abatement (using <Charge>Code="0000000")
  4. Foreign (Canadian or Mexican) DL, foreign plates and foreign address
  5. Include ticket PDFs
  6. Different bond types- cash, non-cash and both.  Tickets with cash bond should have a <Payment> element
  7. Different info in the BMV section of the schema (http://www.goodinassociates.com/schema/Drafts/e_citation_service_producer.html#BMVInfo), such as HazardousMaterialsFlag, DriverPassenger and CommercialVehicleFlag
  8. At least one violator with ALL of the possible identity info in http://www.goodinassociates.com/schema/Drafts/e_citation_service_producer.html#Identity
  9. Scenarios indicating different values for the items in the schema which have a required list of values (those which the schema shows as having multiple values in an "enumeration"), and aren't covered in other scenarios.  These are: 
    1. PersonalInjury
    2. UrbanDistrict
    3. Secured (see the Document element)
    4. Gender
    5. EyeColor
    6. HairColor
    7. AppearanceCode
  10. A ticket on a township road- as per clarification received from AOIC on 11/4/2016, the township name is  is to be provided whenever the officer sets the township road indicator to reflect that the township maintains the road on which the ticket was issued. 
  11. NO LONGER REQUIRED (since ADR doesn't require it)) A ticket involving a passenger (if e-citation system supports that)
  12. NO LONGER REQUIRED ( case is modified as required):  Attempt to create lower-case data where allowed by the e-citation vendor's user interface, on any field containing text (e.g. FullName and AddressLine).  Added 7/19/2016
  13. Create a warning ticket for a litigant named "WARREN, INGE", to make sure that it is not sent to the court.  Added 12/16/2016

Some of these tests will be caught be schema validation by e-citation vendor and GAL.  Others will be caught during Inbox processing of the resulting data.

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:
  • Court NCIC/ORI code is available in PC JIMS, but there's an easier way to get it.  Pick the county from the list at http://www.judici.com/courts/court_list.jsp, then observe the value of the "court" parameter on the resulting URL
  • Agency NCIC/ORI codes are in the court agency table in JIMS
  • Charge code- e-citation shall use the standard statewide codes found in the AOIC offense table.  In some counties, certain offenses eligible to be written on a uniform complaint (DUIs?) are supposed to go to the State's Attorney rather than getting imported right into PC JIMS. The e-citation vendor is responsible for excluding these from the data for import.
  • Officer badge number/name- check them against the arresting officers set up in PC JIMS.
    • Warning: CMS requires "Lastname, Firstname" format.  Our e-citation importer makes new officers "on the fly" if they aren't in JIMS.  And because badge numbers get re-used, we add any officer whose badge number and name don't match JIMS exactly.  So failure to latch both will result in duplicate officer records.  The same thing will occur if you provide the wrong agency NCIC code for an officer.
  • Hearing courtroom and hearing type (which can show up in the <Event> element in the ticket data)-  if the court wants to use a consistent courtroom for all the hearings, the e-citation vendor will need to know this.  Many court's use a hearing type "20" (First Appearance)
  • Township names and codes- per a conversation with AOIC staff on 11/4/2016,  the township road checkbox is to be checked by the officer whenever the road is maintained by the township.  This causes JIMS to set the township as the Pay To agency so that they get money from the ticket.  Since any given township might handle maintenance, or start to do so at any given time, the e-citation system should be set up with a list of all townships in the county, and officers will have to be trained on when to check off the Township Road box on the ticket based on who is maintaining the road at the time.  To determine the code values the e-citation vendor needs to provide township data to the court:
    • Open the Edit Arresting Agencies screen (under the Technical|Case Management Tables menu)
    • Use the value in the Code column for each township.

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:
  • DigiTicket-   they provide a program which gets the data
  • APS- GAL installs a program on your GAL PC which uses web services provided by DuPage County to regularly check for new data.

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?

  • The IP address can be found at http://countyname-judici.clients:8080/gal-nas
  • The share folder is usually \Imaging

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.
Comments