[1] CourtDetails is the intended root element of the schema. [2] CourtDetails:OrganizationKey is a unique identifier for a court. It is different than CourtDetails:CourtKey, which is a unique identifier for a division of a court. If a court has only one division, then the CourtDetails:OrganizationKey value and the CourtDetails:CourtKey value should be the same. For example, if a Juvenile Court had only one division, called Juvenile, then the CourtDetails:OrganizationKey value and the CourtDetails:CourtKey value would both be, as an example, USGADouglasJuvenile. In a court with multiple divisions, the CourtDetails:OrganizationKey value might be USCASacramentoSuperior for all divisions, with other divisions having CourtDetails:CourtKey values such as USCASacramentoSuperiorCivil, USCASacramentoSuperiorCriminal, or USCASacramentoSuperiorSmallClaims. [3] CourtDetails:CourtKey is a unique identifier for a court, a division of a court, or other subdivision of a court. Each division of a court should have a CourtDetails:CourtKey. A list of court keys for each court should be in the court's Policy XML, if it exists. [4] CourtDetails:Country is the two letter ISO country code in which the court has jurisdiction. [5] CourtDetails:State is the two letter state code in which the court has jurisdiction. Courts in countries that use something other than two letter state codes should change this element accordingly. [6] CourtDetails:County is the county in which the court has jurisdiction. [7] CourtDetails:CourtType is the type of court, such as Superior, Juvenile, Magistrate, or Probate.
[8] CourtDetails:Division is the division of the court into which a document is being filed. [9] The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.
[10] CourtDetails:Subdivision is the subdivision of the court, if it exists, into which a document is being filed. [11] The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.
[12] CourtDetails:Group is the group of judges (sitting en banc or in a panel within a court division) within a court, if it exists, into which a document is being filed. [13] The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.
[14] CourtDetails:Location is a human-readable descriptive location of the court. [15] The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element.
[16] CourtDetails:Department is the department of the court, if it exists, into which a document is being filed. [17] The attributes Code and Number are optional corresponding code values or numbers that represent the human readable value in the element. [18] CourtDetails:CourtCode is used for backwards compatibility with Court Filing 1.0 EFMs that use the Qualifier attribute on the Location element. Use of this element is discouraged. [19] CourtDetails:Include is a flag that courts can use to tell applications whether the information on the court is public or not. This flag allows a court to communicate to service providers information needed to submit a filing while limiting some of the information from being published to the public. [20] CourtDetails:Court is the name, address, phone numbers, and other contact information associated with a court. Some of the information in CourtDetails:Court is redundant with the other elements defined in this schema. For example, there is CourtDetails:County and Address:County. The elements declared here are to make it easier to group and organize the information. Sending applications should populate elements in this schema as a first priority and receiving applications should rely on elements in this schema. |