<div dir="ltr"><div dir="ltr">Hi Dave, thanks for checking in on this! I'm sorry to say I have done nothing on it since the last call, but I look forward to getting into it again soon (realistically, probably after the holidays). For the moment I have a suggestion and a question:<div><br></div><div>Suggestion: What if each of us took one route of our choice (check out a row in the spreadsheet) and roughed out what we take to be complete (or improved) documentation? Then we could compare notes and come to some agreement on a model to use going forward. This could save some rework down the road if we have very different styles of documentation going on. I'm thinking a lot of routes will also have very similar documentation and could be templatized. </div><div><br></div><div>A question: I noticed in the screen cast (maybe this was a local branch, I'm not sure?) that Python examples were written using ASnake. I've been wondering, are we going to presume Asnake as the method? I ask somewhat selfishly as I don't use ASnake myself, though I'm probably an outlier. Maybe we should have non-snake examples along side, to minimize dependencies? Any thoughts?</div><div><br></div><div>Best regards,</div><div>David </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 13, 2019 at 2:33 PM Mayo, Dave <<a href="mailto:dave_mayo@harvard.edu">dave_mayo@harvard.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-8891219195766346555WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Hi all,<br>
<br>
Sorry it’s been radio silence from me for a while – I wanted to get in touch before our various holiday breaks and whatnot, with a discussion of what next steps will look like. I’m thinking these should happen sometime soon after the new year, ideally.
<br>
<br>
Our next steps should be some kind of triage (i.e. selecting which endpoints need documenting most) and then distributing the work. I’d like to come to an agreement as a group on how to proceed with each of these steps; I’m going to outline a couple ways I
could see it working up front so we have something to bat around.<br>
<br>
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Triage/figuring out which routes need attention:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><br>
- we could just individually bump priority on routes we know are bad, clear those, and then do another round of triage (maybe with more investigation ala option 2 below) then.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">- we could divide the routes evenly? by capacity? and have each person check N routes and mark which ones need attention<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">- Or something in the middle, like categorize the routes somehow and investigate specific categories?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><br>
Personally, I’m having a hard time saying what’s right here, and that’s making me feel like doing 1 just to have some concrete progress on the table isn’t the worst idea - and maybe exposure to more routes while fixing it will give some ideas for how to improve
triage methods?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><br>
Then, splitting the work:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><br>
I think due to differing capacity and volunteer nature, this has to be pretty driven by individuals - I think “grab routes with high priority and work on them” is more or less a given. I think we might want to specify some low-effort check-in/check-out guidelines,
i.e. maybe whether a person should only assign themselves a route right before they get to work on it, or if grabbing a bunch that you have in mind is better, and so on. People with more PM experience than I in this group, so PLEASE chime in here
</span><span style="font-size:11pt;font-family:"Apple Color Emoji"">☺</span><span style="font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">--<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Dave Mayo (he/him)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Senior Digital Library Software Engineer<br>
Harvard University > HUIT > LTS</span><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
Archivesspace_api_doc_adhoc mailing list<br>
<a href="mailto:Archivesspace_api_doc_adhoc@lyralists.lyrasis.org" target="_blank">Archivesspace_api_doc_adhoc@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_api_doc_adhoc" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_api_doc_adhoc</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div style="font-size:13px"><font color="#999999">David W. Hodges</font></div><div style="font-size:13px"><font color="#999999">Special Collections Analyst</font></div><div style="font-size:13px"><font color="#999999">Columbia University Libraries</font></div><div style="font-size:13px"><span style="color:rgb(153,153,153)">Butler Library</span><br></div><div><font color="#999999"><span style="font-size:13px">535 West 114th St.</span></font><br></div><div style="font-size:13px"><font color="#999999">New York, NY 10027</font></div><div style="font-size:13px"><font color="#999999">212 854-8758</font></div><div style="font-size:13px;color:rgb(0,0,0)"><br></div></div></div></div></div></div></div></div></div></div></div></div></div>