Thank you Niki and Deb (and everyone else who responded already to my question).
One of the findings thus far from my informational interviews is that the staff have adopted GoogleDocs, Dropbox, and other tools to facilitate their work. They know these tools, they're easy and clear to use, and unless the DM/DAMS we implement is as simple to learn and use, we'll have a difficult time with adoption and we'll still have assets all over the place. I've not seen the Piction DMS module in action yet, so I can't judge how it works. But I primarily want to make sure that the ease-of-use factor is extremely high. That means not a lot of upload-download-send email link to asset-download-upload again actions between collaborators; that just gets cumbersome. I like the idea of using APIs to link to SharePoint or GoogleDocs or Dropbox (officially the museum uses Office 365, but its capabilities are applied somewhat inconsistently) so we can encourage collaboration and version control while maintaining some control over our assets. I just don't know if seamless integration exists yet. Sticky problems to think about! ~P On Wed, Sep 30, 2015 at 6:21 AM, Niki Krause <[email protected]> wrote: > Perian & Deb, > > We're used Piction as our primary image & AV assets DAM for six years, and > have a couple more public-facing Piction systems (collections online, > ArtLens and Gallery One asset management). We've just implemented the > Piction DMS module, integrated with our collection management system via > API. We don't have DAM and DMS on the same physical server, but you could > very easily... >
_______________________________________________ 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]/
