Add 'parent' and 'children' properties to annotations and allow all tiers types with 'filter' #41
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.
This pull request proposes to add two new properties to
Annotationobjects:parent, which provides a reference to theAnnotationobject that represents the parent of thisAnnotation(if one exists;Noneif this is a root tier); andchildren, which provides a list ofAnnotationobjects that are the children of thisAnnotation(if any exist; empty if thisAnnotationhas no children).These properties are meant to make it easier to traverse annotations in ELAN transcripts hierarchically by following parent and child relationships between annotations on different tiers. It is already possible to navigate from child tiers to parent tiers with
Tierobjects; this pull requests adds similar functionality toAnnotationobjects, as well.This pull request also fixes a few minor typos (in comments, e.g., "Symbolic-Associtation" -> "Symbolic-Association") and adds the option of filtering non-time-aligned annotations using the starting and ending timeslots of their nearest time-aligned ancestor annotation, making it possible to use the
filtermethod on any tier, regardless of its stereotype.