... | ... | @@ -252,7 +252,7 @@ Use the `pepcli list` command to determine which data is available in PEP: |
|
|
pepcli list -C <column group> -P <participant group> -T <ticket out file>
|
|
|
```
|
|
|
|
|
|
The command outputs its information as a JSON array with one entry per subject. Every such entry contains the subject's polymorphic pseudonym, plus an array listing the columns in which data is stored for the subject. If the data is short enough, it will be included directly in the output. For larger entries, the output will include an id that can be used with the [`get` command](#get). There are flags to change this behavior.
|
|
|
The command outputs its information as a JSON array with one entry per subject. Every such entry contains the subject's polymorphic pseudonym, plus an array listing the columns in which data is stored for the subject. Depending on switches passed to the command, small data may be *inlined*, i.e. included in the command's output. For larger entries, the output will include an id instead of the data itself. Pass the id to the [`pepcli get` command](#get) to retrieve such data.
|
|
|
|
|
|
Important flags are:
|
|
|
|
... | ... | |