GGCE Support issueshttps://gitlab.croptrust.org/grin-global/support/-/issues2021-03-09T08:44:27+01:00https://gitlab.croptrust.org/grin-global/support/-/issues/1MBe: Accession number part22021-03-09T08:44:27+01:00Matija ObrezaMBe: Accession number part2All `accession` records use only `accession_number_part1` (the Prefix) to store the full accession number (e.g. **WAB0021657**).
This prevents GG-CE from automatically assigning the next number when registering new accessions.
`accessi...All `accession` records use only `accession_number_part1` (the Prefix) to store the full accession number (e.g. **WAB0021657**).
This prevents GG-CE from automatically assigning the next number when registering new accessions.
`accession_number_part1` will be split:
|Accession number|`_part1`|`_part2`|`_part3`| |`_part1`|`_part2`|`_part3`|
|--|--|--|--|--|--|--|--|
|WAB0021657|WAB0021657|`null`|`null`|-->|WAB|21657|`null`|
## Changes
After these changes, use `WAB` for your accession prefix **and** a number. You can use number `-1` to automatically assign the next one in `WAB` group.
![image](/uploads/0070d87db83bbfebe0fafa15c5ad628f/image.png)
You can see the number of accessions in each prefix group at https://mbe.ggce.genebanks.org/a/summary -> "Accession Prefix"Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/2Viability replication count2022-05-18T15:13:24+02:00Matija ObrezaViability replication countMaize database seems to use the number of seed per replicate in `replicationCount`:
![image](/uploads/cc59fb03c4dfd1a3847999f37ca800cd/image.png)
Is that correct?Maize database seems to use the number of seed per replicate in `replicationCount`:
![image](/uploads/cc59fb03c4dfd1a3847999f37ca800cd/image.png)
Is that correct?https://gitlab.croptrust.org/grin-global/support/-/issues/3Addis accession numbers2021-04-19T10:52:19+02:00Matija ObrezaAddis accession numbersAddis does not use `accession_number_part2` (similar to #1) and there is no string prefix at all, just numbers.
```sql
update accession set
accession_number_part2=cast(accession_number_part1 as bigint),
accession_number_part1=''
;
...Addis does not use `accession_number_part2` (similar to #1) and there is no string prefix at all, just numbers.
```sql
update accession set
accession_number_part2=cast(accession_number_part1 as bigint),
accession_number_part1=''
;
update inventory set
inventory_number_part2=cast(inventory_number_part1 as bigint),
inventory_number_part1=''
where
form_type_code= '**'
;
```
I need to check if GG-CE Web allows for a blank prefix (`number_part1`).https://gitlab.croptrust.org/grin-global/support/-/issues/6Gitlab groups2021-03-01T06:32:57+01:00Matija ObrezaGitlab groupsThis GG-CE Support (https://gitlab.croptrust.org/grin-global/support/) project is for all CoP members.
> You have been granted Developer access to the *CGIAR / X* group.
I was cleaning up the permissions on our Gitlab and this is how g...This GG-CE Support (https://gitlab.croptrust.org/grin-global/support/) project is for all CoP members.
> You have been granted Developer access to the *CGIAR / X* group.
I was cleaning up the permissions on our Gitlab and this is how gitlab handles groups of users. This is not intended to be the CGIAR gitlab.
You can access all GG-CE Support issues (of other genebanks) to know what goes on.Lilibeth SisonLilibeth Sisonhttps://gitlab.croptrust.org/grin-global/support/-/issues/7MBe inventory barcodes2021-03-01T06:07:39+01:00Matija ObrezaMBe inventory barcodesInventory barcodes at M'Be use the following format: `${inventoryNamePart1}${inventoryNamePart2}`
![image](/uploads/bb6fbb29ef47ce753314fb64b9d4c5b7/image.png)
- Full inventory name: `LTS 43556 SD`
- Barcode contents: `LTS43556`Inventory barcodes at M'Be use the following format: `${inventoryNamePart1}${inventoryNamePart2}`
![image](/uploads/bb6fbb29ef47ce753314fb64b9d4c5b7/image.png)
- Full inventory name: `LTS 43556 SD`
- Barcode contents: `LTS43556`Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/8Manila inventory barcodes2021-06-11T09:04:13+02:00Matija ObrezaManila inventory barcodesWhat is the contents of your current QR code and 1D barcodes on seed packets in storage?
## Fill GG-CE with barcodes
```sql
update inventory set
barcode=concat('GR-', FORMAT(inventory_number_part2, '0000000000'))
where barcode is null...What is the contents of your current QR code and 1D barcodes on seed packets in storage?
## Fill GG-CE with barcodes
```sql
update inventory set
barcode=concat('GR-', FORMAT(inventory_number_part2, '0000000000'))
where barcode is null and form_type_code != '**' and inventory_maint_policy_id in (2,3,4,5,10,11);
-- And for planted
update inventory set barcode = concat('GRC-',inventory_number_part3,'-',inventory_number_part1,'-',convert(varchar,inventory_number_part2)) from inventory
where form_type_code <>'**' and inventory_maint_policy_id=8 AND INVENTORY_number_part3 is not null;
```Lilibeth SisonLilibeth Sisonhttps://gitlab.croptrust.org/grin-global/support/-/issues/9Manila GG-CE setup2021-03-01T07:51:02+01:00Matija ObrezaManila GG-CE setupSet up **manila** GG-CE server and web.Set up **manila** GG-CE server and web.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/10Manila storage locations2021-03-01T13:50:26+01:00Matija ObrezaManila storage locationsI'm looking at `storage_location_partX` and I see in `part2` values like `UB1-2;UA6` or `UB 1 & 2` or `UC4, UC5, & UD2`.
What does this mean?I'm looking at `storage_location_partX` and I see in `part2` values like `UB1-2;UA6` or `UB 1 & 2` or `UC4, UC5, & UD2`.
What does this mean?Lilibeth SisonLilibeth Sisonhttps://gitlab.croptrust.org/grin-global/support/-/issues/11Mbe access levels2021-05-04T13:53:29+02:00Matija ObrezaMbe access levelsThe different levels of permissions:
| Groups | Users: Creation | Users: Update | Users: View | Passport: Creation | Passport: Update | Passport: View | Inv: Creation | Inv: Update | Inv: View |
|----------------|----------|----...The different levels of permissions:
| Groups | Users: Creation | Users: Update | Users: View | Passport: Creation | Passport: Update | Passport: View | Inv: Creation | Inv: Update | Inv: View |
|----------------|----------|--------|------|----------|--------|------|----------|--------|------|
| Administrator | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Senior Curator | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
| Curator | No | No | No | No | No | Yes | No | Yes | Yes |
| Simple user | No | No | No | No | No | Yes | No | No | Yes |Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/12viability date format2021-03-11T18:24:55+01:00Lilibeth Sisonviability date format@mobreza what does question mark ("??") mean?
![image](/uploads/cd5767a9d40bdcad5e2651672d311770/image.png)@mobreza what does question mark ("??") mean?
![image](/uploads/cd5767a9d40bdcad5e2651672d311770/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/13Verify request items.2023-03-14T14:28:59+01:00Ghost UserVerify request items.Where do I input the order id?Where do I input the order id?Juan Carlos Alarcon MaldonadoJuan Carlos Alarcon Maldonadohttps://gitlab.croptrust.org/grin-global/support/-/issues/16GG-CE webinar2021-05-04T13:53:19+02:00Ghost UserGG-CE webinar@1cgiar/all Please, let me know specific questions regarding the GG-CE that we can answer during the next CoP.@1cgiar/all Please, let me know specific questions regarding the GG-CE that we can answer during the next CoP.https://gitlab.croptrust.org/grin-global/support/-/issues/18Security needs?2021-03-22T06:31:31+01:00Matija ObrezaSecurity needs?This is to record discussion with @1cgiar/mbe about their needs for permissions model in GG-CE:
1. User management:
- Admins only.
1. Passport data:
- Admins and Senior Curators can create and update
- others can view
1. Inven...This is to record discussion with @1cgiar/mbe about their needs for permissions model in GG-CE:
1. User management:
- Admins only.
1. Passport data:
- Admins and Senior Curators can create and update
- others can view
1. Inventory data:
- Admins and Senior Curators can create and update
- Curators can update
- Technicians can updateMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/19GG-CE 2021.1 update2021-05-04T13:52:19+02:00Matija ObrezaGG-CE 2021.1 updateGG-CE for manila, addis, mbe and texcoco updated to the **2021.1** release.
Please check the list of changes at:
- Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.1
- API https://gitlab.croptrust.org/grin-g...GG-CE for manila, addis, mbe and texcoco updated to the **2021.1** release.
Please check the list of changes at:
- Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.1
- API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.1
This release adds:
* Inventory barcoding: inventories in GG-CE can be associated with your existing barcodes. Added support for reading barcodes using (mobile phone) camera.
* Inventory tree: displays hierarchy of inventories (when using parent inventory) to display inventory relationships.
* Date formatting with translation support.
* `accession.doi` must be unique in the database.
* Code value translations are included in full-text search (e.g. `MEX` can be found by its translations `Mexico`, `Meksiko`, `Mexíco`).
* The size of (the last layer of the) Docker image reduced for faster updates.
* SOAP: Search Tool is improved for better compatibility with GG.
Bug fixes:
* Removing accession and inventory attachments.
* Navigation in Code Value editor improved.
* Accession and inventory attachments are correctly removed.
* Accession/Inventory numberPart1 is required but can be blank, numberPart3 is not required (trimmed to null).
* After saving a record, related entities are properly scheduled for reindexing.
* SOAP: Fixed handling of empty `IN ()` query. This affected many CT operations.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/20Ibadan accession numbers2022-05-18T15:14:32+02:00Matija ObrezaIbadan accession numbersSame as grin-global/support#1, Ibadan does not use the numeric `accessionNumberPart2`.
Will split the prefix and the suffix.Same as grin-global/support#1, Ibadan does not use the numeric `accessionNumberPart2`.
Will split the prefix and the suffix.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/21Ibadan deployed2021-05-04T13:52:53+02:00Matija ObrezaIbadan deployedIbadan is now deployed at https://ibadan.ggce.genebanks.org.
It appears most tissue culture inventories are not in the database?
@1cgiar/ibadanIbadan is now deployed at https://ibadan.ggce.genebanks.org.
It appears most tissue culture inventories are not in the database?
@1cgiar/ibadanMarimagne TchambaMarimagne Tchambahttps://gitlab.croptrust.org/grin-global/support/-/issues/22creating inventory.generation problem2021-04-29T06:39:02+02:00Lilibeth Sisoncreating inventory.generation problem@mobreza Every time I pull the latest version and start the server, I get the 503 error. When I read the logs, there's an error in creating generation column in the inventory table. I manually create this column in MS SQL server because ...@mobreza Every time I pull the latest version and start the server, I get the 503 error. When I read the logs, there's an error in creating generation column in the inventory table. I manually create this column in MS SQL server because that's where I store the generation number of inventory records.
here is an example
![image](/uploads/aa13e4ee404bc1252a3df16059ee93c3/image.png)
So each time, I rename the generation column to generation1, then the pull and startup would be successful. Do you have any suggestions on how to solve this?Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/23Texcoco Maize missing tables2021-09-06T11:07:18+02:00Matija ObrezaTexcoco Maize missing tablesThe Maize database is missing several `taxonomy_cwr*` and `taxonomy_regulation*` tables.
These tables are standard in GG schema and the next release **2021.2** will not start up with those tables missing.
I have scripted them from the ...The Maize database is missing several `taxonomy_cwr*` and `taxonomy_regulation*` tables.
These tables are standard in GG schema and the next release **2021.2** will not start up with those tables missing.
I have scripted them from the wheat database and recreated them locally for testing.https://gitlab.croptrust.org/grin-global/support/-/issues/24Ibadan Inventory barcode2021-03-15T05:22:06+01:00Ghost UserIbadan Inventory barcodeThe inventory barcode in Ibadan has 8 digits, with zeros (0) on to the right side as padding, but the current data in the barcode field doesn't have padding.
![image](/uploads/9b02a4d05d452d40680679810ace467e/image.png)
in this example...The inventory barcode in Ibadan has 8 digits, with zeros (0) on to the right side as padding, but the current data in the barcode field doesn't have padding.
![image](/uploads/9b02a4d05d452d40680679810ace467e/image.png)
in this example, the barcode must be `00436375` instead `436375`.
to fix the problem, please, execute this script:
**begin transaction**\
update `inventory`\
set `barcode` = right('00000000' + rtrim(ltrim(barcode)),8)\
where barcode is not null\
**commit transaction**Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/25Ibadan Adding an accession. Error message2021-03-19T12:03:10+01:00Ghost UserIbadan Adding an accession. Error messageI got an error message when I added an accession through Curator-Tool.
![image](/uploads/651e823a956f18e2033b78ffdd83fabb/image.png)
but the accession was `added`.
![image](/uploads/b32537e2c6d68b9796d1d22c5924a8a1/image.png)I got an error message when I added an accession through Curator-Tool.
![image](/uploads/651e823a956f18e2033b78ffdd83fabb/image.png)
but the accession was `added`.
![image](/uploads/b32537e2c6d68b9796d1d22c5924a8a1/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/26Ibadan adding inventory record. Error message2021-03-19T12:02:55+01:00Ghost UserIbadan adding inventory record. Error messageThe CT (Curator-Tool) sends an error message when you tried to create an inventory record. The current version of `get_inventory` dataview doesn't have its field.
Attach the `get_inventory` dataview modified.
[get_inventory_20210313.da...The CT (Curator-Tool) sends an error message when you tried to create an inventory record. The current version of `get_inventory` dataview doesn't have its field.
Attach the `get_inventory` dataview modified.
[get_inventory_20210313.dataviewxml](/uploads/b5eeb9f871844370e6fe3cc4518fedc3/get_inventory_20210313.dataviewxml)https://gitlab.croptrust.org/grin-global/support/-/issues/27error in CT v 1.9.9.42021-03-15T08:12:32+01:00Lilibeth Sisonerror in CT v 1.9.9.4@mobreza here is my error
![image](/uploads/0cef97cd085d6ca18c77173885b0cbe0/image.png)
and here is my config
![image](/uploads/5130b96eab513195c59c4ac6145a84f5/image.png)@mobreza here is my error
![image](/uploads/0cef97cd085d6ca18c77173885b0cbe0/image.png)
and here is my config
![image](/uploads/5130b96eab513195c59c4ac6145a84f5/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/28Supplies and chemicals2021-09-07T19:49:12+02:00Matija ObrezaSupplies and chemicals@erojas documents the need for documenting lab **supplies** (including **chemicals**):
- Screen house, In the field: fertilizer, pesticides, insecticides, or pollinators, etc. (plots)
- In Vitro: culture media
- Cryo: culture media
- ...@erojas documents the need for documenting lab **supplies** (including **chemicals**):
- Screen house, In the field: fertilizer, pesticides, insecticides, or pollinators, etc. (plots)
- In Vitro: culture media
- Cryo: culture media
- Seed: types of envelopes, containers
## Supplies table
Supervisors add new chemicals indicating date of expiration, manufacturer, name of the item, category, unit, temperature storage, status, quantity, location, catalogue, who can use, .... Consider managing minimal stock for each item.
Inside the genebank we have groups one for in Vitro and one for seeds in the headquarters. Other groups are outside the headquarters that manage their chemicals and supplies stock.
This is very similar to the `Inventory` table (status, name, quantity, storage location):
- `xxxId` autogenerated ID
- `xxxTypeCode` The type of the supplies item
- `xxxStatusCode` The current status of the supplies item
- `siteId` the site where this supplies item is stored and used
- `name` name of the supplies item
- `receivedDate` date when the supplies item was received
- `expirationDate` date when the supplies item expires and must not be used
- `quantityUnitCode` the unit of quantity
- `initialQuantity` the initial quantity
- `quantityOnHand` current quantity
- `alertQuantity` alert when `quantityOnHand < alertQuantity`, defaults to *25% of initial quantity*.
- `barcode` item barcode
- `storageLocationPart1`, `storageLocationPart2`, `storageLocationPart3`, `storageLocationPart4` Location in storage
- `manufacturerId` link to `Cooperator` record of the manufacturer or person who mixed the medium
- `methodId` the `Method` documenting how the item was mixed
The treatments uses chemicals and supplies to be produced and their individual stocks are discounted for each technician.
For each item indicate which group will consume it, maybe was purchased by Cryo group and another item purchased for in Vitro group, some items are shared as common use.
## Recording treatments
Applying supplies and chemicals to any `Inventory` is recorded as `InventoryAction`:
![image](/uploads/e6fcfffaf6c44bdbeceb21a22ddabda0/image.png)Edwin RojasEdwin Rojashttps://gitlab.croptrust.org/grin-global/support/-/issues/29Missing CodeValueFields2021-08-19T06:06:02+02:00James AriasMissing CodeValueFieldsThe `inventory_viability_environment` and `inventory_viability_rule` tables, in their fields that must have an associated code value, do not have that association.
As shown in the following images.
`inventory_viability_environment`
![...The `inventory_viability_environment` and `inventory_viability_rule` tables, in their fields that must have an associated code value, do not have that association.
As shown in the following images.
`inventory_viability_environment`
![image](/uploads/1280508a6858f83365087e7b78eda805/image.png)
![image](/uploads/407b989ee58ad8e444da77c36d10203d/image.png)
`Inventory_viability_rule`
![image](/uploads/bf74b3a77852bc049ea743afe6851d94/image.png)
Thank you very much for your attention
Greetings.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/30GG-CE 2021.2 update2021-05-04T13:52:19+02:00Matija ObrezaGG-CE 2021.2 updateGG-CE for addis, ibadan, manila, mbe, palmira, rabat and texcoco updated to the **2021.2** release.
The `v2021.2` release introduces **GG-CE security**, enhanced filtering of accession and inventory records and a number of other improve...GG-CE for addis, ibadan, manila, mbe, palmira, rabat and texcoco updated to the **2021.2** release.
The `v2021.2` release introduces **GG-CE security**, enhanced filtering of accession and inventory records and a number of other improvements to existing GG-CE Web functionality, including bug fixes.
Please check the list of changes at:
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.2
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.2
The **Search panel** can be toggled by clicking the "Search" button and it provides a number of options to find records:
![image](/uploads/2d428419af5d8b8651aa21ad392ae57b/image.png)
The entry page features a barcode scanner (on mobile devices or computers with camera):
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/ecc5f9dd62be596acedd68fb5482f9b1/image.png)
... and you can quickly snap and attach a picture of the material using your mobile phone:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/cbea0572a3141cef8a5bb092ef3fdaa8/image.png)
The inventory tree display is improved:
![image](/uploads/29c1cc73fd70bbd2f357cce4dd801769/image.png)
# GG-CE Security
A new **Permission management** tool is available in the */admin* pages where permissions can be granted users and user groups for specific action areas:
1. Passport data
1. Inventory
1. Cooperators
1. Request management
1. Methods
1. Traits
1. Geography
1. ...
1. and System administration.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/d1d2ec5175dbf1ccf593f33de78d03a0/image.png)
Permissions can also be customized by `Site`.
Action buttons are not displayed when the user does not have appropriate permissions. Regardless, the actual permission check is done by the GG-CE Server.
Auditing information *Created By*, *Modified By* and *Owned By* now displays the username instead of the cooperator name.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/31Palmira deployed2021-05-04T13:53:11+02:00Matija ObrezaPalmira deployedGG-CE for @1cgiar/palmira is deployed with beans data at
- https://palmira.ggce.genebanks.org
- API at https://palmira.api.genebanks.org (also for CT connections)GG-CE for @1cgiar/palmira is deployed with beans data at
- https://palmira.ggce.genebanks.org
- API at https://palmira.api.genebanks.org (also for CT connections)https://gitlab.croptrust.org/grin-global/support/-/issues/32Rabat2021-05-04T13:53:02+02:00Matija ObrezaRabatGG-CE for @1cgiar/rabat with sample data is deployed at:
- https://rabat.ggce.genebanks.org
- API at https://rabat.api.genebanks.orgGG-CE for @1cgiar/rabat with sample data is deployed at:
- https://rabat.ggce.genebanks.org
- API at https://rabat.api.genebanks.orghttps://gitlab.croptrust.org/grin-global/support/-/issues/33Rabat Error adding inventories, in batch mode, with Curator-Tool2021-03-24T14:30:39+01:00Ghost UserRabat Error adding inventories, in batch mode, with Curator-ToolI got the next error adding inventory records in batch mode through the `Copy/Paste` action.
![image](/uploads/1b6b5f69d7d46733d879c9b763bc5ac9/image.png)
Here the details of the error message:
See the end of this message for details ...I got the next error adding inventory records in batch mode through the `Copy/Paste` action.
![image](/uploads/1b6b5f69d7d46733d879c9b763bc5ac9/image.png)
Here the details of the error message:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
```
************** Exception Text **************
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at GRINGlobal.Client.Common.UserInterfaceUtils.ImportTextToDataTableUsingKeys(String rawImportText, DataTable destinationTable, Char[] rowDelimiters, Char[] columnDelimiters, Int32& badRows, Int32& missingRows, LookupTables lookupTables, AppSettings appSettings, UserSettings userSettings)
at GRINGlobal.Client.Common.UserInterfaceUtils.ProcessDGVEditShortcutKeys(DataGridView dgv, KeyEventArgs e, String cno, LookupTables lookupTables, AppSettings appSettings, UserSettings userSettings)
at GRINGlobal.Client.CuratorTool.GRINGlobalClientCuratorTool.ux_datagridviewMain_KeyDown(Object sender, KeyEventArgs e)
at System.Windows.Forms.Control.OnKeyDown(KeyEventArgs e)
```https://gitlab.croptrust.org/grin-global/support/-/issues/34Maintenance site is not visible in GG-CE client2021-03-24T05:37:18+01:00Ghost UserMaintenance site is not visible in GG-CE clientThe maintenance site is not visible in GG-CE client for Accessions neither for inventories.
**Accession**
![image](/uploads/447e5dcac0f3905e2efef8016ae40da1/image.png)
**Inventory**
![image](/uploads/08000414260995d796e334a0274a4d25...The maintenance site is not visible in GG-CE client for Accessions neither for inventories.
**Accession**
![image](/uploads/447e5dcac0f3905e2efef8016ae40da1/image.png)
**Inventory**
![image](/uploads/08000414260995d796e334a0274a4d25/image.png)
but the CT does show the maintenance site.
**Curator-Tool**
![image](/uploads/73ba5991bfce145569025c82200f3ff0/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/35OrderRequest: orderTypeCode and intendedUseCode2021-07-21T11:02:45+02:00James AriasOrderRequest: orderTypeCode and intendedUseCodeWhen the user selects the type of order (`orderTypeCode`), the system only loads the intentions of use of that type (`intendedUseCode`), which can be identified using the `orderTypeCode` prefix:
| group_name | code_value.value |...When the user selects the type of order (`orderTypeCode`), the system only loads the intentions of use of that type (`intendedUseCode`), which can be identified using the `orderTypeCode` prefix:
| group_name | code_value.value | title | description |
|--------------------|------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------|
| ORDER_REQUEST_TYPE | DI | Distribution | The primary reason for the order is distribution of germplasm to a scientist at his/her request. |
| ORDER_INTENDED_USE | DI.BREEDING | Plant Breeding | Plant Breeding. |
| ORDER_INTENDED_USE | DI.COMMERCIAL | Request for material for commercial use | Request for material for commercial use. |
| ORDER_INTENDED_USE | DI.HOME | Home Gardening | Non-research personal use. |
I attach an excel file of how the order type prefixes would be and how it would be identified in the intention of use.
[CODE_VALUES_-_ORDER_REQUEST.xlsx](/uploads/a8cef76d6a6800d89b4123db50c6aa8e/CODE_VALUES_-_ORDER_REQUEST.xlsx)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/36Missing inventory in viability API endpoint2021-03-24T07:14:06+01:00James AriasMissing inventory in viability API endpointIn the response of `/api/v1/i/viability/list` endpoint, the `InventoryViability`'s `inventory` field is `null`. The `inventory` information should be included.
I attach a sample image
![image](/uploads/0b2c140a6f8df0f12f1b94393f5d273f/...In the response of `/api/v1/i/viability/list` endpoint, the `InventoryViability`'s `inventory` field is `null`. The `inventory` information should be included.
I attach a sample image
![image](/uploads/0b2c140a6f8df0f12f1b94393f5d273f/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/37GG-CE Demo website2021-03-25T18:04:09+01:00Matija ObrezaGG-CE Demo websiteWe should set up a GG-CE Demo website at https://demo.ggce.genebanks.org using the Training database.
Please send me the database backup file.We should set up a GG-CE Demo website at https://demo.ggce.genebanks.org using the Training database.
Please send me the database backup file.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/38Error message when add accession data2021-03-30T07:48:19+02:00Andrew ChanError message when add accession dataWhen I add a new accession to ggce, both with ggce and Curator tool got this error message:
Validation failed for classes [org.gringlobal.model.Inventory] during persist time for groups [javax.validation.groups.Default, ] List of const...When I add a new accession to ggce, both with ggce and Curator tool got this error message:
Validation failed for classes [org.gringlobal.model.Inventory] during persist time for groups [javax.validation.groups.Default, ] List of constraint violations:[ ConstraintViolationImpl{interpolatedMessage='must not be null', propertyPath=inventoryMaintenancePolicy, rootBeanClass=class org.gringlobal.model.Inventory, messageTemplate='{javax.validation.constraints.NotNull.message}'} ]
The database is mssql and totally new created, and can add user, site normally.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/39Maize trait observation data2021-05-07T05:28:05+02:00Matija ObrezaMaize trait observation dataWe're working on trait data display:
![image](/uploads/402e20134da8c68cc1bfd4432a491372/image.png)
As you can see, there's a mismatch between the declared `obseration.cropTrait` and the trait code `observation.cropTraitCode` that is po...We're working on trait data display:
![image](/uploads/402e20134da8c68cc1bfd4432a491372/image.png)
As you can see, there's a mismatch between the declared `obseration.cropTrait` and the trait code `observation.cropTraitCode` that is pointing to a different `cropTrait`.
Check with:
```sql
select cto.crop_trait_id 'observation.crop_trait_id', ctc.crop_trait_id 'observation.code.crop_trait_id', count(cto.crop_trait_observation_id) 'COUNT_INVALID_OBSERVATION_TRAITID'
from crop_trait_observation cto
inner join crop_trait_code ctc on ctc.crop_trait_code_id = cto.crop_trait_code_id
where cto.crop_trait_id != ctc.crop_trait_id
group by cto.crop_trait_id, ctc.crop_trait_id;
```https://gitlab.croptrust.org/grin-global/support/-/issues/40How is the quantity or the method sent in inventoryActions in the json request?2021-03-31T08:21:35+02:00James AriasHow is the quantity or the method sent in inventoryActions in the json request?How is quantity or method sent in json request?
If the following service only provides me with these options as shown in the image?
Service: `/api/v1/i/action/start`
![image](/uploads/258341bff17f0bb22e5e8a7aed4441c6/image.png)How is quantity or method sent in json request?
If the following service only provides me with these options as shown in the image?
Service: `/api/v1/i/action/start`
![image](/uploads/258341bff17f0bb22e5e8a7aed4441c6/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/41GG-CE 2021.3 update2021-05-04T13:52:32+02:00Matija ObrezaGG-CE 2021.3 updateThe `v2021.3` release adds a number of improvements to **GG-CE** functionality and several bug fixes.
Please check the complete list of changes at:
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.3
* API ...The `v2021.3` release adds a number of improvements to **GG-CE** functionality and several bug fixes.
Please check the complete list of changes at:
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.3
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.3
New features:
* New API endpoints for accessing trait observations, `SysGroup` members
* System `Inventory` cannot be removed directly, it is removed by removing the `Accession`
* Display the map of the accession source
* Adding inventories to groups and to orders uses a new **Inventory picker**
* Filter Accessions and inventories by their maintenance site and inventory maintenance policy
* Added new (too many to list) filtering options for accessions, inventories, orders, ...
* Added management of **Geography** and **Methods** records
* Display members of the *User group* in group details page
* *Preview of* browsing trait observation data -- we need your feedback for improvements!
Bug fixes:
* Fixed bug in the SOAP interface that prevented saving any numeric values
* Group `ADMINS` is granted permissions on all GGCE-SEC actions
* Actions (think Inventory and Accession actions) accept all supported fields
* Implemented filtering of inventories and accessions by site
* Form must not update fields from inventory maintenance policy if the policy did not change.
* Ensure user's permissions are refreshed on page load
* Printing pages from GG-CE is fixed
# Accession source maps
GG-CE displays a map of the location of each accession source that includes coordinate data:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/26b888f8679d0ca6370f926f7a2cc55e/image.png)
# Filters
Many new options are available to find accessions and inventories! You need to test it and let us know if there are filters that are still missing!
# Inventory picker
A new tool for selecting inventories is available for adding records to Groups and Orders! All standard inventory search options are included.
Select the inventory by selecting the *table row* (or more rows), then click "Add":
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/388b9ac91fa090b1bbc00a68412795b4/image.png)
# Trait data
We developed the *DRAFT* version of browsing crop trait observation data.
You can select traits of interest by tapping the trait name and the table will be updated with data for the selected traits:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/c1a324ab5c62605e20d249aba61e2553/image.png)
*Note:* Only the first few records are displayed. We need your input and feedback how to make it more useful!
# Managing permissions
The **Permission editor** is simplified. The more complex options are available under "Advanced" expansion box:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/7ec1cff0aa2b4506faa9efdb07c381b6/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/42Service to query data from any database view2021-05-04T13:53:44+02:00James AriasService to query data from any database viewPerform a service that receives as a parameter the name of an existing view in the GG-CE SQL Server database and that returns the JSON with the headers and the corresponding data. In this way, it is easy to make a view through the databa...Perform a service that receives as a parameter the name of an existing view in the GG-CE SQL Server database and that returns the JSON with the headers and the corresponding data. In this way, it is easy to make a view through the database and then consult it through the services.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/43Creating Inventories for `OrderRequestItem`2022-05-18T07:30:52+02:00James AriasCreating Inventories for `OrderRequestItem`**CASE 1:** This is the current way in which GG creates an order, associating the item of the order to the `parent inventory`. The inventories resulting from the order (`child inventories`) are not related to the order request (only to t...**CASE 1:** This is the current way in which GG creates an order, associating the item of the order to the `parent inventory`. The inventories resulting from the order (`child inventories`) are not related to the order request (only to the `parent inventory`). When you want to know what order one of the `child inventories` belongs to, you cannot know (the `parent inventory` has the relationship with multiple orders).
**CASE 2:** The relation of the order item is made with the `child inventory`, so it is easy to know which order it belongs to. In this way, it improves the traceability of the information.
**Instance diagram is attached**
![Inventarios-CREACION_NUEVA_ORDEN](/uploads/3c5577c859c096b502c6014e20f86159/Inventarios-CREACION_NUEVA_ORDEN.png)
**Thank you very much for your attention**Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/44Adjust Inventory Quantity - not updating2021-04-12T10:40:14+02:00Rizalina SulaboAdjust Inventory Quantity - not updatingHi. The changes in quantity on hand was not updated after saving
![image](/uploads/89c1130c244d9a50620ee4e9dec26f98/image.png)Hi. The changes in quantity on hand was not updated after saving
![image](/uploads/89c1130c244d9a50620ee4e9dec26f98/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/45Bug: Adjust Inventory Quantity - not updating2021-04-20T02:07:39+02:00Rizalina SulaboBug: Adjust Inventory Quantity - not updatingHi. The changes in quantity on hand was not updated after saving
![image](/uploads/cbc2397318aa3f0094eb2c280f655f3a/image.png)
## Form uses invalid date format
```
YYYY-MM-DD is not a valid CodeValue of DATE_FORMAT
```Hi. The changes in quantity on hand was not updated after saving
![image](/uploads/cbc2397318aa3f0094eb2c280f655f3a/image.png)
## Form uses invalid date format
```
YYYY-MM-DD is not a valid CodeValue of DATE_FORMAT
```Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/46Users groups. Remove button is not working2022-05-18T15:14:59+02:00Ghost UserUsers groups. Remove button is not workingThe button `REMOVE` in the **User groups** option doesn't work because although you click on it, the **User group** remained available and visible.
One more thing, how can I remove and user from one group?The button `REMOVE` in the **User groups** option doesn't work because although you click on it, the **User group** remained available and visible.
One more thing, how can I remove and user from one group?Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/47Inventory Picker / filter : request2021-04-20T10:15:38+02:00Rizalina SulaboInventory Picker / filter : requestHi. While testing Inventory filter/picker, found that I could not search for inventory suffix under a specific inventory maintenance policy.
![image](/uploads/270059aa6c880461a57fd80cd0f70458/image.png)
Here is the same filter variabl...Hi. While testing Inventory filter/picker, found that I could not search for inventory suffix under a specific inventory maintenance policy.
![image](/uploads/270059aa6c880461a57fd80cd0f70458/image.png)
Here is the same filter variables just without the Full text search for Base
![image](/uploads/862bc535edbf7a9ab0e5b5e57fce907d/image.png)
Sample inventory to filter
![image](/uploads/e9aaeb2449ec4543d9b2c7cac0e00843/image.png)
Can you please add Inventory Suffix in the inventory filter/picker? ThanksMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/48Trait name repeated many times.2021-04-15T07:41:18+02:00Ghost UserTrait name repeated many times.Why does the trait name repeat two or more times in some cases (see image)?
![image](/uploads/1abf0fe846c7b9b963a057e43c6cea05/image.png)
The problem is in `Wheat Collection`.Why does the trait name repeat two or more times in some cases (see image)?
![image](/uploads/1abf0fe846c7b9b963a057e43c6cea05/image.png)
The problem is in `Wheat Collection`.https://gitlab.croptrust.org/grin-global/support/-/issues/49GG-CE 2021.4 update2021-05-04T13:52:32+02:00Matija ObrezaGG-CE 2021.4 update`v2021.4` enables adding and editing Inventory Actions and makes the forms more user friendly.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/49
* Web https://git...`v2021.4` enables adding and editing Inventory Actions and makes the forms more user friendly.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/49
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.4
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.4
New features and improvements:
* Filter inventories by `inventoryNumberPart3`, full-text search supports filtering by inventory maintenance policies
* Accession and Inventory **summaries support filters**
* Add and edit Inventory actions
* All edit and create **forms use dialogs**, modified form **fields are highlighted**
* Remove or edit selected table rows
* InventoryMaintenancePolicy: added `managementTypeCode` field:
* Code value group `MANAGEMENT_TYPE` of `ACTIVE`, `BASE`, `BACKUP`, `ARCHIVED`, `DISTRIBUTION`, `TEMPORARY`
* Existing policies are assigned `TEMPORARY` type
* Added a "trigger" to update Inventory status based on quantity on hand
* Added a "trigger" to record changes to Accession number and taxonomy species
# Forms
The forms are displayed as dialogs and fields modified by the user are highlighted. This allows the user to decide between saving the updates or canceling their changes.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/61724a4b0c6a6d90df43be361cb50c06/image.png)
Table rows can selected for removal:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/23ad1fef93151165d0ae61b5e8363bc5/image.png)
... or editing:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/31b037fe0e86f1608bc2c371cd3be740/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/50Feedback on GG-CE2021-09-14T10:58:48+02:00Matija ObrezaFeedback on GG-CEFor a healthy development of GG-CE, we need @1cgiar/all genebanks to present their **current GG-CE instance** to a small group of technicians, curators and the genebank manager.
At the next meeting of the CoP on May, the fourth *be with...For a healthy development of GG-CE, we need @1cgiar/all genebanks to present their **current GG-CE instance** to a small group of technicians, curators and the genebank manager.
At the next meeting of the CoP on May, the fourth *be with you*, you will present to the group the feedback from your colleagues about GG-CE.
## Guidelines
1. Add user accounts and assign permissions as required.
1. Provide instructions on how to access GG-CE on the mobile phone (or desktop, tablet) to your colleagues.
1. Make sure they are able to login to GG-CE.
1. Answer their questions with support from @jalarcon and @mobreza about the system (use https://gitlab.croptrust.org/grin-global/support)
# Gathering feedback
Talk to your users!
1. What is their general impression of the system?
1. Can they find the accessions/inventories of interest?
1. What functions would they like to see implemented in the future?
Let us know below if you have questions.
Looking forward to 4 May CoP meeting!https://gitlab.croptrust.org/grin-global/support/-/issues/51New Request/Distribution error2021-04-21T09:06:05+02:00Rizalina SulaboNew Request/Distribution errorHi, New request vcard on our page 'Not found'
![image](/uploads/ff4c7ef7999561f492b27d15d25105fc/image.png)
![image](/uploads/fd3e24e36fef5ca5693a0273e6016d3c/image.png)
while the Add New request from the Distribution vcard is working ...Hi, New request vcard on our page 'Not found'
![image](/uploads/ff4c7ef7999561f492b27d15d25105fc/image.png)
![image](/uploads/fd3e24e36fef5ca5693a0273e6016d3c/image.png)
while the Add New request from the Distribution vcard is working fine
![image](/uploads/dc35179086d2c6ee26084fbfc0d1171e/image.png)
thankshttps://gitlab.croptrust.org/grin-global/support/-/issues/52Verify Request Items error2021-04-21T10:31:38+02:00Rizalina SulaboVerify Request Items errorHi. The verify items button from the this page is not working, or is there a specific item status for it to work? thanks
![image](/uploads/bdef76a3586be702d3783b5f6736fc89/image.png)Hi. The verify items button from the this page is not working, or is there a specific item status for it to work? thanks
![image](/uploads/bdef76a3586be702d3783b5f6736fc89/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/53INTEGRATE ENTITY INVENTORY IN PARENTINVENTORY COLUMN2021-05-04T13:50:26+02:00James AriasINTEGRATE ENTITY INVENTORY IN PARENTINVENTORY COLUMN**Good afternoon!!!**
Is it possible to integrate the `inventory` entity in the `parentInventory` column in the JSON?
Currently the JSON `inventory` comes in this form
![image](/uploads/f0f59a8092c77e9cf93c2c560b395a26/image.png)
Tha...**Good afternoon!!!**
Is it possible to integrate the `inventory` entity in the `parentInventory` column in the JSON?
Currently the JSON `inventory` comes in this form
![image](/uploads/f0f59a8092c77e9cf93c2c560b395a26/image.png)
Thank you very much!Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/54Manila restore2021-04-26T13:40:41+02:00Matija ObrezaManila restore@1cgiar/manila I will begin restoring the lastest database sent by @lsison. GG-CE will be offline until the restore is complete.@1cgiar/manila I will begin restoring the lastest database sent by @lsison. GG-CE will be offline until the restore is complete.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/55CODE VALUE DOES NOT LOAD2021-04-28T08:48:43+02:00James AriasCODE VALUE DOES NOT LOADGood morning @mobreza
What should be done if the code values are not loaded as shown in the image.
![image](/uploads/3282b1eda15f6599deb1feaa79ad2573/image.png)Good morning @mobreza
What should be done if the code values are not loaded as shown in the image.
![image](/uploads/3282b1eda15f6599deb1feaa79ad2573/image.png)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/56PROBLEM IN APPLYING THE CREATEDDATE FILTER IN INVENTORY2021-04-27T06:50:22+02:00James AriasPROBLEM IN APPLYING THE CREATEDDATE FILTER IN INVENTORYGood morning @mobreza
I am trying to re-create the createdDate filter in the inventory entity in the JSON, in order to obtain the inventory records, but it is not applying the filter to me.
I am creating it this way
![image](/uploads...Good morning @mobreza
I am trying to re-create the createdDate filter in the inventory entity in the JSON, in order to obtain the inventory records, but it is not applying the filter to me.
I am creating it this way
![image](/uploads/773d51b221d5ab861eb2201772e310ef/image.png)
The filter result
![image](/uploads/b475eebb689da27e332b0ee43e3a04e6/image.png)
Could you tell me how is the correct way?
Thank youMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/57Error creating a system user2021-04-28T08:49:23+02:00James AriasError creating a system userGood Afternoon @mobreza
When creating a system user an error is appearing as shown in the following image.
![image](/uploads/98cc9f82f238bbba8ea2ebb6d44a6fe8/image.png)
**I attach a .txt file with the logs**
I understand from the l...Good Afternoon @mobreza
When creating a system user an error is appearing as shown in the following image.
![image](/uploads/98cc9f82f238bbba8ea2ebb6d44a6fe8/image.png)
**I attach a .txt file with the logs**
I understand from the logs, is that the `id` field must be from the `sys_user` table is null
[Logs.txt](/uploads/f13f002ac5b4b108c8535ef326b71498/Logs.txt)
Thank you
RegardsMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/58Lima2021-05-11T07:47:53+02:00Matija ObrezaLima@1cgiar/lima your GG-CE instance is set up and accessible at https://lima.ggce.genebanks.org. The CT can connect to https://lima.api.genebanks.org.@1cgiar/lima your GG-CE instance is set up and accessible at https://lima.ggce.genebanks.org. The CT can connect to https://lima.api.genebanks.org.Edwin RojasEdwin Rojashttps://gitlab.croptrust.org/grin-global/support/-/issues/59Docker images not found2021-05-11T07:47:43+02:00James AriasDocker images not found**Good morning** @mobreza
Ciat-Redes informs me that they had problems pulling the images from the docker's both the web and the server.
The images were obtained with the versions that you indicated to Juan Carlos.
> For your local do...**Good morning** @mobreza
Ciat-Redes informs me that they had problems pulling the images from the docker's both the web and the server.
The images were obtained with the versions that you indicated to Juan Carlos.
> For your local docker, upgrade the server to tag 2021.4.1
> and the gg-ce-web:2021.4.2
I attach the link to the images and two screenshots of the problem.
**Web:** https://dockerhub.croptrust.org/grin-global/grin-global-ui/gg-ce-web:2021.4.2
**API:** https://dockerhub.croptrust.org/grin-global/grin-global-server:2021.4.1
![Error1](/uploads/958bd57abe00da7584506275faa90839/Error1.png)
![Error2](/uploads/aa63798de017d5cfd7fde20b7eef3b4e/Error2.png)
Thank you
RegardsMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/61Lima GG-CE instance. Deploy2021-05-11T07:48:06+02:00Ghost UserLima GG-CE instance. DeployPlease, **deploy** the Lima GG-CE instance with the default GG database (Geography, Taxonomy, code values, etc data available).
They will upload their data from the scratch through the CT.Please, **deploy** the Lima GG-CE instance with the default GG database (Geography, Taxonomy, code values, etc data available).
They will upload their data from the scratch through the CT.https://gitlab.croptrust.org/grin-global/support/-/issues/60Order Wizard. Error to load the Order request data.2021-09-10T03:21:30+02:00Ghost UserOrder Wizard. Error to load the Order request data.I got this error when the Order Wizard is opening.
![image](/uploads/a5cc350d66e046eccb0805b1077147b5/image.png)
Curator-Tool version: v1.9.9.8
GG-CE instance: texcoco-w.api.genebanks.org
**Attach the full error message text.**
```
...I got this error when the Order Wizard is opening.
![image](/uploads/a5cc350d66e046eccb0805b1077147b5/image.png)
Curator-Tool version: v1.9.9.8
GG-CE instance: texcoco-w.api.genebanks.org
**Attach the full error message text.**
```
System.IndexOutOfRangeException: Cannot find column received_date.
at System.Data.DataTable.ParseSortString(String sortString)
at System.Data.DataView.set_Sort(String value)
at OrderWizard.OrderWizard.RefreshOrderData()
at OrderWizard.OrderWizard.OrderWizard_Load(Object sender, EventArgs e)
```
[OrderWizardTextErrorMessage.txt](/uploads/b38938de10354b3945927e01c2d19e74/OrderWizardTextErrorMessage.txt)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/62Mbe: Restore recent backup2021-04-30T11:26:05+02:00Matija ObrezaMbe: Restore recent backup@rtohoun asked for a restore of a recent GG backup to GG-CE.
## Missing tables
The `taxonomy_cwr` table is missing from your schema. Please add it to your copy of the database:
```sql
CREATE TABLE [dbo].[taxonomy_cwr](
[taxonomy_cwr_...@rtohoun asked for a restore of a recent GG backup to GG-CE.
## Missing tables
The `taxonomy_cwr` table is missing from your schema. Please add it to your copy of the database:
```sql
CREATE TABLE [dbo].[taxonomy_cwr](
[taxonomy_cwr_id] [int] IDENTITY(1,1) NOT NULL,
[taxonomy_species_id] [int] NOT NULL,
[crop_name] [nvarchar](100) NOT NULL,
[display_name] [nvarchar](100) NULL,
[crop_common_name] [nvarchar](100) NULL,
[is_crop] [nvarchar](1) NOT NULL,
[genepool_code] [nvarchar](20) NULL,
[is_graftstock_genepool] [nvarchar](1) NOT NULL,
[trait_class_code] [nvarchar](20) NULL,
[is_potential] [nvarchar](1) NOT NULL,
[breeding_type_code] [nvarchar](20) NULL,
[breeding_usage] [nvarchar](100) NULL,
[ontology_trait_identifier] [nvarchar](20) NULL,
[citation_id] [int] NULL,
[note] [nvarchar](max) NULL,
[created_date] [datetime2](7) NOT NULL,
[created_by] [int] NOT NULL,
[modified_date] [datetime2](7) NULL,
[modified_by] [int] NULL,
[owned_date] [datetime2](7) NOT NULL,
[owned_by] [int] NOT NULL,
CONSTRAINT [PK_taxonomy_cwr] PRIMARY KEY CLUSTERED
(
[taxonomy_cwr_id] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
ALTER TABLE [dbo].[taxonomy_cwr] ADD DEFAULT ('N') FOR [is_graftstock_genepool]
GO
ALTER TABLE [dbo].[taxonomy_cwr] WITH CHECK ADD CONSTRAINT [fk_tcwr_cit] FOREIGN KEY([citation_id])
REFERENCES [dbo].[citation] ([citation_id])
GO
ALTER TABLE [dbo].[taxonomy_cwr] CHECK CONSTRAINT [fk_tcwr_cit]
GO
ALTER TABLE [dbo].[taxonomy_cwr] WITH CHECK ADD CONSTRAINT [fk_tcwr_created] FOREIGN KEY([created_by])
REFERENCES [dbo].[cooperator] ([cooperator_id])
GO
ALTER TABLE [dbo].[taxonomy_cwr] CHECK CONSTRAINT [fk_tcwr_created]
GO
ALTER TABLE [dbo].[taxonomy_cwr] WITH CHECK ADD CONSTRAINT [fk_tcwr_modified] FOREIGN KEY([modified_by])
REFERENCES [dbo].[cooperator] ([cooperator_id])
GO
ALTER TABLE [dbo].[taxonomy_cwr] CHECK CONSTRAINT [fk_tcwr_modified]
GO
ALTER TABLE [dbo].[taxonomy_cwr] WITH CHECK ADD CONSTRAINT [fk_tcwr_owned] FOREIGN KEY([owned_by])
REFERENCES [dbo].[cooperator] ([cooperator_id])
GO
ALTER TABLE [dbo].[taxonomy_cwr] CHECK CONSTRAINT [fk_tcwr_owned]
GO
ALTER TABLE [dbo].[taxonomy_cwr] WITH CHECK ADD CONSTRAINT [fk_tcwr_ts] FOREIGN KEY([taxonomy_species_id])
REFERENCES [dbo].[taxonomy_species] ([taxonomy_species_id])
GO
ALTER TABLE [dbo].[taxonomy_cwr] CHECK CONSTRAINT [fk_tcwr_ts]
GO
```Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/63Barcode in Check Request items2021-04-30T06:34:12+02:00Rizalina SulaboBarcode in Check Request itemsHi, The barcode to scan items in Form 'Check Request Items' is incorrect for us. It reads the inventory ID but we are using a different format for the barcode here in Manila. Can it be please changed? Thank You
![image](/uploads/6ee92000...Hi, The barcode to scan items in Form 'Check Request Items' is incorrect for us. It reads the inventory ID but we are using a different format for the barcode here in Manila. Can it be please changed? Thank You
![image](/uploads/6ee9200029f5a8c48685c180dbe6ed8a/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/64Adding New Accession error2021-04-30T06:29:20+02:00Rizalina SulaboAdding New Accession errorHi, while adding a new accession, it gave this error of validation for 'NOT SET'
![image](/uploads/b768eca6dba526570a3307d733981919/image.png)
thanksHi, while adding a new accession, it gave this error of validation for 'NOT SET'
![image](/uploads/b768eca6dba526570a3307d733981919/image.png)
thanksMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/65Hyderabad GG-CE instance. Deploy2021-05-11T07:47:29+02:00Ghost UserHyderabad GG-CE instance. DeployPlease, **deploy** the Hyderabad GG-CE instance.
The GG backup of Hyderabad is available in google drive (`2021CGIAR - ICRISAT` folder)
For the moment, the DB only has accessions with basic information (~15K accessions of groundnut cr...Please, **deploy** the Hyderabad GG-CE instance.
The GG backup of Hyderabad is available in google drive (`2021CGIAR - ICRISAT` folder)
For the moment, the DB only has accessions with basic information (~15K accessions of groundnut crop).Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/66Recording MLS status in GG-CE2022-05-18T15:15:30+02:00Matija ObrezaRecording MLS status in GG-CEGG-CE can be extended with a new field `mls_status` in the `accession` table, using the MLSSTATUS code value group to ensure a fixed set of allowed values. The field is not mandatory and is initially set to the undetermined (NULL) value....GG-CE can be extended with a new field `mls_status` in the `accession` table, using the MLSSTATUS code value group to ensure a fixed set of allowed values. The field is not mandatory and is initially set to the undetermined (NULL) value.
Available codes in this group are based on the relevant descriptor used by the GLIS DOI Registration Service:
| Code value | Title | GLIS Description | GLIS Code | Genesys |
|-------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------|
| N | Not in MLS | Not available under the MLS | 0 | 0 |
| Y | In MLS* | Available under the MLS | 1 | 1 |
| ANNEX1 | In MLS (Annex I) | The PGRFA belongs to a crop listed in Annex I and is under the management and control of a Contracting Party to the Treaty and declared to be in the public domain | 11 | 1 |
| ARTICLE15 | In MLS (Article 15) | The sample is in a collection subject to an agreement concluded under Article 15 of the Treaty | 12 | 1 |
| SMTA_SOURCE | In MLS (Received with SMTA) | The holder received the sample with SMTA | 13 | 1 |
| VOLUNTARY | In MLS (Voluntary inclusion) | The holder has voluntarily placed the PGRFA into the MLS | 14 | 1 |
| MLS_DEVELOP | In MLS (Under development) | The PGRFA is derived from, and distinct from, material previously received from the MLS, is still under development and not yet ready for commercialization, and may be made available at the discretion of the developer | 15 | 1 |
Genebanks are advised to avoid the use of the `Y` code and rather use one of the more specific options.
@1cgiar/all Your feedback is appreciated before we make changes.https://gitlab.croptrust.org/grin-global/support/-/issues/67barcodes on planted materials2021-05-05T05:10:20+02:00Lilibeth Sisonbarcodes on planted materials@mobreza , please update barcode in the inventory table for planted materials (inventory_maint_policy_id = 8) :
`update inventory
set barcode = concat('GRC-',inventory_number_part3,'-',inventory_number_part1,'-',convert(varchar,inventor...@mobreza , please update barcode in the inventory table for planted materials (inventory_maint_policy_id = 8) :
`update inventory
set barcode = concat('GRC-',inventory_number_part3,'-',inventory_number_part1,'-',convert(varchar,inventory_number_part2))
from inventory
where form_type_code <>'**'
and inventory_maint_policy_id =8
AND INVENTORY_number_part3 is not null `Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/68barcodes on received seeds and seed file records2021-04-30T23:55:17+02:00Lilibeth Sisonbarcodes on received seeds and seed file records@mobreza please update barcodes for incoming/ received seeds and seed file records (inventory_maint_policy_id IN (6,7))
`update inventory
set barcode =
left(inventory_number_part1,1)+RIGHT('0000' + CONVERT(VARCHAR,inventory_number_part2...@mobreza please update barcodes for incoming/ received seeds and seed file records (inventory_maint_policy_id IN (6,7))
`update inventory
set barcode =
left(inventory_number_part1,1)+RIGHT('0000' + CONVERT(VARCHAR,inventory_number_part2), 4)+'/'+SUBSTRING(inventory_number_part1,2,4)
from inventory
where form_type_code <>'**'
and inventory_maint_policy_id IN (6,7)`Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/69Leuven GG-CE instance. Deploy2021-05-11T07:47:20+02:00Ghost UserLeuven GG-CE instance. DeployPlease, **deploy** the Leuven GG-CE instance.
The GG backup of Leuven is available in google drive (`2021CGIAR - ITC` folder)
For the moment, the DB only has accessions with basic information (1.5K accessions).
@ekempenaersPlease, **deploy** the Leuven GG-CE instance.
The GG backup of Leuven is available in google drive (`2021CGIAR - ITC` folder)
For the moment, the DB only has accessions with basic information (1.5K accessions).
@ekempenaersMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/70GG-CE 2021.5 update2021-05-14T09:20:50+02:00Matija ObrezaGG-CE 2021.5 updateI’m happy to announce the availability of the **v2021.5** release of GG-CE.
This release has a number of improvements to GG-CE functionality and several bug fixes. This release includes browsing aggregated inventory amounts (by accessio...I’m happy to announce the availability of the **v2021.5** release of GG-CE.
This release has a number of improvements to GG-CE functionality and several bug fixes. This release includes browsing aggregated inventory amounts (by accession), FAO WIEWS code can be assigned to Cooperators. A new section of GG-CE Web for **in vitro** collections is added. The data model is (again) synchronized with the USDA version.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/70
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.5
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.5
New features:
* Added a separate section for in vitro tools
* Browse aggregated inventories in storage
* Users can set their passwords and admins can manage user passwords.
* Admins receive important system notifications when accessing /admin page
* Cooperator form and filters updated with `faoInstituteNumber`
Improvements and bug fixes:
* Fixed issue with filtering by auditing fields (e.g. `createdDate`)
* Data model synchronized with USDA version (see f1098d59)
* Barcode scanner only uses inventory barcodes, not inventory `id`
* Accession details page: Backup sites are now displayed
## Admin alerts
Administrators receive notifications of any critical issues encountered by the server:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/8d9aa9b4752b06dc208cdb939999c64b/image.png)
## In vitro: Discarding material
A new section of GG-CE Web for **in vitro** collections is added. The first tool for technicians is for discarding infected or dead tissue culture material by scanning the barcodes on tubes:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/c5716f380828e7e69f0a6f060e5a938d/image.png)
## Aggregated inventory data
Since inventories of any accession are stored in different locations, follow different maintenance policies, it's useful to have access to aggregated quantity on hand (by accession). Apply filters for location to get the summary report:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/94eeeb76123979e220858f11c379767b/image.png)
## Changing your password
Users are (finally) able to change their GG-CE password in the web interface:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/5db2c425f9923f4c46fe83bbac0148de/image.png)
/cc @1cgiar/allMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/71Doesn't show all inventory maintenance policy2021-05-05T05:37:06+02:00James AriasDoesn't show all inventory maintenance policyGood morning/Afternoon @mobreza
When I want to filter the inventories by the `inventory maintenance policy`, it is not showing me all the inventory maintenance policies that are registered in the `database`.
**Do you know why this is?...Good morning/Afternoon @mobreza
When I want to filter the inventories by the `inventory maintenance policy`, it is not showing me all the inventory maintenance policies that are registered in the `database`.
**Do you know why this is?**
- The first image corresponds to the `inventory maintenance policy` that appears in the inventories.
- The second image corresponds to the `inventory maintenance policy` registered in the DB
![ErrorMaintPolicy_Inventory_2](/uploads/aff9cfe869b2d8a11cc5b3d242378d26/ErrorMaintPolicy_Inventory_2.png)
![image](/uploads/8de685dacd3a2e1199f228dd1c5e306c/image.png)
Thank youMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/72Notify sys_user by Email?2022-05-18T06:30:23+02:00James AriasNotify sys_user by Email?Good morning/Afternoon @mobreza
Suddenly are you thinking of creating an email notification to the `sys_user` created, and that it will send you as a link to change the password or confirm the registration?
Thank youGood morning/Afternoon @mobreza
Suddenly are you thinking of creating an email notification to the `sys_user` created, and that it will send you as a link to change the password or confirm the registration?
Thank youMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/73How to use wildcards?2021-05-05T10:01:35+02:00James AriasHow to use wildcards?Good morning/Afternoon @mobreza
How to filter some fields like inventory Prefix, inventory Suffix ..., with wildcards like%?
If you suddenly have this answer in other issues, please attach.
Thank youGood morning/Afternoon @mobreza
How to filter some fields like inventory Prefix, inventory Suffix ..., with wildcards like%?
If you suddenly have this answer in other issues, please attach.
Thank youMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/74Invitro: Discard2022-05-18T15:15:58+02:00Matija ObrezaInvitro: Discard@1cgiar/ibadan Please have a look at the new "In vitro" section accessible at:
![image](/uploads/cabb94792696273e8419649ebd03954f/image.png)
Please explore the form for Discarding material https://ibadan.ggce.genebanks.org/invitro/disc...@1cgiar/ibadan Please have a look at the new "In vitro" section accessible at:
![image](/uploads/cabb94792696273e8419649ebd03954f/image.png)
Please explore the form for Discarding material https://ibadan.ggce.genebanks.org/invitro/discard:
![image](/uploads/782de4c640ce1c966da755bd4607a4bf/image.png)
- Barcode must be invitro inventory
- Must have quantity > 0Marimagne TchambaMarimagne Tchambahttps://gitlab.croptrust.org/grin-global/support/-/issues/75Taxonomy in GG-CE2021-05-19T09:52:34+02:00Matija ObrezaTaxonomy in GG-CELegacy GG requires that accessions link directly to one of GRIN Taxonomy records in `TaxonomySpecies`. This list is curated by experts by USDA (for USDA) and kindly made available for wider use.
Since many @1cgiar/all collections (e.g. ...Legacy GG requires that accessions link directly to one of GRIN Taxonomy records in `TaxonomySpecies`. This list is curated by experts by USDA (for USDA) and kindly made available for wider use.
Since many @1cgiar/all collections (e.g. @1cgiar/nairobi, @1cgiar/addis and others) use taxon names that are not yet in GRIN Taxonomy, I suggest that we introduce a new approach in **GG-CE** that allows you to specify the taxon as you have it in your database today and link it to GRIN Taxonomy when/if it is available.
## Proposal: Genebank taxonomy
A new table `taxonomy_genebank` is added to GG-CE where you register the taxonomic names you already have in your databases. You manage these records separately from GRIN Taxonomy. The table generally follows MCPD descriptors.
This allows you to limit the list only to the species of interest to your collection.
All `Accession` records link to the **genebank taxonomy** not to the GRIN Taxonomy directly. You are able to add `Accession`s with your own taxonomic data.
But, you are still able to spell-check names against GRIN and link your taxonomy record to the matching record in GRIN `TaxonomySpecies`, if available.
## Extras: Hybrids
Many of you also maintain hybrids and those taxonomies are currently difficult to capture in `TaxonomySpecies`.
The genebank taxonomy table would allow for registering names of unnamed hybrids (*M.* *a* x *b*) and applying them to your accessions.
## Bonus: Simple updating of USDA Taxonomy
Since you are not adding records to `TaxonomySpecies`, updating the GRIN Taxonomy from USDA assures you have a valid recent copy from NPGS.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/76MCPD view/report2022-05-18T15:16:06+02:00Ghost UserMCPD view/reportPassport data (MCPD) is the common information that the users want to see. Although most of those data are in the accession detail section, a view/report would be useful for one or a group of accessions.
![image](/uploads/089d6e569fa3c3...Passport data (MCPD) is the common information that the users want to see. Although most of those data are in the accession detail section, a view/report would be useful for one or a group of accessions.
![image](/uploads/089d6e569fa3c3622c70b3e4d7be3edc/image.png)
Here the "mapping" between **MCPD** and **GRIN-Global**.
The rows highlighted in color `grey` are not considered in GRIN-Global mapping.
| Ref | Acronym (MCPD) | Description (MCPD) | GG-table | GG-field | Comments |
|-------|-------------------|-----------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------|
| `0` | `PUID` | `Persistent unique identifier` | | | |
| 1 | INSTCODE | Institute code | Site | fao_institute_number | |
| 2 | ACCENUMB | Accession number | Accession | Accession_number_part1, Accession_number_part2 ,Accession_number_part3 | |
| 3 | COLLNUMB | Collecting number | Accession_Inv_Name | Plant_name | Add category_code COLLNUMB |
| | | | | | |
| 4 | COLLCODE | Collecting institute code | Accession_source / Accession_source_map | Accession_source_type / cooperator_id | Add code value "COLLCODE" to ACCESSION_SOURCE_TYPE code group |
| | | | | | |
| 4.1 | COLLNAME | Collecting institute name | Cooperator | All fields | |
| 4.1.1 | COLLINSTADDRDRESS | Collecting institute address | Cooperator | | |
| `4.2` | `COLLMISSID` | `Collecting mission identifier` | | | |
| 5 | GENUS | Genus | taxonomy_genus | genus_name | |
| 6 | SPECIES | Species | taxonomy_species | species_name | |
| 7 | SPAUTHOR | Species authority | taxonomy_species | species_authority | |
| 8 | SUBTAXA | Subtaxon | taxonomy_species | subspecies_name | |
| 9 | SUBTAUTHOR | Subtaxon authority | taxonomy_species | subspecies_authority | |
| 10 | CROPNAME | Common crop name | Crop | name | |
| 11 | ACCENAME | Accession name | Accession_Inv_Name | Plant_name | The name with the lowest number in plant_name_rank / collection name? |
| | | | | | |
| 12 | ACQDATE | Acquisition date(YYYYMMDD) | Accession | initial_received_date | |
| 13 | ORIGCTY | Country of origin | Accession_source | geography_id | |
| 14 | COLLSITE | Location of collecting site | Accession_source | collector_verbatim_locality | |
| 15.1 | DECLATITUDE | Latitude of collecting site(Decimal format) | Accession_source | latitude | |
| 15.2 | `LATITUDE` | `Latitude of collecting site(Degrees, Minutes, Second format)` | | | |
| 15.3 | DECLONGITUDE | Longitude of collecting site (Decimal degrees format) | Accession_source | longitude | |
| 15.4 | `LONGITUDE` | `Longitude of collecting site (Degrees, Minutes, Seconds format)` | | | |
| 15.5 | COORDUNCERT | Coordinate uncertainty [m] | Accession_source | uncertainty | |
| 15.6 | COORDDATUM | Coordinate datum | Accession_source | georeference_datum | |
| 15.7 | GEOREFMETH | Georeferencing method | Accession_source | georeference_protocol_code | |
| 16 | ELEVATION | Elevation of collecting site [masl] | Accession_source | elevation_meters | |
| 17 | COLLDATE | Collecting date of sample [YYYYMMDD] | Accession_source | Source_date | |
| 18 | BREDCODE | Breeding institute code | Accession_source / Accession_source_map | Accession_source_type / cooperator_id | Add code value "BREDCODE" to ACCESSION_SOURCE_TYPE code group |
| 18.1 | BREDNAME | Breeding institute name | Cooperator | All fields | |
| 19 | SAMPSTAT | Biological status of accession | Accession | improvement_status_code | Add code values to IMPROVEMENT_LEVEL code group |
| 20 | ANCEST | Ancestral data | Accession_pedigree | description | |
| 21 | COLLSRC | Collecting/acquisition source | Accession_source | acquisition_source_code | Add code values to ACCESSION_SOURCE_HABITAT_TYPE code group |
| 22 | DONORCODE | Donor institute code | Accession_source / Accession_source_map | Accession_source_type / cooperator_id | Add code value "DONORCODE" to ACCESSION_SOURCE_TYPE code group |
| 22.1 | DONORNAME | Donor institute name | Cooperator | All fields | |
| 23 | DONORNUMB | Donor accession number | Accession_Inv_Name | Plant_name | Add category_code DONORNUMB |
| 24 | OTHERNUMB | Other identifiers associated with the accession | Accession_Inv_Name | Plant_name | Add category_code OTHERNUMB |
| 25 | DUPLSITE | Location of safety duplicates | Accession | Backup_location1_site & Backup_location2_site | |
| 25.1 | DUPLINSTNAME | Institute maintaining safety duplicates | Site | fao_institute_number | |
| 26 | STORAGE | Type of germplasm storage | Inventory | preservation_method_id (--> Method's table) ? | |
| 27 | MLSSTAT | MLS status of the accession | Accession_ipr | type_code | |
| 28 | REMARKS | Remarks | Accession | Note | |
| | URL | | | | added in app_setting table(optional) |
| | DOI | DOI | Accession | DOI | |
_Note._
You can find more information on GRIN-Global-Genesys wizard [here](https://gitlab.com/GRIN-Global/Wizards/GRIN-Global-Genesys) including the get_passport_data dataview.
@1cgiarhttps://gitlab.croptrust.org/grin-global/support/-/issues/77GG-CE in your language2022-05-18T15:17:40+02:00Matija ObrezaGG-CE in your languageEvery @1cgiar/all **GG-CE** can be used in one of supported languages:
- **`/es/`** for Spanish: https://texcoco-m.ggce.genebanks.org/es/
- **`/fr/`** for French: https://leuven.ggce.genebanks.org/fr/
- `/xx/` for another language
Some...Every @1cgiar/all **GG-CE** can be used in one of supported languages:
- **`/es/`** for Spanish: https://texcoco-m.ggce.genebanks.org/es/
- **`/fr/`** for French: https://leuven.ggce.genebanks.org/fr/
- `/xx/` for another language
Some translations for ES and FR are already in place, many need more work! We are looking for coordinators of translation teams and people who wish to contribute to GG-CE by translating from English to your language.
Help make GG-CE better by contributing translations at https://www.transifex.com/crop-trust/gg-ce-web/ !
Please let me know if you'd like to see GG-CE in another language or if you'd like to contribute!Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/78Wizards available with links till 20202021-09-07T19:46:15+02:00Edwin RojasWizards available with links till 2020Wizards available with links: source code, installers and videos till 2020.Wizards available with links: source code, installers and videos till 2020.https://gitlab.croptrust.org/grin-global/support/-/issues/79Inventory update error2021-05-11T06:55:46+02:00James AriasInventory update error**Good Morning/Afternoon** @mobreza
I am trying to update an `inventory`, but I am getting an error when I set a `parentInventory`.
I attach the forms of how I am sending the `JSON`
**Way 1**
```
{
"id":283639,
"availabilityStatusCod...**Good Morning/Afternoon** @mobreza
I am trying to update an `inventory`, but I am getting an error when I set a `parentInventory`.
I attach the forms of how I am sending the `JSON`
**Way 1**
```
{
"id":283639,
"availabilityStatusCode":"ACTIVE",
"inventoryNumberPart1":"COL003GRP1IMB19981125",
"formTypeCode":"SD",
"accession":{"id":67053},
"inventoryMaintenancePolicy":{"id":6},
"site":{"id":2},
"parentInventory":623338
}
```
![image](/uploads/af21772c58d68f8081f64086816bc81e/image.png)
**Way 2**
```
{
"id":283639,
"availabilityStatusCode":"ACTIVE",
"inventoryNumberPart1":"COL003GRP1IMB19981125",
"formTypeCode":"SD",
"accession":{"id":67053},
"inventoryMaintenancePolicy":{"id":6},
"site":{"id":2},
"parentInventory":{623338}
}
```
![image](/uploads/284a01ae3a1e4a118eac67091211bbfd/image.png)
- I don't know, if the cause is because the field is not in the `serialization`. as the following picture shows.
![image](/uploads/1d81299b49d34bedfb2ba1288dd1cdfd/image.png)
- If the way I am sending it in the `JSON` is not correct, please tell me which one it would be?
**Post Data:** If I don't send the `parentInventory`, the `inventory` updated successfully.
**Thank you, Regards**Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/80Features/requirements evaluated or requested for the GG-CE Web2021-09-10T08:51:54+02:00Matija ObrezaFeatures/requirements evaluated or requested for the GG-CE WebFeedback from ~Lima on GG-CE Web version **2021.?** collated by @erojas 11 May 2021.
[Report_GGCE_Improvements_20210511.xlsx](/uploads/b21747c82469a8a2f248f21f94d11998/Report_GGCE_Improvements_20210511.xlsx)
# Security
| Feature ...Feedback from ~Lima on GG-CE Web version **2021.?** collated by @erojas 11 May 2021.
[Report_GGCE_Improvements_20210511.xlsx](/uploads/b21747c82469a8a2f248f21f94d11998/Report_GGCE_Improvements_20210511.xlsx)
# Security
| Feature | Supported |
|--------------------------------|-----------|
| Reuse user and password of LAN | No |
| Define user groups by crop format/biologicla status/process/owner to restrict edition or read-only | No |
User accounts should use LDAP authentication of CGIAR. User groups:
1. In Vitro potato (6 staff)
2. In Vitro sweetpotato (4 staff)
3. In Vitro ARTC (2 staff)
4. Post quarantine in Vitro (2 staff)
5. Seed wild potato (5 staff)
6. seed cultivated potato (2 staff)
7. Seed sweetpotato (5 staff)
8. Seed ARTC (3 staff)
9. Herbarium (2 staff)
10. Cryo potato (10 staff)
11. Cryo sweetpotato (10 staff)
12. Safety backup (2 staff)
# Ease of Use
| Feature | Supported |
|-----------------------------------------------------------------------------------|-----------|
| Drag-N-Drop Content | Yes |
| Mass Upload of data or files for accessions | No |
| Mass Upload of data or files for inventories | No |
| Friendly URLs after searching like Genesys-PGR | No |
| Multi language | Yes |
| Performance | Good |
| Export to Excel | No |
| Update inventories when internet is not available (offline mode) | No |
| Integrate camera of Android device with attach option | No |
| Manage inventories by list when searching, updating, printing, scanning | No |
| Add the functionality to search by list when pasting a list from Excel and search | No |
# Other modules
| Feature | Supported |
|-------------------------------------------|-----------|
| Module of reports with filters | No |
| Module of notifications defined by users | No |
| Print barcode labels with Bluetooth or IP | No |
| Process support | No |
| Module of seed viability registration | No |
| Add the functionality to see morphological data, evaluation data and datasets/subsets | No |
| Add advanced search options with more filters and customize the output result: Needed in the daily work for curators and technicians, similar to Search Wizard | No |
| Add advanced search options with more filters to cross filters of passport, evaluation and morphological data, as well as inventories in the different conservation methods | No |
| The titles used to show passport data in columns or boxes in the GG-CE to use the MCPD standard titles | Not support MCPD |
**Process support**: For each inventory to facilitate tracking enable two boxes for process and sub-process (current stage). This tool should allow to edit and add process and sub-process as needed. And to enable to track inventories location and number of vessels in stock per each process and/or subprocess. This will facilitate the workflow system around the inventories. A first approach.
1. Post-quarantine
1. sub-process 1
1. sub-process 2
1. sub-process 3
2. introduction
1. sub-process 1
1. sub-process 2
3. Conservation
1. sub-process 1
1. sub-process 2
4. Phitosanitary
1. sub-process 1
2. sub-process 2
3. sub-process 3Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/81ISO. Service monitoring.2021-09-07T19:48:13+02:00Ghost UserISO. Service monitoring.Analysis of the service provided by the Distribution process.
**Seed request (Distribution)**
- Percentage of successful Seed requests processed by year. (indicator)
- Detail of successful Seed requests processed.
- Percentage of Seed ...Analysis of the service provided by the Distribution process.
**Seed request (Distribution)**
- Percentage of successful Seed requests processed by year. (indicator)
- Detail of successful Seed requests processed.
- Percentage of Seed requests processed successfully in 4 or fewer weeks. (indicator)
- Detail of Seed requests processed successfully in 4 or fewer weeks.
- Percentage of not processed Seed requests. (indicator)
- Detail of not processed Seed requests.https://gitlab.croptrust.org/grin-global/support/-/issues/82GG-CE 2021.6 update2021-05-31T12:04:52+02:00Matija ObrezaGG-CE 2021.6 updateI’m happy to announce the availability of the **v2021.6** release of GG-CE.
`v2021.6` adds passport data **mapping to Multi-crop Passport Descriptors**, paving the way for automated publishing of passport data from **GG-CE to Genesys** ...I’m happy to announce the availability of the **v2021.6** release of GG-CE.
`v2021.6` adds passport data **mapping to Multi-crop Passport Descriptors**, paving the way for automated publishing of passport data from **GG-CE to Genesys** and other sytems. Work started on improved support for **Viability testing** with a new section of GG-CE Web.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/82
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.6
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.6
New features:
* Added language selection to the entry page
* Added a separate section for viability testing
* Browse passport data in MCPD format
* Added API endpoints for viability testing actions
* Added API for managing attachment metadata
* Added mapping of passport data to MCPD
Improvements and bug fixes:
* Fixed autocompleter for selecting inventory maintenance policy
* Added basic overview of inventories to the In vitro section
* Added support for managing details of `AccessionInvAttach` records
* Users can schedule actions for multiple selected inventories
Database model:
* There are no changes to the database model between `v2021.5` and `v2021.6` release
## Language selection
**GG-CE** can be used in any of the supported languages. Some translations for Spanish and French language are already in place, but many need more work! We are looking for coordinators of translation teams and people who wish to contribute to GG-CE by translating from English to your language.
Help make GG-CE better by contributing translations at https://www.transifex.com/crop-trust/gg-ce-web/ !
## Viability testing
A new section of GG-CE Web at */viability* focuses on processes around viability testing. The first version allows users to browse and search the existing viability data.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/035bce4a470dca238fd339fc9b8384cd/image.png)
Look for the "Inventory viability" **card** on the entry page!
*Coming soon:* Reviewing inventories in need of testing, making a seed request, labeling and recording observations during germination tests (including tetrazolium tests) and calculation of the final test results.
## Mapping to MCPD
The data model for accession documentation in GG-CE is very rich and goes well beyond what MCPD has to offer. [GG-CE to MCPD mapping](https://gitlab.croptrust.org/grin-global/support/-/issues/76) documents the current approach.
We still need to resolve the following MCPD fields:
* `STORAGE`: Type of germplasm storage
* `MLSSTATUS`: MLS status of the accession (see [MLS status in GG-CE](https://gitlab.croptrust.org/grin-global/support/-/issues/66))
* `CROPNAME`: Common crop name (?!)
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/eec1b356a05b5fafa2a5f58d2bb3c8f2/image.png)
Look for the "Passport data in MCPD" **card** on the entry page!
/cc @1cgiar/allMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/83Feedback from M'be2021-09-07T19:47:04+02:00Matija ObrezaFeedback from M'be@rtohoun provides the results of the demo session of GG-CE for @1cgiar/mbe:
- All the participants were very happy with the GG-CE especially for its speed, its ease and also for the fact that we scan directly the accessions.
- They all...@rtohoun provides the results of the demo session of GG-CE for @1cgiar/mbe:
- All the participants were very happy with the GG-CE especially for its speed, its ease and also for the fact that we scan directly the accessions.
- They all preferred to use WEB GG-CE unlike the API which is very slow because of the connection speed we have here.
## Requests
1. If It's possible to export all row of filter result to excel that will be good
1. It's possible on GG-CE you can have the field for the references of attachments files
1. Obtain only the table on viability inventory
1. It's possible to developpe interface for viability test result entry? Using API to entry the data is very low because the performance of internet
1. In the field of request of acessions it is difficult to choose accessions by accession. If we can review so that we can make drag and drop
1. It's possible to obtain in the Web GG-CE the wizard option that will be very goodMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/84On viability testing2021-09-01T08:48:07+02:00Matija ObrezaOn viability testingThe common procedure for **Viability testing** in GG-CE is as follows:
1. Someone (or something) flags the inventories that need to be tested for viability and adds them to the *Pending viability test list*
1. Someone decides which of t...The common procedure for **Viability testing** in GG-CE is as follows:
1. Someone (or something) flags the inventories that need to be tested for viability and adds them to the *Pending viability test list*
1. Someone decides which of the inventories on the *Pending list* will go into testing now and requests retrieval of seeds.
1. Retrieved seeds are packed and appropriately labeled.
1. The viability team receives the seeds and executes the testing protocol, eventually producing the latest viability results for the tested inventories.
This text describes the tools in GG-CE in support of the procedure.
## Flagging inventories for viability testing
When the user has decided that an inventory should be tested for viability (in the near future) they schedule an inventory action `Viability test` for the inventory. A *scheduled inventory action* is one that is in the database, but does not yet have a `startDate`.
One can schedule inventory actions from the Inventory list page by first selecting the inventories, then clicking the **Schedule inventory action** button:
![image](/uploads/5f35377a792396712e3ef4cdf635bbde/image.png)
In the dialog you select *Viability test* for action type and confirm. If you now check the *Pending inventory actions* list, you'll notice the freshly added records:
![image](/uploads/ce62f4997508642279f2a8ffb00f9d18/image.png)
Until this inventory action is **started** and becomes **in progress** (because it has a `startedDate`), GG-CE considers the inventory is *Scheduled for viability testing*.
## Deciding what to test (this month)
The *Pending viability test list* will grow way beyond what can be tested in a month or two. It may have thousands of inventories waiting for viability testing.
In the *Viability* section you will find the **Prepare order** function. It lists inventories with pending viability tests:
![image](/uploads/858588a6b5d85f77bf0f16320e5c79dc/image.png)
Select the ones that should go for testing (now) and click "Prepare order":
![image](/uploads/9299c5aea0907e1cab0e6e41b5154d6f/image.png)
In the dialog, select the `InventoryViabilityRule`, `Site` and `Cooperator` that will receive the seeds for testing:
![image](/uploads/acc08132ac13029abef305dc54427fc1/image.png)
After hitting "Create Order", the system will:
1. Create the `OrderRequest` for selected inventories with the quantities defined in the `InventoryViabilityRule` (e.g. 2 x 40 seed = 80 SD)
1. Create `InventoryViabilty` records with `null` value for end viability result
1. Mark the *pending* inventory action `Viability test` as started, removing these inventories from the list *Pending viability test*
## Seed retrieval / Order processing
The seed retrieval follows its own process and eventually the seed packets are delivered to the Viability team to do the testing.
## Begin testing
Viability team receives the seed packets. They scan the inventory barcode which will immediately display the `InventoryViability` record prepared earlier.
![image](/uploads/60474163e9eb0da16a53cb7c791fff65/image.png)
The *Print labels* button prints labels for each replicate.
The replicates are prepared for testing based on `InventoryViabilityRule` information.
grin-global/grin-global-ui#256 has details.
## Make observations
The viability test labels printed for each replicate are unique to the replicate. By scanning the barcode, the previous observations are loaded and can be edited. A new observation can be registered.
A button to *Finish testing* is available.
The details are in grin-global/grin-global-ui#257
## Finish viability testing
This function follows @gcapilit's [description](https://gitlab.croptrust.org/grin-global/grin-global-server/-/issues/78#note_54570) and summarizes the test results across replicates.
![image](/uploads/a267c05a37856413b75f61b62a8d0b5b/image.png)
The results may require **Retesting** and since this is more of an exception than a rule, we will discuss that separately.
/cc @1cgiar/allMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/85CT and Admin Tool errors @ manila.api.genebanks.org2021-05-28T11:42:31+02:00Lilibeth SisonCT and Admin Tool errors @ manila.api.genebanks.org@jalarcon I am testing Genesys Wizard on CT (version 1.21.3.29) using the gg-ce database. Below is the error
![image](/uploads/96a48f1cccc1cad0de08c644a368c7a3/image.png)
@mobreza I went to GG Admin Tool to check on get_passport_data...@jalarcon I am testing Genesys Wizard on CT (version 1.21.3.29) using the gg-ce database. Below is the error
![image](/uploads/96a48f1cccc1cad0de08c644a368c7a3/image.png)
@mobreza I went to GG Admin Tool to check on get_passport_data dataview (related to the error above), but I am unable to login
to manila.api.genebanks.org
![image](/uploads/908f449e3425ea102fbed3bf80ff2273/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/86GG-CE Roadmap2023-03-14T14:29:16+01:00Matija ObrezaGG-CE RoadmapThe *Genebank turtle* (by Janny) can help with planning hte development priorities for GG-CE:
![image](/uploads/21dbeca2dc45b96092133f26f651c69c/image.png)
The aim of GG-CE (Web) is to fully support the operations where technicians spe...The *Genebank turtle* (by Janny) can help with planning hte development priorities for GG-CE:
![image](/uploads/21dbeca2dc45b96092133f26f651c69c/image.png)
The aim of GG-CE (Web) is to fully support the operations where technicians spend 80% of their time.
## GG-CE Roadmap
1. Order processing: seed retrieval, packing, checklist.
1. Acquisition: registration, passport data, labeling.
1. Inventory: updating quantity and location.
## Seed collections
1. Multiplication/Regeneration/Rejuvenation: (Order processing), labeling, planting, harvest, seed processing, initial (Viability testing), packing, (Inventory)
1. Viability testing: label printing, recording observations, summarizing test results.
## Clonal crops
1. Discarding material
1. Subculturinghttps://gitlab.croptrust.org/grin-global/support/-/issues/87Android label printing2021-09-01T14:18:06+02:00Matija ObrezaAndroid label printingPrinting labels from GG-CE Web is supported by:
- Zebra PrintConnect https://play.google.com/store/apps/details?id=com.zebra.printconnect&hl=en
- [PrintConnect User Guide](https://www.zebra.com/content/dam/zebra_new_ia/en-us/solutions-v...Printing labels from GG-CE Web is supported by:
- Zebra PrintConnect https://play.google.com/store/apps/details?id=com.zebra.printconnect&hl=en
- [PrintConnect User Guide](https://www.zebra.com/content/dam/zebra_new_ia/en-us/solutions-verticals/product/Software/Printer%20Software/Link-OS/print-connect/PC-UserGuide-P1082444-001.pdf)
- Link-OS https://techdocs.zebra.com/link-os/2-15/labelIndex.html
Capturing data is enabled with Data Wedge
- https://techdocs.zebra.com/datawedge/8-2/guide/profiles/Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/88Printing reports in GG-CE.2022-05-18T15:18:26+02:00Ghost UserPrinting reports in GG-CE.The print of the Formats/reports is part of some processes Genebanks.
Currently, in the CIMMYT distribution process, three reports are available:
**1. Seed preparation.**
![OrderPreparationList](/uploads/799dba0064c8fbd7684122a410064...The print of the Formats/reports is part of some processes Genebanks.
Currently, in the CIMMYT distribution process, three reports are available:
**1. Seed preparation.**
![OrderPreparationList](/uploads/799dba0064c8fbd7684122a410064528/OrderPreparationList.png)
**2. Seed list for SHL.**
![ListOfSeedForSHL](/uploads/e18cdd103523466b09730b09b5108ca0/ListOfSeedForSHL.png)
**3. Seed Distribution list.**
![DistributionListForCooperator](/uploads/371311ac3b0113be6429ec4fb26a4b6c/DistributionListForCooperator.png)
Other reports/formats that could be an option to print, for example, is the SMTA for Cooperator signature.
@gcapilit @lsison
@1cgiar/all Please, any feedback is welcomeMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/89GG-CE 2021.7 update2021-06-14T18:55:18+02:00Matija ObrezaGG-CE 2021.7 updateI’m happy to announce the availability of the **v2021.7** release of GG-CE.
`v2021.7` implements a number of tools to support **viability testing** and brings the first UI
that includes printing ZPL labels (on Desktop computers). We are...I’m happy to announce the availability of the **v2021.7** release of GG-CE.
`v2021.7` implements a number of tools to support **viability testing** and brings the first UI
that includes printing ZPL labels (on Desktop computers). We are exploring how to enable [label printing on Android](#87) mobiles.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/89
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.7
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.7
New features:
* Added management of `AppSettings` for admins
* Support for **viability testing** process
* Added API endpoints for inventory viability rules, viability testing
* Added API for managing `AppSettings`
Improvements and bug fixes:
* Click-and-drag to select multiple rows in tables
* Display duration (in days) for order requests and actions
* Enabled editing of code values using the *Curator Tool*
* Better support for full-text querying with lenient query parsing
Database model:
* There are no changes to the database model between v2021.7 and v2021.7 release
## Managing `AppSettings`
`AppSetting` enable system-wide configuration and the settings apply to all users. The primary example are label templates -- they are configurable (by Administrators) and are used by everyone.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/917168ed3acef80de97325ea3781eb9a/image.png)
## Viability testing
`v2021.7` demonstrates the support for viability testing process. Look for the **Inventory Viability** card on the Welcome page!
1. Flagging inventories for testing
1. Selecting inventories to test (batch) and creating an `OrderRequest`
1. Starting the viablitity test, with printing labels for replicates
1. Capture multiple counts
*Flagging inventories for testing* is the first step in scheduling viability tests. These are recorded as pending inventory actions and can now be registered manually in
the **Inventory browser**. One can schedule inventory actions from the Inventory list page by first selecting the inventories, then clicking the **Schedule inventory action** button:
![image](https://gitlab.croptrust.org/grin-global/support/uploads/5f35377a792396712e3ef4cdf635bbde/image.png)
In the dialog you select *Viability test* for action type and confirm. In future releases we will discuss how the system can automatically schedule inventories for viability testing.
If you now check the *Pending inventory actions* list, you'll notice the freshly added records:
![image](https://gitlab.croptrust.org/grin-global/support/uploads/ce62f4997508642279f2a8ffb00f9d18/image.png)
Until this inventory action is **started** and becomes **in progress** (because it has a `startedDate`), GG-CE considers the inventory is *Scheduled for viability testing*.
Inventores flagged for testing are listed under **Prepare order**:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/7417f4fa8595876196257d3c33974eee/image.png)
Since the capacity for viability testing is limited, a curator *selects which inventories* will go for testing and sets the appropriate Rule for testing:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/d3fd7e56c62a96a493b835491aef3aa7/image.png)
The system then registers a new Order request and when that order is delivered to the viability testing team, all the information is already in the system.
The technician *begins the testing process* by scans the inventory barcode on the received packet (`inventory.barcode`) and is able to print labels for test replicates as per **inventory viability rule**. They prepare and label each replicate and begin the test.
When it is time to *make an observation,* the technician scans the replicate barcode and inputs the counts:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/ee192045ac95cb6eb29066461d8b7588/image.png)
We need to test and discuss this process with the community and design the calculation of final results of a test.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/c813ae90277aa2d89beca7eed2becbcc/image.png)
@1cgiar/allMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/90Inheriting results of Viability testing2021-09-07T19:24:53+02:00Matija ObrezaInheriting results of Viability testing@1cgiar/all I talked to an expert on seed longevity about the results of viability testing.
## "Sharing" the results of a test
Fiona says:
1. The results are applicable only to the inventory actually tested.
1. **But:** curators shoul...@1cgiar/all I talked to an expert on seed longevity about the results of viability testing.
## "Sharing" the results of a test
Fiona says:
1. The results are applicable only to the inventory actually tested.
1. **But:** curators should be able to access the results of test of sibling inventories and draw their own conclusions.
This means that we should not copy the results of one inventory to others of the same generation.
## Outcome of the test
The `InventoryViability` currently does not capture the **outcome** of the test. The outcome of the test is one of:
- The test was `INCONCLUSIVE` and probably needs to be repeated (as a completely new test). `percentViable` does not have a value (is `null`).
- Data across replicates is within allowed error margins and is `VALID`. The `percentViable` has a value.
- `null` value means test results are not yet ready.
(Here you could also introduce `ESTIMATED` for those that want to copy test results across inventories)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/91Request: Withdrawal, packing and shipping2021-09-07T19:33:38+02:00Matija ObrezaRequest: Withdrawal, packing and shippingThis issue is about technicians fulfilling a valid and complete `OrderRequest`. The general outline is as follows:
1. Retrieve source inventories from storage.
1. Extract the specified amount of material of each source inventory and pac...This issue is about technicians fulfilling a valid and complete `OrderRequest`. The general outline is as follows:
1. Retrieve source inventories from storage.
1. Extract the specified amount of material of each source inventory and package it for distribution.
Because the order request is valid and complete, we assume that:
1. **source inventories** are at their designated locations
1. **source inventories** have sufficient quantity for withdrawal
## Detailed workflow
1. **Alert**: Receive information about the `OrderRequest` to fulfill.
- This may be a PDF document, email or a link to GG-CE Web.
1. **Fetch**: Retrieve **source inventories** listed in `order_request_item` list from the storage (requires info on `location` in storage).
- Source inventories are put on the trolley/tray and brought to processing area.
- A printed document or a special label should be used to mark the group of source inventories for one order, if applicable.
1. **Withdraw**: For each inventory (`order_request_item`) retrieved from storage:
- Scan inventory barcode to confirm that it is part of the order request. The system displays the amount of seed/material to withdraw.
- Extract specified amount of material (e.g. `200 SD`, `50 g` or `1 prepack`) and place it in a new container for delivery
- Confirm that material was extracted. The system prints a new label.
- Apply the label to the extracted package.
1. **Verify**: Verify that all extracted packets match all Inventories in the order by scanning all of them again.
## User interfaces
The following are the new GG-CE Web interfaces that support technicians in fulfillment of all requests.
1. Retrieve from storage
1. Extract and package
1. Confirm
### Retrieval list
This UI provides the technician with sufficient information to retrieve source inventories from storage and bring them to the processing area. It is based on *Seed preparation* report:
![OrderPreparationList](/uploads/799dba0064c8fbd7684122a410064528/OrderPreparationList.png)
It must (at least) include the following information about the **source inventories** to be retrieved:
1. Unique inventory identifiers: `barcode`, `inventoryNumber` -- sufficient information to reliably retrieve the right inventory.
1. `Location` in storage
1. Requested `quantity` from `order_request_item`
1. `note` from `order_request_item`
The following may also be included in the display `accession.accessionNumber`, `site.shortName`, `accession.taxonomySpecies`.
It is probably best to have this printed on paper (-20C!) and add notes by hand.
### UI for **Withdrawal of material**
This UI is for extracting the specified `quantity` from the **source inventory** and packing it for distribution. It kicks in once the *source inventories* have been retrieved and
are in the working area for packaging.
1. Technician enters/scans the **order_request.id** number (from the paper version of the `OrderRequest`). This loads the request details from the server.
- Displays the same data as the "Retrieval list" (above)
1. For each **source inventory** (in `order_request_item`) retrieved from storage:
- Scan inventory barcode to confirm that it is part of the order request and displays:
- Requested `quantity` to withdraw from `order_request_item`
- `note` from `order_request_item`
- Technician extracts the specified amount of material (e.g. `200 SD`, `50 g` or `1 prepack`) and places it in a new container for delivery.
- Confirm the amount of material that was **actually extracted** and click the "Packaged!" button. The system prints a new label for the deliver packet.
- Apply the label to the packet of extracted material.
- Clear the screen for the next scan
When this is completed, all **source inventories** are processed and material extracted and labeled for delivery.
### Confirm ordered items
This screen is for technician to check again if all withdrawn inventories match the inventories in the order request.
1. Technician enters/scans the **order_request.id** number. This loads the request details from the server.
1. Technician scans every packaged (small) inventory label
- If the inventory is not part of the order, alert the technician with **sound and flashing message**
1. The extracted material is delivered.
1. The **source inventories** are returned to their storage locations.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/92Request: Creating or updating a request for material2021-09-01T08:46:13+02:00Matija ObrezaRequest: Creating or updating a request for materialRequests for material come from various sources (`web_order_request`, Genesys, email, phone, in person, or even may be *system generated*). This issue is about creating, reviewing and editing the `OrderRequest` and the list of `OrderRequ...Requests for material come from various sources (`web_order_request`, Genesys, email, phone, in person, or even may be *system generated*). This issue is about creating, reviewing and editing the `OrderRequest` and the list of `OrderRequestItems`.
The general procedure outline is as follows:
1. Optional: Register a new `OrderRequest` in the system
1. Review `OrderRequest`
- Review and update requestor information
- Ensure the request is valid: is for research, has SMTA pre-acceptance (shrink-wrap, click-wrap), etc.
1. Review and manage the list of requested material:
- Set or modify the **source inventory** of each requested item (to be withdrawn and shipped)
- Ensure that each `OrderRequestItem` is available and has sufficient quantity for distribution
- Offer alternative inventories to requestor?
1. Negotiate with the requestor about items not (currently) available by offering alternatives.
- Split order?
- Update **source inventory**
1. Finalize the `OrderRequest`
- Withdrawal, packing and distribution
- Reject the request?
@all It would be really helpful if you contribute to how incoming requests for material are handled, and how GG-CE can help with processing incoming requests.
## User interfaces
The person in charge of distribution needs to be able to:
1. Review any incoming request
1. Not reject items, but offer/negotiate alternative material
1. Agree on the final list of **source inventories** with the requester and submit that for **withdrawal and delivery #91**Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/93GG-CE 2021.8 update2021-06-26T12:03:06+02:00Matija ObrezaGG-CE 2021.8 updateI’m happy to announce the availability of the **v2021.8** release of GG-CE.
`2021.8` adds improved support for **Viability Testing**, including label printing for test replications and calculation of the final test results. **Request ma...I’m happy to announce the availability of the **v2021.8** release of GG-CE.
`2021.8` adds improved support for **Viability Testing**, including label printing for test replications and calculation of the final test results. **Request management** is moved to a new "section" and it provides a **Retrieval list** function with an option to print the items requested for retrieval from storage.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/93
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.8
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.8
Database model:
* The data type of all `description` columns in *_lang* tables are converted from `varchar` to `nvarchar` in 797fa28 to allow for UTF-8 text. This change does not affect operations of GG-CE.
* There are no other changes to the database model between v2021.7 and v2021.8 release
New features:
* Recording viability observations and final test results.
* Printing labels on Android to printers connected via Bluetooth Classic or Bluetooth LE.
* *Retrieval list* guides technicians in preparing inventories for distribution.
* Added configurable **password policy**.
* Mapping to MCPD is highly customizable by using the "MCPD" language.
* Administrators can browse and filter **Audit Log** records generated by GG-CE Server.
Improvements and bug fixes:
* Managing attachment details is enabled for Crops and Crop Traits.
* Request management moved to a new "section" of GG-CE Web.
## Viability testing
This release includes improved support for Viability Testing. We added support for printing labels for each replicate. GG-CE provides a default label template, but it is customizable in **Admin > App Settings** screen. The label uniquely identifies each test replication and allows technician to make multiple observations during the test.
**Step 1:** Begin testing
(No change since `2021.7`) The technician begins the testing process by scans the inventory barcode on the received packet (inventory.barcode) and is able to print labels for test replicates as per inventory viability rule. They prepare and label each replicate and begin the test.
**Steps 2-5:** Record counts
Multiple counts are made during the test. The technician scans the barcode of the replicate and is presented with a screen with previously recorded observations. Tapping "Add observation" opens the screen to add a new "count". The screen is significantly updated since the previous release.
1. "Tested count" may be updated to reflect that less than required number of seed are in this test replication.
1. Current observations are entered into "Normal count" and other count fields (see under "Advanced").
1. All counts are aggregated and used to calculate the **Remaining seed** in the test. When this number is `0`, there are no more seed to evaluate.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/51a1125730b93fe4eb721fb26bd99921/image.png)
When inputting the subsequent counts, the technician inputs the **current counts** for that observation.
The previous count **+** the current count represent the sum total that contributes towards **Remaining seed** to be evaluated next time:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/e275ad770a3e11e1d15668a9a9e37fc8/image.png)
**Step 6:** After the observations are complete and there are no more seed to evaluate, the technician may tap the **Finish test** button:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/f2bc36040c7c31ac3cf65842684ced46/image.png)
**GG-CE Server** will calculate the results of the viability test across replications and present the calculation results to the user for confirmation:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/74efa372f0bdd4163528e06eaa30873f/image.png)
1. The results are not yet saved to the database. The technician may update the fields.
1. The screen shows which data contributes to summarized values.
**Percent viable** represents the test results and is calculated across replicates and across different evaluated categories:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/6e2a8bf0e37bcd2f55e1f15c18ed1643/image.png)
**Summarized results for replications** shows final data for each replication and allows the user to return and update individual observations, and then recalculate test results:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/37f03a03d6b35fb0971fd012078ad716/image.png)
**Last step:** hitting the **Save** button stores the results of the viability test in the database.
## Requests: Retrieval list
The *Retrieval list* provides technicians with a special display of requested source inventories: location, quantity on hand, inventory and accession data.
Step 1: Scan the barcode of the `OrderRequest`:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/f631f72a720efd5f55db74b461d9e94b/image.png)
Step 2: Browse (or Print) the source inventories. By hitting the **X** button, user is returned to the barcode scanning screen:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/4d4023dd4645764cf27f6c9359a64a51/image.png)
We will focus on managing withdrawal and printing package labels for `2021.9`. That release also aims to improve support for managing request data in preparation for withdrawal and distribution.
## Audit logs
**GG-CE Server** records changes to the data. Audit logs include who, when, and what **change** was made to the data or **deleted** from the database.
The new tool enables Administrators to explore audit logs, and identify and react to any unwanted changes in the system:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/0350ad850aeea803f9096d55693badb3/image.png)
/cc @allMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/94Connect the GGCE database from GG-USDA website2021-09-07T19:30:43+02:00Andrew ChanConnect the GGCE database from GG-USDA websiteGG-CE is the user interface for curators and genebank staffs, and we still need a website for seed request and data search.
Therefore, we decide to us the GG-website (2.0.5.2) connect to the GG database as the user website. But, during...GG-CE is the user interface for curators and genebank staffs, and we still need a website for seed request and data search.
Therefore, we decide to us the GG-website (2.0.5.2) connect to the GG database as the user website. But, during we were trying the way, we found that, the schema and content of the database build with the GG-CE API server might be some different between the database build with the GG updater. For example, the column “modified_date” and created_date” are not exist in the table “web_user” in GG-CE version, but is necessary for the GG website. Also some content in the tabale “sys_dataview” and relate content in other data table are not exist.
Because of these different pair with GG-CE database and GG-USDA database, I guess the database build by GG updater is more complete rather than the database build by the GGCE SPI server. Then I try the other way to build the database is to create the database by GG updater in a windows computer, and dump the database then recover it into the Linux server where we need. After that I tried to run the GGCE API server but it cannot normally run.
Is there any idea to solve this or any experience about connect the database with the GG-USDA website?Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/95Use Traefik to run the containers2021-09-07T19:30:43+02:00Andrew ChanUse Traefik to run the containersWe already prepare two URL for the API server and client website. And my docker-compose.yml file as follow.
The two containers can run but cannot connect to the database, because the link is point to localhost (should be 35.221.232.153)....We already prepare two URL for the API server and client website. And my docker-compose.yml file as follow.
The two containers can run but cannot connect to the database, because the link is point to localhost (should be 35.221.232.153). Is there any scrip I should add in the docker file?
```yml
version: '3'
services:
ggce-server:
image: dockerhub.croptrust.org/grin-global/grin-global-server:2021.8
restart: always
networks:
- web
logging:
options:
max-size: "100k"
max-file: "3"
labels:
- "traefik.docker.network=web"
- "traefik.enable=true"
- "traefik.basic.frontend.rule=Host:gsercer.worldveg.org"
- "traefik.basic.port=8088"
- "traefik.basic.protocol=http"
ggce-ui:
image: dockerhub.croptrust.org/grin-global/grin-global-ui/gg-ce-web:2021.8
restart: always
networks:
- web
logging:
options:
max-size: "100k"
max-file: "3"
labels:
- "traefik.docker.network=web"
- "traefik.enable=true"
- "traefik.basic.frontend.rule=Host:gclient.worldveg.org"
- "traefik.basic.port=8088"
- "traefik.basic.protocol=http"
networks:
web:
```
[docker-compose.yml.txt](/uploads/f67555a8145ca0104b758c9db39205f9/docker-compose.yml.txt)Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/96Printers integration using API-REST (JSON) with BarTender Automation2023-03-14T14:30:21+01:00Matija ObrezaPrinters integration using API-REST (JSON) with BarTender AutomationGood Morning @erojas, @jalarcon , @mobreza, @rsulabo
![Logital_Topology_Network_-_Printers_Integration_with_BarTender](/uploads/3f1dd0cdc938ab2f53c559c1c5cb3313/Logital_Topology_Network_-_Printers_Integration_with_BarTender.png)
![Fis...Good Morning @erojas, @jalarcon , @mobreza, @rsulabo
![Logital_Topology_Network_-_Printers_Integration_with_BarTender](/uploads/3f1dd0cdc938ab2f53c559c1c5cb3313/Logital_Topology_Network_-_Printers_Integration_with_BarTender.png)
![Fisical_Topology_Network_-_Printers_Integration_with_BarTender](/uploads/4a02b0ddcf5666354b9fb61fb30584cb/Fisical_Topology_Network_-_Printers_Integration_with_BarTender.png)
Advantage
1. Any device or development that communicates by API/REST will be able to use the tag printing service for inventory identification.
1. The printing service is centralized and any request to modify the label design is made only once on the server, without the need to make the changes on the client devices.
1. Dependingon the process, the client calls the service URL corresponding to the design assigned for that particular process.
For better understanding, we make a document for you. And we are already using this in an inventory application. Soon we will make a demo application (apk) that we will share.
[ManualCreacionRFIDBartenderIntegrationBuilder_V1_IG.pdf](/uploads/fa3ef92578da0b537e8b00845db28ab7/ManualCreacionRFIDBartenderIntegrationBuilder_V1_IG.pdf)
Thank you
RegardsJames AriasJames Ariashttps://gitlab.croptrust.org/grin-global/support/-/issues/97increase length of (group) name in cooperator_group table2021-09-07T19:29:49+02:00Lilibeth Sisonincrease length of (group) name in cooperator_group table@mobreza @jalarcon can we increase the length of cooperator_group.name to 100?
![image](/uploads/b4272bfeffeb6955bbb429a217f9bb15/image.png)
we have section names with length > 60
![image](/uploads/f7ad77e022f53924ce2ad665375244e7/ima...@mobreza @jalarcon can we increase the length of cooperator_group.name to 100?
![image](/uploads/b4272bfeffeb6955bbb429a217f9bb15/image.png)
we have section names with length > 60
![image](/uploads/f7ad77e022f53924ce2ad665375244e7/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/98GG-CE 2021.9 update2021-08-12T11:29:19+02:00Matija ObrezaGG-CE 2021.9 updateI’m happy to announce the availability of the **v2021.9** release of GG-CE.
`2021.9` release improves the support for **Request management** in GG-CE and updates the support for "triggers" and permission checks.
Please check the comple...I’m happy to announce the availability of the **v2021.9** release of GG-CE.
`2021.9` release improves the support for **Request management** in GG-CE and updates the support for "triggers" and permission checks.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/98
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.9
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.9
New features:
* Adding accessions to `OrderRequest`.
* User can select/change the `Inventory` of each order request item that will be used for distribution
Improvements and bug fixes:
* The current menu item is highlighted.
* Table header columns are not truncated.
* The distribution *Checklist* respects inventory barcodes.
* CRUD operations are revised for more consistent updating and better support for permission checks
* Missing accession and inventory numbers are generated and assigned in a background thread
Database changes:
* There are no changes to the database model between v2021.8 and v2021.9 release
## Adding accessions to a request
Previous versions only allows to register `Inventories` with Orders. This release includes the option to **Add accessions** to the order.
**Step 1:** Use the filters to find accessions of interest:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/726d5f9157820b2d8070d3bc4891f770/image.png)
**Step 2:** Select the rows and click the **Add accesssions** button:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/1d84b53103792e4e61970d31669b9d50/image.png)
The selected accessions (their SYSTEM inventories actually) will be added as new order request items to the request:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/09abefa370d1e0e724c75cca5cb4c57e/image.png)
With this, the request for material is properly recorded in the system and is ready for the next step: selecting the actual source inventories.
## Selecting source inventories for withdrawal
Depending on the purpose of the request, you may want to change the inventory from where material will be distributed.
The order items displayed in the screenshot above refer to system inventories (i.e. accessions).
**Step 1:** To select or change the **source inventory** of order items, first select the rows of items that you want to adjust, then hit **Source inventory** button:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/e9656f90269b86c4ffcd181a0f83030b/image.png)
This brings up a dialog displaying the list selected items in the top table, and the list of alternative source inventories in the table below.
By clicking the radio button in the top table, the list of alternative source inventories is updated:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/80e5e9edb4de1087f04449ab17c99eda/image.png)
By clicking the radio button in the source inventories table, that inventory will become the **source inventory** from which material is withdrawn for distribution.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/ac742602b1368b38902c40ac5a2ef024/image.png)
After you're done selecting the sources, confirm your selection by hitting the **Save** button.
We will improve these tools in future releases, for now please test them out and provide your feedback and suggestions for improvements!Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/99Selecting Source Inventory for Withdrawal2021-09-07T19:30:43+02:00Rizalina SulaboSelecting Source Inventory for Withdrawal@mobreza In selecting the source inventories for withdrawal in the new released version, it would be nice to add a restriction in selecting sources that are Available only as a form of validation
![image](/uploads/57fcc3e238406ccac3d1c3...@mobreza In selecting the source inventories for withdrawal in the new released version, it would be nice to add a restriction in selecting sources that are Available only as a form of validation
![image](/uploads/57fcc3e238406ccac3d1c35908ab2dbe/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/100PDCI Index for GRIN-Global2021-09-07T19:24:27+02:00GitLab Support BotPDCI Index for GRIN-GlobalFrom: "Rojas, Edwin (CIP)" <E.ROJAS@CGIAR.ORG>
Subject: PDCI Index for GRIN-Global
Date: 20 July 2021 at 19:06:52 GMT+2
Dear All,
To share some steps to add PDCI Index to GG.
Step 1: Create a Crop Trait for PDCI for each crop (Curator...From: "Rojas, Edwin (CIP)" <E.ROJAS@CGIAR.ORG>
Subject: PDCI Index for GRIN-Global
Date: 20 July 2021 at 19:06:52 GMT+2
Dear All,
To share some steps to add PDCI Index to GG.
Step 1: Create a Crop Trait for PDCI for each crop (Curator Tool and Wizard Crop Trait)
Step 2: Create a SQL function to calculate PDCI (TSQL_PDCI.txt)
Step 3: Update PDCI Crop Trait with a SQL script (TSQL_Merge.txt)
Step 4: Create a SQL view by accession with the passport and PDCI column
Step 5: Add PDCI Crop Trait to your reports like PowerBI
Please Matija try to consider add support to PDCI by accession in GG-CE to facilitate improving data curation.
Many thanks,
Edwin
[TSQL_Merge.txt](/uploads/e2b0ee98233406269e504cdef7322558/TSQL_Merge.txt)
[TSQL_PDCI.txt](/uploads/bb9cda6fe1a76a117aec1b00853dbe03/TSQL_PDCI.txt)https://gitlab.croptrust.org/grin-global/support/-/issues/102GG-CE 2021.10 update2021-08-29T08:27:03+02:00Matija ObrezaGG-CE 2021.10 updateI’m happy to announce the availability of the **v2021.10** release of GG-CE.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/102
* Web https://gitlab.croptrust.org/...I’m happy to announce the availability of the **v2021.10** release of GG-CE.
Please check the complete list of changes at:
* Announcement https://gitlab.croptrust.org/grin-global/support/-/issues/102
* Web https://gitlab.croptrust.org/grin-global/grin-global-ui/-/releases/v2021.10
* API https://gitlab.croptrust.org/grin-global/grin-global-server/-/releases/v2021.10
`2021.10` features **integration with Genesys** to fetch requests for material, fully **translated to French and Arabic**, better organized navigation and many other improvements based on your feedback.
GG-CE is now aligned with the original GRIN-Global implementation to **avoid concurrent updates** to records by testing the `modified_date`. This prevents making changes to the database if a record had already been modified by another user.
New features:
* The main menu is organized into sections: Passport data, Inventory, Distribution, Seed viability, Taxonomy.
* Added integration with Genesys to list requests for material.
* Preferred names of `Accession` and `Inventories` are displayed.
* The number of items in `OrderRequests` is automatically calculated.
* GG-CE is translated to `fr` and `ar` (thanks Yassine, Romeo and Kpeki)
* Adding and editing Order request actions
Improvements and bug fixes:
* Improved display of tabular data, including a button to *select all* rows.
* Actions on selected table rows are moved to the *floating action button*.
* Removed *Site locations* from Admin tools.
* Enabled filtering of *Order requests* by duration and number of order items.
* Error handling of the SOAP API (used by the *Curator Tool*) is improved and aligned with the .Net GG implementation.
* Concurrent changes to the data are prevented by testing against `modified_date` as in the .Net implementation.
* Software dependencies are updated to their latest releases.
Database changes:
* Column `mls_status` added to table `accession`.
* The GG-CE specific `site_locations` table is removed.
* There are no other changes to the database model between v2021.9 and v2021.10 release
## GG-CE in French and Arabic
GG-CE needs to be available to genebank staff in their language. This release includes French and Arabic!
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/0a394f947adbfba07b9ee8efff676726/image.png)
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/8784e18adcf696f6f3bffdf424167e07/image.png)
Help us improve translations and add new languages at https://www.transifex.com/crop-trust/gg-ce-web/
## Updated table display
We finally added a button to **Select all** rows in a table! The *Table settings* button can now be found on the opposite side of the table header row.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/8555e6a03eb9c94af028dde52cfb846e/image.png)
After selecting one or more rows in a table, the *floating action button* changes from the usual `+` (to add a record) to a menu of actions to perform on the selected rows.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/eb04bb3b31f0c08b7e10a8d5c565b313/image.png)
## Genesys requests for material
Most genebanks allow Genesys users to file request for material. The requests are relayed to the genebank only after the request is validated (email validation, Easy-SMTA PID validation).
This release enables GG-CE users to browse the requests in Genesys using the *Distribution* section of GG-CE under **Genesys requests**.
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/51127cc73b6c08d3ecf775b0e003bb07/image.png)
The requests are fetched using Genesys API and GG-CE needs to be configured with Genesys API keys. The Genesys requests are displayed in a table and by clicking the email address of the requestor, the complete request is displayed, including requestor's Easy-SMTA PID data and the list of requested accessions.
In future releases we can add support for matching the requestor with an existing `Cooperator` record, or register a new cooperator if necessary. This is a required step before the Genesys request can be converted to a `OrderRequest` in GG-CE.
## Requests for material
Following your feedback we updated the *Distribution* section, especially the **Request** module. It improves the adding of accessions or inventories to a request, changing the source inventory to be distributed, recording order request and request item actions, and editing of individual request items.Matija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/103MCPD filters2021-09-07T19:30:43+02:00Lilibeth SisonMCPD filters@mobreza Please refer to attached
![image](/uploads/043343e747e28c6855f390bf81e7a462/image.png)
![image](/uploads/42ae457ba88973eaefb211c2f7aaf3d4/image.png)@mobreza Please refer to attached
![image](/uploads/043343e747e28c6855f390bf81e7a462/image.png)
![image](/uploads/42ae457ba88973eaefb211c2f7aaf3d4/image.png)https://gitlab.croptrust.org/grin-global/support/-/issues/105Viability test environments2023-06-12T14:13:54+02:00Matija ObrezaViability test environments@1cgiar/palmira I would like to merge the new UI for Viability Environments. This is the current version of the form:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/91e669975693d341f060459dd42b6bda/image.png)
...@1cgiar/palmira I would like to merge the new UI for Viability Environments. This is the current version of the form:
![image](https://gitlab.croptrust.org/grin-global/grin-global-ui/uploads/91e669975693d341f060459dd42b6bda/image.png)
@jarias Can you and your colleagues please provide better texts for field labels and describe what each of these field mean so we can include them in the form?Juan Carlos GuerreroJuan Carlos Guerrerohttps://gitlab.croptrust.org/grin-global/support/-/issues/106How to query accession_inv_group with inventory_id, from services?2021-09-07T19:29:49+02:00James AriasHow to query accession_inv_group with inventory_id, from services?For example :/api/v1/i/group/{inventory_id}/membersFor example :/api/v1/i/group/{inventory_id}/membersMatija ObrezaMatija Obrezahttps://gitlab.croptrust.org/grin-global/support/-/issues/107REPORT JSON ERROR ORDER_REQUEST_ITEMS, INVENTORY2021-09-07T19:29:49+02:00James AriasREPORT JSON ERROR ORDER_REQUEST_ITEMS, INVENTORYGood night Matija, I hope you are well
It was to report two errors in the **JSON** the first, it corresponds when I update the `inventory`, it brings the `"inventoryMaintenancePolicy": null`
**Service: PUT** `/api/v1/i`
![image](/upl...Good night Matija, I hope you are well
It was to report two errors in the **JSON** the first, it corresponds when I update the `inventory`, it brings the `"inventoryMaintenancePolicy": null`
**Service: PUT** `/api/v1/i`
![image](/uploads/845e68f1e7f228b9843d188db6b18857/image.png)
And the second, is when when I consult the `items` of an `order`, the `inventory` does not bring `"inventoryMaintenancePolicy"` in the **JSON**
**Service: POST** `/api/v1/order/items/{id}`
Thank you very much for your help
Greetings.Matija ObrezaMatija Obreza