[Archivesspace_Users_Group] Order of events for 1.5.0

Mon May 16 16:52:55 EDT 2016

Patrick,

On this same note, I'm curious to know exactly how the barcoder plugin works, because I'm concerned that a workaround puts barcodes at the instance level rather than the "top container" or box level, i.e. Box 1, Folder 1 is getting a different barcode than Box 1, Folder 2, because they have different IDs, and then does this get ingested into top_container as one box, or two? I am unsure whether this SQL update mimics whatever logic is being used by the barcoder (if any) and whether it matters.

So the distilled question is: what does the barcoder actually do (for those of us that can't read Ruby) and can we mimic it with a SQL statement?

-V

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Flanagan, Patrick
Sent: Monday, May 16, 2016 2:55 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

Alston,

I'm a bit late to the party, but I'd also be interested in some info on the work-around. I'm not sure where the barcode information is stored in the database. I imagine it's a string and only has to be unique, but I'm not quite sure where to start or if there are any other limitations.

I have a repository with hundreds of thousands of resources that isn't making a good transition to 1.5.0, and I'd like to see if unique barcodes make any difference.

Thank you,

~Patrick Flanagan
KLN Applications Administrator
Keystone Library Network Hub

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 Valerie Addonizio
Sent: Friday, April 29, 2016 6:12 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

Alston,

I for one am interested in the workaround if you wouldn't mind sending it along!

-Valerie

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 Cobourn, Alston
Sent: Friday, April 29, 2016 4:10 PM
To: 'Archivesspace Users Group'
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

Noah,

My IT guy was able to autogenerate barcodes for everything in our whole AS instance directly in the backend of the database so that we did not have to run the plugin on individual resource records; it would have been A LOT of resource records.  Then he upgraded the data to 1.5 on a test server and the data seems fine.  Perhaps this work-around could be useful to you as well? I can have him send more info if you'd like.

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 Noah Huffman
Sent: Thursday, April 28, 2016 11:29 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] Order of events for 1.5.0

Hi Chris,

Is it possible to run the barcoder plugin over all resource records at once? I'm only seeing the option to select one resource record at a time.

Thanks,
-Noah

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 Chris Fitzpatrick
Sent: Tuesday, April 19, 2016 1:41 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

Hi,

Yes, it's :

1.       Migrate from AT into 1.4.2
2.       Run barcoder plugin
3.       Update to 1.5.0

The barcoder plugin<https://github.com/archivesspace/barcoder> makes fake "barcodes" for containers based on the top level Archival Object + indicator 1 + type. The idea is that some institutions don't have unique identifiers for containers...for example, the have multiple box 1 in a collection ( like "Correspondence : Box 1" and "Financial Records: Box 1" ).

Does that make sense?

b,chris.

best, Chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Valerie Addonizio <vaddoniz at jhu.edu<mailto:vaddoniz at jhu.edu>>
Sent: Tuesday, April 19, 2016 7:27 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

The barcoder plugin<https://github.com/archivesspace/barcoder> is a tool that some repositories will need to use to help prepare their data for migration into 1.5.0, but it will depend on the current state of your barcodes. Hopkins falls into the category that will need it; see the following guide, under Preparation: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md

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 Majewski, Steven Dennis (sdm7g)
Sent: Tuesday, April 19, 2016 12:46 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

What is the 'barcodes plugin' ?

On Apr 19, 2016, at 12:11 PM, Valerie Addonizio <vaddoniz at jhu.edu<mailto:vaddoniz at jhu.edu>> wrote:

Thanks Chris. So let me just confirm a more granular order of events:

1.       Migrate from AT into 1.4.2

2.       Run barcoder plugin

3.       Update to 1.5.0

Or is it:

1.       Migrate from AT into 1.4.2

2.       Update to 1.5.0

2.       Run barcoder plugin

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 Chris Fitzpatrick
Sent: Monday, April 18, 2016 3:43 AM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Order of events for 1.5.0

Hi Valerie,

The migrators have not been updated to run against v1.5.0, so you will have to migrate to a previous aspace version then upgrade.

I'm not sure what it would take to upgrade the migrators, since the person who wrote them is no longer on the project.

Definitely let us know if you have any questions...

best, Chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/

________________________________

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Valerie Addonizio <vaddoniz at jhu.edu<mailto:vaddoniz at jhu.edu>>
Sent: Friday, April 15, 2016 9:09 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Order of events for 1.5.0

Great news regarding this progress, and I am seriously grateful for documentation on how to prepare. I would like to inquire about the order of events for migrating into 1.5.0.

We are a repository still in AT and we have not migrated into AS yet. We are running 1.4.2 as our test instance. We do not have barcodes associated with our containers, and our Box 1's do repeat. What would be the order of events (I've made two guesses below)? And don't worry, I haven't put in steps like "backup AS", etc, and I will be testing, I just need to know what events to test in what order.

Would it be:

1.       Update to 1.5.0

2.       Migrate from AT into 1.5.0

3.       Run barcode plugin

Or:

1.       Migrate from AT into 1.4.2

2.       Run barcode plugin

3.       Update to 1.5.0

Thank you for any clarification.

-Valerie

--------------------------------

Valerie Addonizio

Archivist

The Sheridan Libraries

Johns Hopkins University

vaddoniz at jhu.edu<mailto:vaddoniz at jhu.edu>

410-516-5261

_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160516/519dbc39/attachment.html>