Decisions¶
The decisions that shape this project, each with its reasons, so that a later change can see why things are as they are. A decision that changes an earlier one gets a new record, and the earlier one says which record replaces it.
Copy the template to the next free number and describe the decision in the pull request that makes it.
| Record | Decision | Status |
|---|---|---|
| 0001 | Record the decisions that shape the project | accepted |
| 0002 | Write the archive through the filesystem API of Nextcloud | accepted |
| 0003 | Paperless is the source of the archive | accepted |
| 0004 | Delete only what Paperless has confirmed gone, and only what fits into a run | accepted |
| 0005 | Run the end-to-end tests where a change can make them fail | accepted |
| 0006 | Every file name keeps its marker and its extension, within the bytes of Nextcloud | accepted |
| 0007 | Run the end-to-end tests on the databases and the storage of real installations | accepted |
| 0008 | Reach a Paperless in the local network per request, never for the whole server | accepted |
| 0009 | Keep the SHA-256 and the MD5 of every download, for Paperless-ngx 2 and 3 | accepted |
| 0010 | Mirrored files keep their identity: moved, and updated in place | accepted |
| 0011 | Check every permission that a run needs before the settings are saved, and block only what no run survives | accepted |
| 0012 | Ask for version 9 of the Paperless API in every request, and need Paperless-ngx 2.16 | accepted |
| 0013 | The Activity stream tells the target user what a run did, one entry per run and per import | accepted |
| 0014 | Try unsaved settings with the saved connection, and keep the paths the same in every run | accepted |
| 0015 | Check the app and the answers of its unit tests against a real Paperless-ngx every week | accepted |
| 0016 | Translate a message where its reader is known, and check the German catalog against the code | accepted |
| 0017 | Name new folders in the default language of Nextcloud, and keep the names of every installation in use | accepted |
| 0018 | Runs by hand run as background jobs, and occ runs them in the shell | accepted |
| 0019 | Changes from Paperless arrive through the webhook of its workflows, as runs of one document | accepted |
| 0020 | One connection to Paperless for each run, through a client for that connection | accepted |
| 0021 | The metadata of Paperless goes next to the archive, as a sidecar for each copy and one index | accepted |