You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Register all RA models hosted on the EDS TDS instance in IOOS Catalog.
Note: this necessitates RPS creating some type of attribution allowing a reference back to the source RA TDS or other server hosting the data. This is in order to allow users a way to access the source data if they want.
Related to #40. This should be an easier pathway to increase the model coverage in the Catalog. RAs can still register their own services if they want via Harvest Registry.
The text was updated successfully, but these errors were encountered:
@kbailey-noaa Did we decide on whether/how to include metadata from the EDS THREDDS server for RA model output in IOOS Catalog?
I'm trying to clean up lingering issues for our Jan 29 Catalog 1.6 milestone, and this is one of them. It also might allow us to close out #40 at some point because there isn't any traction moving that along.
Register all RA models hosted on the EDS TDS instance in IOOS Catalog.
Note: this necessitates RPS creating some type of attribution allowing a reference back to the source RA TDS or other server hosting the data. This is in order to allow users a way to access the source data if they want.
Related to #40. This should be an easier pathway to increase the model coverage in the Catalog. RAs can still register their own services if they want via Harvest Registry.
The text was updated successfully, but these errors were encountered: