Here is what we do at the Metropolitan Museum. Feel free to contact me off list if you would like more details.
1. MediaBin 4.5, but currently mid-migration to NetXposure
2. Object tombstone data and object rights data
3. We map fields 1:1 from TMS to the DAMS
4. No conscious effort to conform to a standard, though like Houston, what we ended up with is pretty close to a CDWA record
5. On output we concatenate the tombstone data and embed it into dc:description along with the permanent URL to the object in our online collection. Rights data is also mapped into a few different fields. We also embed the fielded tombstone into a custom XMP namespace that pairs with an Adobe file info panel that we use internally.
The only major change up ahead once our migration to NetXposure is complete is that we'll also be bringing data from the media tables into the DAMS, which will enable us to better sync images from the DAMS to TMS and open up some options as far as potentially using the DAMS to serve the images for our online collection directly (currently TMS serves as something of an intermediary in that process).
Jennie
Jennie Choi
General Manager of Collection Information
Digital Media Department
The Metropolitan Museum of Art
1000 Fifth Avenue
New York, NY 10028
212-650-2424
[log in to unmask]
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Dueker, Peter
Sent: Wednesday, July 15, 2015 3:04 PM
To: [log in to unmask]
Subject: Re: TMS data in your DAMS
Getting data in & out would be my #1 requirement when evaluating a potential DAMS. Any good, modern DAMS should have an accessible and well documented API which makes getting the TMS data in and maintained (updated) a fairly straightforward activity. Also helpful to get data & images out and into TMS, which is a bit more complicated.
1. We still use Extensis Portfolio – we expect to issue an RFP for a replacement sometime late 2015
2. We record basic tombstone information (such as artist, title, classification etc). Data is refreshed nightly based on the object ID.
3. Articulated into individual custom fields. We can concatenate data fields for embedding, but not natively within Portfolio.
4. Not for the DAMS specifically, but when sharing object data with partners we certainly try to be consistent.
5. Yes, but not using Portfolio . We have a public facing image delivery website (images.nga.gov) which embeds metadata in downloads and we embed separately for bulk deliveries of assets to partners like ARTstor .
Peter Dueker
Head of Digital Imaging Services
Division of Imaging and Visual Services
National Gallery of Art, Washington
From: Chad Petrovay <[log in to unmask]<mailto:[log in to unmask]>>
Reply-To: "The Museum System (TMS) Users" <[log in to unmask]<mailto:[log in to unmask]>>
Date: Wednesday, July 15, 2015 at 2:19 PM
To: "[log in to unmask]<mailto:[log in to unmask]>" <[log in to unmask]<mailto:[log in to unmask]>>
Subject: TMS data in your DAMS
Hello all!
I am interested in information from anyone who has integrated TMS with a DAMS for supplying or embedding object related information into either the media record or the media file.
Specifically:
1. Which DAMS are you using?
2. What object information is TMS supplying?
3. Are you articulating your data in different fields, or populating a single field with a tombstone block of text?
4. Are you conforming to a standard, such as Dublin Core, VRA Core, IPTC? If so, which standard?
5. Are you embedding the data into the image files?
Thank you in advance for your feedback. ~Chad
--
Chad Petrovay
TMS Administrator
The Morgan Library & Museum
225 Madison Avenue
New York, NY 10016-3405
T: 212 590-0308
F: 212 768-5697
E: [log in to unmask]<mailto:[log in to unmask]>
To unsubscribe, send an email to [log in to unmask]<mailto:[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]<mailto:[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.