Milestones
List view
- Due by August 27, 2021
Except ongoing milestones..
Due by December 31, 2022•79/80 issues closedhttps://docs.google.com/document/d/1lI3xA_ZaObj6O_jGVC9nJCXG5oMYJ4MdKV8bYwuiaT0/edit#heading=h.ehqguat1codl
Due by April 30, 2021- Due by November 26, 2021
- Due by September 17, 2021
- operational csw service (prod site up and running) - follow up evaluation report - integration with geonorge - figure out why it's not working at the moment, and who is responsible - data quality metadata - provenance metadata? (maybe too early) relevant for confident project.. - CSW endpoint testing (geohealthcheck; in kubernetes env?) - DMH - more data - in particular Arome Arctic
Due by May 28, 2021- Permanent Kubernetes staging environment - Documentation - Creating netCDF-CF files - ACDD metadata - Translation from ACDD to MMD - Review and update satellite data production - Integrate MMS in satellite data production - Storage on thredds.met.no + OPeNDAP streaming - Update oscar links - Verify that metadata content is correct - Operational CSW service - Integration with GeoNorge and NINA - Write full ISO19139 record as input to pyCSW - Agree output profile with GeoNorge (INSPIRE?) - Translate to DIF7 and DIF10, possibly WMO ISO profile - New queryables to pyCSW opensearch
Due by March 12, 2021- Due by April 30, 2021
- Due by April 16, 2021
- Due by February 5, 2021
WP6: Operationalize MMS See also: https://docs.google.com/presentation/d/1v_WT7lxozDTVAS3h1uhLjpU4kB6JThMiTHYldcIbMuY/edit#slide=id.g798e228f0b_0_69
Due by March 13, 2021•6/6 issues closed- evaluering etter sprinten (Johannes) - koble med kartverket gjennom csw - netcdf validator - arome-arctic use case, discovery metadata to MMD, use MMS test version - streamline integration of ODA data - prepare test version of MMS - communication plan (Morten)
Due by January 22, 2021*Goal:* Clarify three use cases and make sure that we meet the needs of producers and consumers of dynamical geodata * NINA use case * Klimafremskrivninger bruker * Klimafremskrivninger leveranse * “Simple use”/”lay user” example - see https://docs.google.com/document/d/1j7qYNibMSWYWN6zMDCoL_5sgo84ggDKjLYCAEFnckZU DoD: * We have created several use case examples * We have proposed solutions * We have gotten feedback on the solutions from the users
Due by April 30, 2021* Design document for how provenance data should be made available for the “simple apis”. * Evaluate dars as DAP server component. Alternative is Hyrax. (Evaluate three DAP servers and agree on a recommended solution) * PoC for easy to use DAP distribution from any kind of infrastructure. Extendable to different types of data formats and storage solutions. In a FAIR way. * Think about DNS, loadbalancing, proxy, operational responsibility, monitoring etc. * Consider this as part of a bigger ecosystem of services, aka. senda-access-stack. Old notes: - Data access and (provenance) metadata for the APIs - Establish a group of people responsible for the data used to generate the available products on the various apis, or at least create an overview of the people responsible for the background data - Select one or two APIs for FAIR assessment, and plan and start executing the work required to comply with the FAIR principles according to discussions at the workshop 13th October - make a list of weaknesses and a plan to improve - Maybe start the work on - OPEnDAP access to raster data (thredds/hyrax/dars on new infrastructure?) - New (FAIR) API for weather and ocean point forecasts (pick up ocean forecast from previous sprint)?
Due by November 27, 2020**Sprint goal: Create production release of MMS, which can be set to production for some jobs in ecFlow.**
Due by November 27, 2020•8/8 issues closed**Goal:** Get some MET data from ODA and satellites into the metadata catalogue, and operationalize the metadata ingestion for ODA and weather satellites. **DoD:** https://s-enda-documentation.readthedocs.io/en/latest/definition_of_done.html Old notes: - Metadata catalog - Further work on the metadata catalog - we need to ingest metadata now.. - Data quality in MMD (https://github.com/metno/mmd/issues/114) - NINA discovery metadata - make NINA metadata catalog harvestable from outside with OAI-PMH and CSW - store NINA discovery metadata centrally - Use case for combining data from NINA and MET?
Due by November 27, 2020- Due by October 2, 2020
- Due by October 30, 2020
*Goal:* Prepare interfaces between user and client, and client and backend, and prepare a mockup of the backend system for the replacement of the messaging system in productstatus (L6.4 and L6.5) to help being able to fully remove productstatus * metadata controlled ocean and atmosphere forecast production (follow use case(s))? Some guidelines: * Keep the data dashboard in mind..: http://senda1.lab-a.met.no:8081/ * ... and at readthedocs: https://s-enda-documentation.readthedocs.io/en/latest/general_conventions.html, https://s-enda-documentation.readthedocs.io/en/latest/git_conventions.html, https://s-enda-documentation.readthedocs.io/en/latest/definition_of_done.html
Due by September 11, 2020