Skip to content

Add a changelog and populate it with draft 1.1.0 changes#85

Merged
jeancochrane merged 16 commits into2024-data-updatefrom
jeancochrane/82-add-changelogmd-file-and-document-2024-changes
Apr 29, 2026
Merged

Add a changelog and populate it with draft 1.1.0 changes#85
jeancochrane merged 16 commits into2024-data-updatefrom
jeancochrane/82-add-changelogmd-file-and-document-2024-changes

Conversation

@jeancochrane
Copy link
Copy Markdown
Member

@jeancochrane jeancochrane commented Apr 20, 2026

This PR adds a new file NEWS.md that we can use to document changes to the code and data over time. We populate it with draft changes for version 1.1.0, representing the necessary code changes powering the 2024 data release.

NEWS.md is a tidyverse standard for publishing release notes about R packages. The pkgdown package that we use to build our docs has first-class support for it, and will automatically build it into our deployed docs.

Here's a quick screenshot showing how the changelog renders on the pkgdown docs page:

image

If you would like to render the doc in this format for review, you can run the following code in the RStudio console to launch a preview:

pkgdown::build_news(preview = TRUE)

Closes #82.

Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
data, you will need to use these new columns to handle changes to
agency numbers. See this vignette for a demonstration of how to
use the new columns to construct a crosswalk for agency numbers
across years: _TK: Link to vignette_
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waiting until #84 lands to add a link here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless we change the .RMD file name, the link should ultimately be https://ccao-data.github.io/ptaxsim/articles/agencies.html

Comment thread NEWS.md Outdated
- **How this change affects you**: You should read the latest version of the
vignette if you use PTAXSIM for TIF counterfactuals.
- **Added a new vignette to demonstrate the correct way to handle agency
numbers that changed in 2024 (_TK: Link to vignette_)**
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above: I'm waiting until #84 lands to add this link.

Comment thread NEWS.md Outdated
@jeancochrane jeancochrane marked this pull request as ready for review April 20, 2026 17:17
Copy link
Copy Markdown
Member

@kyrasturgill kyrasturgill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much for documenting all of this! I just have some minor edits and suggested added context. Let me know if you want to talk more through how to frame the agency number change.

Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
Comment on lines +23 to +27
consisted of three digits, and funds with the same `fund_num` in different
agencies always referred to the same type of fund. In 2024, the Clerk changed
their fund numbers so that they consist of six digits, and they are no longer
guaranteed to refer to the same type of fund across agencies. The new types
of funds that this change supports are primarily bond series.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
consisted of three digits, and funds with the same `fund_num` in different
agencies always referred to the same type of fund. In 2024, the Clerk changed
their fund numbers so that they consist of six digits, and they are no longer
guaranteed to refer to the same type of fund across agencies. The new types
of funds that this change supports are primarily bond series.
consisted of three digits, and funds with the same `fund_num` in different
agencies always had the same `fund_name`. In 2024, the Clerk changed
their fund numbers so that they consist of six digits, and they are no longer
guaranteed to share the same `fund_name` across agencies. The new types
of funds that this change supports are primarily bond series.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarifying question before I accept this change: Were the names of funds with the same number indeed guaranteed to be identical prior to 2024? The line on the main branch that calculates fund_name in agency_fund_info makes it seem like they are perhaps similar, but not identical:

summarise(fund_name = calc_mode(fund_name)) %>%

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding was that this was done because of inconsistencies with case and spacing across years - I think that's ultimately why the table did not originally include agency_num as a key.

Copy link
Copy Markdown
Member Author

@jeancochrane jeancochrane Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha, thanks! I implemented your suggested change in fc6ecf7. I think an additional sentence like this might help clarify the situation even further:

In 2024, the Clerk changed their fund numbers so that they consist of six digits,
and they are no longer guaranteed to share the same name across agencies.
+ They also added many new six-digit funds that were previously aggregated into
+ larger three-digit funds. For these new six-digit funds, the first three digits of the
+ fund number always matches the three-digit number for the aggregate fund that
+ existed prior to 2024.

Does this seem correct (and helpful) to you @kyrasturgill?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this makes sense! I was also thinking, should we clarify that for fund_num in years to 2024, we added "000" to make the format consistent?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, done in 30f01df!

Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
Comment thread NEWS.md Outdated
@jeancochrane
Copy link
Copy Markdown
Member Author

@kyrasturgill Thanks for the helpful review! Do you mind giving this another look? All of your comments should be resolved, except for #85 (comment), which I can resolve once we're on the same page.

@dfsnow
Copy link
Copy Markdown
Contributor

dfsnow commented Apr 23, 2026

Dang yall did some work on this.

@jeancochrane
Copy link
Copy Markdown
Member Author

It did some work on us, too 🙃

Copy link
Copy Markdown
Member

@kyrasturgill kyrasturgill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks great to me! I really like the framing of "agencies that changed to funds" in 2024 - I think that is clearest way to explain it. I appreciate added context about fund_num and I defer to you if we want to add more explanation about our change to fund_num for years prior to 2024, but wanted to technically approve so it's ready to merge when you think it's ready.

@jeancochrane
Copy link
Copy Markdown
Member Author

jeancochrane commented Apr 29, 2026

@kyrasturgill I'm going to go ahead and merge this in, even though the agency crosswalk design is not fully settled yet (#88)! If we end up changing the crosswalk, we can tweak this changelog as part of that PR.

@jeancochrane jeancochrane merged commit 4c52f49 into 2024-data-update Apr 29, 2026
7 checks passed
@jeancochrane jeancochrane deleted the jeancochrane/82-add-changelogmd-file-and-document-2024-changes branch April 29, 2026 15:23
@jeancochrane jeancochrane linked an issue Apr 29, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add CHANGELOG.md file and document 2024 changes

3 participants