Add IRI pattern matching to remove/filter selectors #448
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.
See #446, also adds examples to the CURIE matching.
@matentzn I would appreciate if you could test this out for your use case, if you get a chance! Thanks!
Patterns
...
It is also possible to select terms based on parts of their IRI. You may include an IRI pattern using one or more wildcard characters (
*
and/or?
) enclosed in angle brackets.<IRI-pattern>
<http://purl.obolibrary.org/obo/EX_*>
If you wish to match a more complicated pattern, you may also use a regex pattern here by preceding the pattern with a tilde (
~
):<~IRI-regex>
<~^.+EX_[0-9]{7}$>
...
Examples
...
Remove all axioms containing an entity in the BFO namespace from the UBERON module: