2020-06-16 Retrospective

10 min

Roll call

@Maggie Hughes

• Notetaker: @Dave Mayo (Unlicensed)

• Roll call

2 min

Recent contributions

@Maggie Hughes

Shoutouts since April!

Listserv:

• Trevor Thornton

• Kevin Schlottman

• James Griffin

• Dave Mayo

Code:

• Greg Wiedeman

• Bria Parker

• Dave Mayo

• Trevor Thornton

• Maggie Hughes

Bugs/new issues:

• Sarit Hand

• Maggie Hughes
  
  

5 min

Program update

@Christine Di Bella

Open call on June 24th to give people a forum to suggest ways ASpace can improve inclusivity/work toward social justice in this time.

Still working on putting out release

User forum will be held online.

Current plan is to run at same time as SAA as per norm, but interested in feedback on whether that’s the best time to do it.

2 min

TAC updates

@Maggie Hughes

Goodbyes to Greg and Edgar - thank you!

(both issued a soft promise to come back as workload allows )

New TAC Vice Chair

• Rotation for TAC leadership: a member serves a one year term as Vice Chair which is followed by one year as Chair, totaling two years in leadership. 

• Responsibilities are outlined in https://archivesspace.atlassian.net/wiki/spaces/AC/pages/912850978 .

New Google Drive folders - going ok?

• Val is SUPER JAZZED about them

• fulfilled one of their goals

• transmission between incoming/outgoing chairs is a concern

• API Ad-hoc docs stuff maybe ought to move there?

10 min (~2 min each)

Report outs on sub-team restrospectives

Integrations: @Dallas Pillen

Metadata Standards: @Kevin Schlottmann

Tech Docs: @Alicia Detelich

API Working Group: @Dave Mayo (Unlicensed)

Integrations:

https://archivesspace.atlassian.net/wiki/spaces/AC/pages/1291583491

Really positive outcome!

Finding existing integrations was difficult, advertising the subcommittee might mitigate.

Knowledge transfer around data collection efforts (in this case, survey) needs more documentation.

Metadata Standards:

Looking at published metadata profiles

Good groundwork laid for continuing work on them

Test server, sample records. (@Kevin Schlottmann add link?

Focused on MARC/EAD 2002

Reviewed Jira tickets labeled metadata

Time and effort is dear, maybe add deadlines into work plan, scope tighter.

Some of this could maybe be automated? Need more development resources to investigate

Moved spreadsheet to google doc, ease of maintenance

Tech Docs:

Compiled existing docs.

Time and effort dear. Deadlines might help?

Didn’t get around to survey or open call - maybe this year?

More self-promotion, get the word out!

API Ad-Hoc Working Group:

Solid groundwork, ready to start, but lack of person-power for doing the actual documentation production

Maybe look into different model for soliciting participation/distributing work?

• Outward-facing communication to get participation/alert people to services available

• Find ways to allow for community input/contributions

  • break down things into small tasks, reduce amount of training necessary (wikipedia as example)

  • maybe cross-council project with UAC?

  • UAC getting new subteam, User Engagement, working closely with @Jessica Crouch, might be useful to coordinate specifically with them

• maybe add (link to) training for new members in confluence, or a “sandbox” section of wiki?

  • next year there are plans to add some kind of orientation for new members around Jira/Confluence/other “practical tool” issues.

  • Integrations: created an Orientation Document, intended to be copied and altered at end of each term and handed to new members

• Open call with the public?

  • Maybe halfway through term

  • introduce sub-teams, selves, then take questions?

  • Maybe sub-teams rotate and join existing community calls?

  • Possibly a rockin' laser show or disco ball

  • Concrete subjects have been biggest draws

• Long term assessment of kinds of issues incoming on the listserve (categorize questions, i.e. install, plugins, etc)

  • longitudinal data about pain points, analogous to tracking reference queries

• <crickets>

• General consensus that we’re not particularly doing stuff we oughtn’t to be doin'

• heavy impact from external issues

• Google Drive

• focus on continuity documentation (on/offboarding docs and practices)

• Letting each sub-team lead a discussion section