...
From CITI(Pre-population from CITI is required through GET request URL)
Object Photography
Exhibition Photography
Gallery Photography
Labwork(For data in CITI)
From JSD(Pre-population from CITI is not required)
Archive Photography
Non-Object Photography
Labwork(For data not in CITI)
| Info |
|---|
We are not going to allow users to input the id of the object and pull the information from CITI using the captions api rather CITI is going to make the GET call using the browser windows(tabs) and will pass the required parameters in URL itself. |
Ways in which request can be made from CITI
...
Case | Action | Details | URL to be called from CITI | ||||
Single order for object asset labwork, Exhibition asset labwork or gallery rotation asset labwork | User requests using the CITI app for data present in CITI app | User will perform an action in CITI app which will open a browser and a GET request will be made to JSD customer portal | {base_url}?type=case4&id=54324,54645,6543743,343254&title=Labwork%20title | ||||
Multiple orders for object asset labwork, Exhibition asset labwork or gallery rotation asset labwork | User requests using the CITI app for data present in CITI app | User will perform an action in CITI app which will open a browser and a GET request will be made to JSD customer portal. All tickets should be related after submission
| Tab 1 - {base_url}?type=case4&id=54324&title=Labwork%20title Tab 2 - {base_url}?type=case4&id=54327&title=Labwork%20title1
|
| Info |
|---|
For Archive photography, Non-Object photography and Labwork(For data not in CITI) users will directly visit JSD customer portal form and will fill in the details manually. For these there won’t be any data in CITI so there is not no need for pre-population of fields. |
Types of Requests | Object | Exhibition | Gallery | Non-Object | Archive | Labwork(For Data in CITI) | Labwork(For Data not in CITI) |
Parameters to be sent from CITI | Object Id | Exhibition Id | Exhibition Id | NA(These requests will be initiated directly from JSD) | NA(These requests will be initiated directly from JSD) | title | NA |
...
User will create a ticket in JSD using one of the request types
JSD will generate a file name using the following process
JSD will consider the ticket number of the current ticket for ex. JSD-1
JSD will also generate a string which will be equivalent to the Linux timestamp for ex. 1604906024
JSD will combine the ticket number JSD-1 with the linux Linux timestamp → JSD-11604906024 or JSD11604906024 or 101941604906024(using positions of letters in English Alphabet system)
If there are more than one unique file name to be generated under each ticket than we can simply add _1, _2 after the filename generated in the above step
This process will help us track back the files by their names to the tickets in JSD
JSD will push this information to the field like “File Information“ or any other custom field/fields
...