Groups - Action Item "ECF 5.0 - DocketIDs vs DocumentIDs" Modified

[James Cabral<jec@mtgmc.com>]

Action Item Subject: ECF 5.0 - DocketIDs vs DocumentIDs
Item Number: #0061

---

Description
The beginning definition of the GetDocument message in the ecf-4.01-spec states a case number and a document number, but the xsd files show a nc:CaseTrackingID and a nc:CaseDocketID. The niem definition seems to have a definite difference between a docket and a document. It isn't clear how a document can be located with just the case tracking ID and the docket ID without a document number. There can be many documents associated with a case and each document should have its own identifying number.

Shouldn?t we be using NIEM Core ?DocumentIdentification? ?

One use case:

There are some CMS systems where you can only have one document per docket entry while other CMS systems allows for one lead document per docket entry and multiple attachments. There is also a security setting for each level as well. Here is an example: Washoe 2nd District had a situation where the case was public, the docket entry was public, the lead document (a complaint) was public, but the attachments were sealed because they were pictures of a women in a compromising situation and the court was not willing to expose information that is considered lewd or pornographic in nature. When you retrieve a document from a docket entry and there are multiple documents if there is only one ID then the system must first combine the documents into a single document before it can return the information. Sometimes courts split the documents up just due to size and not security as well.

Owner: Bryant Austin
Status: Closed
Priority: Medium
Due Date: 10 Nov 2015

---

Comments
Mr. James Cabral 2015-10-02 14:33 UTC
? Need Event ID, Document ID and Rendition ID
? Add GetCase message add document indicator
? Security: attachments may need to be confidential/sealed.
? Bryant should propose mappings for these elements