BiologicalRecordsCentre / iRecord

Repository to store and track enhancements, issues and tasks regarding the iRecord website.
http://irecord.org.uk
2 stars 1 forks source link

Records not available via the ES verification page #1273

Open kitenetter opened 2 years ago

kitenetter commented 2 years ago

A verifier points out that he can see records on the 'old' verification page that are not visible in the current ES verification page. He also points out that we no longer have the verification buttons available on the old verification page.

It would be good to switch off the old page, but I am reluctant to do that if we are not confident that records are available on the ES one.

Example 1 Occurrence ID; 12484290 Can be seen on the old verification page but not the new one Can be seen on the ES Explore page, and the record details are visible However, having gone to the record details page, if you then click on the button for "Eplore records ..." button, the resulting Explore page is empty If you click on the species details page the resulting page does show map dots and photos

Example 2 Same as example 1, for occurrence ID 23715311

Examples 1 and 2 both link to taxon "Chromatomyia horticola/syngenesiae agg." (taxa_taxon_list_id = 538741) but I can't see anything unusual in the taxon entry.

Example 3 is for "Phytomyza ranunculella" (taxa_taxon_list_id = 538751).

Example 3 Occurrence ID; 23925470 Can be seen on the old verification page but not the new one Can be seen on the ES Explore page, and the record details are visible However, having gone to the record details page, if you then click on the button for "Eplore records ..." button, the resulting Explore page is empty If you click on the species details page the resulting page does show map dots and photos

johnvanbreda commented 2 years ago

These records were in Elasticsearch, but for any taxa added manually to the warehouse, the taxon hierarchy filtering won't work in Elasticsearch unless I update the lookup tables that Logstash uses to populate the index. I've updated the lookups and triggered a refresh of records for recently added taxa.

This is an area that will need some work at some point - completion of automation of the pull from UKSI (which just needs testing) then automating the update of Elasticsearch's lookups.

kitenetter commented 3 months ago

@johnvanbreda has "automating the update of Elasticsearch's lookups" been achieved now? If so we can close this.

johnvanbreda commented 3 months ago

No, though @burkmarr has made a PHP script that can update the lookups and which could be automated.