Alert not matching to occurrences - Sus scrofa

[turley85]

I've just loaded this alert: BioSecurity alert for VIC_DELWP_FeralPigs_list

But it doesn't seem to be detecting the latest sections of feral pigs: https://biocache.ala.org.au/occurrences/search?q=lsid:https://biodiversity.org.au/afd/taxa/948d8ca1-62fc-4d03-a79d-4be2de837264#tab_recordsView

There's nothing I can see that would be preventing it matching to these occurrences.

Any ideas?

[adam-collins]

You can test queries using biocache.

• For the linked list, the fq column appears to be working in biocache.
• The provided name to the linked is Sus Scrofa. This does not appear to be working in biocache when searching with one of the fields that are expected to work, e.g. https://biocache.ala.org.au/occurrences/search?q=scientificName:%22Sus%20Scrofa%22
• The linked list has a matched scientific name that differs from the supplied name, Sus scrofa, this is returning results in biocache for a field that is expected to work for this search https://biocache.ala.org.au/occurrences/search?q=scientificName:%22Sus%20scrofa%22. The number of results returned also matches the lsid biocache search filter results.

Add to the documentation this information

• When checking the list supplied name and the matched name, also check for case changes.
• When debugging a faulty match, construct a biocache search term that is expected to match. See the existing documentation for the list of fields used in name matching.

[turley85]

Ok, list has been corrected for Sus scrofa and appears to be working now. This raises another issue though. Names matching in lists will successfully match Sus Scrofa, but alerts won't. The issue here is that there is no "flag" of an issue in the list/names matching tools to know this needs to be corrected.

[adam-collins]

I do not know where the miscommunication took place. I thought this was sufficiently detailed in confluence. Please update the documentation with the following information.

After uploading a list, all differences between the uploaded name and the matched name must be inspected and resolved.
Resolution will be undertaken with the understanding of what is expected to be matched, how this information is available though the lists application, how biocache queries are constructed, including all relevant name fields, and name matching behaviour during occurrence data ingestion.
This is required because:

• the search includes usage of occurrence processed fields that have ALA's name matching output.
• the search uses the list's uploaded scientificName and synonyms, without matching.