-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust the format of the new concept requests to follow the "official issue templates" #49
Comments
Here is a hopefully more detailed and understandable description of this issue: whenever a user goes to edam-browser, they can navigate the ontology and select a given concept, for instance "Bioinformatics". If the person finds that there is a missing child concept (e.g. here, a topic which would be a child of "Bioinformatics"), he can click on the [+] button on the top right of the Panel This will lead them to a new window that allows to provide the information which should be when asking for a new term. Once they are done providing this information, they click on the [continue to GitHub] button at the bottom right, and end up (after authentication in github) on an issue page which is nicely preformatted. As you can see if you try for yourself, the text for this preformatted issue (title and body) have been simply passed as get parameters to the issue creation page. A nice improvement would be to modify the code which generates these parameters, so that they align more with the format of what is provided in the standard issue templates mentionned above, and results in concept requests such as edamontology/edamontology#609. |
Now it's crystal clear, thanks @hmenager, will implement this. |
for information, this issue is a partial duplicate of #27 |
@hmenager @bryan-brancotte @matuskalas string arr[5]=["format","data","identifier","operation","topic"]; string var = current_branch; //vectors to store input or selected values. //Now on calling function send_to_github() |
Or should I use 16 for no. of attributes for Format type as defined in the new format so that I don't need to count for the no. of attributes for the selected branch. Counting will be needed when I'll generalise, so that if in future no. of attributes is increased then the maintainer don't need to change the code manually for reading those newly added attributes. |
Hi @bryan-brancotte can you review this once 😅 |
Hi, I don't completely get what you are talking in the c++ message and the following message. What I can say is that this issue is not about editing the user interface in the website, it is to change the text of the issue generated by the app and sent to github. Hope this will help |
After suggesting a new concept with EDAM browser, the format of the generated issue should be similar to the following issue templates:
The text was updated successfully, but these errors were encountered: