Contains various data which is one-to-one for a litigant.
Role-related attributes- these indicate the litigant's role on the case
Role- of the role-related attributes, this is the only one with an enumeration of allowed values in the CourtDataTransferFile schema. All other values follow the court's formats.
RoleCode- many courts use P, R, D etc. No requirements on allowed values
RoleSequence- the nth person having that role on the case
RoleDescription . On civil cases, these might indicate Plaintiff or Respondent, but on non-juvenile criminal cases they will usually indicate Defendant.
RoleSequence is a one-up ID (e.g. a 2 would indicate the second litigant of that type on the case).
Key dates- see also Date formats in Judici XML
InitialOpenDate- the date the case was filed/opened
On criminal cases, this is often the date on which the case is both disposed and sentenced, but some courts may not close the case until any fines and fees are paid in full.
A case which has a close date may actually be open -this happens if there is a reopen date prior to any reclose date, indicating post-termination activity such as an appeal.The court may wish to adopt a practice of withdrawing re-opened cases, so the collection agency knows to back off.
ReopenDate- if a litigant has a re-open date which is prior to their re-close date, they are in some sort of post-termination proceedings, such as appeal or a re-offense, which may very well resulting in changes to charges, dispositions, sentences and and/or the amount/balance due on the case.
RecloseDate- the date on which the most recent post-termination proceedings were closed
CaseStatusCode- this indicates whether the case is in original proceedings, on appeal, etc. Schema does not have an enumeration of allowed values.
CaseStatusDescription- see CaseStatusCode, above
Derived security/privacy-related attributes- this data, based on what is in the court's case management system, controls restrictions on whether data will be made public under the restrictions described in Data security and privacy. Due to the need for appropriate data restrictions, the schema contains an enumeration the allowed values for these attributes.
Impounded- to be impounded, and thus non-public. Used to determine whether the case should be made non-public. Setting this flag is what cues Judici to treat the case minutes as Secure Data, as described in Data security and privacy. A value of "Sealed" is used when the case doesn't even seem to exist, not even in search results. A value of "Yes" causes the case to show up in search results, but no case details are then available.
SuppressMinutes- this indicates whether the case/litigant has explicitly been marked in the court's case management system to make the judge's docket sheet Entry records non-public. Setting this flag is what cues Judici to treat the case minutes as Secure Data, as described in Data security and privacy..
Minor- this indicates whether the litigant was a minor (per the rules of the court's jurisdiction) at time of case filing. Setting this flag is what cues Judici to make private (as per Data security and privacy.) a case which is non-juvenile, but involve minors.
Other derived case/litigant-level attributes- the CourtDataTransferFile schema contains enumeration of required values for various attributes derived for very specific roles in determining how the site operates:
Conviction- see Criminal conviction data
Type- to distinguish people from entities.
SOSReportable- indicates that at least one offense on the case is reportable to the Illinois Secretary of State's office.
AppearanceCode- this indicates whether any of the offenses on a case require a court appearance.
OffenseCode- a concatenated list of the the offense codes on the case.
Sentenced- indicates that the defendant has been sentenced
DispositionState- unlike most dispositions, "interim" do not prevent a case from being eligible to be pled on Judici E-Pay/E-Plea.