Investigate / create a mechanism for creating a "tombstone" mechanism
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
To be FAIR (A2), we'll need a way to keep the metadata about a piece of content that is published and then deleted in an automatic manner once the action is taken and issue is closed. Hopefully, this can be done either in github or as part of a built-in workflow process.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by defining what metadata must remain when published content is deleted and when the tombstone should be created or closed. Compare a GitHub-based mechanism with a built-in workflow process, then document the chosen approach and its completion criteria. The issue names no files or tests, so the relevant entry points still need to be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100