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:
Danielle Uchitelle <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Thu, 3 Oct 2002 15:52:19 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
Margie,
 
Simplest solution is to create a custom report that shows the location
corresponding to the most recent move date for each object.
 
--Danielle Uchitelle
Solomon R. Guggenheim Museum
 
-----Original Message-----
From: "Gill, Margie" <[log in to unmask]> 
Sent: Thursday, October 03, 2002 3:34 PM
To: [log in to unmask]; [log in to unmask]
Subject: Accurate location Reports
 
 
I am re-visiting a problem which was discovered during the
implementation/testing phase of TMS, and we have found recently that the
problem still exists.  That is, when running a location report, the
systems
pulls from the most recent date the location MOVE was recorded, not the
date
of the MOVE.  A location change was recorded 4/10/2002 for a MOVE which
took
place on Dec. 5, 2001 (the object's current location)  Another slip was
recorded two days later on 4/12/2002 for a previous MOVE on Nov. 8,
2001. 
Therefore, the system draws from the 4/12/2002 date as the most recent
MOVE &
current location, which is inaccurate.  
 
Jeri was going to look into this problem so please check with her.  I am
sending this out to TMS UsersListServ to see if anyone else is having
this
problem & might have a solution.
 
Thanks,
Margie Gill
Registrar of Collections
The Colonial Williamsburg Foundation
P. O. Box 1776
Williamsburg, Virginia 23187
757-220-7519
Fax: 757-565-8752
email: [log in to unmask]

ATOM RSS1 RSS2