Open davewhiteland opened 8 years ago
There's a slight impedance mismatch there, though. What would the "last updated" at the bottom of http://everypolitician.org/uk/commons/term-table/52.html signify, for example?
Well, there's potentially an impedance mismatch where we list the sources for the whole legislature on each term page too. It's not a naughty problem. And yes we've made it harder for ourselves by these pages sometimes being chunks of data that haven't been changed. But is that a good enough reason not to publicise that the data is being updated often?
EveryPolitician data for this legislature last updated: 2016-08-04
It's true. And it communicates that the data is being updated.
If we want to feature creep this, and properly sweat the details, then we could get fancy and note changes affecting terms with varying amounts of precision (e.g., has the term's CSV changed?), and even add summaries not unlike the bot's PR ones (e.g., "3 people added").
Also cough SEO perhaps. These pages aren't changing when the data they are linking to is, so I can't see the harm in updating them.
We're currently showing "sources" at the bottom of each term page. How about showing "Last updated:" underneath that too?
That the data is so dynamic -- being updated almost daily in many cases -- is something that perhaps we should be making visible to people who aren't looking on github.
The
lastmod
date is easily available (e.g. incountries.json
) when we're building the page, so I think this might be easypeasylemonsqueezy to implement.