informatics-isi-edu / openseadragon-viewer

2D viewer with openseadragon
Apache License 2.0
5 stars 2 forks source link

Implement Multi-Z communication with chaise #61

Closed RFSH closed 3 years ago

RFSH commented 3 years ago

This is part of #57 epic. I wanted to have a pointer so I can document what we decided during our meetings so it might be a little hard to read and follow.

The following are the summary of interactions and what needs to be done for each one:

On load (chaise):

On load (OSD viewer):

On change page in carrousel:

On click on a thumbnail:

RFSH commented 3 years ago

@rastogi-bhavya and I had a call where I explained the new model and how he can modify the records. The recording can be found here. In the following I will just summarize the main points and URLs that we discussed during the meeting:

  1. Make sure the value of uri column in the Image table is saved somewhere.

  2. Send a PUT request to remove the uri value:

    PUT https://dev.rebuildingakidney.org/ermrest/catalog/2/attributegroup/Gene_Expression:Image/RID;uri
    Content-Type: application/json
    
    [
      {
         "RID": "16-2E4P",
         "uri": null
      }
    ]
  3. Find the existing Processed_Image records and make sure existing Z_Index values are not-null

    GET https://dev.rebuildingakidney.org/ermrest/catalog/2/entity/Gene_Expression:Processed_Image/Reference_Image=16-2E4P

    If you need change the Z_Index you would sent a PUT request with the proper value

     PUT https://dev.rebuildingakidney.org/ermrest/catalog/2/attributegroup/Gene_Expression:Processed_Image/RID;Z_Index
     Content-Type: application/json
    
     [
       {
          "RID": "<the rid of processed_image record>",
          "Z_Index": 0
       }
     ]
  4. Send a POST request to add the new entries. Make sure Reference_Image, Channel_Number, and Z_Index values are correct. Also copy the File_URL, File_Bytes, and File_MD5 of one of the existing records. Make sure you've noted the RID of records that you created. So later we won't be confused by this fake data. These are the RID of records that I created during the call for this table: 18-MKVY, 18-MKW0

    POST https://dev.rebuildingakidney.org/ermrest/catalog/2/entity/Gene_Expression:Processed_Image
    [
        {
            "Reference_Image": "16-2E4P",
            "Channel_Number": 0,
            "Z_Index": 1,
            "File_URL": "/hatrac/resources/gene_expression/pyramidal_tiff/2018/3b10e1732b0e5013bf2ec228803fcce2:YVG4QOQ7PR2GRUSJYAIKJ5G4FI",
             "File_Bytes": 225153692,
             "File_MD5": "3b10e1732b0e5013bf2ec228803fcce2"
        },
        {
            "Reference_Image": "16-2E4P",
            "Channel_Number": 0,
            "Z_Index": 2,
            "File_URL": "/hatrac/resources/gene_expression/pyramidal_tiff/2018/3b10e1732b0e5013bf2ec228803fcce2:YVG4QOQ7PR2GRUSJYAIKJ5G4FI",
            "File_Bytes": 225153692,
            "File_MD5": "3b10e1732b0e5013bf2ec228803fcce2"
        }
    ]