You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most likely a “Contact [organisation name]” button, in the dataset card, which puts them in touch with a nominated contact from the organisation that provided the data. That contact can then redirect communication to any relevant local groups.
Need to consider whether we just reveal the contact’s email address (and leave it up to the user to send a message via their usual email client), or whether we mediate the communication, asking the user to fill in a form that then sends an email with a suitable reply-to: header.
Also need to consider whether we change the visibility or behaviour of this feature for public (non-logged-in) users, versus logged-in member users.
The text was updated successfully, but these errors were encountered:
Ok, have thought about this a little more. I think the main bits are:
New attribute on user model, defining whether the user should handle contact requests (defaults to false)
New attribute on dataset model, defining whether the dataset should be displayed with a "Contact" button (defaults to false)
"Contact" button on area page dataset cards, with GA event tracking that records the event type and dataset id
Modal form that collects the user’s name, email address, (optional) organisation, and (optional) short outline of why they’d like to be put in touch, and explains to the user that TCC will use this information to put them in touch with the relevant person at the requested organisation
(nice to have:) If the user is logged in, pre-fill the name, email address, and organisation for them
Form handler that takes the modal form submission, and sends it as a one-time email to all users currently marked as handling contact requests. Email should include:
Meg wants to check that TCC has the capacity to handle these requests, and what the risk might be if the dataset owning org(s) don’t have capacity or don’t want to be put in touch with a person either.
Most likely a “Contact [organisation name]” button, in the dataset card, which puts them in touch with a nominated contact from the organisation that provided the data. That contact can then redirect communication to any relevant local groups.
Need to consider whether we just reveal the contact’s email address (and leave it up to the user to send a message via their usual email client), or whether we mediate the communication, asking the user to fill in a form that then sends an email with a suitable
reply-to:
header.Also need to consider whether we change the visibility or behaviour of this feature for public (non-logged-in) users, versus logged-in member users.
The text was updated successfully, but these errors were encountered: