Hi Hilde,

I'm curious if you've had many responses to this question.  We recently ran into this issue, with a tea set actually, and I ended up changing the records from components to a parent-child record relationship, with the whole set being the parent.  

The usual process here was to create components for pieces of a set that were being shipped separately or to different locations from the rest.  It was fine for tracking movement, but that's it. Otherwise I feel like components tend to create unnecessary confusion and hassle, particularly with less-proficient TMS users. I think we overuse them.

I'd be interested in seeing some nice clear data entry standards for the use of components if anyone has some they'd be willing to share.  It seems to me they should be created only for separable parts of objects, that would likely never be exhibited on their own, for example the lids of containers.  This definition tends to expand over time though, and that causes problems!

Bon vendredi indeed!

Cheers,
Nicola

 



Nicola Astles
Museum Content and Technology Administrator
New-York Historical Society
170 Central Park West
New York, New York 10024
212-873-3400 x338

On Fri, Jun 5, 2015 at 7:41 AM, Bélanger Ariane <[log in to unmask]> wrote:

We are interested here also!

 

Ariane Bélanger

Technicienne en muséologie, Service de la conservation des collections patrimoniales

Direction du dépôt légal et de la conservation des collections patrimoniales

Description : Description : Sigle BAnQ  Description : Description : Icône Facebook  Description : Description : Icône Twitter  Description : Description : Icône YouTube  Description : Description : Icône Historypin

 Livre

 

BAnQ Rosemont-La Petite-Patrie

2275, rue Holt

Montréal (Québec)  H2G 3H1

Téléphone : 514 873-1101 poste 3632

[log in to unmask]

www.banq.qc.ca

 

 

Avis de confidentialité

Ce courriel est une communication confidentielle et l’information qu’il contient est réservée à l’usage exclusif du destinataire. Si vous n’êtes pas le destinataire visé, vous n’avez aucun droit d’utiliser cette information, de la copier, de la distribuer ou de la diffuser. Si cette communication vous a été transmise par erreur, veuillez la détruire et nous en aviser immédiatement par courriel.

 

De : The Museum System (TMS) Users [mailto:[log in to unmask]] De la part de Hilde Bøe
Envoyé : 9 mars 2015 07:02
À : [log in to unmask]
Objet : Linking components to exhibitions/loans?

 

Hello all,

 

Would anyone like to share their best practices for loaning out, or exhibiting, a single component within an object record? For example, loaning out only the teapot from a tea set, where each piece of the set is defined as a component within the tea set object record.

 

Our case is what we call modern copies of Munch’s own photos where we can have several physical copies of a Munch original, and all copies are registered under the same object number. When one of these copies is included in an exhibition or a loan we would of course want to link the single component and not the whole record to the exhibition or the loan. It seems that TMS doesn’t allow this kind of component/object separation for the purposes of loans and exhibitions. We use TMS 2012.

 

Perhaps the only answer is to avoid creating components for sets where loans like this are a possibility, but I’m curious to know how others have approached this.

 

Kind regards,

 

HILDE BØE
Digital samlingsforvalter | Digital Collection Manager

 

MUNCHMUSEET | THE MUNCH MUSEUM

+47 97787931
[log in to unmask] |
munchmuseet.no | stenersenmuseet.no | emunch.no

Følg oss på | Follow us on Facebook | Twitter

 

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.