Closed ggalibert closed 3 years ago
Related issues: #196, #335
The layer was set up very quickly for a TAMS workshop years ago and not maintained since then. We'd need to check whether they (or anyone else) are still using it.
@mhidas, @kereid do you have a point of contact at NOAA or TAMS for this dataset?
@ggalibert no I don't have contact details for anyone at NOAA @smancini might? And Perhaps it would be best to contact Jessica Boomer for TAMS @mhidas will know if she is the best contact for that.
Jessica Boomer is the current coordinator of TAMS. This layer was originally added in 2014 for Jason Everett, and working also with Erik van Sebille (both at UNSW).
I'll contact them to see if they're still using this collection for TAMS.
They are no longer using this layer in the TAMS workshop, so I think we can safely remove it from the portal! @ggalibert @smancini
We could also remove the layers from geoserver-config, the db schema, and the harvester! That would also resolve https://github.com/aodn/content/issues/335 and https://github.com/aodn/content/issues/196
:bird: :bird: :bird: with one stone! (sort of)
Sounds like a great plan!
@atkinsn could you please remove the relevant metadata record from Geonetwork?
@ggalibert as we have had this collection up for a number of years on the Portal. What I would like to do is, to remove the WMS and WFS (etc) from the record, it will then be "removed" from the Portal. But still have it in GeoNetwork, in case someone has used this data and cited it, the link to the metadata will still resolve. I will add text to the metadata to explain when it was taken down etc.
@atkinsn is this done? can be closed?
For this to be closed, the following need to happen:
noaa_drifters_
layers from geoserver-config@atkinsn is this done? can be closed?
WMS and WFS removed, will disappear from Portal from tomorrow.
This collection is available on prod, yet is not being updated (set up a while ago by @mhidas) and associated noaa_drifters_map layer is too slow according to Nagios (looks not too bad on the portal though).
This dataset is not IMOS nor AODN, as far as I understood it was first set up as prototype. The question is should we get rid of it or try to complete this?