We use our API to generate our large print labels, which are available on our collections site, although the same format isn’t carried over to the exhibitions page (not sure why – it seems like it could be).  An example of the labels can be seen here:  https://collection.cooperhewitt.org/exhibitions/907219083/large-print?pt=18

 

Similar to Jeff, we use text entries, although we divide them between the exhibition and object records per attached.

 

If we have didactic materials such as infographics or videos, we create an object record for it and include it as part of the exhibition objects (which is required anyways for our design team), an example here:

 

https://collection.cooperhewitt.org/objects/420556713/

 

For videos that relate directly to an object, we include that as media in the object record.

 

Hope this helps!

 

 

Wendy Rogers, Head of Registrar

phone: 212.849.8433
[log in to unmask]
cooperhewitt.org | Twitter | Instagram | Facebook | YouTube


Cooper Hewitt, Smithsonian Design Museum

2 East 91st Street

New York, NY 10128

 

<a href=[log in to unmask]">

 

NatureCooper Hewitt Design Triennial

On view through January 20, 2020

 

Nature by Design: Selections from the Permanent Collection

Ongoing

 

 

 

From: The Museum System (TMS) Users <[log in to unmask]> On Behalf Of Smith, Jeffrey
Sent: Friday, July 12, 2019 8:55 AM
To: ListServ tmsusers <[log in to unmask]>
Subject: Re: Drawing Exhibition data from TMS to website

 

For many years, I was able to produce a report for our Docents (and for archival purposes) that reproduced the entire text for a show - including object text. To do this, I simply stored the text in the Exhibition text entries, and made the text for each thematic section link by means of the TextEntries.Purpose field.

 

It worked beautifully, and I believe could be ported to the web using the same data relationships. I would love to try it, and hope some of you are successful – it could be very dynamic.

 

The resulting PDF of the exhibition text was then saved as a media file linked to the exhibition record.

 

Attached is a screen shot of the subreport links, plus the report itself, if it can be helpful to reverse-engineer for anyone wanting to explore this possibility.  An actual report is also attached as an example.

 

 

 

-----Original Message-----
From: The Museum System (TMS) Users <[log in to unmask]> On Behalf Of Frances Lloyd-Baynes
Sent: Thursday, July 11, 2019 3:20 PM
To: ListServ tmsusers <[log in to unmask]>
Subject: Drawing Exhibition data from TMS to website

 

Hi Everyone,

 

About this time last year I mentioned that Mia is working out how to use TMS to feed exhibitions information - description, didactics, object labels, images - to our website. We had to put things on hold for a while, but are back to work on it this summer.

 

My colleagues and I are curious whether any of you are doing this --recreating exhibition content not necessarily to reflect the physical exhibition, but the conceptual exhibition of main didactic/wall panels, sub-panels, object labels, etc. If you are, we'd love to hear where you're putting your data and how you are linking then extracting it. (We are aiming to use a variety of TMS record types, establish relationships between them, and channel the data from TMS to the website via our API.)

 

Please get in touch if you are willing to share your thoughts on this. We'd also be interested to hear of good examples out there online that we should look at (i.e. online exhibitions rather than digital exhibition catalogs).

 

Thank you!

All the best,

 

Frances

 

--

Frances Lloyd-Baynes  |  Head of Collections Information Management Minneapolis Institute of Art

2400 Third Avenue South, Minneapolis, MN 55404

+1.612.870.3189  |  [log in to unmask]  |  artsmia.org

 

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.

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.

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.