[Archivesspace_Users_Group] ArchivesSpace Permissions Model
brianjhoffman at gmail.com
Wed Jan 20 18:22:26 EST 2016
Can can is just for rails I think. (I tried to see if anyone has used it with sinatra but only learned about the movie can can, starring frank sinatra :/ )
<div>-------- Original message --------</div><div>From: Alexander Duryee <alexanderduryee at nypl.org> </div><div>Date:01/20/2016 5:02 PM (GMT-05:00) </div><div>To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> </div><div>Cc: </div><div>Subject: [Archivesspace_Users_Group] ArchivesSpace Permissions Model </div><div>
</div>We're investigating expanding the ArchivesSpace permissions mechanisms in order to provide more fine-grained control of user roles. We were a bit surprised to see that ASpace uses a custom permissions architecture instead of an existing library (such as CanCan). Before we potentially modify the authorization architecture, we'd like to make sure that we aren't changing something that shouldn't really be changed.
As such, was there any particular motivation to creating a permissions model from scratch vs. using a preexisting library? If there wasn't, and we implement a library like CanCan in our fork of ASpace, would there be any interest in us pushing the changes back to the core codebase?
New York Public Library
alexanderduryee at nypl.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group