[4987] Annual Reports range Export
Resolves #4987
Reviewer Notes
- please test with various data, I've only used the seed data locally
- if commits need to be squashed, lmk. I believe I need to push w/ force to do that, so I'm holding if off for now.
Description
- new path to get bulk annual reports
/reports/annual_reports/range/{year_start}/{year_end}.csvex:../reports/annual_reports/range/2023/2024.csv
- years in url must be 4 digits or Routing Error will be raised
- the latest year of
earliest_reporting_yearandyear_startwill be used - the earliest year of the current year and
year_endwill be used - will use existing AnnualReport. If latest data is needed, the individual year's annual report will have to be recalculated
Type of change
- New feature (non-breaking change which adds functionality)
- Documentation update
How Has This Been Tested?
- tested on page
- made a small rspec test
Screenshots
https://github.com/user-attachments/assets/25aea7c4-b778-46d4-beca-3bdf181cfe08
Thanks for the info @cielf I'll check back when there's an update then.
Thanks for the info @cielf I'll check back when there's an update then.
I'm sorry -- I thought that we'd included the information that yes -- we can recalculate the reports. They do, however, still end up having different columns.
@douten Are you still able to work on this? If not, we'll open it up for someone else.
More than a month since we last heard from the developer -- I'm going to mark the issue as available (might take it myself).
Notes on what I see that still needs to be fixed after adding the recalculation -- 1/ The "Please wait..." doesn't go away -- It doesn't on the individual report exports either. In Production. So -- perhaps not an absolutely necessary fix to put this forward, but recalculating everything could take a bit of time in prod, so I'd like to see it addressed. [Not happening today.]