Date
Attendees
Goals
- Review our definition of integration. Figure out a roll for our sub-team and for liaisons. Figure out a mission statement.
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5min | Roll call and note taker | Patrick, Kari, Max, Brad were present. | |
| 5min | ArchivesSpace 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. | |
| 10min | Review definition of integration and characteristics and flesh out tiers | Check out the definition 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 characteristics of an integration in the tier and the roles of the program team writ large (i.e. developers and TAC).
| |
| 20min | Establish roles for:
| See notes on our Google Doc (scroll to bottom). Team will focus on tracking integrations: Identity of integration Objective(s) 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.)
| |
| 15min | Create a mission statement | ||
| 5min | Wrap-up and next steps | Next call is Tue, January 12, 2016, 2pm - 3pm |