Interface ideas #1
Description
Concept
Have a semi-unified web interface for both viewing (and potentially providing feedback via comments), and then also for curators to make modification proposals.
Implementation:
- Have a tabular(?) interface to view each term plus description, format, occuraence etc (customisabile)
- For the backend we can use the exisitng LinkML converted JSONs
- Need to investigate a way to import whatever ancient extension proposals we have for viewing
- Speak to Mark abou tthis?
- For providing feedback sessions feedback:
- Name, Date, Email, Feedback Session ID (i.e, which group)
- Has a comment field -> button to open a dialgoue pop up to leave the comments, and then press save
- Once filled, press save, and then can press download button to get a (YAML/JSON/or TSV)
- This YAML has whole mixs schema, but additional 'comment' field that includes the commetns from the person giving feedback
- Then the TSV/YAML get's dumped on GitHub, and YAML could be potentailly loaded into a third interface where commetns canb be compared between each term
- For Curator developer workshop for making term update propsal
- Loads TSV/YAMLs from feedback sessions
- Main interface: is just a dsiplay over all the terms as in the tabular session
- Next to each term, two buttons: One for viewing comments, one for editing the term description
- Once completed reviewing the comments, and term edit has been made, press a download button
- This downlaods MixS schema with the the edits, which the curator can then be put on a branch/fork and open a PR - which should just show lines with changes for review before merging