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

Improve flashed message when source successfully submits a document or message #1525

Closed
redshiftzero opened this issue Jan 18, 2017 · 9 comments
Labels

Comments

@redshiftzero
Copy link
Contributor

This is a UX suggestion by @ninavizz to improve the notification displayed to sources upon submission of a document or message (click on image below to see her suggestion for this issue in greater detail):

screen shot 2017-01-17 at 5 08 23 pm

@ninavizz
Copy link
Member

ninavizz commented Jan 19, 2017

Thanks for posting, @redshiftzero! I'm not a developer, so for whomever chooses to code this—my notes, below. Thank you! :)

Implementation notes:

  1. Mentioning the media organization's name (for my wires, I use "The Daily Bugle"). It's important to remind users who they submitted info to. Remember: many are doing something that will put their livelihoods on the line if they're caught, so that anxiety can impact retention of basic info. Is this possible to somehow dynamically populate w/ the installed org's name?

  2. A link to remind users of their codename. Ideally upon clicking that link, the hyperlink would reveal a new

    below the message text, describing where on the screen they can find it. Something simple and friendly, such as: "Click on the thumbprint above," or "Scroll down and you'll find it mid-screen. Remember, write it down somewhere safe!" The prior suggestion of course, dependent on that separate functionality being added.

Ok!
#079A54 Title: Success!
#555555 Message: Thank you for sourcing this information to <%org-name-here%>. Please check-back later for replies. Forgot your Codename?

Icon SVG: <svg xmlns="http://www.w3.org/2000/svg" width="135" height="99" viewBox="0 0 135.3 98.8"><path d="M86.8 50c0 12.9-10.5 23.4-23.4 23.4 -12.9 0-23.4-10.5-23.4-23.4s10.5-23.4 23.4-23.4C76.4 26.6 86.8 37.1 86.8 50M79.5 43.4l-5.5-4.9L60.8 53.4l-6.6-6.8 -5.3 5.1L61 64.2 79.5 43.4z" fill="#079A54"/></svg>

@jack-mullen
Copy link

@ninavizz I don't think I can get the organisation name to insert into this flash message, as it's not currently declared by the organisation anywhere (that I could find at least!). Is there alternate text that would work here instead?

@ninavizz
Copy link
Member

@jcmcreate The alternative would be "Thank you for sharing this information with us!"

@fowlslegs @justintroutman @redshiftzero This ain't urgent, but generally speaking SD needs to be able to message users with the name of the newsroom in the messaging. Could it be prioritized to include the org name as a declaration upon installation (did I word that correctly?)?

@heartsucker
Copy link
Contributor

@jcmcreate There are steps in the ansible provisioning that allow different variables to be added to the generated config.py. This should be updated to include something where an organization_name variable can be added. Then, in the code, there is something like:

if config.org_name:
    flash('Thanks for submitting to {}!'.format(config.org_name), 'notification')
else:
    flash('Thanks for submitting to us!', 'notification')

And yes, I think it makes sense to make the split into two distinct messages to future proof it from strange grammar errors.

@b-meson
Copy link
Contributor

b-meson commented Oct 18, 2017

Another UX/ UI thing to consider is the Thanks! We received your document message never clears. So a source who wants to upload multiple documents would see their first document sent and then go to see upload their second one and still see Thanks! We received your document before the second document uploads flashnevercleared

@ninavizz
Copy link
Member

^ re: Freddy's observation... any chance this has since been fixed?

@ninavizz
Copy link
Member

ninavizz commented May 1, 2019

Nobody responded to my prior question, so I'll try another poke... anyone know if the issue Freddy brought light to in October 2017 is still an accurate reflection of a Source's multi-file upload experience, today?

This issue imho should be closed @eloquence (as the OG bit it was created for was implemented some time ago), and Freddy's comment carried-over into a new issue.

@ninavizz
Copy link
Member

Take on to close issue in #4967. Macro issue however, remains around single-file-upload as confusing user problem.

@eloquence
Copy link
Member

As noted above, this original design suggestion was implemented; closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants