Versions Compared

Version Old Version 13 New Version 14
Changes made by

Gaurav (Unlicensed)

Gaurav (Unlicensed)

Saved on

Key

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

...

  • Object Type Photography(same workflow as Conservation Photography)

  • Gallery Rotation Photography request

  • Exhibition Photography request

  • Labwork RequestArchive

  • RequestCollections Archive Request 

  • Non Collections Archive Request 

  • Non-Object Photography

Ways to initiate a request for a asset through CITI for each request type

  • From CITI(Pre-population from CITI is required through GET request URL)

    • Object Photography

    • Exhibition Photography

    • Gallery Photography

    • Labwork(For data in CITI)

    • Collections Archive Photography Request

  • From JSD Customer form (Pre-population from CITI is not required)

    • Non Collections Archive Photography Request 

    • Non-Object Photography

    • Labwork(For data not in CITI)

Info

Note: CITI will only be passing us the object ids in the URL. Rest of the information about the object will have to pulled from CITI’s captions api itself

...

Case Name(passed as parameter through url by CITI)

Case Details

case1parentChildType1

Parent and children having same values for fields except object ids (For Object Photography only)

case2parentChildType2

Parent and children having different values for form fields (For Object Photography only)

case3mutiObjectType1

Multi object scenario with all objects having same field values (For Object Photography and Labwork only)

case4mutiObjectType2

Multi object scenario with all objects having different field values (For Object Photography and Labwork only)

case5galleryRotation

Gallery Rotation Photography (For Gallery Rotation Photography only)

case6exhibition

Exhibition Photography (For Exhibition Photography only)

collectionsArchive

Collections Archive Photography (For Collections Archive Photography only)

Ways in which request can be made from CITI -

Info

The creation of sub-tasks depends on values of three fields. They are as follows
Description of View Or Details (Checklist control)
360 spin requested? (Radio control)
Image Capture light type (Checklist control)

Object Photography with multi object relationship

Type

Action

Details

URL to be called from CITI

Process of creation of tickets in JIRA

Multi object scenario with all objects having same field values

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
(There will be only one tab)

{base_url}?typerequestType=case3mutiObjectType1&ids=43243,434213,432143,45325432

Create one ticket for the request on submission
Create N sub-tasks each for the combination objectid, light type, 360 spin and for each object in the request create a sub-task for the main ticket and copy over all the details from main ticket.Main view type requested
Copy the information from parent ticket to each sub task
Filenames are generated for each sub-tasks but not for the parent ticket
Parent ticket should be closed when all the sub -task tickets tasks are closed
Filenames are generated for each sub-tasks
but not for the parent main ticket

Multi object scenario with all objects having different field values

User requests using the CITI app

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

Tab1 - {base_url}?typerequestType=case4mutiObjectType2&requestId=123&id=43243

Tab2 - {base_url}?type=case5&requestId=123requestType=mutiObjectType2&id=53743

Info

requestId - we need an identifier to link all these requests in JSD. This identifier should be common for all the requests across all the tabs.

One main ticket will be created and all the tickets will be sub-tasks for the main ticketCreate one ticket for each request submission(Each Tab)
Create N sub-tasks(for each ticket) each for the combination objectid, 360 spin, light type and view type requested
Main ticket should be closed when all sub-task tickets are closed
Filenames are generated for each sub-tasks
but not for the main ticket

...

Type

Action

Details

URL to be called from CITI

Process of creation of tickets in JIRA

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}?typerequestType=case1parentChildType1&ids=43243,434213,432143,45325432

Create one main ticket for the request. For parent and each child object in the request create a sub-task under the main ticket.On submission creates a single ticket for all order information in it
For each object requested create a sub-task for the combination of ObjectId, 360 spin, view details and light type
Summary of the child sub-task should contain the summary of the parent + objectid + (the light type or view details or 360 spin)
Main ticket should be closed when all sub-task tickets are closed
Filenames are generated for each sub-tasks
but not for the main ticket

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}?typerequestType=case2parentChildType2&parentId=43243&childId=65443

Tab2 - {base_url}?typerequestType=case2parentChildType2&parentId=43243&childId=26553

Create one main ticket for the request. For parent and each child object in the request create a sub-task under the main ticket.request submission(Each Tab)
Create N sub-tasks(for each ticket) each for the combination objectid, 360 spin, light type and view type requested
Main ticket should be closed when all sub-task tickets are closed
Filenames are generated for each sub-tasks
but not for the main ticket

...

Action

Details

URL to be called from CITI

Process of creation of tickets in JIRA

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}?typerequestType=case5galleryRotation&id=54324

On submission create a single ticket with all order information in it
Create one filename for this ticket
No sub-tasks are required

Exhibition Photography

Action

Details

URL to be called from CITI

Process of creation of tickets in JIRA

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=case6&id=54324requestType=exhibition&id=54324

On submission create a single ticket with all order information in it
Create one filename for this ticket
No sub-tasks are required

Collections Archive Photography(For Data in CITI)

Action

Details

URL to be called from CITI

Process of creation of tickets in JIRA

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}?requestType=collectionsArchive&id=54324

On submission create a single ticket with all order information in it
Create one filename for this ticket
No sub-tasks are required

Labwork(For Data in CITI)

requestId - we need an identifier to link all these requests in JSD. This identifier should be common for all the requests across all the tabs.

Create one ticket for each request submission(Each Tab)
Create N sub-tasks(for each ticket) each for the combination objectid, 360 spin, light type and view type requested
Main ticket should be closed when all sub-task tickets are closed
Filenames are generated for each sub-tasks but not for the main ticket

Case

Action

Details

URL to be called from CITI

Process of creation of tickets in JIRA

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}?typerequestType=case3mutiObjectType1&idids=54324,54645,6543743,343254

Create one ticket for the request on submission
Create N sub-tasks each for the combination objectid, light type, 360 spin and view type requested
Copy the information from parent ticket to each sub task
Filenames are generated for each sub-tasks but not for the parent ticket
Parent ticket should be closed when all the sub tasks are closed
Filenames are generated for each sub-tasks but not for the main ticket

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&requestId=123requestType=mutiObjectType2&id=54324

Tab 2 - {base_url}?type=case4&requestId=123requestType=mutiObjectType2&id=54327

Info
Info

Note: For Non-Collections 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.

Info

For all labwork Labwork orders we will pull in the following fields from NETX on initiation of request after creation of ticket in JSD - File Size, dimensions, Resolution, Color Profile, Digital Asset, Creation Date, Original Source, Make, Model, Modified date, MIME type, Focal Length, Aperture and Document Type

...

Types of Requests

Object

Exhibition

Gallery

Non-Object

Archive

Labwork(For Data in CITI)

Labwork(For Data not in CITI)

Parameters to be sent pulled from CITI

Object Id
Title
Artist
Department
Object Type
Thumbnail Path
Parent Object Id
Dimensions
Current Location

Exhibition Id
Title
Opening Date
Closing Date
Curator
Place Id?Short Code in CITI
Place Name/Location

Exhibition Id
Title
Opening Date
Closing Date
Curator
Place Id?Short Code in CITI
Place Name/Location

NA(These requests will be initiated directly from JSD)

NA(These requests will be initiated directly from JSD)

assetId

NA(These requests will be initiated directly from JSD)

...

  • User will create a ticket in JSD using one of the request typesJSD will generate a file name using the following process

  • filenames will be created

    • For Object type photography and Labwork Phtography

      • JSD will

      consider the

      • create N number

      part of the current Jira ticket for ex. 1234 in IMAGEREQ-1234

    • JSD will prepend 'J' to the start of the number part. for ex J1234

    • Now for each option selected in the below fields, JSD is going to generate a unique filename by generating sequential number prepended by '_'JSD will push all the generated filenames in the “File Information“ Jira Field in the CSV format

      • of sub tasks for each combination of following fields

        • Object Id

        • Description of views or details (Checklist. add a view for each option checked)

        • 360 spin needed? (Radio button. If yes, add a view)

        • Image capture light type (Checklist. add a view for each option checked)

    • For ex. Let us assume that there are three options checked in ‘Description of views or details', yes for ‘360 spin needed?’ and two options checked for 'Image capture light type’ then there will be six filenames generated as follows J1234_1, J1234_2, J1234_3, J1234_4, J1234_5, J1234_6

      • JSD will generate a unique filename for each of these sub-tasks by taking into account the sub-task ticket number and prepending ‘J' to it for ex. if sub-task ticket number is IMAGEREQ-22 then the generated filename will be 'J22’

      • JSD will push this filename information in “File Information“ field for the corresponding sub-task

    • For Exhibition, Gallery Rotation and Collections Archive Photography request

      • JSD will generate a single file name for the ticket using the ticket number and character 'J', ex. if the ticket number is IMAGEREQ-78 then the generated filename will be 'J78’

      • JSD will push this filename information in “File Information“ field for the ticket

Process for ingesting data in NETX

...