... | ... | @@ -7,9 +7,7 @@ The `pepcli` utility is documented extensively on a [separate page](Using-pepcli |
|
|
- [uploading data](#uploading-data) using the `pepcli store` command, and
|
|
|
- [downloading data](#downloading-data) using the `pepcli pull` command.
|
|
|
|
|
|
There is also a section on a more [manual approach to downloading](#manually-listing-and-getting-data), which provides more control over the process but comes with some limitations.
|
|
|
|
|
|
The documentation on this page assumes that the user is familiar with the `pepcli` utility's [general usage](Using-pepcli#general-usage) principles. In particular, the user should be able to [ensure that they are enrolled](Using-pepcli#enrollment) with the PEP system. The examples on this page assume a Unix-like environment.
|
|
|
The documentation on this page assumes that the user is familiar with the `pepcli` utility's [general usage](Using-pepcli#general-usage) principles. In particular, the user should be able to [ensure that they are enrolled](Using-pepcli#enrollment) with the PEP system. The examples on this page are based on use of a Unix-like environment.
|
|
|
|
|
|
# Uploading data
|
|
|
|
... | ... | @@ -19,7 +17,7 @@ Data can be uploaded into the PEP system by means of [the `pepcli store` command |
|
|
/app/pepcli store -p POM162733743006 -c Holter.Visit1 -i ~/holter/49170044-1C98-4A21-886C-A6E18DE1F885.ecg
|
|
|
```
|
|
|
|
|
|
Because of PEP's [pseudonymization](Pseudonymization) goals, uploaders will often not be privy to a participant identifier. Instead they'll usually have a *short pseudonym*, i.e. an identifier for the data sample. Short pseudonyms can be passed to the `pepcli store` command using the `--sp` switch, e.g.:
|
|
|
Because of PEP's [pseudonymization](Pseudonymization) goals, uploaders will often not be privy to a participant identifier. Instead they'll usually have a *short pseudonym*, i.e. an identifier for the data sample. The `pepcli store` command is therefore more commonly invoked using the `--sp` switch instead of the `-p` switch. E.g.:
|
|
|
|
|
|
```
|
|
|
/app/pepcli store -sp POM1EC7713461 -c Holter.Visit1 -i ~/holter/49170044-1C98-4A21-886C-A6E18DE1F885.ecg
|
... | ... | @@ -39,7 +37,7 @@ PEP provides built-in processing facilities for some data formats. See the secti |
|
|
|
|
|
# Downloading data
|
|
|
|
|
|
Data stored in PEP can be downloaded by [authorized](Access-control#data-access) users. This is commonly achieved by means of [the `pepcli pull` command](Using-pepcli#pull). In its most basic form, the command is invoked to download data for a specific participant (identifier) and column (name), e.g.:
|
|
|
Data stored in PEP can be downloaded by [authorized](Access-control#data-access) users. Users commonly invoke [the `pepcli pull` command](Using-pepcli#pull) to do so. In its most basic form, the command is invoked to download data for a specific participant (identifier) and column (name), e.g.:
|
|
|
|
|
|
```
|
|
|
/app/pepcli pull -p POM162733743006 -c Holter.Visit1
|
... | ... | |