... | @@ -373,38 +373,28 @@ The flags are: |
... | @@ -373,38 +373,28 @@ The flags are: |
|
- `-d` Data to store. Use either this or `-i`
|
|
- `-d` Data to store. Use either this or `-i`
|
|
- `-T` By default, pepcli will request a write-only ticket. You can use `-T` and give a path to store the ticket in. If you use this flag, pepcli will also request read access to the entry that is stored. You can then use the ID in the output, together with this ticket for `pepcli get`. This way you can check whether the data was stored correctly. Note that pepcli also performs its own checks to see whether the data was stored correctly.
|
|
- `-T` By default, pepcli will request a write-only ticket. You can use `-T` and give a path to store the ticket in. If you use this flag, pepcli will also request read access to the entry that is stored. You can then use the ID in the output, together with this ticket for `pepcli get`. This way you can check whether the data was stored correctly. Note that pepcli also performs its own checks to see whether the data was stored correctly.
|
|
|
|
|
|
# Specific examples
|
|
# Specific usage scenarios
|
|
Let's say we have the following column groups, with the listed columns:
|
|
## Uploading and downloading data
|
|
|
|
See [Uploading and downloading data](Uploading-and-downloading-data)
|
|
- Example
|
|
## Data administration
|
|
* ExampleColumn1
|
|
### Creating participant groups, based on certain attributes
|
|
* ExampleColumn2
|
|
Lets say we want to create a participant group `males`, which contains all male participants. The sex of a participant can be found in a column `Castor.GeneralInfo`.
|
|
* ExampleColumn3
|
|
|
|
* ExampleColumn4
|
|
1. We start by creating the participant group:
|
|
- SomeData
|
|
```
|
|
* SomeData.ColumnA
|
|
pepcli ama group create males
|
|
* SomeData.ColumnB
|
|
```
|
|
* SomeData.ColumnC
|
|
|
|
|
|
2. We then download the data for the column `Castor.GeneralInfo`, for all participants:
|
|
Each participant must have a participant identifier, e.g. `CP1234567890123`, provided by you. This will be the seed of the pseudonymization performed by PEP. These identifiers are very sensitive, and may NOT be sent to others. Instead, they must use the pseudonyms created by PEP.
|
|
```
|
|
|
|
pecpcli pull -c "Castor.GeneralInfo" -P "*"
|
|
To store data from the file `data.txt`, for participant identified by `CP1234567890123` in column `ExampleColumn1`:
|
|
```
|
|
|
|
|
|
```
|
|
3. The data administrator now filters the downloaded data: They take note of the directory names of those participants that, according to the downloaded data, are male. How this is done exactly, is outside of the scope of PEP. The result is a list of directory names. These directory names are the local pseudonyms of the participants.
|
|
pepcli store -c ExampleColumn1 -p CP1234567890123 -i data.txt
|
|
|
|
```
|
|
4. We can now use this list to add participants to the participant group:
|
|
|
|
|
|
To store the string `Hello world` in column `SomeData.ColumnA`:
|
|
```
|
|
```
|
|
pepcli ama group addTo males <local pseudonym>
|
|
pepcli store -c SomeData.ColumnA -p CP1234567890123 -d "Hello World"
|
|
```
|
|
```
|
|
For each `<local pseudonym>` from the list of step 3. |
|
|
|
|
|
To list the data for column groups `Example` and `SomeData`, and store the ticket in the file `ticket.out`:
|
|
|
|
```
|
|
|
|
pepcli list -C Example -C SomeData -P \* -T ticket.out
|
|
|
|
```
|
|
|
|
|
|
|
|
If you executed the previous examples, and `data.txt` was sufficiently large (>1000 bytes), this will display an ID for the column `Example1`. You can get the data (printed to stdout) with:
|
|
|
|
```
|
|
|
|
pepcli get -t ticket.out -i <IDENTIFIER FROM LIST>
|
|
|
|
``` |
|
|
|
\ No newline at end of file |
|
|