Versions Compared

Version Old Version 6 New Version 7
Changes made by

Gaurav (Unlicensed)

Sharmendra Vishwakarma

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • CITI (Collections Management System)

  • JIra Jira Service Desk (JSD)

  • NETX (Digital Asset Management SytemSystem)

Types of request(6 Types)

  • Object Type Photography(same workflow as Conservation Photography)

  • Gallery Rotation Photography request

  • Exhibition Photography request

  • Labwork Request

  • Archive Request

  • Non-Object Photography

...

  • 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 Customer form (Pre-population from CITI is not required)

    • Archive Photography

    • Non-Object Photography

    • Labwork(For data not in CITI)

Info

We Note: Users are not going allowed 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 passed in the required parameters in using URL itself.

Ways in which request can be made from CITI

...

Type

Action

Details

URL to be called from CITI

Parent and children having same values for fields

User requests using the 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=case1&ids=43243,434213,432143,45325432&title=my%20object&artist=Bon%20Jovi&department=Imaging&objectType=2D&thumbnailPath=https%3A%2F%2Fblog.snappa.com%2Fwp-content%2Fuploads%2F2018%2F01%2Fyoutube-thumbnail-size.png&domensions=test&currentLocation=TX

Parent and children having different values for form fields

User requests using the CITI app

Multiple tabs will be opened(limited to 10 per order) one for each object

Tab1 - {base_url}?type=case2&parentId=43243&childId=65443&title=my%20object&artist=Bon%20Jovi&department=Imaging&objectType=2D&thumbnailPath=https%3A%2F%2Fblog.snappa.com%2Fwp-content%2Fuploads%2F2018%2F01%2Fyoutube-thumbnail-size.png&dimensions=test&currentLocation=TX

Tab2 - {base_url}?type=case2&parentId=43243&childId=26553&title=your%20object&artist=Picaso&department=Imaging&objectType=2D&thumbnailPath=https%3A%2F%2Fblog.snappa.com%2Fwp-content%2Fuploads%2F2018%2F01%2Fyoutube-thumbnail-size.png&dimensions=test&currentLocation=TX

Info

Note : Parent child relationship and multi-object scenarios are only valid for Object type photography

...

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

Warning

How are we going to connect these requests?

Tab 1 - {base_url}?type=case5&requestId=case4123&id=54324&title=Labwork%20title

Tab 2 - {base_url}?type=case5&requestId=case4123&id=54327&title=Labwork%20title1

Warning

Can we expect any other parameter in URL?

Info

Note: 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 no need for pre-population of fields.

...