Seal Wildbook: Can I filter all Saimaa ringed seal individuals that have a "name"?

What Wildbook are you working in?
Seal Wildbook

In Saimaa ringed seals, our identified individuals all have a Phs-code but only some have a name. I noticed that with most individuals that have a name, it is located in the individual page metadata, in a box named “AdoptionName” instead of “Nickname” that would show in individual search result table.

Can I somehow find all named seals that have the name in AdoptionName box? If I can’t, can you provide me a list of all those individuals (Phs-codes)? If I copy the name from “AdoptionName” to the “Nickname” box, it will be visible in the individual search in the future. Or could that be done in your end? Either move the name from AdoptionName to Nickname or copy the name, so it shows on both.

I can find the named seals from database that have additional ID, like a flipper tag code. But that is not all seals with a given name.

For reference, Phs106 or “Pullervo” individual page, where the name is in both boxes: Seals Wildbook

Furthermore: It seems that the “AdoptionName” box is not there in the individual page by default. It might be that only seals that were named before moving to Seal Wildbook have this field. Phs177 was named in Seal Wildbook and has only “Nickname” box with the name “Inkeri”.

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report

These are all good questions. Though I suspect that the answer to searching for only individuals that have an AdoptionName field might be something we can do on our side, but isn’t user-facing. From my testing, an individual search by name will search for that name in all available name fields (marked individual ID, nickname, adoption name, etc.).

I’ll need more time to research and I’ll get back to you with an update.

@jason for visibility

Thanks for your patience!

There currently isn’t a way to search only for individuals that have an AdoptionName value in their metadata. It does appear to be a carryover from getting Norppagalleria into Codex since Codex didn’t support adoptions.

I believe I was able to get you what you needed by doing an encounter search with the following filters:

  • Observation atrribute filters
    Genus and species: Pusa hispida saimenses
  • Identity filters
    Individual name contains “phs”

I did a Standard export and then added the filter option in Excel (Data > Filter) and set it to display only encounters with “AdoptionName” as a value in the Name2.label field. Then when you go over to Name0.value, you can open the list of Phs IDs to see which of your seals are in this list.

I’ll email you this export shortly.

Right now, an individual search by name will search for the keyword across all name-related fields (default, nickname, other value, adoption name, etc.). You can add the adoption name as a nickname to for any of the individuals in the list if it will help with standardizing your marked individual pages.

  1. Hi, Thank you for the export excel. Part of the seals that have “AdoptionName”, are there as expected, but some are still missing. Like Norbert Phs116 or Flinkenberg Phs336. I checked that they have their name actually in the AdoptionName field and they did. Why they are not showing in the export list?

  2. Also there is a difference with Pullervo Phs106 and Ritva Phs052 with the fields Name1.lable (Alternate ID/Nickname) and Name1.value. (Pullervo/RI-98)
    (I already manually copy/pasted Pullervo’s AdoptionName to Nickname field.)

Phs106 Nickname Pullervo AdoptionName Pullervo
Phs052 Alternate ID RI-98 AdoptionName Ritva

So, is adding the AdoptionName to Nickname field causing an issue here?

Good question. I’ll need to work with the devs to find out why some individuals have been excluded from the results.

I’ll have to wait to discuss this with the devs as well, but it does look like Name1 will display the metadata for whichever field happens to be present (alternate ID or nickname) and it shouldn’t interfere with AdoptionName because that data lives in the Name2 fields.

I’m going to send you an updated file!