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
Sender:
"The Museum System (TMS) Users" <[log in to unmask]>
Subject:
From:
Jonathan Thristan <[log in to unmask]>
Date:
Fri, 4 Oct 2002 11:13:11 +0100
Content-Type:
text/plain
MIME-Version:
1.0
Reply-To:
"The Museum System (TMS) Users" <[log in to unmask]>
Parts/Attachments:
text/plain (67 lines)
I guess creating a custom report is one way to solve the problem, but it
would be good if a report bundled with TMS, that's designed to show current
location, actually did that. It wouldn't be a big change for GS, whereas not
all institutions have the resources, in-house, to do this.
 
The glitch may be caused by your use of TMS. If you're recording a
retrospective move, use the 'Historical' transaction type - TMS disregards
these when calculating the current location of objects - the report should
be designed in a similar way. Not sure from your posting whether you're
doing this.
 
Regards
 
Jon Thristan
Tate
Systems Manager
 
call +44 (0) 20 7887 8983
email [log in to unmask]
 
 
-----Original Message-----
From: Danielle Uchitelle [mailto:[log in to unmask]]
Sent: 03 October 2002 20:52
To: [log in to unmask]
Subject: Re: Accurate location Reports
 
 
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