search

NCATSTranslator / Feedback

A repo for tracking gaps in Translator data and finding ways to fill them.
7 stars 0 forks source link

Automatically send email for users follow up #529

Open sandrine-m opened 1 year ago

sandrine-m commented 1 year ago

@Rosinaweber discussed on slack licensed software to keep engagement through sending automatic follow up email to users. Perhaps one easy way to deal with that would be that now that we have the users login, send them an email when they fill in the feedback form with the GitHub issue ticket?

sandrine-m commented 1 year ago

Is contact through email part of Translator consent agreement when using the UI? Also, I think we would need a Translator help desk ticket for that. Does one exist atm?

dnsmith124 commented 1 year ago

@sandrine-m this is a great idea! I'm honestly not sure re: the consent agreement though. We'd need to make sure before we log the user's email in either any created tickets or send any follow ups

Genomewide commented 1 year ago

I think any consent type of agreement is implicit if they say that want updates, but we could add some language. I think this is a great idea and PubMed does it as well. However, it is likely a big lift and will have to be weighed with other feature requests. We basically have one year left on the contract (which of course we hope will be renewed). But we have to prioritize either way. So, can you add this as a feature request ticket? That would help. Some specifications on what you think would trigger the alert that new things were available and how often we would check it. And anything else you can think of that would nail this down would be great!

gprice1129 commented 1 year ago

@sandrine-m this requires more discussion on implementation details and groups responsible for handling follow up. This is not a priority for the UI team this release cycle.

karafecho commented 1 year ago

@gprice1129 : The ROBOKOP UI had a feature in place to send registered users automatic emails when a query was submitted and when results were ready. This was very helpful for complex queries that took a long time to complete. I suspect you could modify this capability to support your goals, once defined. I don't believe there were any costs associated with the capability, but @kennethmorton or @maximusunc can confirm.

Agreed that this should not be high on the UI team's priority task list.