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

Update user-facing error messages that refer to Slack channels to now refer to #dlss-aaas #4428

Open
andrewjbtw opened this issue Apr 30, 2024 · 0 comments

Comments

@andrewjbtw
Copy link

There are a number of user-facing error messages that appear in Argo banner messages. Some of these suggest that the user contact a Slack channel for assistance. We have not been consistent on which Slack channel to contact for various reasons, including a lack of a central SDR support channel, changing contexts of work, and so on.

Since these banner messages are meant for Argo users (unlike HB messages), and since the #dlss-aaas channel has become the de facto SDR support channel (not just for accessioning), we should update all messages to refer to that channel.

A couple of channels that have been put into error messages in the past that we should no longer use:

  • #sdr-operations - this was created around the time I started and never gained traction. It's still around but basically it's just me and Tony C. and Tony Z. We used to have to do much more operational support (remediation of errors, etc.)
  • #dlss-infrastructure - this is too dev-focused for Argo messages. Especially as we get further from the Fedora migration, issues that show up in Argo are less likely to directly involve the dev team.
@andrewjbtw andrewjbtw changed the title Update user-facing error messages that refer to Slack channels to refer to #dlss-aaas Update user-facing error messages that refer to Slack channels to now refer to #dlss-aaas Apr 30, 2024
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

1 participant