Open ryparker opened 1 year ago
Thanks for your comment. We'll add this to our list for possible future development.
Thanks Mike. Am I correct in assuming other list APIs that have updateDate
(e.g. /nomination
) are sorted by this value in descending order (most recently updated are first)?
Would you consider adding this to Near term backlog? The committee API is one of the only APIs that does not offer the updateDate
on the list response. Even if it's not sorted by updateDate
, it's faster to regularly check all list items (4 requests) for updateDate
changes, rather than check each individual committee detail API (811 requests).
I'd be happy to split this up into multiple issues:
updateDate
to committee list responseupdateDate
updateDate
to congress list response updateDate
The congress API requests are not as important since I don't expect the data to change except every 2 years.
Howdy, @ryparker - thanks for following up on this. I am going to add these to the near-term backlog milestone. Please check the change log for any updates related to these once they are scheduled. Thanks!
Thank you!
Committee endpoint work is tentatively scheduled to be released on September 3, 2024. Check the change log for relevant updates. Thanks!
This has been divided up, just FYI:
<updateDate>
element for the committee list-level endpoint will be released, tentatively, in October 2024.<updateDate>
for the committee endpoint will be released, tentatively, in early November 2024. The <updateDate>
element for the congress list-level endpoint will be released, tentatively, in December 2024.
It would be helpful to have
updateDate
on the list APIs where it is missing and to sort by that value (just like how the other list APIs are setup). This would allow us to cache byupdateDate
and only query details on items that have changed. Currently I have to query every item's detail API regularly if I want to keep my dataset up to date.List APIs missing
updateDate
:Related: https://github.com/LibraryOfCongress/api.congress.gov/issues/61