GGCE Web issueshttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues2024-01-23T20:56:59+01:00https://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/649Migrate descriptor information to Genesys2024-01-23T20:56:59+01:00Alejandro VelazquezMigrate descriptor information to GenesysWe need to migrate the accession descriptor information from GGCE to Genesys.
This is possible?We need to migrate the accession descriptor information from GGCE to Genesys.
This is possible?Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/562API Error when running GGCE from code2023-05-17T09:47:13+02:00Rizalina SulaboAPI Error when running GGCE from codeHi,
We have been experiencing API errors when running GGCE from code, using the manila.api.genebanks.org as the API server. Our server here at IRRI has been down since last week.
Error starts with saying there is no permissions availabl...Hi,
We have been experiencing API errors when running GGCE from code, using the manila.api.genebanks.org as the API server. Our server here at IRRI has been down since last week.
Error starts with saying there is no permissions available after Login
*Does not have GROUP_ADMINS but ROLE_CLIENT
Does not have ROLE_USER but ROLE_CLIENT
same error when using our API_server here at IRRI
v2023.3-22-gd96cb7a4
![image](/uploads/028f53042a5974819c2676d0e6f63d18/image.png)
![image](/uploads/0544732f7fca7b401d619eb9cdb5000f/image.png)
Thanks2023.4Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/286Application documentation2023-05-12T06:32:54+02:00Milko SkoficApplication documentationForms and lists, in an application such as GG-CE, should have more documentation than only the labels. I think there are three levels of documentation that should be included:
1. _High level documentation_. This documentation should des...Forms and lists, in an application such as GG-CE, should have more documentation than only the labels. I think there are three levels of documentation that should be included:
1. _High level documentation_. This documentation should describe the main operations of the application. It should not enter in any specific user-interface or operative details, but link the general intent of users with the main sections of the application. In other words, it would be an explanation of what the left main menu of the application represents. (Inventory represents the germplasm material stored in the gene bank, the operations...) This documentation should be accessible application wide and served as independent web pages. At this level we might not need to reference any user interface elements.
2. _Activity-related documentation_. This documentation should show users how to perform specific tasks with the application. It should be a series of 1-2-3-... screens or pages that describe the steps needed to complete a task, which elements of the user interface should be used and how to complete each step. For instance if I want to do viability testing with a set of inventories step 1 would be to select the inventories that need to be tested, step 2 involves creating a "Viability test" action, etc. This should be an in-depth tutorial that explains which steps have to be completed in order to fulfil the requirements for the operation. The _specific form documentation_ should be independent, reachable also by an info button on the form itself, so that if I am following a step-to-step tutorial, or if I am in the form and I have doubts on how it works, in both cases we can reach the same page.
3. _Form specific documentation_. This represents documentation to be displayed on the form itself. This is not a separate page, but information to be displayed directly next to the related control. There are several ways to provide such documentation: it could be a text area under the label of an input field, or a popup text area triggered when the user hovers over a control, or the actual content of the form. While the other types of documentation are provided in their own pages, this content should be linked with the labels and language translations currently in the JSON files. Ideally, forms should only show the labels and by pressing an info button activate the display of the documentation.
![Screenshot_2021-07-08_at_15.21.00](/uploads/ab83662ee858ce3b38206aefdbcc9f5d/Screenshot_2021-07-08_at_15.21.00.png)
Let's take this form, for instance. Many of the labels apparently are self explanatory, but in reality they don't provide any indication about the format and content of the related control. For instance "Material or Method Used" may be crystal clear to the gene bank curator, but may be a mystery to the technician that has been tasked to fill the information. Latitude and Longitude seem obvious, but is it decimal degrees? Is it degrees-minutes and seconds? Is there a conversion utility? Uncertainty is numeric, but is it meters or not? We must assume a user that has one more level of ignorance.
We could include from the start the descriptions in the forms, but this will change the layout of all forms and eat up a lot of input space. We can use hovering to display documentation, but what about tablets?
With this ticket I would like to open a discussion to find the best way to organise documentation, both as an ideal user experience and an easy implementation for the development.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/294Ontology-like structure for some controlled vocabularies?2021-07-23T16:04:05+02:00Milko SkoficOntology-like structure for some controlled vocabularies?For instance, "action name" has a larger than usual number of items. These items are also relatively complex, meaning that you need to read well what each item exactly means and you need to read all of them to determine which is the good...For instance, "action name" has a larger than usual number of items. These items are also relatively complex, meaning that you need to read well what each item exactly means and you need to read all of them to determine which is the good choice.
Could it be possible to have a choice interface where these items can be structured as a tree?
For instance you have a series of items that refer to "insects": these could be grouped under an "Insects" section. I think that this would be very helpful when somebody needs to find the right choice among more than 10 items.
Also, "action name" should be managed by users: it should be possible to add new elements in the list, since actions are very closely related to how each gene bank is organised and works. This means that a fool-proof interface for managing controlled vocabularies should be made available, activated or deactivated depending on the specific user's permissions.Vladyslava MokliakVladyslava Mokliakhttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/285Inventory list columns order2021-07-23T13:06:18+02:00Milko SkoficInventory list columns orderIn the Inventory list screen, maybe the “Accession” and “Inventory Number” columns should be swapped, since the latter represents the unique ID and is the one that you click to get the detail view. I mean that the first clickable link on...In the Inventory list screen, maybe the “Accession” and “Inventory Number” columns should be swapped, since the latter represents the unique ID and is the one that you click to get the detail view. I mean that the first clickable link on the left (OK, if we deal with right to left scripts it's all reversed...) represents the link to the item, if the first link is the accession this might confuse?
![Untitled](/uploads/d6d5014a2764d6718d468e63836a65bf/Untitled.png)Vladyslava MokliakVladyslava Mokliakhttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/298Quantity on hand from value and to value2021-07-20T10:34:37+02:00Milko SkoficQuantity on hand from value and to valueI was looking at _Inventory/Amount_ in storage form and I wanted to query by _Quantity on hand_. In the query fields I saw _Quantity on hand from value_ and _Quantity on hand to value_:
- What do those fields mean and accept?
- Is _Quan...I was looking at _Inventory/Amount_ in storage form and I wanted to query by _Quantity on hand_. In the query fields I saw _Quantity on hand from value_ and _Quantity on hand to value_:
- What do those fields mean and accept?
- Is _Quantity on hand_ numeric?
- How can I select all records with positive quantity on hand, or within an interval?
![Screenshot_2021-07-19_at_14.06.33](/uploads/e7c97e2b141d6eb9ef309c1ed20e2b42/Screenshot_2021-07-19_at_14.06.33.png)Vladyslava MokliakVladyslava Mokliakhttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/282Partial image download2021-07-12T10:44:41+02:00Milko SkoficPartial image downloadIn the Inventory/Inventory/Attachments form image attachments don’t download completely. Maybe it is a problem with my internet, or maybe it would help to create a thumbnail?
![Screenshot_2021-07-08_at_14.08.43](/uploads/efcadde8442c3f50...In the Inventory/Inventory/Attachments form image attachments don’t download completely. Maybe it is a problem with my internet, or maybe it would help to create a thumbnail?
![Screenshot_2021-07-08_at_14.08.43](/uploads/efcadde8442c3f5068cc9b05d4bc65fd/Screenshot_2021-07-08_at_14.08.43.png)Vladyslava MokliakVladyslava Mokliakhttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/111Empty blocks2021-02-15T10:32:49+01:00Kiril MorhalenkoEmpty blocks@mobreza Probably we shouldn't show for users blocks without any information? (e.g on any accession page) What doy you think about it? Is it a bug or It connected with incorrect saved accession's data?
![image](/uploads/ca955d318e949462...@mobreza Probably we shouldn't show for users blocks without any information? (e.g on any accession page) What doy you think about it? Is it a bug or It connected with incorrect saved accession's data?
![image](/uploads/ca955d318e949462a8147fb6aa7d56d5/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/grin-global-ui/-/issues/104Client running2020-08-12T13:17:06+02:00Kiril MorhalenkoClient running@mobreza Today I pulled new versions of client and server images and now when I try to start docker with the client I catch an error:
`Error refreshing app token ApiError {
status: 401,
statusText: 'Unauthorized',
data: {
erro...@mobreza Today I pulled new versions of client and server images and now when I try to start docker with the client I catch an error:
`Error refreshing app token ApiError {
status: 401,
statusText: 'Unauthorized',
data: {
error: 'invalid_client',
error_description: 'Bad client credentials`
Could you help me with this issue? Probably it related to problems from my side?
![image](/uploads/0561321606ec22f9b8b6c0ef68a75375/image.png)Matija ObrezaMatija Obreza