openlibhums / openlibhums/janeway
Repository: Preprint metadata fields need WYSIWYG editor
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 a Janeway preprints author, I expect to be able to use relevant scientific notion, including superscript and subscript, in the title and abstract fields of the Janeway submission and metadata update forms.
Describe the solution you'd like
The abstract field of the Janeway Repository submission/update form should incorporate the WYSIWYG editor. The field should also remove stray HTML or other code, or have the option to "clean code".
Optionally: The title field of the Janeway Repository submission form should include the WYSIWYG editor.
Example of HTML in Janeway Repository title and abstracts: https://doi.org/10.31223/X50Q6X
Originally the title displayed as Preliminary Development of Machine Learning Emulators for Long-Term Atmospheric CO\textsubscript{2} Evolution because the author had copied & pasted from another viewer. We resolved by editing the title and abstract to include HTML: Preliminary Development of Machine Learning Emulators for Long-Term Atmospheric CO<sub>2</sub> Evolution
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 with the Janeway Repository submission and metadata update forms, focusing on the abstract field and the optional title field. Reproduce the pasted scientific formatting example, then verify that the requested WYSIWYG editing and removal or cleaning of stray code work without leaving unwanted markup in the displayed title or abstract.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, python
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100