Published dataset number should pull from socrata API on the home page

[jasonlally]

Currently, I'm just manually updating which is actually quick and easy and the number updates at a regular cadence anyway, so it hasn't become overwhelming to do quickly when we finish a round of publishing. However, it should just be automatic.

I just need to repurpose some javascript from DataSF in Progress. Part of the delay on this is that I want to make sure I'm implementing this in a way that reuses a library of elements, especially as we'll want to pull certain measures and indicators into other parts of the site (beyond the in progress dashboard).

[brennv]

Are we looking to periodically:
GET http://data.sfgov.org/api/catalog/v1
and parse for resultSetSize

[jasonlally]

I realized that I probably mislabeled the issue a little. I updated it to reflect the real issue better.

We don't want to get the resultSetSize of that because the catalog contains both datasets and other assets like visualizations so that inflates our number.

So it's just making a call to the inventory dataset.

Here's an example call that returns both published and unpublished.

https://data.sfgov.org/resource/q6xv-9c3b.json?$select=publishing_status,count(dataset_name)+AS+count&$group=publishing_status&$order=count+desc&$where=publishing_status%20%3C%3E%20%27Retired%27

In this case we only need the published count:
https://data.sfgov.org/resource/q6xv-9c3b.json?%24select=publishing_status,count(dataset_name)+AS+count&%24group=publishing_status&%24order=count+desc&%24where=publishing_status=%27Published%27

This is actually straightforward ajax call and parsing when you load the page. I guess my dilemma, and maybe a separate issue is bringing more sensibility to the overall site javascript (refactoring) to adopt a modular pattern so we can simply structure these calls across the site.

I'm open to just getting the first thing fixed, but would love help on refactoring maybe focusing on how to query and display objects like charts, numbers, etc. flexibly across the site.

[jasonlally]

Currently the number doesn't update from the API: