Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-22331

Changes to Portal application logic for finding related assets


    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: SUIT
    • Labels:
    • Templates:
    • Epic Link:
    • Team:
      Science User Interface


      The following changes are needed in the lsst/suit code, probably all in SUIT.js:

      1. Obtain the appIcon property in a way which does not leave the loading of the icon relative to the page URL (which in the JL extension is generally something like https://lsst-lsp-int.ncsa.illinois.edu/nb/user/gpdf).
      2. Add to the findCorrectLSSTTapService function logic this reasoning: first look for "/portal", then, if that is not found, look for "/nb" (and then regardless of which one was found, use the URL up to that point as the base onto which to append the TAP_PATH.
      3. Display the base URL from which that reasoning was performed, i.e., the value of window.location.href, in the error message dialog. Text like "Could not infer the location of the TAP service for this LSP instance from the page URL (window.location.href)" would be reasonable.
      4. Check over the SUIT code for anything else that looks like it might break if loaded in the nested context of the JL Firefly extension. (I wonder about some of the import statements at the beginning of the file.)

      Note that the issues addressed here affected the behavior of the Firefly JupyterLab extension, which is based on the slate endpoint, even though the TAP search screen is not even referenced at that endpoint.


          Issue Links



              • Assignee:
                roby Trey Roby
                gpdf Gregory Dubois-Felsmann
                Gregory Dubois-Felsmann
                Gregory Dubois-Felsmann
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:

                  Summary Panel