Can the viz type be included in the JSON data definition?

[pmackay]

In the drupal site we want to display and filter on the types of visualization. Extracting this info from the JSON data when its generated seems like the best way. Thoughts?

[dataunity]

There's a list of renderers that get store in VizShare. Every time a renderer gets registered with VizShare it's added to the list. At the moment, not a lot of information gets stored with the renderer, it's just it's render function (used to draw the visualisation) and it's name. I could open up this information with something like a vizshare.getRenderers() method call?

Initially I was going to put renderer metadata in VizShare, but I've been planning to have it server side in Data Unity for the moment as it's useful to interact with it through the Web API.

I'm not too good on Drupal so not sure the best way for Drupal to interact with the information in the VizShare js library.

[pmackay]

Method call sounds good if there can be a "type" field that has a standard name for each viz type.
I thought vizshare was designed to be independent of DU? How would it work if the metadata was server side?
If the field is there, I can pull into Drupal. But could the renderer type be stored in the JSON structure passed into vizshare?

[dataunity]

VizShare is independent of Data Unity. Just wanted to work out the renderer metadata so it's somehow compatible with Linked Data. It just seemed easier to do this server side, then derive a JSON-LD format for the javascript side.

I'll add a 'type' field to the renderer metadata documentation (part of the VizBuilder doc). Would we need this information on the VizShare JSON? Seems more like renderer metadata?