openlibhums / openlibhums/janeway
Repository: A single object should be able to support multiple types across different versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
As an author, I may submit my multiple versions of my article to a Janeway Repository in various stages: preprint, preprint, postprint. I expect to be able to assert the type when submitting a new version of my article.
Describe the solution you'd like
"Submission type" should able to be associated with a version of a repository object, and may be updated by the submitting author when submitting a new version post-acceptance.
Contributor guide
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 tracing the repository object version and submission flow, focusing on where submission type is currently assigned. Define how a type is stored per version and how the submitting author can update it for a new version after acceptance. Done means different versions of one object can retain distinct submission types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100