[Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Brad Westbrook brad.westbrook at lyrasis.org
Fri Jul 17 17:10:52 EDT 2015


No, Doug, “refactored” means rebuilt, if you will.  It’s a project Nathan is currently working on and the results are not yet available for users.  See (https://archivesspace.atlassian.net/browse/AR-1278  for details.

Brad


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Douglas James Simmons
Sent: Friday, July 17, 2015 11:10 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Wait, I need to check my assumptions: does “refactored” simply mean “newest”?

What I have is 25,504,422 bytes.

Doug Simmons
SIUC

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Douglas James Simmons
Sent: Friday, July 17, 2015 9:37 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

These are not being handled by the latest migration tool, the test migration I did yesterday shows the bbtags still present in aspace.

Doug Simmons
SIUC


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens
Sent: Friday, July 17, 2015 9:20 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

The refactored Archon migration tool should automatically handle these conversions, so no need to do manual clean up.

On Fri, Jul 17, 2015 at 9:39 AM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:
Thanks Brian. I found it. I am doing quite a bit of cleanup on the Archon DB side of things it seems.

Thanks,

Phil


Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>
504-865-5607<tel:504-865-5607>



From: Brian Hoffman [mailto:brianjhoffman at gmail.com<mailto:brianjhoffman at gmail.com>]
Sent: Friday, July 17, 2015 8:02 AM
To: Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>>
Cc: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>; Matthew J Gorzalski <mGorzalski at lib.siu.edu<mailto:mGorzalski at lib.siu.edu>>

Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Hi Phil,

I think the Archon experts could answer this better than I can - I do know that Archon uses a square bracket markup style for things like italics, and I would assume that the markup is stored in the DB.

I don’t think the Archon php files have any bearing on ArchivesSpace - during the migration process all Archon content is served to the migration tool as JSON objects over HTTP.

Brian


On Jul 6, 2015, at 4:39 PM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:

Brian,

     While I am not a SQL pro, I know my way around well enough to look at the tables, perform queries, and so forth. Where exactly are these [b] and [i]’s that are showing up in the ArchivesSpace Component Lists & Headers located in the SQL tables? I am not seeing them in the sql data (either the original Archon data or the created ArchivesSpace data post-migration).

I am seeing a reference to the [b] and [i] in the common.inc.php files on the Archon side, but I am not sure if/how ArchivesSpace is using this file for the migration.

Thanks,

Phil

From: brian [mailto:brianjhoffman at gmail.com]
Sent: Monday, July 06, 2015 1:37 PM
To: Suda, Phillip J; Archivesspace Users Group; Matthew J Gorzalski
Subject: RE: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Hi Phil,

That's correct- it can actually only be done in the context of a single resource record and a single sub record type. For example, "replace 'abc' with 'def' in all container summaries of all extent records associated with the g.g. Alin papers". There isn't currently a way to do a global search and replace, and I'd recommend leaving that to someone facile with sql who can do it at the database level.

Brian


Sent from my T-Mobile 4G LTE Device

-------- Original message --------
From: "Suda, Phillip J" <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>>
Date:07/06/2015 2:17 PM (GMT-05:00)
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>, Matthew J Gorzalski <mGorzalski at lib.siu.edu<mailto:mGorzalski at lib.siu.edu>>, Brian Hoffman <brianjhoffman at gmail.com<mailto:brianjhoffman at gmail.com>>
Cc:
Subject: RE: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Brian,

       From what I can tell, the Batch Find & Replace cannot be done on a “global”/instance-wide scale (i.e. finding all the <i>’s and <b>’s at component level). It seems like it only works collection by collection. Please let me know what I am missing.


Thanks,

Phil


Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>
504-865-5607<tel:504-865-5607>



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of brian
Sent: Monday, July 06, 2015 12:40 PM
To: Matthew J Gorzalski; Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Hi Mathew,

This will probably be resolved by deleting your solr index and restarting the application, then waiting for the index to rebuild.

Brian


Sent from my T-Mobile 4G LTE Device

-------- Original message --------
From: Matthew J Gorzalski <mGorzalski at lib.siu.edu<mailto:mGorzalski at lib.siu.edu>>
Date:07/06/2015 11:33 AM (GMT-05:00)
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc:
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

I just went in manually in the ASpace admin view, selected one of our repositories, and went into classifications and deleted the empty ones.  I found that the name of the repository and the good classification matched.  In other words, the Manuscripts classification under the Manuscripts repository was the only classification within that repository to have collections linked to it.

In the process I noticed that the migration produced some weird results, like it was creating false or empty collections that didn’t exist in our Archon.  So I would have Mr. Smith’s Papers, correctly linked to the Manuscripts classification in the Manuscripts repository.  But an empty, no data Mr. Smith’s Papers might also appear in the Photographs classification in the Manuscripts Repository.  After deleting the bad classifications, the empty Mr. Smith would still be there.  So when I found that record in the resource list and tried to delete it, I couldn’t because it would say “record not found.”  So the result is a public view showing two Mr. Smith Papers, one of which has content and the other is “record not found,” which it seems I am powerless to delete.  That is the current issue.

Matt

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens
Sent: Monday, July 06, 2015 10:25 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

For deleting the bad classifications, use the post data migration tool at the link below, which also performs other clean up operations on the data.  Of course, create a backup of the Archivesspace database before running this tool.

https://github.com/archivesspace/aspaceDBUtil

On Mon, Jul 6, 2015 at 10:03 AM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:
Matt,

         Thanks for your reply. With regard to deleting the “bad” classifications, does it matter which ones are deleted? Will there be any orphaned data? I am wondering how I could check, via SQL queries? Thanks again for your help. I am glad to know there are others out there facing the same problems.

Thanks,

Phil


Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>
504-865-5607<tel:504-865-5607>



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>[mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Matthew J Gorzalski
Sent: Thursday, July 02, 2015 1:04 PM

To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

We just tried the batch replace and a remigration to see if it worked, but ran into an error that crashed the migration and are waiting for a response to Doug Simmons’ email yesterday afternoon.

But Phil, a lot of you’re issues are problems we’re experiencing too (we’re Archon users).  I will be talking about our migration adventure at SAA next month and highlight some of these same issues.  The reason classifications are duplicated is because Archon’s classification structure is shared globally throughout Archon, but in ASpace the classifications are replicated per repository.  I deleted our “bad” classifications post migration to knock it back down to 5 from the 30 ArchivesSpace spit out.


Matt Gorzalski
SIU Carbondale

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>[mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone
Sent: Thursday, July 02, 2015 11:54 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Archon to ArchivesSpace Migration Problems & Questions

Hi Phillip,
With regards to number 5, it is a known issue. I have one of the earlier emails about this saved: "This is not a bug, but rather has to do with how the information was entered into archon in the first place. To fix, a find-replace on all records with will need to done changing [i] into <i> and [/i] into </i>, directly on the backend data."

Brian detailed a bit more: "You can do this with the Batch Find and Replace feature (found in the “Background Jobs” section). But you need to test this first in a test environment using a copy of your database. When you are ready to proceed and use your production database, make sure to back it up first."

I'm not sure if something like that would need to be done for your other special characters as well.
-Maura

On Thu, Jul 2, 2015 at 12:44 PM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:
Good morning all,

                 I have performed migrations from Archon to ArchivesSpace successfully. I have then upgraded to the most recent version of ArchivesSpace (v.1.3.0) for each of my instances. This all works better locally (MacBook for me). I have a few questions regarding problems we are noticing with the migrations. I do not know who to ask specifically, but here it goes:


1.       Public Interface Special Characters & Diacritics:

a.       Example: Alcée Fortier papers, 1894-1911 in Archon changes to Alc√©e Fortier papers in ArchivesSpace (v.1.04-v.1.3.0).

2.       Public Interface Scope & Content Notes: these are migrated to ArchivesSpace as large text blobs; they were formatted in Archon (indentation, paragraphs, etc.)

3.       Public Interface Repositories Odd Behavior:

a.       Are all “types” supposed to appear when selecting Repositories? It seems that if you select a repository, it should show you the collections only  OR signify the associated collection for each object/type in question

b.      When selecting a repository, the appropriate collections appear but “global” appears with results below the selected repository:





4.       Classifications appear to be duplicated:

5.       Components show [b] and [/b] OR [i] and [/i] in lists and headers:



6.       Can the Collections be sorted by Collection #/Identifier?


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--
Nathan Stevens
Programmer/Analyst
Digital Library Technology Services
New York University

1212-998-2653
ns96 at nyu.edu<mailto:ns96 at nyu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150717/4b5918ba/attachment.html>


More information about the Archivesspace_Users_Group mailing list