Browse Prior Art Database

Improvement in Attribute Presentation for Attribute-Intensive Objects

IP.com Disclosure Number: IPCOM000105967D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 48K

Publishing Venue

IBM

Related People

Dawson, CA: AUTHOR [+3]

Abstract

Today, architected stores such as X.400 mail and DIA- and DFR-based libraries have numerous attributes for the objects they contain. Some are commonly used while many are less interesting yet may still be important at times.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 61% of the total text.

Improvement in Attribute Presentation for Attribute-Intensive Objects

      Today, architected stores such as X.400 mail and DIA- and
DFR-based libraries have numerous attributes for the objects they
contain.  Some are commonly used while many are less interesting yet
may still be important at times.

      Available document managers either support (and present) a
useful subset or handle them all.  The former is open to standards
violations while the latter has inherent usability problems.

      The problem with choosing what attributes need to be included
in a useful subset, is that an attribute may be required by some
companies and not needed at all by any others.

      Our DFR-based library system has some 3 dozen attributes which
may be useful at times.  Less than half of these are modifiable.
Furthermore, customers are allowed to add additional customized
attributes to serve their own needs.

      These attributes have been grouped in categories so that they
are easier to conceptually locate.  This is a common practice.  The
CUA notebook control is used to manage the presentation.

      Still, commonly referenced attributes may span categories
(pages in the notebook).  Consider a document store scenario where
users typically provide a subject, abstract, keywords, and access
privileges to a document.  These attributes may be scattered across
several pages of the notebook.  If these are all required fields,
this will cause usability p...