Move seaspan datasets to datasets_development folder #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on some exchange with @steviewanders, it will be tricky on the servers end to be able to start relying on the ERDDAP authorization system at least in the near future.
Goose ERDDAP
Due to that, we will rely on the goose development erddap and its google authorization to serve the protected data (for now). Using this feature has a few downsides:
We are not able to retrieve the data through the ERDDAP api without manually retrieving an authorization. With ERDDAPs authorization system we could potentially avoid it with the custom passwords or https://coastwatch.pfeg.noaa.gov/erddap/download/AccessToPrivateDatasets.html. Since goose erddap right now isn't using the ERDDAP protection, we can't really use any suggestions present in the link above.
Development ERDDAP (goose) is using the development branch, while production erddap servers the main branch. This will bring the issue of either keeping some datasets only within the development branch or having datasets continuously failing in the production erddap.
Suggestion: create a new datasets_development folder
We will keep the protected datasets available on Goose only and keep their associated dataset's xml in a dataset_development folder. Goose will concatenate the xmls in the
datasets
anddatasets_development
servers while production will only use thedatasets
folder.That way, we can keep the two branches near each other and be sure that none of the protected datasets will ever make it to the public production server.
TO DO on servers
dataset_development
.