Hmmm! I never thought of that. Thanks for the suggestion!
David
From: The Museum System (TMS) Users [mailto:[log in to unmask]]
On Behalf Of Chad Petrovay
Sent: Thursday, September 08, 2011 4:08 AM
To: [log in to unmask]
Subject: Re: Limited number of containers in advanced query
David,
Have you tried including another field in the search to help drill down? For instance, in the ObjGeography.Country field we had almost every country in the world, but if you searched for "North America" in Object.Department first, when
you selected ObjGeography.Country the distinct list was "Canada; The Bahamas; USA" (only the Countries that met the first Criteria).
The crate numbers use three fields to create unique identifiers, including Project and Crate Number (at the moment the third is eluding my memory). Perhaps you can use these two fields in conjugation with one another to help create smaller
distinct lists.
I hope this helps. ~Chad
On Wed, Sep 7, 2011 at 8:58 PM, Diane Lee <[log in to unmask]> wrote:
I would be interested in this as well as we’ve just started to do something similar, and I’d like to be
able to troubleshoot any problems before they come up.
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 Aylsworth, David
Sent: Wednesday, September 07, 2011 1:00 PM
To: [log in to unmask]
Subject: Limited number of containers in advanced query
We’ve run into a problem that hopefully one of you brilliant people out there has solved already.
We very heavily use the linked containers in the locations fields as a way of tracking location changes for photographs
and works on paper. Each container will have 10-20 individual works on paper housed inside, and the links work great in TMS to identify which box the pieces are in.
When we search for the contents of a certain box, the advanced query tool works great for looking for all of the
contents of a given box by having the query set to search a distinct list in queries.
BUT while set to search a distinct list, we currently cannot search for any container number that is named anything
alphabetically greater than D:NATIVE AMERICAN 5. And if a box got added that is named something alphabetically lower than this, this will be bumped off of the displayed distinct list.
This has caused us to do all sorts of workarounds—none of which are at all satisfying—mostly involving creating
object packages for the boxes. Changing the query to NOT search by distinct list would cause problems too, since so many of the box names are named similarly.
Am I describing my problem clearly enough? Can we expand the number of boxes that would display in the advanced
query?
Thanks for any advice you have.
David
David Aylsworth
Collections Registrar
Museum of Fine Arts, Houston
P.O. Box 6826
Houston, TX 77265-6826
telephone:
713-639-7824
fax:
713-639-7780
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.
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.