Indicator Catalog Review

[kimberly-bastille]

Lead: Kim

Brief Description: We decided to develop an indicator catalog to store info about indicators we collect that may not make it into the SOE.

Discussion topics:

• Walk through Template
• Sections missing
• What do we want this to look like?
• How do we want it to function?

Time:

Additional resources: https://keen-golick-345d62.netlify.app/

[andybeet]

So i think we could use the indicator catalog as the master, generate it however we want (from a csv, cut/ paste, user input) and style it however we like it, then when SOE comes around, just have script in the tech doc that pulls the relevant indices (and styles them however we want).

We could include a table (like you have in the ecodata landing page) that describes which indices are used in which product in which year. This table can then used by tech doc to pull the appropriate indicators. I think i like this better than generating both from a csv (google form) because inevitably edits will be required, and you dont want to have to be editing a csv and then recreating. I think maybe it is better to create the master catalog from the csv, as a one time deal, then edit the catalog.

I also like Sarah's the idea of sorting/filtering the indicators, but unsure as the best way to do this. Since the pages are all static and generated based on a travis build (or github action) not sure how you could sort them. I am assuming that is what Sarah meant: a user wishing to sort the html content

[kimberly-bastille]

I like the idea of using it as a master and I can use test doc as a dummy bookdown to see if I can get the workflow sorted out.

I also like the idea of being able to filter for specific chapters but I am not sure that is even possible based on how it is built. I wonder if it is possible to indicate somehow which are selected or at least return a list of chapters?