Hi Jessica,
Would you be willing to share your in-house manual for object packages? We just upgraded and I've started writing a user guide for packages, but if someone else has one that I could use for a reference it would be incredibly helpful. The new packages are so much more robust that I am afraid I am going to miss some important detail and everyone will have a mental breakdown when their object packages don't do what they want!
Thanks,
Amber
the warhol:
Amber E. Morgan
Associate Registrar
117 Sandusky Street
Pittsburgh, PA 15212
T 412.237.8306
F 412.237.8340
E [log in to unmask]
W www.warhol.org<http://www.warhol.org/>
The Andy Warhol Museum
One of the four Carnegie Museums of Pittsburgh
Email newsletter http://members.carnegiemuseums.org/email
Membership http://members.carnegiemuseums.org/SupportCMP
warhol: facebook<http://www.facebook.com/thewarholmuseum> | warhol: twitter<http://www.twitter.com/thewarholmuseum>
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Milby, Jessica
Sent: Wednesday, February 13, 2013 5:18 PM
To: [log in to unmask]
Subject: Re: 2012 object packages
Prior to the TMS2012 upgrade, we had a system of naming global packages with department abbreviations as prefixes. Now, we are using the new functionality to move those packages into departmentally named global folders instead. By the way, TMS 2012 uses "public" for "global"--potentially confusing, but you can change it.
After the upgrade, your global packages become shortcuts in the main global/public folder and the list is frustratingly long if you have a lot of users. Breaking up the global packages into department folders started us on the road to reorganization. We also use shared folders (accessible only to designated users) for specific projects to cut down on the always growing global list.
There is a glitch in the searching across modules though. If you plan on using a shared or global package that is not living in your personal folder (with a shortcut pasted into public/global/shared folder) then it will not be searchable from other modules.
If that sounded ridiculously confusing, feel free to email me off list. We've already produced an in-house manual for PMA users. They were almost universally confused post-upgrade.
I think there's more potential in the shared packages, but this is as far as we've gotten.
--Jessica
Jessica Milby
Collections Information Project Manager
Philadelphia Museum of Art
215-684-7283
[log in to unmask]<mailto:[log in to unmask]>
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Smith, Jeffrey
Sent: Wednesday, February 13, 2013 4:42 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: 2012 object packages
Thanks, Stephanie.
I'd like to hear about that too, since we're almost about to upgrade. How are folks using the new package folders for workflow? Any tips to make the new format work with old package habits?
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Hansen, Stephanie
Sent: Wednesday, February 13, 2013 4:39 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: 2012 object packages
Hello TMSers,
I'm looking for thoughts on organizing the package folders in TMS 2012. Our package list became a bit messy over the years and I would like to tidy it up now that that we can structure a bit more with the folders. Anyone have examples they are willing to share on how they manage packages?
Thanks!
Stephanie
--
Stephanie Hansen
Rights & Reproductions / Database Administrator
Milwaukee Art Museum
700 N. Art Museum Dr. | Milwaukee, WI 53202
Tel. 414.224.3268 | Fax. 414.271.7588 | [log in to unmask]<mailto:[log in to unmask]>
OPENING FEB 22
COLOR RUSH
75 YEARS OF COLOR PHOTOGRAPHY IN AMERICA
More at www.mam.org<http://www.mam.org/>
Kids 12 and under are FREE
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]<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]<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.
The information contained in this message and/or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. Any views expressed in this message are those of the individual sender.
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.
|
