embargo roll out check: check restriction taking into account object hierarchy#1
Open
embargo roll out check: check restriction taking into account object hierarchy#1
Conversation
…hierarchy assuming that inner nodes that do not have restriction status set inherit from parents
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes the check for restricted status on given channel to take into account what is set on the parent objects (station, network), if the restricted status is not set on the channel.
To my knowledge, FDSN StationXML is not really very clear on some details here. It does not specify what the default is when restricted status is not explicitly set.
Also, it is not clear how restricted status should be interpreted when it is set on multiple levels.
This change assumes that..