usenix conference policies
Designing, Developing, and Implementing a Document Repository
Our company had grown large enough and complex enough to require a centralized repository for its documentation. Various internal groups produced all sorts of documentation; regions and districts produced documentation for and about clients, including proposals for work and the results of work performed. Often the documentation produced did not take advantage of previously-produced work.
The Repository project intended to centralize all documentation in a single "one-stop shop" for creating, updating, storing, and searching documents, to provide various information about every document so documentation authors and information gatherers could search for and use or reuse existing similar documentation as appropriate. It also was intended to be minimally intrusive for both the authors and the users of the documentation. This allowed the company to enforce a common look-and-feel for all documents within a certain type and for consistency in content as well. Other goals included the ability to update content in exactly one location and have that change propagated throughout all relevant documentation.
The user interface had to be simple enough for nontechnical people (managers, sales staff, administrative assistants, and so on) to be able to use it to add, edit, and search for documents meeting their variable criteria, and yet complex enough to be meaningful in terms of the results. Because of the high costs of solving this problem correctly, we decided to take a low-key internal approach to the project instead.
author = {Liza Weissler},
title = {Designing, Developing, and Implementing a Document Repository},
booktitle = {17th Large Installation Systems Administration Conference (LISA 03)},
year = {2003},
address = {San Diego, CA },
url = {https://www.usenix.org/conference/lisa-03/designing-developing-and-implementing-document-repository},
publisher = {USENIX Association},
month = oct
}
connect with us