Every time you make a dump using CleverMaps Shell, a dump directory structure is created.
All dumped metadata objects are saved to the file system in a wrapper, which contains detailed metadata about the object itself.
In addition, dump metadata (or "metadata about the metadata") file is created. It is used to store useful information, like dump time, or the original project ID. It is also used to store the dump content and to track local file changes.
These directory structures and files are generated by Shell and should not be modified.
Dump directory structure is created either in:
- the default directory you specified in the config file (recommended)
- working directory, e.g. the directory you run Shell from
Let's assume that in this case,
/var/local/projects is our default directory. The dump structure is following:
So, in practice:
If we list the contents of this dump directory, we see data and metadata directories, and the dumpMetadata.json file (described below).
The data folder contains .csv files. The metadata folder contains subdirectories of the metadata object types. Each dumped file is wrapped in a dump object wrapper.
Dump object wrapper
Simple wrapper, which contains metadata about the dumped object.
URL link uniquely identifying the object
timestamp of when the object was dumped
version of the object
starts at 1, is incremented everytime the object is pushed to the project
the object itself
may contain valid content of one of metadata object types
The dumpMetadata.json file is located the dump directory, one level above the data and metadata directories. It contains metadata about the dump itself, and list of its contents.
server, from where the project was dumped
ID of the project
human-readable title of the project
|string||GENERATED||timestamp of when the project was last dumped or fetched|
|string||GENERATED||email of the user who performed the dump|
|object||OPTIONAL||list of metadata object files contained in the dump, with their respective md5 hashes (used for local file modification detection)|
metadataContent, but with .csv files