You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: When you filter the database from our homepage by a tag, the resulting vertical bar chart (far right DV) shows 12 months that sometimes / often belong across many different years on the x-axis
Two screenshots attached as examples:
Filtering for the tag "Israel-Gaza war" / "all time" = bar chart showing 12 months that belong across two different years, with Jan.-May belong to 2024 and Oct.-Dec. belong to 2023 (it loops, essentially, but no way to tell user that info);
Filtering for the tag "Black Lives Matter" / "all time" = a bar chart showing data from 2017-present, but May is distorted (due to 2020)
Solutions include, but are not limited to — when a user selects "all-time," the bar chart reflects incidents by year rather than month (similar to the "last 6 months" view); replace Jan with a year number if there are multiple years displayed, etc
The text was updated successfully, but these errors were encountered:
Issue: When you filter the database from our homepage by a tag, the resulting vertical bar chart (far right DV) shows 12 months that sometimes / often belong across many different years on the x-axis
Two screenshots attached as examples:
Filtering for the tag "Israel-Gaza war" / "all time" = bar chart showing 12 months that belong across two different years, with Jan.-May belong to 2024 and Oct.-Dec. belong to 2023 (it loops, essentially, but no way to tell user that info);
Filtering for the tag "Black Lives Matter" / "all time" = a bar chart showing data from 2017-present, but May is distorted (due to 2020)
Solutions include, but are not limited to — when a user selects "all-time," the bar chart reflects incidents by year rather than month (similar to the "last 6 months" view); replace Jan with a year number if there are multiple years displayed, etc
The text was updated successfully, but these errors were encountered: