... | ... | @@ -39,6 +39,20 @@ Note that the PEP system can only accommodate a single file in any given cell. I |
|
|
|
|
|
PEP provides built-in processing facilities for some data formats. Special considerations may apply when uploading data to affected columns. See the [section on that topic](#data-format-processing) for details.
|
|
|
|
|
|
## Deleting data
|
|
|
It is also possible to delete data using `pepcli`. Note that data is never truly deleted, since PEP keeps a version history, and this history is also kept for a file that is deleted. But the data will no longer be visible in new downloads from PEP.
|
|
|
|
|
|
The `pepcli delete` command works very similar to the `pepcli store` command. The only difference is that it does not get any input data. We can for example delete data using:
|
|
|
|
|
|
```
|
|
|
/app/pepcli delete -p POM162733743006 -c Holter.Visit1
|
|
|
```
|
|
|
|
|
|
Or by using a short pseudonym:
|
|
|
```
|
|
|
/app/pepcli delete -sp POM1EC7713461 -c Holter.Visit1
|
|
|
```
|
|
|
|
|
|
# Downloading data
|
|
|
|
|
|
Users commonly invoke [the `pepcli pull` command](Using-pepcli#pull) to download data from PEP. In its most basic form, the command is invoked to download data for a specific participant (identifier) and column (name), e.g.:
|
... | ... | |