Thanks for your patience! I’ve verified this is intentional as it was part of the broader security updates made to Wildbooks.
Do you want us to roll this back for SeadragonSearch? I know some degree of visibility is desirable when an active citizen science program is involved, so let us know if you find these changes prohibitive to that effort.
Hi @Anastasia, thanks for checking into that! In terms of the automated updates sent to participants when ‘their’ animal has been resighted, we would like to restore visibility to that data. Would it be possible to get an overview on what other aspects were restricted at the same time so we can check if they should remain as they are too? Maybe that was the only function that tightened up privacy? thank you!
Let me work with my teammates on this for you and I’ll follow up here.
hi @Anastasia, just checking in to see what you have found. People are keen to get this functionality restored. thanks!
Hey @NeridaWilson thanks for your your patience.
In your screenshot, this encounter is assigned to you: https://wildbook.seadragonsearch.org/encounters/encounter.jsp?number=034d8af2-48bf-4241-bc35-1e226388f44e
It’s correct for that information to be obscured because this isn’t a public Encounter.
However, we looked at a recent public encounter and saw that one was equally restricted. In attempting to tighten up security, we’ve introduced a bug that made public data a little too secure. I’m going to write up a ticket for this and post the link here when it’s ready.
Here’s the ticket link: Public Encounter data is too restricted · Issue #416 · WildMeOrg/Wildbook · GitHub
Thanks @Anastasia . just checking though- the location data should be restricted if its ‘just’ anyone public exploring/not logged in. but if its via an update on an encounter the person being notified should be able to see location. That was my understanding anyway!
Just to clarify, if someone was logged out and viewing a public encounter, they would have seen the same information whether they accessed it from a link in their email or found it while exploring the site. Wildbook has always checked whether a user is logged in or not and then determines what information to display based on that status.
ahh ok, no worries. then we need to hide * Location description
@Anastasia, just wondering if this has progressed any further? The troops are still very antsy about not being able to engage. thanks!
No, not yet. Since there’s a ticket for this, any progress updates will appear in the link I shared upthread. We have an increase in open source contributors, so tickets like these are more likely to get resolved faster than they have in the past when it was just Wild Me staff working on the backlog.
hi @Anastasia, I’m a bit confused about the resolution of this one. It appears that the additional ticket that was created has been resolved. However, when I’m logged out I still cant see any of these expected behaviours outlined in your ticket. I’d also clarify that these are not the expected behaviours that we had…but that might be another story. I just wanted to update that this is not resolved for us. Thanks
Expected behavior
When viewing an encounter submitted by username “public” (/encounters/encounter.jsp), the following metadata is visible to any viewer, even when not signed in:
Great question! Tickets can be resolved, but not yet deployed. We bundle up resolved tickets and include them in the latest Wildbook versions. Once the Wildbook version that includes the bug fix is live, then it gets updated from “not deployed” to “done”. This one has a fix in place, but it’s not yet live. When it is live, I make sure to update the Community thread cited in the ticket to officially resolve the support request.
Ahhh, that makes sense! Sorry for jumping the gun!!! Too keen 
Hey @Anastasia, I think this fix has been deployed but we still have the issue in SeadragonSearch. Can you pls clarify if this should be sorted for us? I had a user update me yesterday that they still cant see photographer or submitter names fro previous sightings, thank you!
This is actually going live this morning. Keep an eye out on the forum for the upcoming post where I summarize all the changes that come with this Wildbook release. 
Quick update: the new release may not be ready until Monday.
Thank you! I’ll keep an eye out!
We’re still in the process of updating everyone to Wildbook 10.3.0. You can check this post to see how to tell if you’re on the latest version: A Note About the Wildbook 10.3.0 Update