Use value to check for duplicate metadata property in the visualization graph #30
Conversation
This file contains 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
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.
When building visualization graphs (with NetworkX), there is a check to avoid inserting ambiguous metadata in the nodes (if different objects exist with the same identifiers). However, when merging multiple graphs for visualization, the RDF description of the same data object may exist in both RDF files. Therefore, the graph visualization would fail because the check did not consider the attribute's value. This fixes the behavior by throwing an exception only when inserting the same attribute with different values in an existing node where that metadata attribute is already defined.