Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

Thanks,

Margaret


________________________________

Margaret T. Kidd

Project Archivist, Special Collections & Archives

VCU Libraries | Tompkins-McCaw Library for the Health Sciences

509 N. 12th Street / Box 980582, Richmond, VA 23298-0582

(804) 828-3152
[em_twitter.png]<https://twitter.com/VCUTMLibrary>[em_fb.png]<https://www.facebook.com/VCUTMLib>


[http://identity.vcu.edu/images/photos/vcu_brand_mark_email_sig.jpg]<http://www.vcu.edu/>
     
[http://pages.shanti.virginia.edu/Virginia_Heritage/files/2013/01/vhpban.jpg] 
<http://vaheritage.org>


On Fri, Nov 10, 2017 at 12:02 PM, Tang, Lydia 
<lta...@lib.msu.edu<mailto:lta...@lib.msu.edu>> wrote:
Mark,
Thank you for identifying my problem!  Just for the sake of technological 
dummies like me, what should I do?  Everything there (besides removing the 
<unitid> tags is exactly as it spat out of ArchivesSpace, so I wonder if the 
export allowed the invalid characters?  I also wonder if the importing process 
could be improved within the ArchivesSpace code to search for “aspace_" and not 
batch add it as well as recognize (or not export out in the first place) the 
"Linear Feet" / linear_feet controlled vocabulary?  Ideally, after establishing 
with the database that linear_feet should publish as Linear Feet, I wish it 
would continue to recognize that rule when new stuff is imported in.
I was also meaning poll people on “how do I even get started” with learning 
more about working the ArchivesSpace guts?  I can understand EAD but obviously 
don’t know the wizardry possible with XML, there’s JSON, python, etc, and I 
would be interested in starting courses with Code Academy to learn, but I don’t 
even know where to begin.  Advice appreciated!
Lydia

From: 
<archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Custer, Mark" <mark.cus...@yale.edu<mailto:mark.cus...@yale.edu>>
Reply-To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Friday, November 10, 2017 at 11:50 AM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Lydia,

In the EAD files that you attached, both have invalid XML characters in them 
(Unicode: 0x14).  Those are easy to remove before re-importing in an XML editor 
like oXygen, but I'm curious how they got into ASpace in the first place?   In 
any event, it's possible that that's what's blocking your imports this time 
around, and if that's the issue, if you just fix on those issues, then the 
ASpace importer won't tell you about the next issue until it runs again.

In any event, I'd also suggest making  the following changes to your XML file 
before re-importing, so perhaps the snag is a good thing for now 😊 :

·         ASpace adds "aspace_" to all of the @id values in the EAD file upon 
export.  If you don't remove those before reimporting, then on the next export 
you'll get "aspace_aspace_".  Removing them will invalidate the EAD file, but 
ASpace doesn't care whether the file is valid or not upon re-importing it.
·         ASpace expects to have the database values for the controlled value 
terms in the exports, not the translation values.  So, if you don't change 
things like "Linear Feet" to linear_feet and "Mixed Materials" to 
mixed_materials, then you'll wind up with new database values in ASpace after 
the import.  Those of course can be merged after the fact, but that's another 
step, and it would be unfortunate to have to do that on every occasion.

There's a lot more to say on the practice of re-importing EAD into ASpace, but 
I haven't still come up with a great strategy for that, so basically we try to 
avoid it 😊

Mark


-----Original Message-----
From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>]
 On Behalf Of Tang, Lydia
Sent: Friday, 10 November, 2017 10:47 AM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Wizardry!  Thank you, Olivia!  I would have NEVER figured that out.  It seemed 
to take out the <unitdate> tags perfectly but I ended up getting snagged on 
importing because of, um, a seemingly benign line which was marked as not 
well-formed.  Oof, so close, but snagged up!
Lydia

From: 
<archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Olivia S Solis <livso...@utexas.edu<mailto:livso...@utexas.edu>>
Reply-To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Friday, November 10, 2017 at 10:36 AM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

<unitda[^>]+>[^<]+<\/unitdate>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto: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

Reply via email to