Every time you make a dump using CleverMaps Shell, a dump directory structure is created. Every dump is uniquely identified by its dump ID - a time stamp of when the dump was created. Format of the dump ID is "yyyy-MM-dd_HH-mm-ss".
All dumped metadata objects are saved to the file system in a wrapper, which contains detailed metadata about the object itself.
...
- the default directory you specified in the config file (recommended)
- working directory, e.g. the directory you run Shell fromthe directory you specify as a value of
--directoryparameter of thedumpProjectcommand
Let's assume that in this case, /var/local/metadata is projects is our default directory. The dump structure is following:
| Code Block | ||
|---|---|---|
| ||
/var/local/metadataprojects/{projectId}/{dumpId}/ |
So, in practice:
| Code Block | ||
|---|---|---|
| ||
/var/local/metadataprojects/q1zdp9d0ao78rdv5/2017-08-28_20-17-51/ |
If we list the contents of this dump directory, we see data and metadata directories, and the dumpMetadata.json file (described below).
...
| Key | Type | Optionality | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
dumpId | string | ||||||||||
| Status | |||||||||||
| colour | Blue | ||||||||||
| title | generated | ID of the dump | server | string |
| server, from where the project was dumped | |||||
projectId | string |
| ID of the project | ||||||||
projectTitle | string |
| human-readable title of the project | ||||||||
dumpTime | string |
| timestamp of when the project was last dumped or fetched | ||||||||
user | string |
| email of the user who performed the dump | ||||||||
metadataContent | object |
| list of metadata object files contained in the dump, with their respective md5 hashes (used for local file modification detection) | ||||||||
dataContent | object |
| like metadataContent, but with .csv files |
...