TMSUSERS Archives

The Museum System (TMS) Users

TMSUSERS@SI-LISTSERV.SI.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Peter Dueker <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Thu, 22 Sep 2011 13:58:35 -0400
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (4 kB) , text/html (6 kB)
With the DAMS and TMS  managing access structured directories exist
primarily for legibility and cleanliness ­  with modern OSıs you could just
put all of your  dedicated TMS images into a single directory and not worry
about it.  For captures (master and derivatives),  a date based folder
structure is generally quite effective, Iım not so sure about trying to
define specific folders for each object based on ID , seems like youıd end
up with a lot of extra folders and work.  Leverage the metadata in Portfolio
for that (e..g prepared searches or galleries) to find these assets.

Although geared towards commercial workflows, Peter Kroghıs the DAM book is
has valuable, sensible advice on folder structure and file naming.
http://www.thedambook.com/

Peter Dueker
Head of Digital Imaging Services
Division of Imaging and Visual Services
National Gallery of Art, Washington D.C.



On 9/22/11 12:45 PM, "Ryan Donahue" <[log in to unmask]> wrote:

> We have an uploader that pushes images from our Dam to tms. It puts them in
> folders by date Transferred to tms. The uploaded is a combo of a dam asset
> action and script that preps the media loader access db. 
> 
> Sent from my iPhone
> 
> On Sep 22, 2011, at 12:25 PM, Hassan Najjar <[log in to unmask]> wrote:
> 
>> This is a question I need the answer to as well. Is there a software package
>> that allows you manage this?
>>  
>> Thanks!
>>  
>> 
>> 
>> From: The Museum System (TMS) Users [mailto:[log in to unmask]] On
>> Behalf Of Radvak, Liana
>> Sent: Thursday, September 22, 2011 12:05 PM
>> To: [log in to unmask]
>> Subject: Another DAM Question!
>>  
>> Hi,
>>  
>> I am looking for any advice from TMS institutions that use DAMS. We are in
>> the middle of an integration project, Extensis/TMS, and would like to know
>> how other places organize their image folders. Our initial thought was to
>> organize by object ID, each object having itsı own folder, the most recent
>> recommendation is a directory structure that is chronological ­ date of
>> capture.
>>  
>> Many thanks,
>>  
>> Liana
>>  
>>  
>> Liana Radvak
>> Manager, Collection Information & Resources
>> Art Gallery of Ontario
>> 317 Dundas St. West
>> Toronto, ON. M5T 1G4
>> 416.979.6660 x.463
>>  
>>  
>> 
>> From: Vuleta, Virginia
>> Sent: September 22, 2011 10:03 AM
>> To: Radvak, Liana
>> Subject: Update on Portfolio progress
>>  
>> Image Resources have finally agreed to move ahead with using Object Number as
>> the master field between TMS and Portfolio, and to reorganize the image
>> catalogs from the CD/DVD based directory structure to a chronological
>> structure (i.e., Images\YYYY\YYYYMM).
>>  
>> Iım going to bring in an extra body to work on the file migrations, but itıs
>> going to take a lot of searching (since the image files donıt have date
>> information embedded in metadata, I expect the person will have to cross
>> reference TMS to decide where to move images).  Do you know of anyone who has
>> the right combination of skills and would be interested in a temporary
>> position?
>>  
>> We canıt implement the TMS scripting until the directories are restructured,
>> so I want to get this going quickly.
>>  
>> Virginia Vuleta, PMP
>> Deputy Director, IT & New Media
>> Art Gallery of Ontario
>> 317 Dundas Street West
>> Toronto, ON M5T 1G4
>> 416.979.6660 x.244
>>  
>> To unsubscribe, send an email to [log in to unmask] with the
>> following commands in the body of the email:
>>  signoff TMSUSERS
>> 
>>  //  eoj 
>> 
>> You will receive a confirmation that your subscription has been removed. To
>> unsubscribe, send an email to [log in to unmask] with the following
>> commands in the body of the email:
>> 
>>  signoff TMSUSERS
>> 
>>  //  eoj 
>> 
>> You will receive a confirmation that your subscription has been removed.
>> To unsubscribe, send an email to [log in to unmask] with the
>> following commands in the body of the email:
>> 
>>  signoff TMSUSERS
>> 
>>  //  eoj 
>> 
>> You will receive a confirmation that your subscription has been removed.


To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

     signoff TMSUSERS

     //  eoj


You will receive a confirmation that your subscription has been removed.


ATOM RSS1 RSS2