Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

Attendees

Not Present:

Goals

  • Review our definition of integration. Figure out a roll for our sub-team and for liaisons. Figure out a mission statement.

...

TimeItemWhoNotes
5minRoll call and note taker Patrick, Kari, Max, Brad were present.
5minArchivesSpace Hackathon 

Are there any Next Steps we could collaborate on?

 

Maureen and Patrick are working on migration guidelines for container management functionality. Max noted this might not be an integration per se, but volunteered to assist where needed.

10minReview definition of integration and characteristics and flesh out tiers 

Check out the definition for integration on the Preliminaries page.

"Tiers" of integration mean a range of integrations of differing scope, complexity, and automation, and, most importantly, the amount of work necessary for preparing / accommodating an integration in ArchivesSpace. An integration that requires a change to the ArchivesSpace data model would be more complex than a simple plugin to a service. Each tier will characterize both the common characteristics of an integration in the tier tiers and the roles of the program team writ large (i.e. developers and TAC) for members of a tier.

 

20min

Establish roles for:

  • Integrations sub-team as a whole
  • Liaisons
 

See notes on our Google Doc (scroll to bottom).

Team will focus on tracking integrations, focusing on these and possibly other data points:

  • Identity of integration
  • Objective(s)
  • Projected date of completion
  • Status
  • URLs to associated resources

 

Create a list of forums in which integrations are likely to be discussed or announced.

Create a Google form where people could report integrations, which would feed a Google sheet.

Actions:

Decide data points (collectively)

Create a Google Form for reporting a single integration according to data points (Patrick G.)

Create a process for posting all integration reports to a cumulative report (in Google or directly on ASpace wiki (Patrick?)

Canvas forums for reports (repeat this task periodically (Max E.)

 

 

 

 

15minCreate a mission statement 
5minWrap-up and next steps 

Next call is Tue, January 12, 2016, 2pm - 3pm

...

15minCreate a mission statement 
5minWrap-up and next steps 

Next call is Tue, January 12, 2016, 2pm - 3pm

Action items

Propose tiers of integrations on Google sheet (All)

Collect information about ongoing integrations:

  • Decide data points for a cumulative report of integrations to be posted on the ASpace wiki (Kari S. (Unlicensed))
  • Create a Google form (on basis of cumulative report form) for collecting singe reports of ongoing integrations (Patrick Galligan (Unlicensed))
  • Devise a process for posting single integration reports to cumulative report on ASpace wiki (Patrick Galligan (Unlicensed))
  • Solicit integration reports by posting information request to suitable forums, e.g., ASpace Users Group, ArchivesSpace Google group, CMT round table list, Code4Lib, etc. (Max Eckard)

Contribute verbiage to Mission Statement on Google sheet (All)

 

 

 

  •