Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include a date range picker on the Analytics page #2612

Open
caaster opened this issue Oct 18, 2024 · 0 comments
Open

Include a date range picker on the Analytics page #2612

caaster opened this issue Oct 18, 2024 · 0 comments
Assignees

Comments

@caaster
Copy link

caaster commented Oct 18, 2024

Early discussion points to the fact that UX design may not be needed for this feature, provided the specification below is sufficiently clear and if there are other date range picker patterns in use for other DLSS apps that might be able to be re-used.

Please let me know if there are questions about the spec listed below, or things I have overlooked.

  • Jacob informs me that we started gathering GA4 for Exhibits in April 2023, possibly on 3 April 2023. The start date needs to be verified -- does anyone on the DLSS Access Team know?
  • We need a UI at the top of the Exhibits Analytics page that allows the exhibit admin to select a from - to date range, including day, month, and year.
  • The from date can't start any earlier than the first date we started gathering GA4 for Exhibits (whatever that date is verified to be).
  • The dates should be able to be edited as many times as the exhibit admin would like, in a single session.
  • If it makes sense, the default date range displayed should be for the past 365 days (unless this is not possible to implement).
  • A brief text explanation should be included immediately above or below the date range picker, stating: "The from date selected can't be any earlier than 3 April 2023, which was the implementation date for Google Analytics 4. Data for earlier versions of Google Analytics are not compatible with the current GA4 platform and SUL is unable to offer analysis of this older data." [Note: this is info straight from Jacob Hill about what we are able to support, re-stated by me in a way that hopefully makes sense to exhibit admins.]
  • It is the exhibit admin's responsibility to know when their exhibit was first published. So, if they select a date range that covers all or part of a time period when the exhibit was not published, the UI does not not need to indicate that all or part of the selected date range is during a period when the exhibit was not published.
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

No branches or pull requests

2 participants