Bug #12998

Cached XML is not being used for EAD downloads when expected

Added by Corinne Rogers over 1 year ago. Updated 5 months ago.

Status:VerifiedStart date:05/03/2019
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:XML import / export
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:2.4, 2.5
Sponsored:No Requires documentation:

Description

This was reported in the user forum: https://groups.google.com/forum/#!msg/ica-atom-users/w8XvZ4fRnaE/vzQoBYCTAwAJ

When "Cache description XML exports upon creation/modification" is set to "Yes" in Admin/Settings XML exports are pre-generated whenever an archival description is created or modified through the UI. See:

Expected behaviour:
When a user attempts to download XML from the view page of an archival description, AtoM will check if there is a cached copy of the requested XML and if so, it will serve it. If there is no cached version available, then AtoM will fall back to the default behaviour of generating the XML on request.

Observed behaviour:
When a user attempts to download XML from the view page, AtoM appears to always use the default of generating the XML on request.

To observe this behaviour:
  • log in to AtoM as an administrator
  • set "Cache description XML exports upon creation/modification" to "Yes" in Admin/Settings
  • make a change to an archival description and save the change
  • add the description to the clipboard
  • export EAD for that description from the clipboard
  • from the terminal, go to the atom/downloads/exports/ead and open the cached ead for that description
  • make a change in the ead from the terminal, save, and return to the AtoM UI
  • export the EAD again
  • notice that the change made to the cached file does not appear in the new export
  • because no change was made to the description in the UI, no new cache should be generated - this can be observed by returning to the cached file to see that the change is still there

This was tested in 2.4.1 and 2.5 (16.04) with the same results in both


Related issues

Related to Access to Memory (AtoM) - Bug #11197: XML representation caching for EAD: drafts are getting ca... Verified 05/25/2017

History

#1 Updated by David Juhasz over 1 year ago

  • Tested version 2.4, 2.5 added

#2 Updated by Dan Gillean 12 months ago

  • Related to Bug #11197: XML representation caching for EAD: drafts are getting cached added

#3 Updated by Mike Cantelon 11 months ago

  • Status changed from New to Code Review

#4 Updated by Steve Breker 11 months ago

  • Status changed from Code Review to Feedback
  • Assignee set to Mike Cantelon

CR complete - Looks great!

#5 Updated by Mike Cantelon 11 months ago

  • Status changed from Feedback to QA/Review
  • Assignee deleted (Mike Cantelon)

Merged into qa/2.6.x for QA.

#6 Updated by Dan Gillean 5 months ago

  • Category set to XML import / export
  • Target version set to Release 2.6.0

#7 Updated by Dan Gillean 5 months ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF