Sorry for the slow reply. This behavior is true of most, if not all, DAMS. So you would have your primary directory of assets, then point the DAMS to it. It does mean some legwork should be performed to consolidate your images when you install the DAMS, but then you won't need to move files around after that. If you do, you'll need to point the DAMS to the new location.
On Fri, Apr 22, 2011 at 12:18 PM, Julie Riley <julie at entermediasoftware.com>wrote: > I can speak for EnterMedia, after all, I work there! EnterMedia points to > digital files, whether they reside on another server, hard drive, in the > 'cloud', etc. Like you stated, it uses a filepath, you do not have to move > or copy images. EnterMedia will also catalog your images the way you have > them sorted on your drives. You won't lose filepaths of files, metadata or > structure. > > http://entermediasoftware.com > > Thanks! > > Julie Riley > > On Fri, Apr 22, 2011 at 12:04 PM, Rothman, Steve > <srothman at fas.harvard.edu>wrote: > > > <<If you're at all interested preserving your images and making sure you > > don't have multiple copies of the same image in your directories (albeit > in > > different sizes), what you probably want is a digital asset management > > system. There are a number of them on the market, and some pretty decent > > open source alternatives. Since it seems like your needs are fairly > modest, > > something like Razuna, DSpace, EnterMedia, or ResourceSpace would work > > well>> > > > > This wasn't a concern of the OP, but I'm curious: Of these open source > > products, would any of them would work well in a situation where the > image > > files are on an independent server with its own filesystem, not held > within > > the database or as part of the database server? In other words, along > with > > whatever metadata is in the DAM it would have to track a filepath for > each > > image, rather than actually "having" a copy of the image? > > > > > > -Steve, Peabody Museum, Cambridge Massachusetts USA >
