-
Notifications
You must be signed in to change notification settings - Fork 23
Some Europeana images showing up as broken images #188
Comments
Hi,
Example query: This is because thumbnails in Europeana are created asynchronously after publication. If you look at the search result above and go to Europeana Collections you will see that some (most!?) of them now do have thumbnails. So if Creative Commons would reharvest Europeana content to CC Search using the same base search as the first harvest most of the currently missing thumbnails would appear. One can also reduce the amount of missing thumbnails somewhat by adding thumbnail=true to the Europeana API-query that forms the first step of your harvest, like so:
The full size images aren't hosted by Europeana. We hotlink them in from source (just as you do). So we can't control them. What we can do is that if you find a Europeana partners whose entire image set is basically broken let us know and we'll get in touch with them. |
@robmyers what do you think? |
Thank you for that thorough explanation @DavidHaskiya . @little-wow We can run another import / harvest. After that if we do find any broken image sets we can report them. Does that sound OK? :-) |
great, thanks! I'll let the folks from the Europeana comms team know that we're ready to announce as soon as that's done. @robmyers |
@robmyers ping! Just checking in on this ticket! Thank you so much! |
I won't be doing this until next week as I am still trying to catch up after being out sick. I'll ping you when it's done (and if it becomes any more urgent do re-ping me). |
I've started the import. I will check its progress in the morning (it will take a while....). |
👍🏽 Thanks Rob!
On Tue, Apr 11, 2017 at 9:09 PM Rob Myers ***@***.***> wrote:
I've started the import. I will check its progress in the morning (it will
take a while....).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#188 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGw-ToY6Xflvrg-pxgS8qeeCRuLCHm0lks5rvCRLgaJpZM4MuzX7>
.
--
---
Jennie Rose Halperin
Communications Manager
Creative Commons
Invest in an open future. Support Creative Commons today:
http://bit.ly/19IjSKl
|
OK I'm now very confused. :-) Here is the search from above: And here is the first image that doesn't have a thumbnail in the results for that: Which links to this results page: https://ccsearch.creativecommons.org/image/detail/JTd80iTV1J0IqJ_P43bO7g== Note how the skull looks, and that the title matches that from the search results preview. When I click on the link it goes to this page: Note that the skull is different but that the title is the same. The image on the page on Europeana does have a thumbnail available, the one in ccSearch doesn't. I'm concerned about the different images. @DavidHaskiya do you have any idea what we might be doing wrong? :-) |
I'm confused as well - as in not sure this is an issue with our API or your implementation - let's see if our joint confusion can lead to some insights! When I query our API for http://www.europeana.eu/portal/en/record/2021668/naturalis_specimen_ZMA_MAM_7523.html by searching on its dc:identifier, like so I get this thumbnail in return: which does resolve correctly in my browser. What's the URI of the offending thumbnail in your search display? I'd try to check but can't seem to get the same first hit as you do. Other example: CC-search thumbnail link which does not resolve and so gets a default thumbnail: Working 200px thumbnail called in Europeana Collections via the Europeana API: http://www.europeana.eu/api/v2/search.json?wskey=apikeyhere &query=proxy_dc_identifier:%22ZMA.MAM.7252_01216961143%22&profile=rich&rows=98 which includes this thumbnail URI Does this help in your troubleshooting? |
For example here: https://ccsearch.creativecommons.org/image/detail/TaNnY_wrKsmSMWYkFId3Yw==
or here:
(which does display after clicking on blank image: https://ccsearch.creativecommons.org/image/detail/TaNnY_wrKsmSMWYkFId3Yw==)
The text was updated successfully, but these errors were encountered: