We here at ISU have started to use the EAD Archive export regularly. We've found a major problem with the subject terms being incorrect when exporting all. This is happening with both of our installations of Archon. Each XML file in the exported ZIP file has the subject terms of the previous XML file and the correct terms. In other words the zip/xml tree looks like this:
- zip:
- a.xml
- b.xml
- c.xml
- subject terms
- term A
- term B
- term C
- term D
Steps to reproduce:
- Select Export -> EAD Archive
- Click Launch
- Select any Repository(leave the classification on (Select One)
- Click Export
I was able to fix it(with a sledgehammer) via adding this on line 503 in packages/collections/templates/ead/collection.inc.php
$arrEADSubjects = null;
So that section would read like this:
`
<?php
if (!empty($objCollection->Subjects)) {
$arrEADSubjects = null;
foreach ($objCollection->Subjects as $objSubject) {
$arrTraversal = $_ARCHON->traverseSubject($objSubject->ID);
$objParent = reset($arrTraversal);
$arrEADSubjects[$objParent->SubjectType->ID][$objSubject->ID] = $objSubject->toString(LINK_NONE, true, ' -- ');
}
}
`
I'm not sure what other repercussions this fix will introduce though as I haven't done any testing other than the EAD export.
We here at ISU have started to use the EAD Archive export regularly. We've found a major problem with the subject terms being incorrect when exporting all. This is happening with both of our installations of Archon. Each XML file in the exported ZIP file has the subject terms of the previous XML file and the correct terms. In other words the zip/xml tree looks like this:
Steps to reproduce:
I was able to fix it(with a sledgehammer) via adding this on line 503 in packages/collections/templates/ead/collection.inc.php
$arrEADSubjects = null;So that section would read like this:
`
`
I'm not sure what other repercussions this fix will introduce though as I haven't done any testing other than the EAD export.