Improve how Report relationships/links are handled

oasis-open / cti-stix-visualization

OASIS TC Open Repository: Lightweight visualization for STIX 2.0 objects and relationships

http://oasis-open.github.io/cti-stix-visualization

BSD 3-Clause "New" or "Revised" License

138 stars 43 forks source link

Improve how Report relationships/links are handled #12

Open gtback opened 7 years ago

gtback commented 7 years ago

If a Bundle contains a Report which refers-to most other objects in the bundle (like the current apt1.json file), the graph view is hard to read, since most objects arrange themselves in a circle around the report at the center.

Possible suggestions:

Don't create links for Report objects
Make the links much lighter (in color) and lighter (in weighting for the force-directed graph). That would let you see all the report links but not obscure the more "important" relationships.

I'm sure other people have better ideas.

gtback commented 7 years ago

The same is probably true for created_by_ref links.

Another solution would be to have a toggle switch for each of these types of relationships, and (perhaps) disable by default when there are more than a fixed number of each type (5 or 10, maybe).

gtback commented 7 years ago

Also, the marking references should be toggle-able in the same way.

Bojak4616 commented 7 years ago

Just a status update I've had to rework the repo to use D3js v4 to get access to the collide() function which allows a node to have a collision radius. Doing so allows greater node separation when looking at a lot of SDOs.

There are no more syntax errors but functionality is not the same as v3. Turns out a lot of functions change parameters, output, and may not even exist anymore. Backwards compatibility was extremely limited.

Once core functionality is restored a pull request will be made. Then a separate branch will be created for the collide capability.

Bojak4616 commented 6 years ago

Current status outlined in 098e1749fa69d5aed093ccf96be4547a1f4a4584. Unfortunately, without taking the time to learn Javascript and D3js v4 from the ground up, there are still usability issues to iron out.