AtoM is apparently linking broken URLs for digital objects in EAD
|Assignee:||Sarah Romkey||% Done:|
|Target version:||Release 2.1.1|
|Google Code Legacy ID:||Tested version:||2.1|
Go here: http://qa-21x.test.artefactual.com/sudbury-sun-vol-1-no-4
You'll notice that the actual URL for the image isn't there, just the upload/ path and on, e.g.:
<dao linktype="simple" href="uploads/r/city-of-greater-sudbury-archives/8/1/81033/006-3-1-4.pdf" role="master" actuate="onRequest" show="embed"/>
When trying to import this file back into AtoM, it crashes with a 500 error, so I'm setting this ticket high. I've attached an example file that will crash AtoM that was exported from the URL mentioned above.
#3 Updated by Mike Gale about 6 years ago
- Status changed from New to QA/Review
- Assignee changed from Mike Gale to Sarah Romkey
- Priority changed from High to Medium
I believe the reason it worked for you was because you were linking to an external digital object on a non-AtoM site, whereas I was testing just exporting EAD with regular on-site, uploaded digital objects.
At any rate, I think I fixed it so hopefully we can get this into 2.1.1 :)