Join GitHub today
some nodes don't expand; use gvp:narrower #1
So which predicate do you use to navigate? You should use gvp:narrower.
Thanks for pointing this out. I am indeed using
A strict dendrogram is not actually entirely sufficient for displaying the relationships within the AAT, because individual nodes can have multiple parents. For example, one of the children of node aat:300389850 is node aat:300073708. This child has a separate "parent" (via the
One solution for this problem is to simply allow the same node to be written into the JSON hierarchy multiple times. I originally wrote the program this way, however the script would get stuck in an infinite loop on a troublesome section of the AAT where a node had a "child" (
Solutions may include:
I suspect the former approach would be easier to implement. I will try to address that when I can find the time, but it may take a while. In the meantime, I'll be sure to update my post to reference this issue. It actually raises a very interesting discussion about how to visualize these vocabularies.
After some testing, I've isolated two troublesome nodes whose own children have listed their parent nodes as "narrower", thus causing infinite looping:
I'm having the hierarchy script skip these specific nodes until I can find a more elegant way to address the issue.
Hi! Yours is like the 3rd actual use of AAT LOD, so we very much appreciate your detailed feedback to fix these points.
But first: have you read the AAT Semantic Representation Documentation? If so and it leaves things unclear, I'd appreciate if you point out the specific sections that need expanding.
Sure, AAT is a poly-hierarchy. But each has just one gvp:broaderPreferred
gvp:broaderPartitive, gvp:broaderInstantial, gvp:broaderGeneric are sub-props of gvp:broader so you don't need them.
Thanks for the report! This is a data bug.
I've started a doc section 4.5 Data Quality Queries, and the above is subsection 4.5.3 Check For Loops in the Hierarchy. But Getty hasn't yet decided about this.
We're collecting use stories at an internal confluence. You're at number 3 :-)