c2corg / c2corg/c2c_ui

Feature: setting up a logical deletion of documents

Open
#3,981 1 comment 0 reactions 0 assignees View on GitHub
need API modification
Dominant language
Vue
Stars
29
Forks
33
Avg merge
7m
Merged PRs (30d)
2

Description

**Community discussion about this feature (mandatory)**
[Link to where this feature has been validated
](https://forum.camptocamp.org/t/cahier-des-charges-suppression-logique-des-documents/329807?u=loic_p)

**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 to understand the validated requirements. Then inspect the document deletion flow and activity feed cards; the issue calls for hiding deleted documents, retaining their cards, and supporting later permanent cleanup. Done should cover the deleted status, visibility rules, restoration path, and cleanup behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.