Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Automatic Note Log File Cleaner

IP.com Disclosure Number: IPCOM000111626D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 98K

Publishing Venue

IBM

Related People

Johnson, S: AUTHOR [+4]

Abstract

A methodology is described that automatically organizes and cleans note log repositories by deleting duplicated notes (that may or may not contain previous or subsequent attachments or detachments).

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

Automatic Note Log File Cleaner

      A methodology is described that automatically organizes and
cleans note log repositories by deleting duplicated notes (that may
or may not contain previous or subsequent attachments or
detachments).

      In today's electronic mail computing environment, files, notes,
meeting notices, messages, documents and many other forms of data are
sent to users on an ever increasing scale.  Subsequently, in the
electronic implementation of informal notes, methods are provided for
filing a particular note in different repositories (note logs, named
logs, folders, note books, file cabinets, etc.).  Once a user has
received and saved a note in a note log, it frequently occurs that
the same note will be received again by the user (either resent from
the original sender or forwarded from another user), with new
attachments to it (i.e., preface notes, comments, corrections, files,
etc.).  Thus, repositories may contain many notes of the same
subject, but from different originators and different send dates.

      This invariably results in a 'messy' office with cluttered and
unorganized note repositories, and reduced user productivity.  The
use and management of these repositories currently requires more
effort than should be required.  This methodology will facilitate the
need for automatically organizing and cleaning these repositories by
deleting duplicated notes (that may or may not contain previous or
subsequent attachments or detachments).

      A note's constituent parts are "author", "recipient",
"subject", and "body".  Hereinafter, "note log" refers to note logs,
named logs, folders, note books, file cabinets, etc., anything used
in a note-saving capacity as a note repository.

      Both the sender and receiver may choose to keep a copy in a
note repository.  These are generally unorganized except, perhaps,
chronologically.  Typically, in today's electronic implementation of
notes the "from" and "to" information is contained in the trailing
delimiter.  The note boundaries are determined by locating the
delimiter records comprising the "from" and "to" information and the
subject information.  These are distinct from the body of the note.

      Our methodology utilizes this information in its automatic note
log file cleaning function.  This allows a user to save just what he
needs in his note logs.

      In the preferred embodiment, once a user has chosen to file a
note into a note log, a dialog box appears giving the user the option
to remove the notes related to the note he is now attempting to
store.  Related notes are predecessor relatives of the current note
with respect to forwarding (or perhaps resending).  In the following
example the same note could be propagated many times (each previous
note would be a subset of later notes):

                    1)  Jim  -->  Bob...