search

gbif / portal-feedback

User feedback for the GBIF API, website and published data. You can ask questions here. 🗨❓
30 stars 16 forks source link

alert dataset POC about github ticket creation when giving feedback #5077

Open sformel-usgs opened 9 months ago

sformel-usgs commented 9 months ago

When you click on the chat symbol in GBIF to give feedback on content, you are given the option of either contacting the dataset POC or creating a github issue. It would be useful to have a third option to send an email that alerts the dataset POC about the github issue creation.

Here is an example where it would have been useful: https://github.com/gbif/portal-feedback/issues/4624 The POC was very responsive to my outreach, but they do not monitor this repo since they are not github users. If the creation of the github issue could also trigger an email to the POC then it would reduce some of the intervention needed in these tickets. However, I'm not sure if this is something that can be done via github-actions.

MortenHofft commented 9 months ago

technically it is possible to automatically send out email on issue creation through the website. I guess the potential problem with automatically sending emails is that we "spam" POC with irrelevant issues (e.g. backbone related issues, ui comments, angry users, etc).

Another approach: since dataset contact information is public, i guess there is no harm in adding a button similar to send email but to dataset contacts - and it didn't have to be protected (unlike our "send-email-to-user"). It could be an easier way to notify dataset POC when it is considered relevant?

ping @ahahn-gbif

ahahn-gbif commented 9 months ago

As you suspect, @MortenHofft, we stayed away from automated email notification. Blanket automatic forwards could be perceived as spamming and be counterproductive, due to a very mixed bag of relevant and actionable feedback vs the other kind. If we wanted to go this way, we would need some kind of transparent opt-in solution. In principle, this is one step from occasionally running a GitHub filtered search that anybody could do. Maybe an idea for the GBIF user profile, rather than a general GitHub rule?

sformel-usgs commented 9 months ago

I hadn't really considered the spamming aspect of it. Although the 'opt-in' solution might be helpful, I don't think the returns would be worth prioritizing it. So, for now, let's leave it as is. As the node manager, I can be the person who occasionally runs the filtered searches and contacts people. After thinking some more about it, a silver lining of such interactions is strengthening the network between dataset POCs and the node.

Thanks for taking the time to answer so quickly. @MortenHofft I'll let you close the issue in case you have more thoughts.