TMSUSERS Archives

The Museum System (TMS) Users

TMSUSERS@SI-LISTSERV.SI.EDU

Options: Use Monospaced Font
Show HTML 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:
"Morgan, Rob" <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Mon, 5 Oct 2020 18:53:15 +0000
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (2033 bytes) , text/html (7 kB)
Hello Fatima,

We did a similar upgrade, TMS 2012 to 2018.

The biggest change I remember is LoanObjStatus is no longer in the LoanObjXrefs table (that field is now LoanObjStatus_OLD).  There is now a LoanObjStatuses table with a LoanObjStatusID, etc.  This is true for AltNumDescriptions too (in 2020, there is an AltNums.Description_OLD field and a new AltNumDescriptions table).  Quite a few reports needed to be rewritten due to these changes.  If you have reports with the aforementioned fields, they will no longer work with the new, 2020 data structure.


  *   Rob Morgan

IT Specialist in Data Management and Systems Administration

Office of the Chief Information Officer

Smithsonian Institution

From: The Museum System (TMS) Users <[log in to unmask]> On Behalf Of Mahdi, Fatima
Sent: Monday, October 5, 2020 2:37 PM
To: ListServ tmsusers <[log in to unmask]>
Subject: Issues to look for in TMS upgrades?

External Email - Exercise Caution
Hello folks!

We are upgrading from TMS 2012 to TMS 2020. Happy Day!

We are getting ready to review the test instance, and I am not sure what I should be looking out for. What issues have other institutions come across as they upgrade? Any other suggestions of things to keep an eye on?

Thanks muchly,

Fatima

--

Fatima Mahdi
Collections Information Specialist/TMS

Virginia Museum of Fine Arts
200 N. Arthur Ashe Boulevard
Richmond, VA 23220-4007
T 804.340.1443

[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] with the following commands in the body of the email:

     signoff TMSUSERS

     //  eoj


You will receive a confirmation that your subscription has been removed.

ATOM RSS1 RSS2