sponsoring from museum display page (including if it's not sponsorable for any reason) about oztree HOT 10 OPEN

We want people to be able to click sponsor on the museum display, but we shouldn't solicit payment info etc on the museum screen. So the museum display sponsor page needs to have something with an explanation and e.g. a QR code, a textual link (i.e. not actually hyperlinks, but something you can take a picture of), and possibly a box to enter your e-mail, so that you can be sent a sponsorship link.

from oztree.

After some discussion around this - we now think that to request e-mails from the user may be complex from a privacy policy perspective - as gmail (the default mail service we use at OneZoom) automatically stores all mail sent via smtp, so we would end up storing any entered email addresses. Also, where the code is being locally hosted by museums, they would need either to set up their own smtp server (and the return address would probably be faked => treated as spam) or use ours, in which case they would need our password[1].

Therefore the key information on this page should be
QR code
onezoom.org
'Creature code' (for use to enter into the website later)
some pretty images of the tree and of the leaf
the onezoom logo and charity number
'take a picture of this screen to help you remember, (or send it to me by e-mail option possibly to be added much later but not part of the job for now'

[1] we could give museums a single-use password via 2 step authentication, but we still have the problem that there is no way to stop emails sent via gmail smtp being saved in our sent mail. Even filtering these into trash on the gmail servers does not instantly delete them.

from oztree.

We also want to have a nice-looking page (e.g. on the museum display or even online) when a species has already been sponsored, or is banned. This all requires editing the sponsor_leaf view. It is recorded as an issue in https://github.com/jrosindell/OneZoomComplete/issues/189 and that item can be closed when this is done

from oztree.

We've agreed that the following six separate pages should be made to handle these cases....

1. Available
   a. On MD (with or without partner)
   b. Online (with or without partner)
2. Not available
   a. It’s been sponsored (this should feel a bit like a species page and should big up the sponsor as well as include e.g. popularity of the species).
   b. It can’t be sponsored for some reason (e.g. no OTT or banned or expensive) contact us to sponsor
   c. It’s been reserved
   d. It’s been sponsored and awaiting admin check.

from oztree.

We discussed this briefly and had some partial solutions exposed at #148

from oztree.

Probably the QR code is not considered part of the essential needs here.

Also the 'creature code' will bet the OTTID in practice. We'll need to edit http://onezoom.org/sponsor and update that page in order for the online experience to make that part easier

We won't need a partner version of the pages for September this can be saved for later - however it is important that the pages look very appealing.

There is a page at the moment that basically works so the starting point will be to add a nice leaf to this and also take care of the 'creature code' part

from oztree.

I'm tentatively assigning Yan to this as he's done lots of the recent work on the sponsorship pages

from oztree.

Thinking still of getting something minimal working.... I've basically updated the three main pages

spl_elsewhere.html
spl_elsewhere_not.html
spl_sponosred.html

I think they look reasonsable now.

Still to do...

• Fix controller so that calling of the page with sponsorship not allowed does not reserve the species
• Add mock up leaf for the case where sponsorship is available
• Make the example leaf on spl_elsewhere_not.html be automated so that it's not always the same.
• update the sponsorship page on the main site so that 'creature codes' (OTTIDs) can be entered.

from oztree.

Creature code fixed with #296

from oztree.

I think this can now be closed, is that right @jrosindell ?

from oztree.