Skip to content

Commit

Permalink
add note to release notes about fix in 7acebed
Browse files Browse the repository at this point in the history
  • Loading branch information
sckott committed Jun 14, 2022
1 parent 7acebed commit 23878d3
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions RELEASE_NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ both its appearance and its underlying data.
This means you will often see changes in the UI/UX, and sometimes in the presented data.
Most of these changes are too small to note, but we'll keep a record of the larger ones here:

- 2022/06/14 Copying a scenario within a consortial package was broken due to a bug in our code. It is now fixed!
- 2022/06/02 Integrate OpenAlex metadata into the Unsub backend. For now this includes journal metadata (e.g., ISSN, title, publisher, etc.) as well as journal concepts/subjects (e.g., Medicine, Ecology). Later we'll integrate additional OpenAlex data. To be clear, subjects throughout Unsub (in the user interface and in data exports) are now from OpenAlex. This change of journal metadata does affect what titles are included in your Unsub dashboards. We analyzed 212 scenarios before OpenAlex and after integrating OpenAlex, and there are only tiny differences: on average number of titles included in scenario are 0.62% different, forecasted costs are 0.18% different and forecasted access (fullfimment) is 0.05% different.
- 2022/06/02 Scenario exports used to have two subject fields (subject, era_subjects), but now have three subject fields: subject, subject_top_three, and subjects_all. See the docs (https://docs.unsub.org/reference/data-export) for further details.
- 2022/03/23 Fix for Unsub dashboards: When a title's CPU was less than -1 the title (grey square) wasn't appearing in the histogram (but was present in the table view). Very few users were impacted by this. No Unsub backend changes - front end fix only.
Expand Down

0 comments on commit 23878d3

Please sign in to comment.