Bug #5788

After XML import screen stays on import

Added by Jessica Bushey over 8 years ago. Updated over 8 years ago.

Status:VerifiedStart date:10/12/2013
Priority:HighDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:EAD
Target version:Release 2.0.1
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

Not sure this is the desired behaviour.

I would like to receive a message that the xml was imported successfully and be shown the archival description or authority record that I just imported.
Instead, the way it is working now, you have to do a search for the archival description you just imported. This archival description was created from scratch in AtoM 2.0 and then exported as EAD, deleted, and imported as EAD, it had digital objects that did not roundtrip. (Attachment cricket club ead.xml)

I tested with a couple files and this response was inconsistent. In another case it loaded with errors and the screen prompted me to View archival description. This archival description was migrated with the database from 1.3.1 AtoM to 2.0 instance, then exported as EAD, deleted, and imported as EAD, it had NO digital objects. (Attachment canadian environmental law associ.ead.xml)

cape-town-cricket-club;ead.xml Magnifier (8.19 KB) Jessica Bushey, 10/12/2013 03:16 PM

canadian-environmental-law-association-fonds;ead.xml Magnifier (10.8 KB) Jessica Bushey, 10/12/2013 03:16 PM


Related issues

Related to Access to Memory (AtoM) - Bug #5786: Archival description with item-level digital objects don'... Verified 10/12/2013
Duplicated by Access to Memory (AtoM) - Bug #5787: After XML import screen stays on import Duplicate 10/12/2013

History

#1 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from New to QA/Review
  • Target version changed from Release 2.1.0 to Release 2.0.1
  • % Done changed from 0 to 100

Hi, the problem here was that the error section doesn't appear in 2.x if the import failed at some point. Now the errors will appear.

#2 Updated by Dan Gillean over 8 years ago

  • Status changed from QA/Review to Feedback

I have yet to get a file that doesn't produce ANY errors on import (even if the EAD was created in AtoM... hmm...) - Radda, can you confirm that when there are NO errors, the user still gets a "View archival description" and a "Back" button? It seems that in the past we used to offer basic stats when an import was successful - time elapsed, etc. There should always be an option to get to the imported description if something is imported, even if there are errors or warnings. If NOTHING is imported, this should be made clear to the user as well. As such, the error produced with the test case in issue #5786 (where there is an error, but the file is still imported, only the user does not get a link to the imported description), should never occur.

#3 Updated by José Raddaoui Marín over 8 years ago

Hi Dan,

The only thing I made here is fix the error section. With the changes in the templates made for 2.0 that section never appears in 2.x.

If there is a problem in the import that breaks the process you're returned to the same page, maybe part of the xml file has been processed and some descriptions created, but you won't see the 'View description' button, just the same import page but with the error (this error section is the one I've fixed here).

If the import finishes properly then you'll see the time elapsed, 'View description' button, etc. In this page there is another error section where the errors that doesn't break the process are showed (e.g. libxml errors). We can call it warning section.

After the fix made in issue #5786 a non existing resource doesn't break the whole process and is showed in the warning section instead of in the error one. But this is only in 1.x for the moment.

Hope that clarified.

#4 Updated by Dan Gillean over 8 years ago

  • Status changed from Feedback to Verified

Tested in 1.x as well. Even with warnings, the "View" button will be shown.

Also available in: Atom PDF