Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4689

LOTSS data represented in CAOM and demonstrated with new query service

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      BH: Demonstrate the benefits of a richer science metadata querying functionality with the radio astronomy extension to the CAOM data model with a reference mapping using the LoTSS DR2 mosaics.

      Show
      BH: Demonstrate the benefits of a richer science metadata querying functionality with the radio astronomy extension to the CAOM data model with a reference mapping using the LoTSS DR2 mosaics.
    • Hide

       

      AC1: LoTSS data engineering represented in the newly deployed service.

      AC2 : Demonstrate the LoTSS CAOM2.5 representation.

       

      Show
        AC1: LoTSS data engineering represented in the newly deployed service. AC2 : Demonstrate the LoTSS CAOM2.5 representation.  
    • 1
    • 0
    • 0

    • Feature SP-4397 Develop a first working draft of an IVOA standard for a rich science metadata model that includes improved support for radio data

    • Team_RED

    • PI24 - UNCOVERED

    • PI24 PI24-PB SRCNet0.x Team_RED science-metadata science-metadata-services

    Description

      This work consolidates the outcomes from two previous Features:

      1. SP-4397
      2. SP-4420 

      This work will be to refactor the LoTSS DR2 data modelling work to be represented in the proposed radio astronomy model.

      Attachments

        Issue Links

          clones

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4593 A radio-specific query service to support CAOM model for SRCNet

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Program Backlog
          is cloned by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4690 eMERLIN data represented in CAOM and demonstrated with new query service

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Funnel
          is informed by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4397 Develop a first working draft of an IVOA standard for a rich science metadata model that includes improved support for radio data

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Releasing

          Structure

            Activity

              People

                b.mort Mort, Ben
                s.goliath sharon goliath
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel