Good evening DAMS SIG, We are in the beginning phases of standing up a new digital asset management system and I am trying to survey of the landscape around integrating user permissions and restrictions between systems. I was wondering if anyone here leverages their collections management system's user/security directly to directly (or indirectly drive) restrictions and permissions in their DAMS? That is, does anyone tie to their CMS's user groups directly to their DAMS via API or some other connector, or otherwise base their DAMS' user configuration around some user metadata point from their CMS?
And if you do leverage that user/security group metadata, what sort of actions in your DAMS do you drive with it? Restricting access to certain assets in your DAMS, hiding certain metadata fields, etc.? Any insights you could provide would be most helpful and welcome, Thanks all! Jon Jonathan Hoppe Digital Asset Librarian t 215-684-7926 Philadelphia Museum of Art PO Box 7646, Philadelphia, PA 19101-7646 www.philamuseum.org<http://www.philamuseum.org/> _______________________________________________ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: [email protected] To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/[email protected]/
