[Archivesspace_Users_Group] Configuring multiple tenants in ArchivesSpace?

Mon Jun 8 14:46:03 EDT 2015

Greetings all,

I found this email from 2013 while searching through the listserv and it has intrigued me. Has anyone pursued the multi-tenant approach in AS? Mark, did Yale ultimately take this approach?

-Valerie

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Thursday, December 12, 2013 12:31 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Configuring multiple tenants in ArchivesSpace?

Hi Chris,

It’s not exactly that you would have separate installations of ArchivesSpace with the current multi-tenant approach, since the tenants share the same ArchivesSpace core code.  But you would have separate MySQL databases for each tenant.  So by default, I *think* that this means that you would indeed have a separate public interface for each and every tenant.

That said, I’d say that our goal is to pursue a multi-tenant approach that uses a shared database.  If that isn’t feasible, we might still go with a multi-tenant installation that uses separate databases.

The use case for multiple tenants is very similar to why you’d use multiple repositories (and a few of our “tenants,” if not all, might still have multiple repositories).  The difference, as I see it, is that with multiple tenants you would have more control over the data (e.g. you could share all the name records across all of the repositories, as is the default AT/ASpace set up, or you could make those name records tenant-specific) and how the application is extended (e.g. one tenant could use a plugin that’s specific to born-digital workflows, which could be suppressed from view for other tenants who might not need that functionality yet).

Mark

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman
Sent: Thursday, December 12, 2013 10:43 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Configuring multiple tenants in ArchivesSpace?

Hi Chris,

I conflated multi-tenancy and multi-repository in my response to Mark, I realize now. As far as I understand it, setting up multiple repositories allows an institution to share certain data (users, authorities, etc. -- https://groups.google.com/forum/#!topic/archivesspace/r5WBdw-9S7o), while multi-tenancy is defined as "isolated installations of the system in a common deployment environment."

Penn State intends the former. (I should avoid email just before vacation.)

Best,
Ben

________________________________
From: "Christopher John Prom" <prom at illinois.edu<mailto:prom at illinois.edu>>
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Sent: Thursday, December 12, 2013 10:32:17 AM
Subject: Re: [Archivesspace_Users_Group] Configuring multiple        tenants        in        ArchivesSpace?

As a very basic question, I am wondering if someone can explain what the effect would be of doing a multi tenant setup as opposed to managing several repositories in one DB?

I am as suing that If you have four tenants, would you have four completely separate instances, each with their own staff and public interface at a designed URL?  Is that correct?

Or would it be possible to have one public interface through which information in all four tenants could be searched and displayed side by side?  In addition to separate public interfaces for each tenant?

I guess what I am asking is what use cases does the specific implementation of the multi tenancy that was put into aspace allow for?

Chris

On Dec 12, 2013, at 8:55 AM, Ben Goldman <bmg17 at psu.edu<mailto:bmg17 at psu.edu>>
 wrote:

Hey Mark,

We're not there yet at Penn State, but planning/hoping to go there with our installation in the Spring, in order to serve satellite archives at Penn State commonwealth campuses. I'd be happy to follow up then.

-Ben

________________________________
From: "Mark Custer" <mark.custer at yale.edu<mailto:mark.custer at yale.edu>>
To: "Archivesspace Users Group" <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Sent: Thursday, December 12, 2013 9:46:18 AM
Subject: [Archivesspace_Users_Group] Configuring multiple tenants in        ArchivesSpace?

Hi all,

At Yale, we just started experimenting with setting up a multi-tenant installation of ArchivesSpace (https://github.com/archivesspace/archivesspace/tree/master/clustering).  Have any other institutions set one of these up already?  If so, I’d love to talk with you on- or off-list about how you’ve opted to configure everything.

Additionally, it would also just be really nice to know who else is opting to go this route.

Mark Custer
Archivist / Metadata Coordinator
Beinecke Rare Book & Manuscript Library
203-432-2969

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150608/5c33896b/attachment.html>