...
Reach out to the community via the ArchivesSpace Users Group and Member Representatives lists, as well as the ArchivesSpace Google Group, or find a potential partner with Who’s Using Archivesspace. You may be able to generate additional ideas or use cases for your integration, or even find partners to help with development resources. This process can also help you identify whether the integration you have in mind is generalizable so that it can be used by other institutions.
Of course, the ArchivesSpace Technical Advisory Council Integrations sub-team is also charged in part with “liaising between those developing integrations, the ArchivesSpace Program Team and the ArchivesSpace community,” so we’re happy to generate ideas and/or support as well! Fill out the ArchivesSpace Integrations Information form so that the Integrations sub-team can learn more about it.
Step 3: Build a case for integration and define technical requirements
...
Furthermore, if the ArchivesSpace Program Team decides that this integration should be worked into the ArchivesSpace core code due to universal applicability and use, you will need to work closely with LYRASIS, the Organizational Home of ArchivesSpace as well as a Registered Service Provider, and Hudson Molonglo, an ArchivesSpace development partner.
...
ArchivesSpace strives to maintain an architecture that is integration-friendly and the program is always interested in hearing from developers and software projects interested in building connections and integrating their applications with ArchivesSpace. If possible, make your code publicly available so others can test or add to it.
Methodology
ArchivesSpace strives to maintain an architecture that is integration-friendly and the program is always interested in hearing from developers and software projects interested in building connections and integrating their applications with ArchivesSpace. You can start by filling out the ArchivesSpace Integrations Information form so that the Integrations sub-team can learn more about it.
The ArchivesSpace REST API
The ArchivesSpace RESTful Application Programming Interface (API) is a programmatic interface to the ArchivesSpace backend, and consists of a number of exposed endpoints used by the backend server to edit records in the application.
Note: Using the API may be better than doing direct SQL updates to the backend server, as it helps to shield you from accidentally failing to update a related table, creating broken links or using receiving errors when using SQL code written for a previous version of the database.
...