Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • GGCE Web GGCE Web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GGCEGGCE
  • GGCE WebGGCE Web
  • Issues
  • #319
Closed
Open
Issue created Aug 27, 2021 by Matija Obreza@mobrezaOwner

Genesys request to Order Request

@jalarcon said in #316 (closed)

the Genesys Requests works well, so the next step would be to create a New Order with the data of Genesys request.

Below, you can see the "mapping" between Genesys and GG requests, and the cooperator data.

To identify the "origin" of the request, the value of the order_request.order_obtained_via field would be 'Genesys' in these cases.

I have a doubt about Order_type_code because I'm not sure if the value must come from Is internal request? or from Type.

Request from Genesys Data GRIN-Global
Requestor email j.alarcon@cgiar.org
Created date 5 hours ago order_request.ordered_date
Modified date 5 hours ago
Is received by genebank? Request confirmed
Purpose type Research order_request.intented_use_code
Is internal request? Yes order_request.Order_type_code(?)
SMTA pre-accepted Yes
Last reminder date 5 hours ago
Institute code MEX002
Institute email j.alarcon@cgiar.org
Created by jalarcon9198@gmail.com
Modified by jalarcon9198@gmail.com
Source request 7be81760-7912-4c09-bb8e-6bb11b9d8222
Easy-SMTA PID data Data GRIN-Global
Type in order_request.Order_type_code(?)
Name Juan-Carlos Cooperator.first_name
Surname Alarcon Cooperator.last_name
Email j.alarcon@cgiar.org Cooperator.email
Address Km. 45 Carr. Mex-Ver Cooperator.address_line1,2,3
Country MEX Cooperator.geography_id
Country name Mexico
Organization name CIMMYT Cooperator.Organization

To create a New request from Genesys Request, the suggestion is to add a button to go to the New Request form, carrying with the Id or data of the Genesys Request.

image

With the Id or data of the Genesys request, some fields can be filled as Intended use and Order type, and the Cooperator must be verified previous any action through its email as the first key, if not match with some Cooperator, the second search must be by the last name. Of course, if the search gets more than one record, the list box must be shown to the user in order to decide if the cooperator must be added.

image

Once the cooperator was identified or added, the user must save the request, and the items will be added to the Request, from the Genesys Request.

image

@mobreza updates

To create a New request from Genesys Request, the suggestion is to add a button to go to the New Request form, carrying with the Id or data of the Genesys Request.

You already identified that we need to find a matching Cooperator based on PID data, or create a new one.

There's also a need to specify the request type:

I have a doubt about Order_type_code because I'm not sure if the value must come from Is internal request? or from Type.

After clicking New Request button, I think the best UI to help the user make the right decisions about order type and cooperator is to use 2 columnns and display the Genesys request data on the left and OrderRequest fields on the right:

Genesys Order request
Created date Ordered date
...
Purpose type Dropdown for Order type
Notes Textarea for Intended use
...
Requester PID info Search for Cooperator or "Add new"

When clicking the button we can test if an existing OrderRequest for order_obtained_via == Genesys and a matching Genesys request id. If we find one, then we just redirect the user.

Edited Aug 27, 2021 by Matija Obreza
Assignee
Assign to
Time tracking