Use of Google Cloud Storage for AtoM

[Miles Clemson]

Hi all - 

Our digital asset collection is stored on Google Drive Cloud storage. When trying to link an ATOM object to its digital picture file in this GDrive location, we have hit a bit of a brick wall. 

GDrive uses URLs (https://....) to define and share location, whereas ATOM only seems to accept a server file path (UNC - \\\\ServerName\\ShareName\\FolderName).

We have tried using a GDrive URL to no avail.

Has anyone worked with a similar GDrive environment in combination with ATOM and managed to make it work?

Any help really appreciated!

Southbank Centre

Belvedere Road

SE1 8XX London

southbankcentre.co.uk

southbankcentre.co.uk/support/support-us/donate 

Registered Charity No. 298909

[Mario Villar]

Maybe you should try this : https://medium.com/@ajarus/how-to-mount-a-google-drive-directory-to-a-headless-linux-ubuntu-system-in-2-minutes-92e22218eb3e

[Dan Gillean]

Hi Miles, 

AtoM can link digital objects via URL and automatically generate local derivatives (i.e. lower-resolution access copy on the related description's viewpage; thumbnail for search and browse results), but ONLY when 3 conditions are met with the provided URL: 

1. There MUST NOT be any barriers to access - no "click to continue" or captchas requiring interaction, no password prompts or firewalls. The objects must be available on the public web
2. The links provided MUST use HTTP or HTTPS - local share drive links, or FTP / SFTP links for example, will not work
3. The links MUST end in the file extension of the target object - .e.g .jpg, .pdf, etc. Otherwise AtoM cannot identify the target object.

It is this third criteria why Drive links do not typically work - Google does not provide a link directly to the object, because it generates arbitrary permalinks that remain stable even if the object is moved to another location in the user's Drive. It is similar with YouTube videos for example - to prevent unauthorized downloads, YouTube does not provide a direct link to the MP4 (or AVI, etc) video file - instead they generate a unique abstract permalink to the video player page and only allow end users to access that. 

This is mentioned in the admonition below step 5 in the documentation instructions found here: 

• https://www.accesstomemory.org/docs/latest/user-manual/import-export/upload-digital-object/#link-a-single-digital-object-to-an-archival-description

Perhaps the solution that Mario provided might offer a workaround that can generate a URL that meets the 3 criteria. 

Otherwise, you CAN add such a link anyway to AtoM and when clicked it will follow - but to properly display the target object metadata you'd need to manually edit that, and for derivatives you'd need to create and upload your own. See: 

• https://www.accesstomemory.org/docs/latest/user-manual/import-export/upload-digital-object/#edit-digital-objects

Keep in mind as well that if a system administrator ever ran the derivative regeneration command-line task, your hand-made derivatives would be lost, and would need to be manually created and reuploaded again as well!

Cheers, 

Dan Gillean, MAS, MLIS
Business & User Experience Analyst
Artefactual Systems, Inc.
604-527-2056

he / him

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/bc23a9d5-8bee-4149-a9c3-e106f281868en%40googlegroups.com.