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:
Chad Petrovay <[log in to unmask]>
Reply To:
The Museum System (TMS) Users
Date:
Fri, 12 Aug 2011 00:12:55 +0300
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (5 kB) , text/html (21 kB)
Alexis,

With Parent-Child relationships, I try to make the terminology of the parts
parallel:

Set - Part of a Set
Framed Artwork - Frame
Ensemble - Part of an Ensemble

Displays like this in TMS:

Ensemble
Framed Artwork
Set
-------------
Frame
Part of an Ensemble
Part of a Set

In my experience, even when you have clearly defined relationships written
up, people don't always reference them, so making the relationship labels
mirror one another helps to clarify their relationships with one another.

~Chad

On Thu, Aug 11, 2011 at 9:30 PM, Diane Lee <[log in to unmask]> wrote:

>  Oh, and I haven't been using the Group Completeness.  I started to with
> the Constituent relationships, but it seemed like everything would be
> incomplete so it wouldn't be all that useful. And given the type of
> Object-Object relationships we are now doing it didn't seem relevant. ****
>
> ** **
>
> ** **
>
> D. ****
>
> ** **
>
> ==========================================****
>
> *Diane Lee*, Collections Manager   860-236-5621 x242****
>
> *Connecticut Historical Society*****
>   ------------------------------
>
> *From:* Diane Lee [mailto:[log in to unmask]]
> *Sent:* Thursday, August 11, 2011 2:26 PM
> *To:* 'The Museum System (TMS) Users'
> *Subject:* RE: Linking Object Records****
>
> ** **
>
> I would be interested in what others are doing as well. We use the linking
> primarily in the Constituents module for actual family relationships between
> constituents, such as: ****
>
> Ancestor - Descendant****
>
> Aunt - Nephew****
>
> Aunt - Niece****
>
> Business - Business****
>
> Father - Daughter****
>
> Father - Son ****
>
> ** **
>
> ...and so on. (Family relationships between Constituents are very useful
> considering the types of collections we have.)****
>
> ** **
>
> For Objects we previously had a Parent/Child linking structure set up just
> as****
>
> Related Object - Related Object, ****
>
> ** **
>
> but I've been working on changing those to a See Also link just as Object -
> Object since the objects aren't really related in a Parent/Child structure,
> but just as something that relates to another object in the collection on an
> equal level.  I would like to expand the See Also links, as I think they
> could be useful, so any ideas are welcome, along with seeing what others are
> doing with the Parent/Child for objects. ****
>
> ** **
>
> Diane. ****
>
> ** **
>
> ==========================================****
>
> *Diane Lee*, Collections Manager   860-236-5621 x242****
>
> *Connecticut Historical Society*****
>   ------------------------------
>
> *From:* The Museum System (TMS) Users [mailto:[log in to unmask]]
> *On Behalf Of *Linda Pulliam
> *Sent:* Thursday, August 11, 2011 12:50 PM
>
> *To:* [log in to unmask]
> *Subject:* Re: Linking Object Records****
>
>  ** **
>
> Hi Alexis,****
>
> ** **
>
> These are our Parent/Child pairs:****
>
> ** **
>
> *Parent-Child*
>
> Accessories-Accessories****
>
> Exhibit case-Works of art****
>
> Final-Prep for final****
>
> Mold-Cast****
>
> Object-Accessory****
>
> Object(s)-Crate****
>
> One of pair-One of pair****
>
> Original-Reproduction****
>
> Part of set-Part of set****
>
> Part of whole-Part of whole****
>
> Print-Printing surface****
>
> Recto-Verso****
>
> Same object-Same object****
>
> Shared history-Shared history****
>
> Virtual object-Real object(s)****
>
> ** **
>
> We do not use the Association Assistant.****
>
> ** **
>
> Good luck with your project.****
>
> ** **
>
> Linda, MFA****
>
> ** **
>
> ** **
>
> *From:* The Museum System (TMS) Users [mailto:[log in to unmask]]
> *On Behalf Of *Lenk, Alexis
> *Sent:* Thursday, August 11, 2011 12:27 PM
> *To:* [log in to unmask]
> *Subject:* Linking Object Records****
>
> ** **
>
> Hello,****
>
> ** **
>
> I've recently been rethinking the linking structure between object records
> in our TMS and I was wondering if anyone would be willing to share the list
> of relationships they are currently using? I'm interested mainly in the
> language being used and how specific other users are being with their links.
> I'm also curious to know if anyone is making use of the "Group
> Info/Completeness" section of the Association Assistant (setting  the links
> to "complete", "incomplete", "not relevant" or "mixed")?****
>
> ** **
>
> Any examples would be appreciated. Thanks****
>
> ** **
>
> Alexis Lenk****
>
> TMS Administrator****
>
> 617-384-6762****
>
> [log in to unmask]****
>
> ** **
>
> Harvard Art Museums****
>
> 32 Quincy Street, Cambridge, MA 02138****
>
> www.harvardartmuseums.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.
>
>

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