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:
"Welsh, Sylvia C." <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Wed, 14 Feb 2018 14:54:33 +0000
Content-Type:
multipart/related
Parts/Attachments:
text/plain (16 kB) , text/html (10 kB) , image001.jpg (16 kB)
Hi Fatima,

We use the Events module to track construction and related projects that occur in the buildings (Sites) that we manage the architectural archives for. It is great way for us to organize our information in a way that helps to track the chronology of activities in a Site. We include information about the scope of the work, the constituents involved (Architecture & Engineering firms), and notes related to the acquisition and processing of the materials.

We think the module could be even more robust though as it has no direct relation to the Sites.

It has been great to learn about how others are using the module.

Sylvia,

_____________________________
Sylvia Welsh, MS LIS, CSI, LEED AP BD+C

Harvard Property Information Resource Center
1350 Massachusetts Avenue, 547
Cambridge, MA 02138
T 617-496-8275  F 617-495-0559

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Julie Thies
Sent: Wednesday, February 14, 2018 9:40 AM
To: [log in to unmask]
Subject: Re: Uses for the Events Module

Hi Fatima,
We use the event module to track visiting scholars, photo sessions, gallery rotations, collections committee, outgoing loan invoicing and in development to track courier trips.
We can link the objects looked at by scholars and link any paperwork for their visit, as well as any paperwork they provide us when their research is done.
We do not have an on-staff photographer, so we can track when the photo session is occurring and which objects are expected to be photographed. Imaging services then uses that record to track when the images are received and processed by them.
Our gallery rotations are typically quarterly. We'll switch a few pieces here and there for light exposure limits, outgoing loan requests, conservation, etc. We use sub event 1 to track if the work is coming in or out and use the remarks for notes about conditions, mounts, etc.
For the Collections committee we can link the objects up for possible accession. We can also link documents from the meeting.
Outgoing loan invoicing uses the flex fields for our invoice amounts.
Using it for couriers is still a work in progress, but uses flex fields and attributes for details.

I feel the event module has many possible uses and those uses would be wider and greater if the event module linked directly to all the other modules, like the media module. It would also be beneficial to have more fields available at the object level, such as flex fields and text entries.

Good luck.
Julie

Julie Thies
Head of TMS Administration
The Menil Collection
713-525-9468

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Mahdi, Fatima (VMFA)
Sent: Tuesday, February 13, 2018 5:00 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Uses for the Events Module

Hello everybody! I'd love to know what people are doings with the Events module. The only thing that anyone has done with ours is to record some old deaccession events, but I am sure there are more creative uses than that!

Fatima Mahdi
Collections Information Specialist/TMS
[VMFA-web-sig]
Virginia Museum of Fine Arts
200 N. 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]<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