2015-2016 Integrations sub-team work plan
Preliminaries
Come up with a working definition of "integration."
Determine our role with regard to various integrations.
Come up with a mission statement.
Develop a system for keeping track of integrations
Determine what we need to know about various integrations.
Develop system.
Determine the best place for this to live and have it live there.
Implement.
Develop integration guidelines
Create general guidelines that include our definition of "integration," outline ArchivesSpace integration points and "reverse engineer" integration by highlighting current integration work.
Outline ArchivesSpace integration points
Outline where/how AS could be integrated (such as where in the data model, API, etc.).
Highlight current integration work
Outline a list of questions that can be used to investigate current integration work.
Determine the role of liaisons for particular integrations.
Appoint liaisons for particular integrations.
Investigate current Aeon integration further (or maybe not, given Brad's update).
Investigate current Archivematica integration further.
Investigate current SNAC integration further.
Investigate current Preservica integration further.
"Reverse engineer" integration principles.
Other
When AS needs to be extended for a particular integration, determine the roll of this group with regard to addressing those issues, especially as it relates to the community at-large.
At some point, begin work on specific integrations (that is, determining scope, writing specifications, and testing implementations, like our charge says).
Comments
Dec 8, 2015
Dec 11, 2015
The Preservica demo should be available as a recording fairly soon, and we should have slide access fairly soon. I was keeping an eye on that as well.
Can the Integration guidelines include production of a resource to that's like a 'I want to integrate with ArchivesSpace. What's the process for integrating? ' I can see that being something that's added to the main ArchivesSpace wiki under 'Community Resources'. The Committers' Oversight group is currently working to define a process for committing code - so this would be a useful related resource that would help build transparency and hopefully encourage institutions and individuals to develop integrations - and do it in a way that's shareable, etc.