Hi Carolina,
Can you please confirm how you are attempting to import these digital objects? For example:
- If via the user interface, are you using the single "Link digital object" option or the multiple "Upload digital objects" option? Are you linking via file upload, or via URL?
- If via CSV (i.e. using an archival description CSV import to create new descriptions and link them to new digital objects via the digital object columns in the the CSV_, or are you performing the import via the user interface or the command-line? Are you using the digitalObjectPath column or the digitalObjectURI column, or a mix of the two? Are any local digital objects located in a directory that AtoM can access (e.g. somewhere in the AtoM root installation directory)?
- If you are using the Digital object load task to import from the command-line, do the target descriptions already exist in AtoM? What CSV column are you using to identify the target descriptions (the task supports information_object_id, slug, or identifier as options)?
In any case where you are using URIs to create the links, have you confirmed that these URIs meet AtoM's expectations for linking remote digital objects? Namely:
- They are available publicly online on the web - no firewalls, password protections, VPN requirements, etc.
- They use either HTTP or HTTPS: no FTP links, local share drives, etc.
- They end in a file extension (e.g. .jpg, .pdf, .mp4, etc). Links to landing pages (like a YouTube link, which does not lead directly to the video file but to a player on a webpage) will not work since AtoM cannot directly grab the digital object
If you're trying to do this via an import, have you tried manually linking a digital object to a description via the user interface to confirm that digital object linking is working as expected?
Is there anything relevant in the webserver error logs? See:
Alternatively, if your attempt uses the job scheduler, is there anything in the related job details page about the import attempt? Or in the atom-worker logs? Try:
- sudo journalctl -f -u atom-worker
Do you have any sample files that I might look at and possibly use to recreate the issue locally?
Any additional information you can provide that you think will help us better understand and reproduce what's happening will also help us offer you better troubleshooting suggestions. For example, does your 2.6.4 installation differ from our recommended installation instructions in any way? Do you have any local customizations (i.e. code changes) or custom theme plugins present? Etc. Thanks in advance!
Cheers,