E_CITATION Service Producer Schema

2024-11-22T09:45:06.486823-06:00


General notes on this schema:
EXTERNAL SPEC REFERENCES
The e-citation spec contains a data element listing which identifies a DDN number. This corresponds to the data elements in the ADR spec (6/18/2013 version of ADR spec). This can be used to locate data items in this schema: to find ADR data element #60, search for 'DDN 60'
All e-citation spec/std. references herein are from the 5/14/2014 version of the e-citation spec
NOT ALL SCHEMA DATA IS NECESSARILY IN USE
The presence of a data element in the this schema doesn't necessarily mean that it is used by Judici.com.
DATA SECRITY AND PRIVACY RESTRICTIONS
Judici courts implement a variety of restrictions on what data is shown to the public. Some of these restrictions are required and others are at the court's discretion. For a list of all data subject to possible restriction as Secure Data or Private Data, see https://www.judici.com/agreements/Exhibit_D_to_Web_Service_Subscriber_Agreement
NOTICE: DERIVED DATA VALUES
All data defined herein as "Derived Data" is set by court, and is for internal Judici.com use only. It is derived by the court from one or more underlying case data elements, which can be quite complex. Derived Data may control restrictions on whether case data will be made public under the data security and privacy restrictions (see previous note) and/or applicable statutes or regulations such as the federal Fair Credit Reporting Act (FCRA) requirements on reporting past non-convictions. Derived Data might not, at any given time, be calculated in accordance with applicable statutes and regulations and it is subject to change. Derived Data is shown on an "as is" basis, given the relevant underlying case data. In the event of any conflict between such data and the underlying data, the latter shall govern and the conflict should be brought to the attention of the court.
Retention in Compiled Index Record not allowed for any Derived Data.
CODE, DESCRIPTION AND TEXT ATTRIBUTES
Enumerations are used when the code/value list is modest in size and fairly static. If the code is meaningful text (e.g. BLK, BLU...) it will be used as the enumeration Otherwise, the enum will contain the VALUE. This is because most codes are sequence/ordinal numbers which can be effectively be derived from the ordinal position in the enum (and even when the number sequences have GAPS, the right code can still be derived).
When there is no enum:
-Code can be required
-Value should be optional (unless there is a write-in value such as with 999999 offenses)
-Schema may include enumerations, if the codes meaningless numerics and the list of values is not long.
MORE ON CODES
- Courts often use "standard" codes in different ways (e.g. indicating modified judgments using a different sequence of dispositions). So while Service Provider may provide guidance on interpreting court offense data, it is recommended that any user of this data work directly with the court for a full, complete and correct interpretation of that court's data.
BOOLEAN
In order to be able to convey explicit "Unknown" value, the schema uses an enumeration (Yes/No/Unknown) rather than Boolean.
DATE FORMAT
Producers have to supply Date type attributes (omitting any of the optional time zone info), while Consumer schemas will continue to be text.
CODES FOR STATES, PROVINCES, TERRITORIAL POSSESSIONS AND COUNTRIES
Wherever the schema calls for a state/province code for the U.S., Canada or Mexico, use one of the applicable two-character codes in Appendix A in ADR spec. Note that the state/province codes for Mexico and Canada used by the AOIC don't always match international standards.
Wherever the schema calls for a country code, only the following countries need be indicated: US = United States, MX = Mexico, CA = Canada. 

For most data values associated with table lookups, Judici can OUTPUT any combination of the following:

- An attribute containing "Code" contains the code value (e.g. a value of "405" for the <CriminalDisposition> Code attribute)

- An attribute containing "Name", or "Description" holds the exact text corresponding to the code (e.g. "Withhold Judgment/720 ILCS 5/12-4.3"). 

- An optional third attribute containing "Text"- this exists to give courts the option to provide more human-readable content.  But practically speaking, courts rarely do this.  So this last attribute is typically just a concatenation of teh other two.