[Archivesspace_Users_Group] User management policy

[Prom, Christopher John]

Mark,

We never had technical documentaiton for this but my assumptions (specific to Univeristy of illinois) are:


  *   a repository manager or delegee manages the user accounts
  *   one person = one user name; i.e. generic accounts are evil.
  *   don't require anything beyond login and password but review occasionally to remove stale accounts (we will probably use LDAP)
  *   We have always deleted/removed user accounts.  Ideally, it would be best to either deactivite or keep a list of deleted accounts for audit purposes.

Chris Prom
University of Illinois

On Feb 7, 2014, at 12:34 PM, "Custer, Mark" <mark.custer at yale.edu<mailto:mark.custer at yale.edu>> wrote:

Hi all,

Has anyone created any non-technical guidelines about managing users in ArchviesSpace (or other systems, like AT, Archon, their ILS)?  What I’m primarily thinking of is a short document that details:

•         Who manages usernames
•         Who requires usernames (e.g. I want to avoid having generic accounts for students, volunteers, etc.)
•         What information is required as part of a user’s account (beyond the “Username” and “Full name” fields)
•         How user accounts are deactivated (not deleted)
•         Etc.

I’m planning to work on a document like this today, but I was hoping that there might be others who were further along in their adoption of ArchivesSpace who’d be willing to share.

All my best,

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

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