Feature: setting up a logical deletion of documents
- Dominant language
- Python
- Stars
- 26
- Forks
- 28
- Avg merge
- 4h
- Merged PRs (30d)
- 9
Description
Community discussion about this feature (mandatory)
[Link to ](https://forum.camptocamp.org/t/cahier-des-charges-suppression-logique-des-documents/329807?u=loic_p)https://forum.camptocamp.org/t/cahier-des-charges-suppression-logique-des-documents/329807 where this feature has been validated
Is your feature request related to a problem? Please describe.
I deleted by error an outing of a contributor instead of the pictures he wanted to delete.
There is currently no way to retrieve a deleted document.
It would be good to set up a logical deletion of documents, in order to be able to correct a possible error.
So when a contributor (if he has the right) or a moderator deletes a document, whatever it may be, it would have a “Deleted” status in the database and would no longer be visible on the site.
Every year (or more often?), all old documents in the “Deleted” state would be permanently deleted from the database (via a robot?).
We need to add a “deleted” field to the activity feed cards, if it is a separate table. In order to be able to redisplay a deleted document, you must not delete the corresponding card, but only hide it.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked community discussion, which contains the validated requirements. Identify the document and activity-feed data models and the deletion and visibility entry points; the work is done when deleted documents are hidden but recoverable, activity cards are preserved with deleted status, and old deleted records can be permanently purged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100