File
Schema definition for the publicfile message POSTed to the API frontend.
Message Structure
Required Fields
| Field | Type | Description |
|---|---|---|
object_id | string | UUID v4 format identifier for the current object |
agent_id | string | Identifier for the processing agent |
project | string | Project identifier |
timestamp | datetime | ISO 8601 formatted timestamp indicating when the file was downloaded |
expiration | string | ISO 8601 formatted timestamp indicating when the data should expire in Nemesis |
Optional Fields
| Field | Type | Description |
|---|---|---|
path | string | File system path to the relevant resource. Can use either forward (/) or backward (\) slashes |
originating_object_id | string | UUID v4 format identifier referencing a parent or source object |
nesting_level | number | The level of nesting for the file within an originating container. Used to prevent indefinite container nesting. |
creation_time | datetime | ISO 8601 formatted timestamp for when the file was created |
access_time | datetime | ISO 8601 formatted timestamp for when the file was last accessed |
modification_time | datetime | ISO 8601 formatted timestamp for when the file was last modified |
Example Message - Derivative File
Example Message - File Extracted from a Container
Notes
- All timestamps must be in ISO 8601 format with timezone information
- File paths can use either forward (/) or backward (\) slashes
- UUIDs should follow the v4 format
- The schema may be extended with additional optional fields in the future
- If
originating_object_idis present butnesting_levelis not or is 0, then the file is a derivative file. - If
originating_object_idis present andnesting_levelis present and > 0, then the file was extracted from a container.