We have now instituted the option of using entry serial numbers so that all entries (and therefore all submissions) can be uniquely identified. This will allow us to identify an email that has been sent twice by accident so that we don't process it again. To do this we are using the extended branch of the object tree with a type of "Entry-Serial-Number". (See the example below.) You may use the subtype item if you wish. That would allow each type of entry (Petition, Aid, Garnishment, etc.) to have its own serial number (and daily count using format 1 below).
extended(1).type = Entry-Serial-Number extended(1).subtype = (whatever you want, up to 10 characters) extended(1).value = 1999-07-13-1
You are allowed up to 60 characters for the serial number in the value item. If you use a simple counting scheme you can have 1 x 1060 unique serial numbers starting with 0 and counting up to 999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999,999 (without the commas). [That should last you several hundred years. If not, please let us know so we can buy a much, much bigger computer system to handle the work load and storage needs. ;-)]
Suggested value formats:
1) YYYY-MM-DD-n, or YYYY/MM/DD-n, or YYYYMMDD-n
where YYYY is the year (1999),
MM is the month (07),
DD is the day (13),
and n is the incremental count of entries for that day starting at 1
2) YYYY-DDD-n
where YYYY is the year (1999),
DDD is the day number of the year (1 through 366),
and n is the incremental count of entries for that day starting at 1
For example: The first submission today has five entries in it so they are numbered 1999-07-13-1 through 1999-07-13-5. The second submission today has twenty entries in it so they are numbered 1999-07-13-6 through 1999-07-13-25. The next day the entry number would start over at one with 1999-07-14-1.
The extended branch with the Entry Serial Number will be returned to you in the Court Response so you can use it to identify the entry's response when you receive it from the Court.