Dear fellows-users,

 

I join Rupert on his comments regarding changing spaces over time.

Deactivating old spaces equals for me to delete in a huge part the history of our collection and museum. And of course I can’t subscribe to this.

 

Idem for the complexity of codes for spaces used by other departments.

Here’s an example of what we managed to do for publication on our web site when rooms are open:

 

But no history is made possible by this system.

 

Did anyone use the Site module to track and document former buildings as a musée du Jeu de Paume or musée du Luxembourg who were our predecessors or a former collection as the flat of Mr. Durand-Ruel decorated by some of our works in his time?

Thanks for your returns,

Elsa

 

 

 

 

Hi All

 

Enhancing Locations is still under review at Gallery Systems. It’s quite a complicated area and there are lots of different perspectives to take into account. Perhaps the ‘Ideas’ area of the Community Portal would be a good way to find out more about how others would like to see this area of TMS and the Web Suite of products enhanced? Ideas can be submitted and up-voted etc. Rupert, perhaps you could add your proposal? Or I could do this, if you wish, copying the outline you provided to me – please let me know.

 

Best wishes

Jon

 

 

EXTERNAL: Do not click links or open attachments if you do not recognize the sender.

Dear Renee

 

Apologies for coming to this late; it is, however, a question that’s’ been vexing me for some time, as we potentially have location records for our collection going back to the mid-nineteenth century – and our rooms have changed their names / numbers (never mind physical spaces being reconfigured) several times since then. I find TMS’s inability to log location name changes over time frustrating, and this has led to multiple location entries for the same physical space having been set up and deactivated as they have changed name and function over the years; to my mind, this is Just Wrong.

 

Different departments also refer to the same space in  different ways, although we do have a system of space codes used on our building plans. But one space can be covered by multiple codes, depending upon how the space was originally configured; and of course we have the problem of spaces which ceased to exist before the codes were first allocated.

 

So I’ve implemented a kludge: I use the Flex Fields in the location authority to store all relevant space codes for the particular location. I put the code in the Value field, and the date at which that space name (which is what our location records actually represent) was first allocated to the code in the Date field. We’re using this to join TMS data to our Artifax room booking system, so that we can pull back whether or not a room is closed for our website (implementation pending, but the joins are currently live in our middleware).

 

I discussed this all a while back with Nicola Astles at the New-York Historical Society and Cathryn Godwin at Princeton. I sent a fairly detailed proposal for how to extend the current data structure to accommodate historical location names and changing space configurations to Jon Thristan in September 2017; no doubt, if he’s reading this, he will let us all know what stage that proposal has reached …

 

Best wishes

 

Rupert

 

 

 

 

Good Morning TMS Users,

 

We are beginning to thinking about how location areas are numbered due to a construction project.  Are blueprint numbers incorporated as part of the location name?  How are previous blueprint numbers tracked?  Has anyone encountered renumbering entire floors?  All ideas are appreciated.

 

Thanks!

Renee

 

Renee Bomgardner
Database Standards Administrator

t 215-684-7288
f 215-235-0035

Philadelphia Museum of Art
PO Box 7646, Philadelphia, PA 19101-7646
www.philamuseum.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.