[Archivesspace_api_doc_adhoc] Digging in!

[Mayo, Dave]

Lemme know if I can give you a hand – worst case, maybe we can get a virtualbox set up or something like?

Also, at my day job, we’re getting a docker dealie set up specifically for ongoing ASpace dev, I might be able to either yoink it completely, or strip out any Harvard-specific stuff and give it to you, but we’re a ways out from there.

--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS

From: <archivesspace_api_doc_adhoc-bounces at lyralists.lyrasis.org> on behalf of Rachel Donahue <donahrm at gmail.com>
Reply-To: "archivesspace_api_doc_adhoc at lyralists.lyrasis.org" <archivesspace_api_doc_adhoc at lyralists.lyrasis.org>
Date: Wednesday, January 15, 2020 at 9:07 PM
To: "archivesspace_api_doc_adhoc at lyralists.lyrasis.org" <archivesspace_api_doc_adhoc at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_api_doc_adhoc] Digging in!

Hi Dave (and everyone!),

Sorry for the radio silence here. My snag is that I tried installing from master with Ruby 2.7 and it failed at a different point every time, ha ha ha. (Seriously. I'd specify a local path in a Gemfile and suddenly it would fail three Gemfiles earlier. What they hay, Windows!)

I'm heading out of country through Monday, but Tuesday (1/21) I'll scroll through and figure out which endpoints I've been using the most and claim a few to work on.  I think endpoints related to Agents are likely targets because Resources are pretty well documented, iirc.

-- Rachel
(The same Rachel from USDA, but I'm subscribed here as well since I'll be doing the bulk of the work on my personal desktop. See: Windows shenanigans.)

On Wed, Jan 15, 2020, 1:55 PM Mayo, Dave <dave_mayo at harvard.edu<mailto:dave_mayo at harvard.edu>> wrote:
Hi all,

I hope everyone is doing well – just wanted to call round and see how people were doing.

Last I recall, we’d decided we were going to grab some stuff as it suited us, work on them, and revisit after we got a few in to see if we needed more process.

In that spirit, I’ve grabbed POST /vocabularies – it’s not super-high priority, but it’s potentially something that might be remediable at a lower layer than the individual endpoint, and it’s something I think I can turn around pretty quickly.

Is everyone else well situated to do the same?  I want to reiterate, please reach out to me if you hit any snags, and I think for the first route or so per person, it’d be nice to send an email to the list saying what you did, how it went, etc?

Anyway, thanks y’all!
--
Dave Mayo (he/him)
Senior Digital Library Software Engineer
Harvard University > HUIT > LTS
_______________________________________________
Archivesspace_api_doc_adhoc mailing list
Archivesspace_api_doc_adhoc at lyralists.lyrasis.org<mailto:Archivesspace_api_doc_adhoc at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_api_doc_adhoc<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fapi-5Fdoc-5Fadhoc&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=Hlb7-_NywtjBYewz2VEal_4WXH1CfbswenrN-vDuBsc&s=EIsTTHKMJOHr2v_IIlG8QgVw3_-nUc6t8yNwQFy2RiE&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_api_doc_adhoc/attachments/20200116/b91f86d2/attachment-0001.html>