Browse Prior Art Database

MORE EFFICIENT EXCEPTIONS PAGE PROGRAMMING

IP.com Disclosure Number: IPCOM000027229D
Original Publication Date: 1995-Oct-31
Included in the Prior Art Database: 2004-Apr-07
Document File: 4 page(s) / 223K

Publishing Venue

Xerox Disclosure Journal

Abstract

A system for exceptions page programming is proposed where the user simply marks with a (colored) pencil in the corner of a page with a number (or code) to indicate an exceptions program. The User Interface dialog allows the user to relate each number to specific programming. When the job is run, the scanner and software recognize the colored numbers and treat them as instructions rather than printing them.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 40% of the total text.

Page 1 of 4

XEROX DISCLOSURE JOURNAL

MORE EFFICIENT EXCEPTIONS Proposed Classification PAGE PROGRAMMING U.S. C1.358/296 Murray 0. Meetze Int. C1. G03g 15/00

A system for exceptions page programming is proposed where the user simply marks with a (colored) pencil in the corner of a page with a number (or code) to indicate an exceptions program. The User Interface dialog allows the user to relate each number to specific programming. When the job is run, the scanner and software recognize the colored numbers and treat them as instructions rather than printing them.

Many printers and copiers have advanced features (usually called exceptions page programming) which allow the user to program different feature options for different pages in a document. For example, the body of the document may be printed on regular letter size 201b paper, but the first and last pages may be wide cover stock and various pages within the document may be printed on tab stock. The programming of exceptions pages is facilitated by an interactive dialog on a modern User Interface (UI).

Various designs for such a dialog have been developed with the objection of making the programming easy to learn and efficient to use. However, the efficiency of using exceptions page programing features is generally limited by requiring the user to carefully count the pages in the original leading up to each exceptions page. This page counting is tedious, and it is difficult to get it right the first time, So it is not unusual to have to run a proof set and then to correct the programming at least once. To deal with this problem, a system has been previously proposed which would allow the user to place the original in an RDH which would automatically circulate the pages of the originaL document slowly. The user would then press a stop button for each page which requires exceptions programming. This method would not be simple to use for duplex originals, however.

Another design uses "key sheets" which are coded with machine readable indicia (such as bar codes). The key sheets are inserted into the appropriate places in the documet, and the RDH circulates the stack once to read the key sheets (ejecting the key sheets from the set), then circulates the set again for scanning and printing. Key sheets make the job more efficient to set up, but it is difficult to develop a simple system for dealing with duplex originals. Additionally, the extra scan for key sheets is not optimal, and sorting and maintaining the supply of key sheets is a burden.

XEROX DISCLOSURE jOURNAL Vol. 20 No. 5 September/October 1995 463

[This page contains 1 picture or other non-text object]

Page 2 of 4

MORE EFFICIENT EXCEPTIONS PAGE PROGRAMMING (Cont'd)

DocuTech integrates the features into several alternatives for editing the programming page by page either pre-scan or post-scan. The pre-scan alternatives involve page counting, and the post-scan alternatives involve stepping through the document pages electronically.

The...