Re: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace

2018-03-15 Thread Bria Lynn Parker
Hi Cheryl,

I'll also chime in here - I just got (mostly) through converting a ton of
data that were eloquent data exported to tab delimited text/spreadsheet. We
had a LARGE collection we purchased, and that was what we got with it: a
dump of their eloquent data.

I made use of Stead: https://github.com/jronallo/stead to do the conversion
to EAD, and some local scripts to do some stuff to the converted EAD prior
to upload to ArchivesSpace.
A colleague and I made some local modifications/enhancements Stead to get
it to work with our data. I would be more than happy to talk with you
offline about how I did this if this is something you're interested in. And
I would of course share my code.


-- 
Bria L. Parker
Head, Discovery and Metadata Services

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu



On Thu, Mar 15, 2018 at 9:24 AM, Mayo, Dave  wrote:

> Hi Cheryl,
>
> Oof, that’s rough.  I have a few questions, if you don’t mind.
>
> 1. Can you provide more detail on why EAD export is impossible?  I only
> ask because they claim EAD export on their website pretty prominently, and
> it would be, I think, much easier than doing a migration from proprietary
> text format.
> 2. Are you comfortable with programming in a scripting language (Python,
> Ruby, Perl, etc.) or do you have access to someone who is?
> 3. What does the ASCII format actually look like?  An example record would
> be really helpful in giving advice.
>
> Assuming that EAD is entirely out of reach, I think this would take
> either, as you mentioned, manual transfer, or someone writing a script to
> take the ascii output, turn it into ASpace JSONModel objects, and import it
> via the API.  The hardest part is probably the conversion step – there’s a
> fair amount of code out there for doing imports of JSONModel objects (or
> you can just strip the EAD -> JSONModel part out of EAD import scripts),
> but I don’t know that there’s a way around significant programming effort.
> Even EAD migrations have in my experience involved a fair amount of
> programming, though size and scope of collection matters a lot for how
> important that is.
>
> - Dave Mayo
> ASpace Core Committers Group
>
>
>
> *From: * on
> behalf of Christine Di Bella 
> *Reply-To: *Archivesspace Users Group  lyralists.lyrasis.org>
> *Date: *Thursday, March 15, 2018 at 8:59 AM
> *To: *Archivesspace Users Group  lyralists.lyrasis.org>
> *Subject: *[Archivesspace_Users_Group] FW: [Archivesspace_member_reps]
> Migrating Data from Eloquent Systems to ArchivesSpace
>
>
>
> Hi all,
>
>
>
> I’m forwarding this for Cheryl from the Member Representatives list in
> case anyone here has made a move from Eloquent and has suggestions or
> advice. The program team will also reach out with some ideas.
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibe...@lyrasis.org
>
> 800.999.8558 x2905 <(800)%20999-8558>
>
> 678-235-2905 <(678)%20235-2905>
>
> cdibella13 (Skype)
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
>
>
>
>
> *From:* archivesspace_member_reps-boun...@lyralists.lyrasis.org <
> archivesspace_member_reps-boun...@lyralists.lyrasis.org> *On Behalf Of *Cheryl
> Ziegler
> *Sent:* Wednesday, March 14, 2018 8:58 PM
> *To:* archivesspace_member_r...@lyralists.lyrasis.org
> *Subject:* [Archivesspace_member_reps] Migrating Data from Eloquent
> Systems to ArchivesSpace
>
>
>
> Hello all,
>
>
>
> I am under significant time constraints to move my data from Eloquent
> Systems to ArchivesSpace as my contract with Eloquent is over effective
> April 30. I was led to believe that my data could be exported in EAD
> format. Unfortunately, that is not true. I can only export my data into
> ASCII delimited text format.
>
>
>
> I am flying blind here and I know there is not an easy "fix." If I need to
> manually input my records, then I need to start doing that right away. If
> there is a way to convert ASCII into a workable migration format, then I
> need advise on how to accomplish that conversion.
>
>
>
> Some background: earlier in the year, my IT Director told me he had
> figured out how to do this migration. He has resigned taking that
> information with him although I am not sure that he actually *had*
> figured it out.
>
>
>
> I am willing to do the work. I just need a process.
>
>
>
> Thank you,
>
> Cheryl
>
>
> Cheryl L. Ziegler, MLIS
>
> Director of Library & Archives
> Union League Club of Chicago
>
> 65 W. Jackson Blvd.
>
> Chicago, IL  60604
>
>
> P: 312.435.4818 <(312)%20435-4818>
>
> www.ulcc.org
> 
>

Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

2017-01-25 Thread Bria Lynn Parker
Well, so it turns out the issue wasn't so much with my data, but that I did
not realize that deleting a resource does not also delete the top
containers created when importing a resource and associated with that
resource. So my own testing was my downfall! Thankfully this was all on a
test server, so I could easily purge all the old top containers...

Thanks all for the guidance, though!

On Tue, Jan 24, 2017 at 11:24 AM, Majewski, Steven Dennis (sdm7g) <
sd...@eservices.virginia.edu> wrote:

>
> I was getting that error on 1.5.2 migration ( see other email thread ) and
> that one turned out to be due to an erroneous duplicate  barcode assigned
> to different containers with different indicators.
>
> In the other cases, where there were trailing spaces in one of the
> barcodes, the message was a mismatch between barcode and barcode_1 — the
> inverse error of the one above: same container, different barcodes.
>
> — Steve.
>
>
>
> On Jan 24, 2017, at 11:10 AM, Bria Lynn Parker <blpar...@umd.edu> wrote:
>
> I should add:
>
> I'm running 1.5.2, and I have checked for sneaky whitespaces within any of
> these attributes and have found none.
>
> On Tue, Jan 24, 2017 at 11:06 AM, Bria Lynn Parker <blpar...@umd.edu> wrot
> e:
>
>> Hi all - I'm hoping someone has a tip or hint at where I'm going wrong:
>>
>> We've finished cleaning up/normalizing our EAD (including implementing
>> container attributes and the like for container management). The majority
>> are importing fine, no errors (or, at least no errors I can't find and fix,
>> like bad begin/ends). However, for some of our finding aids, I'm getting
>> the following:
>>
>> indicator_1 : Mismatch when mapping between indicator and indicator_1
>>
>> No other info about location, etc. I've about torn my hair out trying to
>> find *any* mismatch of container data - I've checked every instance's
>> dummy barcode (which is constructed in part from the id), id, and parent
>> against itself, crosschecked with the container indicator, and they all
>> match within themselves. We're importing barcodes in the label attribute,
>> which
>> works (except when it doesn't here?). The error message getting thrown is
>> from this ruby function https://github.com/archivesspa
>> ce/archivesspace/blob/5e1ca66f1f04f142f2695024efb72008250463
>> 25/backend/app/lib/aspace_json_to_managed_container_mapper.rb#L173
>>
>> Help? If someone has encountered this and figured it out, let me know -
>> I'd love some help. If you want to contact me off list, I can sent you a
>> full xml file.
>> Here's an example from my xml:
>>
>>
>>
>> 
>>   
>> Financial Records -- General -- Bound Volumes --
>> Financial Reports
>> 1905-1908
>> 1
>> 1.0
>>   
>> 
>>
>>
>>   
>> Financial Records -- General -- Bound Volumes --
>> Financial Reports
>> 1909
>> 1
>> 2.0
>>   
>> 
>>
>>
>> 
>>   
>> Financial Records -- General -- Bound Volumes --
>> Financial Reports
>> 1910-1911
>> 1
>> 3.0
>>   
>> 
>>
>> (historical background - some of our series restart box numbers at 1, and
>> the container ids reflect that, so 89.1 is the 89th box in the collection,
>> but 1st in the series. This is not causing the error as far as I can tell,
>> since other collections with same numbering style import fine)
>>
>>
>> --
>> Bria L. Parker
>> Metadata Librarian
>> 2200 McKeldin Library
>> University of Maryland
>> College Park, MD 20742-7011
>> (301) 405-9067
>> blpar...@umd.edu
>>
>
>
>
> --
> Bria L. Parker
> Metadata Librarian
> 2200 McKeldin Library
> University of Maryland
> College Park, MD 20742-7011
> (301) 405-9067
> blpar...@umd.edu
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] EAD import error - indicator mismatch

2017-01-24 Thread Bria Lynn Parker
I should add:

I'm running 1.5.2, and I have checked for sneaky whitespaces within any of
these attributes and have found none.

On Tue, Jan 24, 2017 at 11:06 AM, Bria Lynn Parker <blpar...@umd.edu> wrote:

> Hi all - I'm hoping someone has a tip or hint at where I'm going wrong:
>
> We've finished cleaning up/normalizing our EAD (including implementing
> container attributes and the like for container management). The majority
> are importing fine, no errors (or, at least no errors I can't find and fix,
> like bad begin/ends). However, for some of our finding aids, I'm getting
> the following:
>
> indicator_1 : Mismatch when mapping between indicator and indicator_1
>
> No other info about location, etc. I've about torn my hair out trying to
> find *any* mismatch of container data - I've checked every instance's
> dummy barcode (which is constructed in part from the id), id, and parent
> against itself, crosschecked with the container indicator, and they all
> match within themselves. We're importing barcodes in the label attribute,
> which
> works (except when it doesn't here?). The error message getting thrown is
> from this ruby function https://github.com/archivesspace/archivesspace/
> blob/5e1ca66f1f04f142f2695024efb7200825046325/backend/app/lib/
> aspace_json_to_managed_container_mapper.rb#L173
>
> Help? If someone has encountered this and figured it out, let me know -
> I'd love some help. If you want to contact me off list, I can sent you a
> full xml file.
> Here's an example from my xml:
>
> 
>   
> Financial Records -- General -- Bound Volumes --
> Financial Reports
> 1905-1908
>  "box" id="89.1">1
> 1.0
>   
> 
>
>
>   
> Financial Records -- General -- Bound Volumes --
> Financial Reports
> 1909
>  "box" id="89.1">1
> 2.0
>   
> 
>
>
> 
>   
> Financial Records -- General -- Bound Volumes --
> Financial Reports
> 1910-1911
>  "box" id="89.1">1
> 3.0
>   
> 
>
> (historical background - some of our series restart box numbers at 1, and
> the container ids reflect that, so 89.1 is the 89th box in the collection,
> but 1st in the series. This is not causing the error as far as I can tell,
> since other collections with same numbering style import fine)
>
>
> --
> Bria L. Parker
> Metadata Librarian
>
> 2200 McKeldin Library
>
> University of Maryland
>
> College Park, MD 20742-7011
>
> (301) 405-9067
>
> blpar...@umd.edu
>



-- 
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Deleting in Bulk From the Staff Interface

2016-12-15 Thread Bria Lynn Parker
I have command line access to the API, and I've had decent success using
the API to do bulk updates and deletions. It's been great for when we
notice something didn't import as we had expected/hoped.

I used the API extensively when the processing status moved to an event
and
we didn't want to manually add each one.

I'm not an expert at it by any means, but I could answer questions for
anyone who is new to the API and is interested in trying it!

-- 
Bria L. Parker
Metadata Librarian

2200 McKeldin Library

University of Maryland

College Park, MD 20742-7011

(301) 405-9067

blpar...@umd.edu

On Thu, Dec 15, 2016 at 12:03 PM, Jason Loeffler  wrote:

> In general, I'm interested to know more about how people currently perform
> bulk operations on ArchivesSpace objects, including record creation
> (without the RDE), bulk updates, deletions, etc.
>
> Just curious if any of you have command line access to the server running
> your ArchivesSpace instance and are able to work with the API. Without it,
> you have to resort to workarounds which, though helpful, can be a little
> clunky and/or error prone.
>
> It would be great to include a set of bulk operation tools in a future
> ArchivesSpace release.
>
> Jason Loeffler
> Technology Consultant | The American Academy in Rome
> Minor Science | Application Development & Metadata Strategy
> Brooklyn, New York
> ja...@minorscience.com
> (347) 405-0826
> minorscience (Skype)
>
>
>
> On Thu, Dec 15, 2016 at 10:07 AM, Noah Huffman 
> wrote:
>
>> Suzanne,
>>
>>
>>
>> In addition to Mark’s strategy (I’d never thought of that), here’s
>> another way to batch delete components, especially if you need to search
>> for them:
>>
>>
>>
>> 1.   Go to Browse>Resources
>>
>> 2.   Check the “show components” box
>>
>> 3.   Search for matches in the “Filter by text” box
>>
>> 4.   Use facets to filter results if necessary
>>
>> 5.   Check all the archival object records you want to delete
>>
>> 6.   Click Delete.
>>
>>
>>
>> -Noah
>>
>>
>>
>>
>>
>> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
>> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of 
>> *Custer,
>> Mark
>> *Sent:* Thursday, December 15, 2016 9:49 AM
>> *To:* Archivesspace Users Group > alists.lyrasis.org>
>> *Subject:* Re: [Archivesspace_Users_Group] Deleting in Bulk From the
>> Staff Interface
>>
>>
>>
>> Suzanne,
>>
>>
>>
>> Here’s one workaround for that:
>>
>>
>>
>> · Add a child-level component to the resource, and name it
>> something like “delete-me”, and give it any level whatever (since those two
>> fields are required to create a new archival object).
>>
>> · Select all of the archival components that you want to delete
>> (you can use the shift and/or control keys to select whatever you need to
>> select), and then use the “move” function to move them into the
>> newly-created delete-me wrapper.
>>
>> · Then, just delete that delete-me component.
>>
>>
>>
>> Mark
>>
>>
>>
>>
>>
>>
>>
>> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [
>> mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org
>> ] *On Behalf Of
>> *Stasiulatis, Suzanne
>> *Sent:* Thursday, 15 December, 2016 9:32 AM
>> *To:* archivesspace_users_group@lyralists.lyrasis.org
>> *Subject:* [Archivesspace_Users_Group] Deleting in Bulk From the Staff
>> Interface
>>
>>
>>
>> Is there any way to delete multiple archival objects in a resource. Can
>> you select multiple archival objects and delete them in bulk? What are your
>> workarounds or solutions?
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>> Suzanne
>>
>>
>>
>>
>>
>> *Suzanne Stasiulatis *| Archivist II
>> Pennsylvania Historical and Museum Commission | Pennsylvania State
>> Archives
>> 350 North Street | Harrisburg, PA 17120-0090
>>
>> Phone: 717-787-5953 <(717)%20787-5953>
>>
>> http://www.phmc.pa.gov
>> 
>>
>> sustasi...@pa.gov
>>
>>
>>
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org