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

ObsCore extractor config fixes for DP0.2

    XMLWordPrintable

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: dax_obscore
    • Labels:
      None
    • Sprint:
      DB_F22_6, DB_S23_6
    • Team:
      Data Access and Database
    • Urgent?:
      No

      Description

      During testing of the full DP0.2 ObsCore dataset, we found some issues that we patched on the live qserv data but need to push "upstream" to the extractor config.

      • access_format should be application/x-votable+xml;content=datalink
      • data-int.lsst.cloud needs a different config from data.lsst.cloud so that the access_url points to http://data-int.lsst.cloud.

       

        Attachments

          Issue Links

            Activity

            Hide
            ctslater Colin Slater added a comment -

            We should add an "lsst_exposure" column derived from the dataId, since raws don't have a visit number. (My mistake forgetting this the first time, and it's not urgent to fix)

            Show
            ctslater Colin Slater added a comment - We should add an "lsst_exposure" column derived from the dataId, since raws don't have a visit number. (My mistake forgetting this the first time, and it's not urgent to fix)

              People

              Assignee:
              fritzm Fritz Mueller
              Reporter:
              ctslater Colin Slater
              Watchers:
              Andy Salnikov, Colin Slater, Fritz Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.