"1 to 1" and "1 to many" communication

[yumiendo]

Below are the comps that accommodate our new feature - 'contact the contributor'(1 to 1) and 'group message'(1 to many)

Changes on dataset page: (screenshot below, pink underline)

Im cleaning up the actions available on dataset page:

Follow this dataset (visible for all logged in users) Contact the contributor (same) Group Message (org members only for both private + public data. eg. on Global Food Prices Database (WFP) dataset page, Group Message is only visible to WFP members) Edit (admin/editor only) Delete (admin only) social share icons (visible to everyone including non-registered users) (icons assets are here: https://drive.google.com/open?id=0BzNYvYpDh-dabGJ0Rk5lMGI5R1k)

contact the contributor modal(available to all logged in users)

contents: - [Dataset] 'name of dataset' group message modal contents:

• [Dataset] 'name of dataset' <- not editable (perhaps truncate after 2 lines...)
• "Select Recipient group(s)" dropdown options: Users from your organisation
• All members (members, editors, admins) [ x ]
• All editors [ x ]
• All admins [ x ] (" x " should show number of users)

After submitting "contact the contributor" or 'group message" confirmation screen appears

[yumiendo]

things to consider: Not sure if we discussed this a year ago - have we decided if we'd cc all messages to HDX?(if so, we'd need to include a disclaimer) it seems a little creepy that HDX is monitoring people's conversations. But if the inquiry is either 'report a problem' or 'suggest edits' (things that affects HDX as a service)- we might want to CC [email protected]. Any opinions/better ideas? @cjhendrix @JavierTeran @takavarasha @ochadataproject ?

Also, @takavarasha was asking if we'd be able to save + archive the messages for future reference/use. I thought it'd be good idea if one day we have our messaging server/system within HDX but wasn't sure if its a big effort for dev.

[cjhendrix]

Hi Yumi,

When we discussed this a while back, we did decide to copy hdx.feedback when a user contacts a maintainer. We didn't think through it in too much detail, but in general we wanted to know if users were reporting problems with datasets. I think a disclaimer on the form makes sense.

--cj

From: yumiendo [email protected] To: OCHA-DAP/hdx-ckan [email protected] Cc: cjhendrix [email protected], Mention [email protected] Date: 24/06/2016 21:09 Subject: Re: [OCHA-DAP/hdx-ckan] "1 to 1" and "1 to many" communication (#4260)

things to consider: Not sure if we discussed this a year ago - have we decided if we'd cc all messages to HDX?(if so, we'd need to include a disclaimer) it seems a little creepy that HDX is monitoring people's conversations. But if the inquiry is either 'report a problem' or 'suggest edits' (things that affects HDX as a service)- we might want to CC [email protected]. Any opinions/better ideas? @cjhendrix @JavierTeran @takavarasha @ochadataproject ? Also, @takavarasha was asking if we'd be able to save + archive the messages for future reference/use. I thought it'd be good idea if one day we have our messaging server/system within HDX but wasn't sure if its a big effort for dev. ? You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[danmihaila]

@yumiendo

• disclaimer
• template for email

[yumiendo]

@danmihaila disclaimer copy: Your message may be monitored by the HDX team for internal use: such as improving your user experience, the overall quality of our services and introducing service enhancements for the future.

where to put: (same for group message)

[yumiendo]

both emails are pending data team's approval/edits -

email template for contact the contributor: https://docs.google.com/document/d/18ezdFET74It72Dgpz9k_YGxOjPKXtTab5fYsgZ919RE/edit?usp=sharing

email template for group message: https://docs.google.com/document/d/1b6NPYWdIQCOIGbYt4LM4-dd2q-GgdYeeYISpSxQkryI/edit?usp=sharing

[ochadataproject]

Thanks with edits

disclaimer copy: Your message may be monitored by the HDX team for internal use such as improving your user experience and the overall quality of our services.

On Wednesday, July 6, 2016, yumiendo [email protected] wrote:

disclaimer copy: Your message may be monitored by the HDX team for internal use: such as improving your user experience, the overall quality of our services and introducing service enhancements for the future.

where to put: (same for group message) [image: screen shot 2016-07-06 at 9 35 50 am] https://cloud.githubusercontent.com/assets/8006323/16619652/044102c6-435d-11e6-91a0-ddfe9a63df92.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OCHA-DAP/hdx-ckan/issues/4260#issuecomment-230772830, or mute the thread https://github.com/notifications/unsubscribe/AE2qoSMqa9iI59MlbtzETkDMvP6pl1laks5qS69IgaJpZM4I-CfV .