Chad, Does Portfolio not operate on the Oracle platform? -- Tamsen Schwartzman Museum Media Manager The Museum at FIT, Room E116 Seventh Avenue at 27th Street New York, NY 10001 212~217~4547 ** 212~217~4561 fax www.fitnyc.edu/museum Visit our collections online at fashionmuseum.fitnyc.edu Find us on Facebook Follow us on Twitter @MuseumatFIT
Closes April 10: American Beauty Closes May 11: Night & Day Opens March 9: Scandal Sandals & Lady Slippers: A History of Delman Shoes -----Original Message----- From: mcn-l-bounces at mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of Chad Petrovay Sent: Monday, December 07, 2009 7:11 PM To: Museum Computer Network Listserv Subject: Re: [MCN-L] Digital Asset and Collection Management Extensis Portfolio uses a proprietary flat-file format for data storage - you'll need to purchase the SQL Server back-end option to make cross-system communication possible. I only mention it because licensing for Extensis Portfolio is reasonable, but the SQL back-end is an additional product. Chad Petrovay ?| ?Collections Database Administrator MIM-Musical Instrument Museum | 8550 S. Priest Drive ?| ?Tempe, AZ 85284 480.481.2460 main ?| ?480.353.2746 direct | 480.481.2459 fax ?| www.themim.org -----Original Message----- From: mcn-l-bounces at mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of Dueker, Peter Sent: Monday, December 07, 2009 1:09 PM To: Museum Computer Network Listserv Subject: Re: [MCN-L] Digital Asset and Collection Management An evergreen topic - came up recently on the TMS listserve as well. > so much of what is required for > DAM is irrelevant and usually not present on a CMS My personal belief is that the functional requirements differ enough that it is rarely practical to shoehorn the functionality of a DAM into an existing CMS (or vice versa). You end up short changing one area or another and rarely get everything you need. However, I've talked with others on the list who feel quite the opposite. Perhaps it's material enough for a panel sometime at MCN ... >Is anyone using a DAM that is usefully connected >to their CMS? What is good/not so good about what you've got? We assign object data to images in our DAM [Extensis Portfolio] using extract data from our CMS [TMS] , we also push images into the CMS from the DAM. Absolutely essential. In this day and age, I don't see a reason to select systems that cannot communicate with other systems. I would be hesitant to work with a vendor who is unwilling or unable to provide information regarding integration [such as a comprehensible data dictionary] with other products. Again, personal opinion, but I think this one of the real strengths of both Portfolio and TMS - they really do work well together. Peter Dueker Contract DAMS Manager Division of Imaging and Visual Services National Gallery of Art, Washington D.C. On 12/7/09 2:07 PM, "Ari Davidow" <aridavidow at gmail.com> wrote: . >Is anyone using a DAM that is usefully connected >to their CMS? What is good/not so good about what you've got? _______________________________________________ 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: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://toronto.mediatrope.com/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://toronto.mediatrope.com/pipermail/mcn-l/ _______________________________________________ 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: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://toronto.mediatrope.com/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://toronto.mediatrope.com/pipermail/mcn-l/
