[Archivesspace_Users_Group] Update: Classification problem fixed, almost
Matthew J Gorzalski
mGorzalski at lib.siu.edu
Thu May 14 14:32:57 EDT 2015
I think I found the problem. The two bad classifications had 1-2 collections attached to them because of human error when entering the data in Archon to begin with. So I reassigned the repository information in the Archon records and our next migration test should fix it.
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Matthew J Gorzalski
Sent: Wednesday, May 13, 2015 8:11 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Classification problem fixed, almost
Previously I wrote about how our public ASpace listed 30 classifications while our staff interface listed only 5. This was a problem because only 5/30 classifications actually had collections linked to them and the other 25 where empty, duplicative shells. I remembered that the classifications are duplicated across repositories, so in the ASpace staff view I switched repositories in the drop-down menu in the upper right and found the other classifications I thought were missing previously. I was able to delete all of the bad classifications by going into each of our repositories and locating the empty shells. It turned out that the repository name matched the name of the good classification. In other words, the only classification in the Manuscripts repository with content happened to be the Manuscripts classification.
I've attached a screen shot of an error I get that prevents me from deleting the final 2 bad classifications. You're looking at the Manuscripts repository and I get this error when trying to delete Photographs and University Archives. I did not get this error in any other circumstance.
MAIL CODE 6632
SOUTHERN ILLINOIS UNIVERSITY
605 AGRICULTURE DR
CARBONDALE, IL 62901
mgorzalski at lib.siu.edu<mailto:mgorzalski at lib.siu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group