-
Notifications
You must be signed in to change notification settings - Fork 6
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
Biosecurity Alerts admin function - page content clarity & function implementation #198
Comments
My two cents: my understanding regarding with terms used in subscriptions is: We subscribe to a subscription. If new records come into this subscription, we send email/notification/alerts to the subscribers |
qifeng-bai
added a commit
that referenced
this issue
Apr 16, 2024
qifeng-bai
added a commit
that referenced
this issue
Apr 16, 2024
qifeng-bai
added a commit
that referenced
this issue
Apr 16, 2024
Since query_result has been linked to query
qifeng-bai
added a commit
that referenced
this issue
Apr 16, 2024
qifeng-bai
added a commit
that referenced
this issue
Apr 17, 2024
qifeng-bai
added a commit
that referenced
this issue
Apr 18, 2024
Looking good for v1, UAT to follow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Review content on Biosecurity Alerts admin page, specifically to improve the clarity and consistency. For example, semantics around 'alerts' versus 'subscriptions', 'subscribers', and so on.
Possible examples:
"Create a new alert"
"Reporting"
subtitle/para: "Download CSV list of all occurrences from all alerts"
"Manage alerts"
Subtitle, replace there are 22 subscription(s) with "22 active alert(s)"
The text was updated successfully, but these errors were encountered: