Court case management system interfaces with Judici

KB article ID: 300

The following describes different approaches to getting data to and from Judici.

General notes regarding web services for providing Judici data

  • The exact syntax of the web service calls described herein is not specified.  This is in order to accommodate the existing export tools already available in the court, so as to minimize the court's time and effort to participate.
  • The format of the data returned in response to the web service calls is also negotiable.  See XML schema considerations for more.
  • It is preferred that web services be RESTFUL
Non-batch approach to providing the data-  this near-real-time approach requires the court to operate three or four web services returning XML results:
  • get list of all cases- this will be used for the initial loading of all cases. 
    • If the court prefers to limit these queries in any way, using a specified start date, or not sending juvenile or otherwise secured cases, this web service can certainly do so.  That said, it's important to remember that Judici does have the capability of showing restricted data such as juvenile cases to court-specified individual users.  See  Data security and privacy for more.
    • At a minimum, the response shall provide the ID required in order to "get" a specific case as described below. 
  • get list of changed cases- same as above, except the list is restricted to cases known to be changed.  There are at least two ways this can be determined:
    • Based on database timestamps
    • Using database triggers to maintain a list of what has been changed,   This approach can be more tolerant of communications failures, by implementing the "remove case from list..." web service described below.
  • get specific case 
    • Judici will use this to get the details while iterating through a list of cases provided by the court. 
    • In order to make Judici's data somewhat "self-healing", this web service should return the entire case so Judici can swap out everything on the case.  
    • Even if the court provides its data using a batch approach, this web service call will still be required if E-pay and E-plea interfaces are desired in order to allow online payments.
  • remove case from list of changed cases (trigger-based implementations only)- Judici can call this whenever it successfully acquires a case.  Only then should the case be removed form the trigger-based list of changed cases.  Among other things, this copes with possible communications failure.

Batch approach to providing data

The court may prefer to extract a single file of all cases changed since the previous extract.  This is certainly acceptable, though it is commonly done at intervals which make it is less "real-time". 

Although a web service is a common way to make this "self-service", there are many other ways (e.g. FTP etc.) which could work. 

Other interfaces