cwrc / HuViz

LOD visualization tool for humanities datasets
8 stars 1 forks source link

Nodes sticking to Shelf #129

Open antimony27 opened 6 years ago

antimony27 commented 6 years ago

If I load a dataset (in this case, SHARP2017), and drag in people, some of the nodes stick to the shelf and won't drag into the center. Here, I pulled Sophia King into the middle of graph, and everything joined her except for English.

screen shot 2017-11-01 at 10 42 57 am

smurp commented 6 years ago

I've not been able to make this happen anymore -- perhaps I'm unclear on which dataset/ontology combo is doing this -- or maybe some changes in code or rdf have solved this. My experience has been that this arises when the sorting of the nodes has been interfered with by -- in the past -- the sort routines being sensitive to some tricky detail.

antimony27 commented 6 years ago

image

Still happening. We think this is likely a data issue, but I'm leaving it here for @smurp to investigate.

Data file: HuVizSharp2017 Onto: OwlMini (because CWRC onto not working)

antimony27 commented 6 years ago

And one more example: image This always happens with the CWRC onto node. It won't move away from the shelf. If you drag it to make it part of the node clustered inside, it still goes back to the shelf when you release.

antimony27 commented 5 years ago

Closing because this is covered in #99. Duplicate Issue.

smurp commented 5 years ago

I think we should distinguish between nodes which are not connected (#99) and nodes which are stuck on the shelf -- which I am still seeing occasionally.

smurp commented 5 years ago

The broken sort order in #109 might be related to this stick shelf issue -- that was the case the last time I dealt with this a few years ago -- the sort order being broken caused the sticky shelf.

antimony27 commented 5 years ago

Closing, hopefully this is fixed.

smurp commented 5 years ago

Sadly I think we're still seeing this one. I'd even say it is a very top priority.

antimony27 commented 5 years ago

Where did you see this @smurp ? I think we should investigate the datasets, unless its coming from the Sparql endpoint?