Here at the Morgan, we started by compiling our documentation into PDF documents. This became cumbersome, because we were repeating blocks of text in multiple documents. Stored on a network drive, discoverability was limited, and these were not widely utilized. Additionally, since PDF's are also printable, when people did find them, they wanted to print copies for reference, and were missing critical updates to the documents.

We are currently working on converting our documentation to a wiki, using Dokuwiki. The system allows users to subscribe to articles, so they can be notified when there are updates. Currently we are restricting rights to edit the articles on the wiki, I am also hoping to expand the use of the wiki in the future: creating namespaces for technical server documentation, such as configuration changes to the DBMS, passwords for service accounts, etc. These are currently in text documents on my network drive, but can now be centralized in the wiki, and only accessible to SA's and our IT staff.

Chad Petrovay
TMS Administrator
The Morgan Library & Museum
225 Madison Avenue
New York, NY 10016-3405

T: 212 590-0308

F: 212 768-5697

E: [log in to unmask]

On Wed, Apr 26, 2017 at 11:35 AM, Marin J. Lewis <[log in to unmask]> wrote:

Greetings,

Our collection of TMS cataloging guidelines is growing. We’re interested in how others have made their local guidelines easily accessible to users. We would love to hear about any innovative and particularly effective tools you’ve adopted or have thought of adopting.

Some options we’re considering:

1.       A PDF Binder or Portfolio

2.       A digital publication (PUB HTML5)

3.       An internal knowledge base (Zendesk)

4.       A document sharing software (Evernote)

Has anyone had success with any of the above? Or success with a completely different approach?

Many thanks,

Marin

_______________________________

Marin J. B. Lewis

Collections Information Specialist

Princeton University Art Museum

Princeton, New Jersey 08544

(609) 258-0477 | [log in to unmask]

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.