Litigation Schema and User-Defined Functions
The litigation schema is used for global litigation data. This data is available through the CLAIMS Direct platform as a separate subscription. For information about the Litigation API, see Litigation.
Schema
litigation.t_cases
Column | Type | Modifiers | Comment |
|---|---|---|---|
case_id | serial | primary key | Table primary key |
case_number | varchar(32) |
| Identifying case number |
filed | date |
| Filing date of case |
closed | date |
| Date case closed |
created_load_id | integer | not null | Load id of case creation |
modified_load_id | integer | not null | Load id of last modification |
deleted_load_id | integer |
| Load id when case was deleted |
litigation.t_publication_cases
Column | Type | Modifiers | Comment |
|---|---|---|---|
publication_case_id | serial | primary key | Table primary key |
case_id | integer | not null | Case ID referencing litigation.t_cases (case_id ) |
publication_id | integer | not null | Integer representation of the publication referencing xml.t_patent_document_values (publication_id ), unique to each on-site instance Note: Once a new ucid (document) is loaded, it receives an auto-generated publication_id created specifically to join the XML tables for a given ucid. The publication_id never changes within a given instance. The relationship between publication_id and ucid remains intact even if the document is modified or deleted. In rare situations when a patent office “rekeys” a ucid (e.g., to change a mistaken kind code or change the format of the document number), the original ucid is marked “deleted” and the new ucid is added with a new publication_id. |
litigation.t_parties
Column | Type | Modifiers | Comment |
|---|---|---|---|
parties_id | serial | primary key | Table primary key |
case_id | integer | not null | Case ID referencing litigation.t_cases (case_id ) |
modified_load_id | integer | not null | Load id of last modification |
status | char(1) |
| XML validity flag (v=valid;i=invalid) |
content | xml |
| Parties XML container |
litigation.t_related_publications
Column | Type | Modifiers | Comment |
|---|---|---|---|
related_publications_id | serial | primary key | Table primary key |
case_id | integer | not null | Case ID referencing litigation.t_cases (case_id ) |
modified_load_id | integer | not null | Load id of last modification |
status | char(1) |
| XML validity flag (v=valid;i=invalid) |
content | xml |
| Related publications XML container |
litigation.t_related_cases
Column | Type | Modifiers | Comment |
|---|---|---|---|
related_cases_id | serial | primary key | Table primary key |
case_id | integer | not null | Case ID referencing litigation.t_cases (case_id ) |
modified_load_id | integer | not null | Load id of last modification |
status | char(1) |
| XML validity flag (v=valid;i=invalid) |
content | xml |
| Related cases XML container |
litigation.t_litigation_case_extract
Column | Type | Modifiers | Comment |
|---|---|---|---|
litigation_case_extract_id | serial | primary key | Table primary key |
case_id | integer | not null | Case ID referencing litigation.t_cases (case_id ) |
modified_load_id | integer | not null | Load id of last modification |
status | char(1) |
| XML validity flag (v=valid;i=invalid) |
content | xml |
| Main XML case container |
User-Defined Functions
litigation.f_build_case(integer, text)
This function returns an entire XML case given a case_id as first argument. The second argument is currently unused.
SELECT litigation.f_build_case(534987, null);