I’m intrigued by parent-child relationships in collection management systems. In many ways more context is needed in terms of what sort of child is this?
I’m just going to throw out some anecdotal experiences to see if they strike any chords:
1. A Set, e.g. a Tea Service
a. Parent = Virtual Record acknowledging the entire set
i. Object Number: 2015.37
b. Child = individual, physical records for each component of the set
i. Object Number: 2015.37.1-2015.37.105
c. Relationship established from Parent Virtual Record = Child, Part of a Set
d. This also applies to a suit of armor as each component could possibly be displayed individually than as a completed suit.
2. Bound Portfolio
a. Parent = Physical, tangible object record
i. Object Number: 2014.365
b. Child = Intellectual children of the art objects within the bound volume that cannot be separated
i. Object Number: 2014.365.1-2014.365.22
3. Woodblocks and Prints
a. Parent = Woodblock
i. Object Number: 1925.37
b. Child = Print
i. Object Number: 1943.55
Associated components with one object are treated differently and do not receive separate records, but rather component records. That way we have one record for the object, and all associated components pertaining to that object.
1. Jade Figure, associated based is a component
a. Object Number: 1972.35
b. Object Number broken down in Component: 1972.35.1, 1972.35.2
2. Teapot, cover of tea pot is a component
a. Object number, same as above
3. Vessel, associated shared are components (merge components after treatment is complete)
4. Portfolio with a dust case/sleeve (sleeve is the component)
So these are my initial thoughts out loud when thinking about cataloguing objects and associated components and showing their relationship. I hope this stream of consciousness helps to answer some questions, or at least spur the dialogue forward?
Best Regards,
Sarah L. Gillis | Assistant Registrar, Image Management
WORCESTER ART MUSEUM / www.worcesterart.org<http://www.worcesterart.org/>
fifty-five salisbury street / worcester, massachusetts 01609
direct 508.793.4427 / general 508.799.4406
[cid:475C9A79-9E11-4E3F-A83D-C212B0ECE104]
HASSAN HAJJAJ: <http://www.worcesterart.org/exhibitions/hassan-hajjaj/> MY ROCK STARS<http://www.worcesterart.org/exhibitions/hassan-hajjaj/>
November 7, 2015 - March 6, 2016
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Erin McDonald
Sent: Tuesday, February 16, 2016 8:28 PM
To: [log in to unmask]
Subject: Re: Asking a child what their parent's accession number is...
Is there a way to link objects in Child Records? It would be better if it was a hard link to the Parent if that is possible?
We’re discussing this as well.
Erin McDonald - Manager, Art Collections
Arts Branch, Alberta Culture & Tourism
10708 – 105 Avenue, Edmonton, AB T5H 0A1
P: 780-415-0815 C: 780-868-8885
www.affta.ab.ca<http://www.affta.ab.ca/>
[cid:image003.png@01D1696D.1B687F80]
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Chad Petrovay
Sent: Sunday, February 07, 2016 9:19 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Asking a child what their parent's accession number is...
I am looking for some advice on cataloging best practices concerning accession numbers and child records. If an object has related children, do you include the accession number of the parent somewhere in the child record?
For instance, if 2015.2 includes 2015.2.1 through 2015.2.20, do you have the string "2015.2" as an alternate number (or another field) in each of the children?
If so, which field do you use?
If not, how do you determine the accession number of the parent? Through the relationship or as the root of the object number?
Many thanks in advance for your time and consideration. ~Chad
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.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
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.
|
