openlibhums / openlibhums/janeway

Customize Submission Field Options and metadata for Different Calls/Issues

Open
#4,593 0 comments 0 reactions 1 assignee View on GitHub

@ajrbyers is already working on this.

Since Sep 11, 2025.

new feature
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.
Currently, if additional submission fields are added under “submission fields”, those fields are added globally to all articles of all issues. Even to articles in issues that have already been published, those fields and their metadata are added, even though it is not wanted as those submission fields might only be relevant to a specific issue.

Describe the solution you'd like
Allow file options and metadata fields to be customized based on specific issues or article types
Add an option to prevent certain metadata fields from being displayed or
Have an option in the submission field configurator on whether or not the information provided should be fed into the metadata.

Additional context
We have published 12 issues with different types of articles.
For the next issue, we asked authors to write articles of a certain “type”, including certain elements in their articles. We define an article type by the way it's structured. For the 13th issue we only want articles of a specific type (teaching concepts) and thus asked for specific elements in the article. To ensure that authors included these elements, we therefore created different submission fields to be checked by the authors. We later realized that these submission fields also became part of the metadata of the already published articles, even though they did not apply to them.
For our next issues, we may again ask authors to write different types of articles again and we will want authors to confirm that they have uploaded certain elements. At the same time we do not want the information from submission fields to be added to the metadata of all previously published articles.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.