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

Provide an interim definition of the obs_publisher_did field in ObsCore that is usable for Gen3-based image data

    XMLWordPrintable

    Details

    • Type: Story
    • Status: In Progress
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Design Documents
    • Labels:
      None
    • Team:
      Architecture

      Description

      In order to facilitate the independent development of both:

      1. ObsCore-compliant image metadata services (ObsTAP and SIAv2); and
      2. a SODA service

      we need a near-term-usable definition of how to construct ObsCore obs_publisher_did values for data in a Gen3 repository.

      "Near-term" is meant to mean at a minimum "expected to work for Gen3-based HSC datasets" and usable for them for the DP0 data release and the Spring 2020 LSP testing round.

      It would probably be good to have an idea for how this would also work for LSST simulated images (e.g., from DESC DC2), should these end up being part of DP0 but this is not a requirement for this ticket.

      Nor is it a requirement for this ticket that either

      1. we devise a solution that is relevant to the LSST operations era or
      2. the proposed solution continue to work without change throughout the rest of construction and commissioning.

      It is OK if a redesign turns out to be needed somewhere along the way. It is more important that we get this off the ground.

      The deliverable from this ticket is a written spec, not code.

        Attachments

          Issue Links

            Activity

            gpdf Gregory Dubois-Felsmann created issue -
            gpdf Gregory Dubois-Felsmann made changes -
            Field Original Value New Value
            Description In order to facilitate the independent development of both:
            # ObsCore-compliant image metadata services (ObsTAP and SIAv2); and
            # a SODA service

            we need a near-term-usable definition of how to construct ObsCore {{obs_publisher_did}} values for data in a Gen3 repository.

            "Near-term" is meant to mean at a minimum "expected to work for Gen3-based HSC datasets" and usable for them for the DP0 data release and the Spring 2020 LSP testing round.

            It would probably be good to have an idea for how this would also work for LSST simulated images (e.g., from DESC DC2), should these end up being part of DP0 *but this is not a requirement for this ticket*.

            Nor is it a requirement for this ticket that either
            # we devise a solution that will work in the LSST operations era *or*
            # the proposed solution continue to work without change throughout the rest of construction and commissioning.

            It is OK if a redesign turns out to be needed somewhere along the way. It is more important that we get this off the ground.

            The deliverable from this ticket is a written spec, not code.
            In order to facilitate the independent development of both:
            # ObsCore-compliant image metadata services (ObsTAP and SIAv2); and
            # a SODA service

            we need a near-term-usable definition of how to construct ObsCore {{obs_publisher_did}} values for data in a Gen3 repository.

            "Near-term" is meant to mean at a minimum "expected to work for Gen3-based HSC datasets" and usable for them for the DP0 data release and the Spring 2020 LSP testing round.

            It would probably be good to have an idea for how this would also work for LSST simulated images (e.g., from DESC DC2), should these end up being part of DP0 *but this is not a requirement for this ticket*.

            Nor is it a requirement for this ticket that either
            # we devise a solution that is relevant to the LSST operations era *or*
            # the proposed solution continue to work without change throughout the rest of construction and commissioning.

            It is OK if a redesign turns out to be needed somewhere along the way. It is more important that we get this off the ground.

            The deliverable from this ticket is a written spec, not code.
            gpdf Gregory Dubois-Felsmann made changes -
            Watchers Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Tim Jenness [ Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Tim Jenness ] Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness [ Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness ]
            kennylo Kenny Lo made changes -
            Link This issue relates to DM-17742 [ DM-17742 ]
            gpdf Gregory Dubois-Felsmann made changes -
            Remote Link This issue links to "Page (Confluence)" [ 23798 ]
            tjenness Tim Jenness made changes -
            Link This issue blocks DM-34483 [ DM-34483 ]
            tjenness Tim Jenness made changes -
            Watchers Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness [ Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness ] Andy Salnikov, Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness [ Andy Salnikov, Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness ]
            gpdf Gregory Dubois-Felsmann made changes -
            Link This issue relates to DM-35177 [ DM-35177 ]
            gpdf Gregory Dubois-Felsmann made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              gpdf Gregory Dubois-Felsmann
              Watchers:
              Andy Salnikov, Colin Slater, Fritz Mueller, Frossie Economou, Gregory Dubois-Felsmann, Kenny Lo, Kian-Tat Lim, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.