TMSUSERS Archives

The Museum System (TMS) Users

TMSUSERS@SI-LISTSERV.SI.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Content-Transfer-Encoding:
quoted-printable
Sender:
"The Museum System (TMS) Users" <[log in to unmask]>
Subject:
From:
Jonathan Thristan <[log in to unmask]>
Date:
Thu, 5 Jun 2003 17:36:39 +0100
Content-Type:
text/plain; charset="US-ASCII"
MIME-Version:
1.0
Reply-To:
"The Museum System (TMS) Users" <[log in to unmask]>
Parts/Attachments:
text/plain (88 lines)
Hello!

At Tate we attach Objects to Exhibition records (directly if Tate
collection works or via Loan records if Object records for short term
loans-in to Displays/Exhibitions), as GS suggest, and run reports etc to
retrieve information on Exhibition history.  We record the status of
Objects relative to an Exhibition (agreed, declined, provisional etc) on
the Objects tab of the Exhibition record.  We don't currently use the
Bibliography module.  Secondly, our issue, we wondered whether anybody
has encountered any problems with Object, Exhibition or Loan records
where a Work is borrowed more than once, into different Exhibitions, but
using the same Object record each time (whether problems resulting from
the way TMS functions or from procedures).  

EGs 

if an Object changes hands between the first time it was borrowed and a
second time, then although the correct history of an Object can be
viewed via the Related function, because we display Acquisition related
constituents on Object records, this information doesn't display
correctly to reflect both the present loan and the previous one (I guess
we could simply stop recording Acquisition related Constituent Xref
details for short term loans in...).

If data about an object changes over time i.e. it's re-attributed or its
title is amended, it may be difficult to identify an object that is
currently being considered for loan-in as the same as an Object for
which we already have an Object record. A duplicate object record is
created and the ability to construct a complete exhibition history for
that object becomes problematic.


Regards
Jon

Tate


  



-----Original Message-----
From: Scott Nacke [mailto:[log in to unmask]] 
Sent: 04 June 2003 17:00
To: [log in to unmask]
Subject: Exhibition history


Hello,
I have a question about how others may be documenting exhibition history
and bibliographic data using TMS. It appears there are two ways to enter
this information and here at SAM both ways have been used in the past.

Here's the issue:  In the Documentation tab of the Object record, there
is a text field called "Exhibition History".  Here past exhibitions are
cited for that object.  Then in the Related tab of the Object record,
Exhibitions that were entered in the Exhibition module are listed.
These two fields are not combined. Therefore, one must look in both
places if one wants a complete picture of the exhibition history.  Ditto
for Bibliography.

Gallery Systems says:

                1.      Exhibition history
                        Note: this is not an active field; any relevant
information should be entered in the "exhibitions module." Any
information contained in the field is "legacy data" and must be entered
into its correct field.
                        This information can be accessed by selecting
"Exhibitions" from the "Related" pull-down at the very top of the
computer's monitor. Additionally, This information can be exacted
through the object worksheet and other specialized reports.
                        It Says basically the same thing for
Bibliography data. I am curious to know how others are using these
fields to create accessible data for the exhibition history of an object
in the collection.

Scott Nacke
Assistant Registrar/Image Rights Manager
Seattle Art Museum
100 University Street
PO Box 22000
Seattle, Washington 98122-9700
206.654.3130 Direct
206.654.3135 Fax
[log in to unmask]

ATOM RSS1 RSS2