Loving the screen shots and all the different ideas from everyone! Is anyone using the Registration>Handling Notes for any of this? I’ve been trying to figure out the best way to use this field, but you wouldn’t know there is a note there unless you actually go into it, or create a status flag.
I’m liking some of these other ideas much better actually.
==================================================================
Diane Lee | Collections Manager
[log in to unmask] | (860) 236-5621 x(242)
Connecticut Historical Society | One Elizabeth Street | Hartford, CT 06105 | www.chs.org
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Kate Blanch
Sent: Wednesday, July 16, 2014 9:06 AM
To: [log in to unmask]
Subject: Re: tracking installation requirements
Hi Cathryn,
We track requirements that are specific to the object but could apply to any exhibition, loan or installation as an object text entry. This allows us to “reuse” installation requirements that might have been recorded for a previous loan to an upcoming exhibition, in addition to being able to see a chronological view of how Loan Conditions, for example, have changed over time.
The text entry types that we use at the object level are Loan Conditions, Handling Requirements, Storage Requirements, Mount and Cradle Information, Travel Restrictions. Loan Conditions stores light levels, silica gel, case/vitrine requirements.
The most recently dated text entry for an object is pulled onto the exhibition checklist reports. Here’s an example from an object record:
On the exhibition object level, we repurposed (renamed) a big text field to serve as Installation Notes. Here we store installation needs specific to that exhibition. See Installation Notes at the bottom of the Cataloguing card below.
Kate Blanch
Administrator, Museum Databases
[log in to unmask] / 410.547.9000 ext. 266
The Walters Art Museum
600 N. Charles Street, Baltimore MD 21201
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of TMSUSERS automatic digest system
Sent: Tuesday, July 15, 2014 5:00 PM
To: [log in to unmask]
Subject: TMSUSERS Digest - <first ever> to 15 Jul 2014 (#2014-1)
|
|
Browse the TMSUSERS online archives. |
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.
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.