Carrot Rules Diagram

[AndyRae]

This probably needs completely rethinking.

It was clearly created with small sets of rules in mind, but the current implementation is a liability for any normal amount of rules. It creates long running calls that can crash the application.

So, what?

We should definitely add filtering of some level, whether source, domain etc.
Maybe this should be dynamic, so the DAG is built in Javascript from data, rather than currently by Django/Python queries.

https://github.com/erikbrinkman/d3-dag

Relevant: #757

[AndyRae]

We are trying to visualise "What is going where?", "In the right place?"

[AndyRae]

Could we use a Sankey diagram to visualise mappings instead, with a "table" filter to configure.
But for only the mappings, not the person_id, date columns are relevant.

What mappings are going where?
Going from source_field to destination_table

[AndyRae]

https://github.com/Health-Informatics-UoN/explore-rulesets