...
Jira Fields | NetX Fields | |
|---|---|---|
| 1 | Object ID | Ryerson call number |
| 2 | Object ID | CITI relationships |
| 3 | Photographer assigned | Creator |
| 4 | Production staff assigned | Contributor |
| 5 | Description of views or details | Image view |
| 6 | Treatment status of conservation | Treatment status |
| 7 | Image capture light type | Image capture light type |
| 8 | Ticket number(Not in the Jira Test Instance) | Jira order number |
| 9 | Filename assigned by Jira(Not in the Jira Test Instance) | Preferred title |
| 10 | Filename assigned by Jira(Not in the Jira Test Instance) | Imaging UID |
Approaches for collecting data from CITI app
Using JSD forms
Steps | User clicks on the link in the CITI app to raise the request |
Pros | JSD will handle the creation of tickets through its internal mechanism and will take care of attachments if any automatically as a part of same form submission |
Cons | Pre-filling of fields is not supported. User will have to fill all the necessary details manually |
Using JSD create request api
Steps | User clicks on the link in the CITI app to raise the request |
Props | JSD will handle the creation of tickets through its internal mechanism and the caller app(CITI) will have full control over the entire process of redirection of the user after request is created in JSD |
Cons | -- |
Doubts and Clarifications
Questions | Details | Clarification | Status |
|---|---|---|---|
What kind of mechanism do we want to use for making the request from CITI to JIRA? | Do we want to use JSD customer portal forms or do we want to use JSD create customer ticket api? | Unresolved | |
On what event do we have to send data from JSD to CITI app? | After creation of a request? | Unresolved | |
What are the different types of scenarios we will encounter while making a request from CITI app to JSD | parent/child relationship in orders | Unresolved | |
Whats a briefcase in CITI app? | In one of the mails it is mentioned that a briefcase in CITI app can be used to make an imaging order. Are there any other such features that we should know about? | Unresolved | |
Are the data points sent from CITI to JSD remain the same for different request types? | Object ID, Object title, Artist, Department, Object Type, Thumbnail path, Place ID/Place shortcut codes, Location/Place Name, Exhibition ID, Exhibition Title, Exhibition Opening Date, Exhibition Opening Date, Exhibition Closing Date, Exhibition Curator | They remain the same (only the actual values will differ). Also for one request type some proportion of these data points may be sent over to JSD and for other request type the remaining may be sent over for ex. for object photography the CITI app may send Object ID ,Object title, Artist, Department and Object Type, Thumbnail path but for conservation photography the CITI app may send Place ID/Place shortcut codes and Location/Place Name only | Resolved |
Transitions of requests through different workflows and process to follow for each workflow | Unresolved | ||
Communication NETX api | Unresolved |