<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >Hi Alex,<div><br></div><div>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><div><br></div><div>Brian</div><br><br><div>-------- Original message --------</div><div>From: Alexander Duryee <alexanderduryee@nypl.org> </div><div>Date:01/20/2016 5:02 PM (GMT-05:00) </div><div>To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> </div><div>Cc: </div><div>Subject: [Archivesspace_Users_Group] ArchivesSpace Permissions Model </div><div><br></div><div dir="ltr"><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.<br><br></div>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?<br><br></div>Many thanks,<br></div>--Alex<br clear="all"><div><div><div><div><div><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Alexander Duryee<div>Metadata Archivist</div><div>New York Public Library</div><div>(917)-229-9590</div><div><a href="mailto:alexanderduryee@nypl.org" target="_blank">alexanderduryee@nypl.org</a></div></div></div></div></div>
</div></div></div></div></div></div>
</body>