Hi, @ACWadmin1 !
- I hope this will still pick up the submitter if the assigned to isn’t populated with a different user ID but we would still like to have the option to select the submitter ID as a search filter option. “Assigned to” isn’t a field we use currently so the current list, particularly in the Sighting search is counter-productive,
This is still using submitterID (i.e., “Assigned to” is the new “submitterID”. I’m not sure why the wording changed, but knowing Tanya, it was deliberate and well-justified):
- The current “assigned to” dropdown options now populates with a whole lot of ‘anonymous’ user IDs - I don’t understand where these are coming from and this dropdown really should only reflect actual user accounts not what I assume are system-generated “anonymous” IDs.
These accounts are actually the result of the user reconciliation effort; essentially, these are user accounts that did not have usernames (so, the accounts were likely generated when someone submitted a photo without logging in) and were not claimed during the 90-day “hey, consolidate your users” window. We need each user to have a unique username and a unique password before the codex migration, so this step simply assigned, “Anonymous_userID” as the username to any user account that had NO username in the first place.
If you’re curious, as an admin, I believe that you could find out whether any of these “Anonymous_userID” accounts are associated with particular email addresses in the “User Management” tab by simply searching for “Anonymous”. If you see any email addresses that you recognize, you could encourage those people to log in to their main account and claim that “Anonymous_userID” account by following these instructions. There’s still time for that for sure!
I don’t think either of these issues are bugs as much as changes with the update. Do you think this one’s ready to be marked as resolved?
Thanks,
Mark