Details
-
Type:
Story
-
Status: In Progress
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Design Documents
-
Story Points:4
-
Epic Link:
-
Sprint:Arch 2018-09-24, Arch 2018-10-01, Arch 2018-10-08, Arch 2018-10-15, Arch 2018-10-22, Arch 2018-10-29, Arch 2018-11-05, Arch 2018-11-12, Arch 2018-11-19, Arch 2018-11-26, Arch 2018-12-03, Arch 2018-12-10, Arch 2019-01-07, Arch 2019-01-14, Arch 2019-01-21, Arch 2019-01-28, Arch 2019-02-04, Arch 2019-02-11, Arch 2019-02-18, Arch 2019-02-25, Arch 2019-03-04, Arch 2019-03-11, Arch 2019-03-18, Arch 2019-04-01, Arch 2019-04-08
-
Team:Architecture
Description
As an initial step toward fleshing out our internal architecture and how it uses IVOA standards, I will write a series of tickets and documentation related to our use of the ObsCore standard, ranging from the ObsCore-to-ButlerGen3 interface, to Firefly support for ObsCore data, to DAX provision of services (SIAv2 and ObsTAP) returning ObsCore-based results.
Starting work by documenting the ideas on utilization of ObsCore in the Portal that emerged from last week's Portal design meetings.