TMSUSERS Archives

The Museum System (TMS) Users

TMSUSERS@SI-LISTSERV.SI.EDU

Options: Use Monospaced Font
Show Text 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:
Ryan Donahue <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Fri, 19 Jun 2009 14:38:08 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (101 lines)
For clarification, our DAM's generated thumbnails do not get imported  
into TMS, they are regenerated by the Thumbnailer plug-in.

We could, theoretically, use the same thumbnail, but building that  
bridge seems a like a lot more work than just generating new thumbnails.

The workflow is essentially:

	 <--Images---
TMS                       DAM
	-----Data---->

The Images flow to TMS by the following:

0. Creation of collection in the DAM (DAM's "Object Package")
1. Export collection from DAM (to .CRE file, and asset action to  
resize for TMS and store it in the proper location)
2. Convert Cumulus CRE file to format Media Loader can understand (via  
excel import into the access DB)*
3. Run Media Loader plugin
4. Run Thumbnailer plugin

The data flows FROM TMS to the DAM
0. Create an object package of things that need data, or all data if  
its a total refresh
1. SQL call to a view on the DB, which gets exported as a delimited  
file [we often move 10,000 objects at a time.. too big for object  
packages in our experience].
2. Convert SQL output to .CRE*
3. Import CRE into DAM to update necessary records.

To seamlessly integrate this workflow, we had to develop a cohesive  
file naming scheme that is an extension of our accessing scheme.

Its certainly not without pain, but it didn't cost us a ton of money  
either.

If anyone is interested in what we did in more detail, I'd be happy to  
share what I can.

-Thanks
Ryan



*Using an internally developed data migration tool.


Ryan Donahue
Manager of Information Systems
George Eastman House
International Museum of Photography and Film

[log in to unmask]
585.271.3361 ex386





On Jun 19, 2009, at 12:45 PM, Chad Petrovay wrote:

> If you DAMS is auto-generating the thumbnails, what is their length  
> on the long side?
>
>
> 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
>
> http://www.petrovay.com/tmsblog
>
> From: The Museum System (TMS) Users [mailto:[log in to unmask] 
> ] On Behalf Of Ryan Donahue
> Sent: Wednesday, June 17, 2009 1:26 PM
> To: [log in to unmask]
> Subject: Thumbnailer woes...
>
> So we've worked out a lot of the kinks in our workflow between our  
> DAM and TMS for image exchange.. we have the DAM exporting asset  
> information into csv, from which it flies to TMS via the Media  
> Loader plugin.. but we've noticed that our thumbnails are getting  
> slightly cut off on the right edge.. it appears that the thumbnail  
> is not cut off, but display in the data entry window is a bit.. it  
> doesn't seem to be an issue with our old thumbnails.. any thoughts?
>
> -Thanks
> Ryan Donahue
> Manager of Information Systems
> George Eastman House
> International Museum of Photography and Film
>
> [log in to unmask]
> 585.271.3361 ex386
>
>
>
>
>

ATOM RSS1 RSS2