... | ... | @@ -153,7 +153,7 @@ Values of error `code` in **upload_file** responses: |
|
|
|
|
|
**Note:** The problem is, that the Datovka application makes a difference between a data message (**dm** -- which contains all the attachment files) and a delivery info (**di** -- which does not contain any attachments but contains only information about the delivery status). Therefore `locations` should be related only to the uploaded **dm** or **di**; `locations` must not mix **dms** and **dis** with equal ISDS identifier to prevent any confusion in Datovka application.
|
|
|
|
|
|
### Query for ZFO Files Held within the Record Management (**stored_files**)
|
|
|
### Query for ZFO Files Held within the Records Management (**stored_files**)
|
|
|
|
|
|
Queries the storage service for the presence of data messages or delivery information files.
|
|
|
|
... | ... | @@ -169,7 +169,7 @@ JSON request: |
|
|
}
|
|
|
```
|
|
|
|
|
|
* `dm_ids` is a list of data message identifiers (strings holding integer numbers as used by ISDS) whose location in the record management service the client wants to obtain. The list may be empty.
|
|
|
* `dm_ids` is a list of data message identifiers (strings holding integer numbers as used by ISDS) whose location in the records management service the client wants to obtain. The list may be empty.
|
|
|
* `di_ids` is a list of delivery info identifiers (strings holding integer numbers as used by ISDS) whose location the client wants to obtain. The list may be empty.
|
|
|
|
|
|
Strings containing positive integers are used because of the ambiguity in integer representation/size when converting from/to JSON on various architectures/implementations. We need to ensure that 64-bit integers are safely accommodated within the structure. It is necessary that 64-bit integers are used when converting these identifiers to numbers as the ISDS data message identifiers are soon going to exceed the range of 32-bit integers.
|
... | ... | |