One more thing to add to the wish list – could the list of numbers in the Object Package window sort themselves out by Object Number instead of by the order they were added to the package? This would make removing objects from the package so much simpler.

Thanks

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Hansen, Stephanie
Sent: Friday, July 30, 2010 3:04 PM
To: [log in to unmask]
Subject: Re: Object Package Names

We have a lot of cross-departmentals too and the staff person who created them is not always relevant (or memorable),  so that could get confusing for us, but the option to bundle some packages by project could work nicely. I’d like to see the object package name field longer and easier to read (Like you did with reports in 2010.)

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]

American Quilts: Selections from the Winterthur Collection

May 22–Sept 6, 2010

Uncover rich stories, hand-stitched into exquisite works of art

More at www.mam.org

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Moxley, Jeri
Sent: Friday, July 30, 2010 1:51 PM
To: [log in to unmask]
Subject: Re: Object Package Names

A great many object packages in our database are cross-departmental, and I think our users would be annoyed by an extra step required in creating new packages – so would be good if any hierarchy were an optional feature.

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Jay Hoffman
Sent: Friday, July 30, 2010 2:48 PM
To: [log in to unmask]
Subject: Re: Object Package Names

That would mean adding department to object packages – at least in the objects module. We are adding packages to other modules which may not have the same concept of department as objects. Would you expect department on object packages to be security related or just for organization?

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Linda Pulliam
Sent: Friday, July 30, 2010 2:45 PM
To: [log in to unmask]
Subject: Re: Object Package Names

By department

Then by staff member

Then by project

Cheers

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Jay Hoffman
Sent: Friday, July 30, 2010 2:41 PM
To: [log in to unmask]
Subject: Re: Object Package Names

I was thinking the same thing. It could be organized by owner, project (a new field), global, etc.  How do you see the hierarchy groupings?

From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Ryan Donahue
Sent: Friday, July 30, 2010 11:27 AM
To: [log in to unmask]
Subject: Re: Object Package Names

We are actually looking at this problem now, folders would be a really welcome addition to object packages (that is to say, a hierarchical organization for object packages).

Our present plan is to expose a web interface for un/archiving object packages on demand (we already have such an interface for transferring object packages to our DAM).

My other thought was to treat global object packages like a communal fridge -- periodically (2x year?) turning all global object packages (with some exception) non-global, and letting people bug my department when they need it (or use the web interface) to turn object packages back on.

-Ryan Donahue

George Eastman House