Bug Report - media links not showing up on GBIF for UTEP:Herb #8430
Labels
Bug
Arctos is not performing as it should.
Extended Specimen
Issues which are critical to participating in the Extended Specimen Network.
Priority-High (Needed for work)
High because this is causing a delay in important collection work..
Milestone
Describe the bug
images not showing up in GBIF even though they are not on Arctos for our herbarium images. There are supposed to be about 48K but there's only 22k on gbif.
To Reproduce
Steps to reproduce the behavior:
On GBIF
on Arctos:
Screenshots
If applicable, add screenshots to help explain your problem.
Data
If this involves external data, attach the actual data that caused the problem. Do not attach a transformation or subset. You may ZIP most formats to attach, or request a Box email address for very large files.
Desktop (please complete the following information):
windows, chrome
Additional context
Sorry i lost track of this Dusty
Checked with David, but he said:
Hey Vicky,
I've had a look on my side of this process and what I see is that GBIF has 26,897 "records with images". When I download the DwC-A from GBIF, there are 27,950 images listed, which means there are about 1000 records that have two images, or perhaps fewer records with 2 or more images associated with them.
I cannot account for the difference of 22,000 images that you have reported. The IPT and the publishing protocols all appear to be working just fine. My next thought would be to have Dusty check to see how many images from UTEP Herb are in the arctosmedia table, which is where I link the IPT (or maybe you can see that table?). Whatever is in there is what goes to GBIF, but I do not have access to view the tables. If you are 22k images short in that table, then I would think there is something on the dbase side of things that is not pulling all of your images. All I know is that on my end, I'm pulling everything that has been made discoverable and publishing to GBIF and beyond.
Sorry that is not much help.
best
dav
The text was updated successfully, but these errors were encountered: