More metadata about each project as table

[DanielJWood]

Whenever I do a dailygraphic I wonder if I've done something similar. I'm not particularly good at remembering specific stories. One easy way to narrow the search into past would be to include the type of template a slug was built from. For instance, if you wanted to find all line charts, you could have a column in the home menu that listed the type of chart. This could be autopopulated by the metadata column from the template and then editable if things substantially change or become more like tools (covid gfx, etc).

[DanielJWood]

I could try to build this on a branch but I'm curious if @alykat thinks this or something similar could be helpful.

[thomaswilburn]

If you're interested in doing this, instead of basing it on the metadata in the sheet, you should use the manifest and add a key at graphic creation that includes the name of the template--otherwise, you'll need to pull every sheet in the repo in order to scan for particular graphics, and the API will not like that.

[thomaswilburn]

You could do that here: https://github.com/nprapps/dailygraphics-next/blob/master/lib/createGraphic.js#L68 and then just grep the repo for that template key to find matching graphics, you wouldn't even need a UI right away (although it's not hard to build).

[DanielJWood]

Oh hey Thomas 😜. Yeah that's a good point. that would be very slow/inefficient. I'll see what I can do...

[DanielJWood]

this is taking place the metadata-view branch. A few things tk:

• sortable columns
• collapsable lineage cell
• style clean ups

[DanielJWood]

In fd248e3

• removed lineage and date columns. (Lineage is still captured in the manifest.json but quietly.)
• Added a simple search input for the template column.