CourtDataTransferFile

KB article ID: 1000

GAL internal docs regarding search parms

Description:

This XML file can contain a single case, or multiple cases- the creator of the file makes this decision, often based on the memory required to put a large number of cases in the file. These files follow the CourtDataTransferFile schema, which indicates what data is required. The documentation herein offers details on some of the associated data.

In the event of conflicts between this documentation and the schema, the schema shall govern.

General notes on CourtDataTransferFile

The entire structure of the data in a transfer file is laid out below.

Attributes:

- FileCreationDateTime- this is a timestamp corresponding to when the case was extracted from the court. For various reasons, this may or may not represent an actual change in the underlying court data. For this reason, the caseMD5 attribute on each case and in each case in any search results is a better way to spot changes when comparing results from different searches.
- Version- this should be the same value used in the version attribute of the CourtDataTransferFile schema used in creating the data file
- Judici populates the following attributes when it provides a transfer file in response to a "get" for a specific case . Courts providing data to Judici need not provide this:
  - md5- this is a unique ID for the case, reflecting its precise data state at the time when it was obtained in a get or in a search. If the transfer file was in response to a get, this will correspond to the CASEMD5 parameter used in the get.
  - RelatedActorID- corresponds to the LITIGANTID on the get.
- In schema, but not used
  - PhysicalFileLocation
- CivilDispostionText
- ComplaintText