search

gbif-norway / helpdesk

Please submit your helpdesk request here (or send an email to helpdesk@gbif.no). We will also use this repo for documentation of node helpdesk cases.
GNU General Public License v3.0
3 stars 0 forks source link

Image hosting solution for GBIF Norway #100

Closed rukayaj closed 1 year ago

rukayaj commented 2 years ago

Think about thumbnails/resizing, API access to images, persistent identifiers, ...?

Possible solutions:

Anyone else have any ideas for it?

dagendresen commented 2 years ago

If I understand right -- "Don't use your account to host web graphics or as a replacement for a content distribution network." -- "generic graphic elements of web page designs, logos, banners, icons, and other non-photographic elements" -- is NOT what we would do anyway. We would want to archive actual photos, not graphics to make a website look nice...???

dagendresen commented 2 years ago

I recall that Meise Botanical Garden was using Zenodo to archive photos Example (?) https://zenodo.org/record/2864809#.YkxFejdBzzc

rukayaj commented 2 years ago

If I understand right -- "Don't use your account to host web graphics or as a replacement for a content distribution network." -- "generic graphic elements of web page designs, logos, banners, icons, and other non-photographic elements" -- is NOT what we would do anyway. We would want to archive actual photos, not graphics to make a website look nice...???

I think that the GBIF caching mechanism (for the images to appear on GBIF) might count as us hosting the images, even though it's GBIF cached...? I am not sure, but anyway if we end up hosting the images on the hosted portal or something similar then it will count as 'hosted' I guess?

dagendresen commented 2 years ago

OpenUp! --> Europeana Norvegiana --> Europeana

rukayaj commented 2 years ago

I think this is actually part of the same problem as the data backups/hosting #83. We should store images on a server or in a cloud service bucket which is backed up and secure, and use a cdn e.g. https://imagekit.io/ or https://imageengine.io/ for image resizing and delivery.

I just trialed imageengine and it seemed to work ok, it creates a custom imageengine domain for your images and you can add resize/crop/etc via the URL so it does it on the fly. I think it's also supposed to do some device detection/image adjustment but perhaps you have to use their react or vue plugins for that.

We could possibly point our persistent identifiers at the new CDN domain, which would then (if it is not already cached there) retrieve the image from our servers. But perhaps we don't actually even need to do that.

We don't need to worry about the CDN bit (i.e. image resizing and thumbnails) until we have our own website which needs it, as GBIF are doing all of this stuff for images stored there already.

One thing that springs to mind - do we trust USIT to host all the MUSIT specimen images, or is this something we'd want backups of as well?

dagendresen commented 2 years ago

We could possibly point our persistent identifiers at the new CDN domain

Do we have persistent identifiers declared for the images? I hope the materialSampleID persistent identifiers would not be redirected to the image files (or image file metadata) :-D

do we trust USIT to host all the MUSIT specimen images

I guess this is completely up to the museums - if THEY trust MUSIT to host the images. Not our responsibility?

rukayaj commented 2 years ago

Do we have persistent identifiers declared for the images? I hope the materialSampleID persistent identifiers would not be redirected to the image files (or image file metadata) :-D

We have purl urls for some of our images in this format: https://purl.archive.org/gbifnorway/img/[imageUUID].jpg. We don't have them for all images yet.

I guess this is completely up to the museums - if THEY trust MUSIT to host the images. Not our responsibility?

Hmm... I suppose so, but I'm not sure about this, it's not really our responsibility to e.g. back up Ukrainian IPTs either, but we think it's worthwhile so we do it. But on the other hand the IPT backups aren't very big, and the MUSIT specimen images are. Hmm...

dagendresen commented 2 years ago

We might want to explore the new Sigma2 Research Data Archive -- to explore if it might also have research image hosting facilitation...?

rukayaj commented 1 year ago

https://github.com/gbif-norway/documentation/wiki/Image-hosting I think we kind of have something working for this now, described here in the wiki page.