Bug #4162
MemoryBC: Server 500 error on importing EAD XML file
| Status: | Duplicate | Start date: | ||
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Jesús García Crespo | % Done: | 0% | |
| Category: | - | |||
| Target version: | Release 1.4.0 | |||
| Google Code Legacy ID: | atom-2214 | Tested version: | ||
| Sponsored: | No | Requires documentation: |
Description
Google user: CameraWo...@gmail.com
To reproduce this error:
========================
1) In MemoryBC, import the attached EAD XML file from the Whistler Museum & Archives
2) The file will load and then MemoryBC will eventually return a Server 500 error
3) BCANS Coordinator attempted to import three times over two days
Resulting error: ================
Server 500 error
Expected result: ================
File should import as it was exported from an ICA-AtoM installation at the Whistler Museum & Archives. The XML file, however, is supposed to have links to digital objects.
[g] Legacy categories: EAD
Related issues
History
#1 Updated by Jessica Bushey almost 10 years ago
- Priority set to Medium
- Target version set to Release 2.1.0
[g] Labels added: Priority-Medium, Milestone-Release-2.0, Component-EAD
[g] New owner: Jessica Bushey
#2 Updated by Jesús García Crespo almost 10 years ago
[g] New owner: Jesús García Crespo
#3 Updated by Jessica Bushey over 9 years ago
I just tested this EAD.XML file and I was able to successfully import it into ICA-AtoM 1.3. Elapsed time to import around 90 seconds.
In looking at the EAD.XML file I can't see any elements for digital objects, e.g. <dao>. The lowest level of description represented is "File".
#4 Updated by Jesús García Crespo over 9 years ago
- Status changed from New to Duplicate
- Sponsored set to No
#5 Updated by David Juhasz about 9 years ago
- Target version changed from Release 2.1.0 to Release 1.4.0