TMSUSERS Archives

The Museum System (TMS) Users

TMSUSERS@SI-LISTSERV.SI.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"The Museum System (TMS) Users" <[log in to unmask]>
Subject:
From:
"Milby, Jessica" <[log in to unmask]>
Date:
Fri, 30 Jul 2010 11:18:04 -0400
Content-Type:
multipart/alternative; boundary="----_=_NextPart_001_01CB2FFA.6897D81C"
MIME-Version:
1.0
Reply-To:
"The Museum System (TMS) Users" <[log in to unmask]>
Parts/Attachments:
text/plain (2739 bytes) , text/html (15 kB)
I like that expiration date concept!

 

We encourage users to prefix their non-global packages with their
initials but require that they prefix global packages with their
department or project acronym.  This works insofar as it keeps them
organized, and it alleviates some of the frustration of the very very
long list of all packages.

 

--Jessica

 

 

__________________________________
Jessica Milby 
Collections Information Project Manager 
Philadelphia Museum of Art 
Phone: 215-684-7283 
Fax: 215-235-0035 
[log in to unmask]

 

From: The Museum System (TMS) Users [mailto:[log in to unmask]]
On Behalf Of Chad Petrovay
Sent: Thursday, July 29, 2010 2:23 PM
To: [log in to unmask]
Subject: Re: Object Package Names

 

We're facing the same problem here as well. We have 1059 Object
Packages, with 487 set to Global. I've recently sent a list of Object
Packages to each user (where that user is listed as the owner), asking
users to identify packages aren't required any more. They're given the
option to keep, delete or archive the package. If a package is archived,
the owner is changed to "ARCHIVED" and Global is set to 0.  (We have
since archived 238 packages, and deleted 50 packages - and we're not
finished cleaning up yet).

 

We're thinking about asking users to add notes to all packages,
including what the Object Package is  and when it will expire (therefore
deleteable).

 

As to a naming convention, we do not have one, although I encourage
users to prepend their initials to the name so they can quickly identify
their own packages. I also mention to Bob Farrell that I think Object
Packages should be organized like Reports are organized, so that we
don't end up with one continuous list of them. I'm hoping this becomes a
feature in an upcoming release.

 

 

Chad Petrovay  |  Collections Database Administrator
MIM-Musical Instrument Museum | 4725 E. Mayo Boulevard  | Phoenix, AZ
85050 
480.478.6000 main  |  480.478.6058 direct | 480.471.8690 fax  |
www.themim.org

 

Blog: www.petrovay.com/tmsblog

 

 

 

From: The Museum System (TMS) Users [mailto:[log in to unmask]]
On Behalf Of Jeanne Noonan
Sent: Thursday, July 29, 2010 10:39 AM
To: [log in to unmask]
Subject: Object Package Names

 

Hello all-

 

Does anyone out there have naming conventions or standards for object
package titles?

I, and my users, are tired of looking at a long and disjointed list.

I've come up with a few ideas, but I'd love to hear what everyone else
does!

 

 

Thanks in advance,

Jeanne

 

 

*************************

Jeanne Noonan

Associate Registrar

Chrysler Museum of Art

245 West Olney Road

Norfolk, VA  23510-1509

Phone 757-333-6275

Fax 757-664-6201

http://www.chrysler.org/ 

FREE ADMISSION to our permanent galleries!

 

 

 

 



ATOM RSS1 RSS2