Content-Type: |
multipart/alternative;
boundary="_000_BL0PR12MB245127C0699A19ACF4FD420ACF710BL0PR12MB2451namp_" |
Date: |
Thu, 30 Jul 2020 19:34:16 +0000 |
Reply-To: |
|
Subject: |
|
From: |
|
Message-ID: |
|
In-Reply-To: |
|
MIME-Version: |
1.0 |
Sender: |
|
Parts/Attachments: |
|
|
One thing I do to cut down on Public Package Bloat is secretly move object packages to the user who made them, especially if I know the purpose has already been served. No one has gotten mad at me...yet 🙂
________________________________
From: The Museum System (TMS) Users <[log in to unmask]> on behalf of Mahdi, Fatima <[log in to unmask]>
Sent: Thursday, July 30, 2020 3:00 PM
To: ListServ tmsusers <[log in to unmask]>
Subject: Object Package Explorer Management?
External Email - Exercise Caution
Hello, fellow TMSers!
With the number of our packages ever increasing and the names of the packages mostly unintelligible, I am wondering what rules and procedures other institutions have put in place about object package naming, how and when to delete/retire old packages, and/or the creation and management of shared and public folders.
Thanks muchly,
Fatima
--
Fatima Mahdi
Collections Information Specialist/TMS
Virginia Museum of Fine Arts
200 N. Arthur Ashe Boulevard
Richmond, VA 23220-4007
T 804.340.1443
[log in to unmask]<mailto:[log in to unmask]>
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.
|
|
|