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:
Brent Mitchell <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Fri, 13 Jul 2018 19:17:59 +0000
Content-Type:
multipart/mixed
Parts/Attachments:
text/plain (19 kB) , text/html (13 kB) , image001.jpg (19 kB) , Highlights July 2018~Gallery2.pdf (964 kB)
We've just started using the Exhibitions Module for these PC rotations. We normally title these as Highlights from the Permanent Collection so that's what we're using as the exhibition title for each record. We then put the month and year of when the rotation took place in the SubTitle field to help differentiate the various iterations.

We attach the related objects, and in the Section field (Cataloguing tab) we enter the gallery name/number such as Gallery 4 or East Foyer 3. We have a checklist report that sorts objects by Section so this helps with that report should we need it down the road.

We don't normally have professional photography taken to document our PC rotations (we don't have a staff photographer) so our registrars use an app to document the artwork in the various galleries and then export the images and related notes in a pre-formatted PDF. We then attach a PDF for each gallery to the exhibition record in the Media tab for future reference. I've attached an example of one of these PDFs.

We don't do a lot of these PC rotations so we're hopeful they won't clutter up our Exhibitions Module, but time will tell. Since we've only just begun this process, I'm sure we'll discover some drawbacks (and hopefully some unexpected benefits) as we travel down this road.

Interested to learn what others are doing too!

Brent Mitchell
Head of Exhibition and Collection Management
T:  817.840.2149

From: The Museum System (TMS) Users <[log in to unmask]> On Behalf Of Smith, Jeffrey
Sent: Friday, July 13, 2018 1:15 PM
To: [log in to unmask]
Subject: Re: Tracking rotations in TMS Exhibitions module

We use a single exhibition record for every show, and create multiple venues for each rotation. I repurposed the mnemonic field as "Rotation" so that each repeated venue can be named "Rotation 01", "Rotation 02" etc.

Locations are linked at the venue/rotation level. Not a big deal.

From: The Museum System (TMS) Users <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Meredith L. Steinfels
Sent: Friday, July 13, 2018 11:20 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Tracking rotations in TMS Exhibitions module

Hi TMS-ers,

Writing in to see how everyone tracks their rotations or non-titled exhibitions in TMS (beyond location updates).  Three solutions have been posited so far:


  1.  A single exhibition record per gallery, with a changing list of objects attached to it.  It seems a little burdensome in practice and doesn't account for the frequent changeouts, moveable walls, or multi-gallery hangs, though it's been the front-runner so far.
  2.  A single exhibition record per gallery, made with each rotation. This one seems even more burdensome and could clutter our archives and website.
  3.  Leveraging parent-child relationships in Exhibitions.

If anyone utilizes any of the above, or has a fourth option that I haven't added, I'd love to hear from you (especially those of you who utilize parent-child relationships in exhibitions).

Thanks!
Meredith


Meredith Steinfels
Digital Platforms Specialist
Hood Museum of Art, Dartmouth
6 East Wheelock Street
Hanover, NH 03755
Office    603.646.2664

[final logo for email sigs2 (003)]<https://hoodmuseum.dartmouth.edu/>

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