To import digital objects via an archival description CSV import, you will need to either have access to the server that AtoM is installed on (for local file path upload), or your images will need to be publicly available on the web (for URL uploads). I will provide the relevant documentation links below, but also try to add a few clarifying tips to see if it helps resolve the issue you are facing. First, see:
Local digital objects - using the digitalObjectPath column
For this option to work, the digital objects must be on the same server that AtoM is installed on - NOT your local computer. It also needs to be in a directory that AtoM's www-data user can access - so generally, we recommend placing a temporary directory right in the root AtoM installation directory, which is typically located at /usr/share/nginx/atom if you follow our recommended installation instructions.
There is already a subdirectory called images that AtoM uses, so in the example below, we will call the directory of our digital objects import-objects. First, copy that directory and its objects to AtoM's root directory - so it should be at /usr/share/nginx/atom/import-objects.
Now, let's say you want to attack 0001.jpg to the first metadata row in your CSV. In that row, in the digitalObjectPath column, you should be able to add /usr/share/nginx/atom/import-objects/0001.jpg as the value. Repeat as needed for each row. Remember that AtoM has a 1:1 relationship between a digital object and a description, so do not try to add more than one digital object to the same description row in your CSV.
If this still doesn't work, one other quick thing you can try while you have command-line server access is to confirm that the filesystem permissions are properly set. Run the following to confirm:
- sudo chown -R www-data:www-data /usr/share/nginx/atom
Remote digital objects- using the digitalObjectURI column
For this option to work, there are 3 conditions that must be met for the URIs you use:
- The target object MUST be available on the public web - no password prompts, VPN requirements, firewalls, etc. Anyone with an internet connection should be able to enter the URL you intend to use and see the digital object.
- The target object MUST use either HTTP or HTTPS - FTP or SFTP links, or local share drives, etc. will not work.
- The URL MUST end in the file extension of the digital object (e.g. .jpg, .pdf, etc). You cannot link to a landing page (for example, a YouTube link) that has a digital object on it somewhere, because AtoM will not know how to find it. This is usually the same link you would get by finding an image on a web page, and then right-clicking on it and selecting "Open Image in New Tab."
If you meet all these conditions, then you should just be able to add the related full URL to the digitalObjectURI column for each row in your CSV.
Hopefully this helps!