search

Language-Mapping / language-map

Front-end codebase for Language Mapping web map
https://languagemap.nyc
MIT License
7 stars 4 forks source link

Add splash screen with disclaimer #21

Closed abettermap closed 4 years ago

abettermap commented 4 years ago

Summary

Add an initial welcome dialog/splash screen on page load that would contain, potentially among other things, a disclaimer about data precision:

I think a disclaimer when the map opens would be good about the lack of precision of the data. The lat/longs that are precise are the ones associated with social or religious institutions, and we have discussed in the past a level of concern about the data being used by immigration authorities to target places.

Ideally the dialog would include the semi-standard Do not show this again checkbox and the confirmation button to close the dialog might be "I understand" or something.

Related

rperlin-ela commented 4 years ago

Brief introduction, disclaimer, and brief credits would all be good. Another good model is http://old.musqueam.bc.ca/applications/map/index.html. Could ask people to Accept or Decline. Consider bumping up the priority on this unless we password-protect the map for now.

abettermap commented 4 years ago

Wow Accept/Decline feels pretty heavy for a languages map splash! I see the reasoning but my first thought when visiting that link is that it might scare some folks off if they have to make a legal-sounding decision straightaway.

I was hoping that after Aug 31 it would no longer be considered Draft, so does that make the accept/decline less necessary?

Not hard to code on my end, just thinking user-wise what the response might be. And speaking of not hard to code, I'd just like to fetch the splash content from WP like we're doing for About and Glossary. Think you could start cooking up a WP page for that?

rperlin-ela commented 4 years ago

Will work on a WP page ASAP. For a small but important subset of users—especially speakers of some of the endangered languages or members of relevant communities—there are some key sensitivities here, so we just want to make sure people take a beat and really hear us that we’re aware of those sensitivities, this is not the end-all-be-all, just our snapshot, beta, we’ve done our best and want feedback etc. Will try to write it so it doesn’t sound overly legal, but does make people really stop for a second.

On Aug 14, 2020, at 6:19 PM, Jason Lampel notifications@github.com wrote:

Wow Accept/Decline feels pretty heavy for a languages map splash! I see the reasoning but my first thought when visiting that link is that it might scare some folks off if they have to make a legal-sounding decision straightaway.

I was hoping that after Aug 31 it would no longer be considered Draft, so does that make the accept/decline less necessary?

Not hard to code on my end, just thinking user-wise what the response might be. And speaking of not hard to code, I'd just like to fetch the splash content from WP like we're doing for About and Glossary. Think you could start cooking up a WP page for that?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/21#issuecomment-674294820, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5CZPWHPWH2NLIEKCSDSAWZ7RANCNFSM4OGCI46A.

abettermap commented 4 years ago

Sounds good. I feel the average user won’t read anything, but your text will cover the bases for all users since they can’t see the map until they accept.

So rather than accept/decline, how about just two checkboxes and a button in dialog footer:

  1. “I accept the terms” or whatever. They have to click it in order to enable the “Proceed” button or whatever.
  2. “Do not show on startup”. I can make the browser “remember” settings like this.
  3. “Proceed” or “Go to map” button, which is disabled until the terms box is checked.

That work?

abettermap commented 4 years ago

You may still lose a few “why do I need to accept anything, this seems shady, I’m out” folks but hopefully they’re the exception.

rperlin-ela commented 4 years ago

Sounds pretty good to me — I can get started on a WP page. Because it’s the first thing everyone sees, let’s get everyone’s opinion on this.

On Aug 15, 2020, at 1:00 PM, Jason Lampel notifications@github.com wrote:

Sounds good. I feel the average user won’t read anything, but your text will cover the bases for all users since they can’t see the map until they accept.

So rather than accept/decline, how about just two checkboxes and a button in dialog footer:

“I accept the terms” or whatever. They have to click it in order to enable the “Proceed” button or whatever. “Do not show on startup”. I can make the browser “remember” settings like this. “Proceed” or “Go to map” button, which is disabled until the terms box is checked. That work?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/21#issuecomment-674423330, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5GWJWNQ2QKGTXHMDEDSA25KRANCNFSM4OGCI46A.

rperlin-ela commented 4 years ago

Probably a lot to tweak, but I've made a start here: https://languagemapping.org/disclaimer/

abettermap commented 4 years ago

@rperlin-ela sorry just now getting to this. The text is well-written as usual, just a few comments/suggestions:

Remove the "print map" link

Even though it's something relevant and related, it might be better not to encourage users to leave the page, especially right off the bat. It is an important link though, so I would say add it to the About page if it's not already in there.

If you do remove the link then change "the print map" to "a printed map". Personally I'd just drop every after the comma though (so end the first sentence at "areas"). ELA still gets the shout in the last paragraph, and the print map can be linked in About.

Nitpick

I think my only strong feelings are about the print map link and the indigenous capitalization. Maybe @markturin and @fiddleHeads will have more insight.

Also let me know if my wording for "By continuing I acknowledge that I have read and accept the above information" is ok ("accepted" not "accept" maybe?). I went back and forth on some variations, but I think the text-not-checkbox is a good approach that's proportionate to Ross's wording. No intimidating terms agreement checkbox seems to work here.

rperlin-ela commented 4 years ago

Thanks for these, very useful, implemented most. Capitalizing “Indigenous” is becoming common practice—@markturin can comment more.

On Aug 29, 2020, at 2:05 PM, Jason Lampel notifications@github.com wrote:

@rperlin-ela https://github.com/rperlin-ela sorry just now getting to this. The text is well-written as usual, just a few comments/suggestions:

Remove the "print map" link

Even though it's something relevant and related, it might be better not to encourage users to leave the page, especially right off the bat. It is an important link though, so I would say add it to the About page if it's not already in there.

If you do remove the link then change "the print map" to "a printed map". Personally I'd just drop every after the comma though (so end the first sentence at "areas"). ELA still gets the shout in the last paragraph, and the print map can be linked in About.

Nitpick

"lat/long coordinates" to "locations" or just "coordinates" no italics on deliberately just a partial snapshot to just a partial snapshot with only those two words italicized or, better yet "this map represents a partial snapshot" "usually" to "often" indigenous does not need capital Final sentence of paragraph 3: "As languages are always changing, this map is a work in progress so please send us corrections, comments, and other feedback." I think my only strong feelings are about the print map link and the indigenous capitalization. Maybe @markturin https://github.com/markturin and @fiddleHeads https://github.com/fiddleHeads will have more insight.

Also let me know if my wording for "By continuing I acknowledge that I have read and accept the above information" is ok ("accepted" not "accept" maybe?). I went back and forth on some variations, but I think the text-not-checkbox is a good approach that's proportionate to Ross's wording. No intimidating terms agreement checkbox seems to work here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/21#issuecomment-683323823, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5GTYOAJHMA637DA7CTSDE7PFANCNFSM4OGCI46A.

markturin commented 4 years ago

Please do capitalize Indigenous, cf.

https://www.ictinc.ca/blog/indigenous-peoples-terminology-guidelines-for-usage

https://www.sapiens.org/language/capitalize-indigenous/

https://j-source.ca/article/canadian-press-style-now-capitalizes-aboriginal-and-indigenous/

thanks

M

From: rperlin-ela notifications@github.com Reply-To: Language-Mapping/language-map reply@reply.github.com Date: Sunday, August 30, 2020 at 05:14 To: Language-Mapping/language-map language-map@noreply.github.com Cc: "Turin, Mark" mark.turin@ubc.ca, Mention mention@noreply.github.com Subject: Re: [Language-Mapping/language-map] Add splash screen with disclaimer (#21)

Thanks for these, very useful, implemented most. Capitalizing “Indigenous” is becoming common practice—@markturin can comment more.

On Aug 29, 2020, at 2:05 PM, Jason Lampel notifications@github.com wrote:

@rperlin-ela https://github.com/rperlin-ela sorry just now getting to this. The text is well-written as usual, just a few comments/suggestions:

Remove the "print map" link

Even though it's something relevant and related, it might be better not to encourage users to leave the page, especially right off the bat. It is an important link though, so I would say add it to the About page if it's not already in there.

If you do remove the link then change "the print map" to "a printed map". Personally I'd just drop every after the comma though (so end the first sentence at "areas"). ELA still gets the shout in the last paragraph, and the print map can be linked in About.

Nitpick

"lat/long coordinates" to "locations" or just "coordinates" no italics on deliberately just a partial snapshot to just a partial snapshot with only those two words italicized or, better yet "this map represents a partial snapshot" "usually" to "often" indigenous does not need capital Final sentence of paragraph 3: "As languages are always changing, this map is a work in progress so please send us corrections, comments, and other feedback." I think my only strong feelings are about the print map link and the indigenous capitalization. Maybe @markturin https://github.com/markturin and @fiddleHeads https://github.com/fiddleHeads will have more insight.

Also let me know if my wording for "By continuing I acknowledge that I have read and accept the above information" is ok ("accepted" not "accept" maybe?). I went back and forth on some variations, but I think the text-not-checkbox is a good approach that's proportionate to Ross's wording. No intimidating terms agreement checkbox seems to work here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/21#issuecomment-683323823, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5GTYOAJHMA637DA7CTSDE7PFANCNFSM4OGCI46A.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Language-Mapping/language-map/issues/21#issuecomment-683413243, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKCODWDA3PTTNMQSTCOCL2LSDI7CPANCNFSM4OGCI46A.