core issueshttps://git-r3lab.uni.lu/minerva/core/-/issues2024-03-22T19:58:24+01:00https://git-r3lab.uni.lu/minerva/core/-/issues/2013SBGN-ML export may produce invalid notes2024-03-22T19:58:24+01:00Adrien RougnySBGN-ML export may produce invalid notesWhen exporting in SBGN-ML, nodes that are skipped because not SBGN-compatible are reported in a \<notes\> element at the end of the \<sbgn\> element; this \<notes\> element is not properly formatted as it is not valid xhtml (the \<body\>...When exporting in SBGN-ML, nodes that are skipped because not SBGN-compatible are reported in a \<notes\> element at the end of the \<sbgn\> element; this \<notes\> element is not properly formatted as it is not valid xhtml (the \<body\> element lacks xmlns="http://www.w3.org/1999/xhtml").https://git-r3lab.uni.lu/minerva/core/-/issues/1594rewrite API2024-02-29T14:52:38+01:00Piotr Gawronrewrite APICurrent API implementation is becoming hard to extend and maintain. Here are base points that should be considered when rewriting API:
* all input/output should be entity based json (except when passing file content)
* serialization shou...Current API implementation is becoming hard to extend and maintain. Here are base points that should be considered when rewriting API:
* all input/output should be entity based json (except when passing file content)
* serialization should be done automatically using Jackson
* patch/post/delete requests should handle properly simultaneous modifications of the objects (https://www.mscharhag.com/api-design/rest-concurrent-updates)
* when accessing collections use Pageable interface
* use JPA validation for input parametershttps://git-r3lab.uni.lu/minerva/core/-/issues/2002Feature request: handle user overlays across projects on the same platform2024-02-20T13:46:46+01:00Marek OstaszewskiFeature request: handle user overlays across projects on the same platformCurrently, when new versions of a project are uploaded to the same MINERVA PLatform, overlays have to be manually transferred.
This is error-prone and time consuming, with data potentially propagating against users' intention. MINERVA sh...Currently, when new versions of a project are uploaded to the same MINERVA PLatform, overlays have to be manually transferred.
This is error-prone and time consuming, with data potentially propagating against users' intention. MINERVA should support easier handling of the user overlays within the same platform.
Suggested solutions:
Solution 1:
- user overlays are common across projects, visible for their owner on each project (on the same platform) the owner has access to.
- public/global overlays: a given overlay would be decided as public/global per project.
- challenge: removal of a single root overlay would result in removing it from other projects
- suggestion 1: allow this behaviour under a warning prompt
- suggestion 2: block a removal of an overlay until it's made private on all related projects
Solution 2:
- implement a functionality for user data transfer (in bulk) across projects
- challenge: this would be a manual solution, with data potentially propagating against users' intentionhttps://git-r3lab.uni.lu/minerva/core/-/issues/136Map overlay - flux thickness to big on overview2024-01-11T07:23:04+01:00Alberto NoronhaMap overlay - flux thickness to big on overview![Screenshot_from_2017-07-05_20-52-48](/uploads/43cd33b480124abcd39cc0c366d79f31/Screenshot_from_2017-07-05_20-52-48.png)
The reaction edge thickness for overlay are too thick at the full zoom out.![Screenshot_from_2017-07-05_20-52-48](/uploads/43cd33b480124abcd39cc0c366d79f31/Screenshot_from_2017-07-05_20-52-48.png)
The reaction edge thickness for overlay are too thick at the full zoom out.v18.0https://git-r3lab.uni.lu/minerva/core/-/issues/225User should be able to change his data2024-01-11T07:14:35+01:00Piotr GawronUser should be able to change his datav18.0https://git-r3lab.uni.lu/minerva/core/-/issues/20Advanced search2024-01-09T19:42:53+01:00Piotr GawronAdvanced searchThere should be a way to perform advanced search.
Search should allow to limit results by type/name/annotation.There should be a way to perform advanced search.
Search should allow to limit results by type/name/annotation.v18.0https://git-r3lab.uni.lu/minerva/core/-/issues/166Left panel - User data layout2024-01-09T19:34:36+01:00Marek OstaszewskiLeft panel - User data layoutIn the Info panel, User data is clumped together. This layout should be improved, if possible.In the Info panel, User data is clumped together. This layout should be improved, if possible.v18.0https://git-r3lab.uni.lu/minerva/core/-/issues/278Search and zoom function2024-01-09T19:30:13+01:00Kerstin NeiningerSearch and zoom functionAfter hitting the search button, it is zoomed out completely (which is unfavourable in some applications). I would recommend that the default is not zooming out after a search. But to enable both (zoom out completely or not), an extra bu...After hitting the search button, it is zoomed out completely (which is unfavourable in some applications). I would recommend that the default is not zooming out after a search. But to enable both (zoom out completely or not), an extra button/checkbox that can be checked to enable a zoom out would be nice.v18.0https://git-r3lab.uni.lu/minerva/core/-/issues/599Add possibility to create link from element to overview image2024-01-09T19:27:56+01:00Piotr GawronAdd possibility to create link from element to overview imagerequested by faiz.khan3@uni-rostock.derequested by faiz.khan3@uni-rostock.dev18.0https://git-r3lab.uni.lu/minerva/core/-/issues/952Changes in the layout of the window "Select annotators"2024-01-09T15:25:17+01:00Ewa SmulaChanges in the layout of the window "Select annotators"Please change window *Annotate model automatically:* as below:
- adjust right side windows *available annotators* and *selected annotators*,
- move "Please click on selected annotator to display details at the bottom" next to the *Selec...Please change window *Annotate model automatically:* as below:
- adjust right side windows *available annotators* and *selected annotators*,
- move "Please click on selected annotator to display details at the bottom" next to the *Selected annotator* window, at height of the first annotator,
- shorten the let panel and place Copy from and dropdown list below the list,
- sort the list and categorised as per below. Please put spacing or linr between the categories.
hi @marek.ostaszewski Do you agree with theses changes?
![Screen_Shot_2019-09-13_at_15.59.41](/uploads/2516577fbf9ff495f7e08ad70e042ae0/Screen_Shot_2019-09-13_at_15.59.41.png)![Screen_Shot_2019-09-13_at_15.18.47](/uploads/ebcbcf4211fb3a205c8db64da151cb59/Screen_Shot_2019-09-13_at_15.18.47.png)https://git-r3lab.uni.lu/minerva/core/-/issues/1250Permalinks for maps? URL shortening service for MINERVA maps? - Not a high pr...2024-01-09T15:20:27+01:00Alexander MazeinPermalinks for maps? URL shortening service for MINERVA maps? - Not a high priority but easy to implement?We have long URLs for MINERVA maps, and they do not look too good in papers or emails, especially if one wants to go with zoom level https://asthma.uni.lu/minerva/index.xhtml?id=AA_V42_SBGN&x=2050&y=1050&zoom=4 or even shorter version is...We have long URLs for MINERVA maps, and they do not look too good in papers or emails, especially if one wants to go with zoom level https://asthma.uni.lu/minerva/index.xhtml?id=AA_V42_SBGN&x=2050&y=1050&zoom=4 or even shorter version is not too short https://asthma.uni.lu/minerva/index.xhtml?id=AA_V42_SBGN
On our Disease Maps website, all pages have short URL via permalinks. For example, it is
https://disease-maps.org/parkinsons
and not
https://disease-maps.org/pages/projects/parkinsons.
Maybe we can do something like that?
So for that AA map we could have, for example:
https://asthma.uni.lu/aav42tx
or at least
https://asthma.uni.lu/minerva/aav42tx
instead of
https://asthma.uni.lu/minerva/index.xhtml?id=AA_V42_SBGN&x=2050&y=1050&zoom=4
The permalink can be generated or customised.
It has covered me for some time, I thought of using one of URL shorteners but maybe could be done for all MINERVA users?
Not a high priority but easy to implement? Maybe via creating redirections, or using permalinks, or somehow else.https://git-r3lab.uni.lu/minerva/core/-/issues/1780genome browser isn't working for hg382024-01-09T14:42:03+01:00Ewa Smulagenome browser isn't working for hg38- original ref hg38:[refGene.txt.gz](/uploads/3d473eeca2271a4f6add16cc8ec191dc/refGene.txt.gz)
- corresponding bb file (isn't displaying genes): [refGene38.bb](/uploads/735a7e51e375248e790c5d45cbfa546b/refGene38.bb)
- ref hg38 trimmed...- original ref hg38:[refGene.txt.gz](/uploads/3d473eeca2271a4f6add16cc8ec191dc/refGene.txt.gz)
- corresponding bb file (isn't displaying genes): [refGene38.bb](/uploads/735a7e51e375248e790c5d45cbfa546b/refGene38.bb)
- ref hg38 trimmed to 'basic chromosomes chr1, chr2...': [chromosoms-basic.txt.zip](/uploads/d79819d54cde1dbe9a11d40b1e410ccd/chromosoms-basic.txt.zip)
- bb file that displays hg38 genes in browser (after removing redundant chromosomes): [chromosoms-basic.txt.bb](/uploads/d076008e0acafb03b114839c2c52c151/chromosoms-basic.txt.bb)v18.0Piotr GawronPiotr Gawronhttps://git-r3lab.uni.lu/minerva/core/-/issues/1836Overlay files containing raw numerical data2024-01-09T14:39:12+01:00Luiz LadeiraOverlay files containing raw numerical dataIt would be nice to be able to upload overlay files with one more additional column containing the raw numerical data (without scaling from 0 to 1, or -1 to 1).It would be nice to be able to upload overlay files with one more additional column containing the raw numerical data (without scaling from 0 to 1, or -1 to 1).v18.0https://git-r3lab.uni.lu/minerva/core/-/issues/1867INFO - EXPORT- ELEMENTS - Improved defaults and order?2023-12-21T14:04:55+01:00Alexander MAZEININFO - EXPORT- ELEMENTS - Improved defaults and order?Now I know more about how to export a list of entities with annotation but earlier it was a bit confusing. So, some suggestions:
1. There could be defaults in terms of boxes checked. I would suggest 'Name' in COLUMNS checked together wit...Now I know more about how to export a list of entities with annotation but earlier it was a bit confusing. So, some suggestions:
1. There could be defaults in terms of boxes checked. I would suggest 'Name' in COLUMNS checked together with 'Simple molecule', 'Protein' and 'Gene' in TYPES. When used for the first time, nothing is checked by default and when you click download, you have nothing.
2. The order of checkboxes could be updated, for example 'Name' should go first (top-left corner) as the most needed
3. For some reason I was not noticing options for exporting annotation via the Annotation section. It might to do something with the visual but I simply was ignoring that. Kind of not on the "same level" or not intuitive, I am not sure exactly why. Instead I was focusing on checkboxes, which ones I should actually use. I tried several before discovering that the information I needed was in 'References' in COLUMNS. And now I know that there is a much better way to export it via Annotation section.
4. Defaults could be for Annotation too. I think 'ChEBI', 'HGNC Symbol' and 'UniProt'.https://git-r3lab.uni.lu/minerva/core/-/issues/699Search panel options (admin panel) - small amendments2023-12-21T14:04:41+01:00Ewa SmulaSearch panel options (admin panel) - small amendments1. Divide the table on two parts, with headers:
* Reactions
* Elements
Please review *Name* fields, "element" and "reaction" can be removed.
2. Please change "Show element title" in *Search panel options* tab onto "Show a pin"1. Divide the table on two parts, with headers:
* Reactions
* Elements
Please review *Name* fields, "element" and "reaction" can be removed.
2. Please change "Show element title" in *Search panel options* tab onto "Show a pin"https://git-r3lab.uni.lu/minerva/core/-/issues/1768downloadModel API call with reactionIds with errors2023-11-09T13:01:07+01:00Marek OstaszewskidownloadModel API call with reactionIds with errorsCurrently the API call to download a diagram part by reactionIds:
`$ curl 'https://minerva-service.lcsb.uni.lu/minerva/api/projects/test_project/models/665:downloadModel?handlerClass=lcsb.mapviewer.converter.model.celldesigner.CellDesig...Currently the API call to download a diagram part by reactionIds:
`$ curl 'https://minerva-service.lcsb.uni.lu/minerva/api/projects/test_project/models/665:downloadModel?handlerClass=lcsb.mapviewer.converter.model.celldesigner.CellDesignerXmlParser&reactionIds=1032' -i -X GET`
does not behave properly. In the following example diagram:
[minervar_example](https://minerva-dev.lcsb.uni.lu/minerva/index.xhtml?id=minervar_example)
when calling for:
`curl 'https://minerva-dev.lcsb.uni.lu/minerva/api/projects/minervar_example/models/2578:downloadModel?handlerClass=lcsb.mapviewer.converter.model.celldesigner.CellDesignerXmlParser&reactionIds=496329' -i -X GET`
I get the diagram as in the picture, one element (DRD2) should not be there.
![Screenshot_2022-09-21_at_11.42.06](/uploads/04d74fe3a15ccaa378f2a67ce55a0c82/Screenshot_2022-09-21_at_11.42.06.png)https://git-r3lab.uni.lu/minerva/core/-/issues/1727The field "notification email" should be visible only to admins and project a...2023-11-09T12:25:58+01:00Marek OstaszewskiThe field "notification email" should be visible only to admins and project authorshttps://git-r3lab.uni.lu/minerva/core/-/issues/1656cache drugs/mirnas/chemicals in the background2023-11-09T12:25:55+01:00Piotr Gawroncache drugs/mirnas/chemicals in the backgroundCaching of data for every project should be done in the background.
Moreover, changing organism/disease should trigger re-caching.Caching of data for every project should be done in the background.
Moreover, changing organism/disease should trigger re-caching.https://git-r3lab.uni.lu/minerva/core/-/issues/1655remove project validation and change it to plugin2023-11-09T12:25:52+01:00Piotr Gawronremove project validation and change it to pluginhttps://git-r3lab.uni.lu/minerva/core/-/issues/1740validation of required annotator not working2022-08-25T09:07:36+02:00Ewa Smulavalidation of required annotator not workingParameters selected in "required" are not saved if I change the species. f. ex. if I select required annotator for RNA and close the dialog, they are saved. But if after setting RNA I set up f ex. chemical, required annotators for RNA ar...Parameters selected in "required" are not saved if I change the species. f. ex. if I select required annotator for RNA and close the dialog, they are saved. But if after setting RNA I set up f ex. chemical, required annotators for RNA are forgotten.
![Screen_Shot_2022-08-02_at_18.30.14](/uploads/d022b0689e056091ba99f3e8ab4685db/Screen_Shot_2022-08-02_at_18.30.14.png)Piotr GawronPiotr Gawron