Abstract:
A method is provided for presenting documents using a binder file stored on a computer-readable storage medium where the documents in the binder file are presentable within a graphical interface that appears as a notebook binder. The method includes opening a printer driver; selecting a binder file from an interface of the printer driver; selecting a section of the selected binder file from the interface of the printer driver; and adding the document to the selected binder file with an indicator for the document specifying the selected section.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This patent application claims the benefit of U.S. Patent Provisional Applications Ser. Nos. 61/241,739 and 61/241,722, both of which were filed on Sep. 11, 2009, both of which are incorporated herein by reference. 
    
    
     BACKGROUND 
     Many people who use computers in their day-to-day business are not computer experts. It would often be counter-productive to require them to be; they are needed for their other skills. As a result one of the challenges in designing software applications that will be used on computer workstations is to ensure that the users of such software can perform the tasks of their jobs rapidly and efficiently. If the user interface for an application is complex or confusing then an organization may provide significant training for their employees to use the application and may supply help desk personnel to deal with queries and problems; both of which may reduce productivity and increase the total cost of using the software. 
     Over the past few decades it has become commonplace to represent page-based documents on a computer display in a roughly consistent way, often as a more-or-less white rectangle with the same aspect ratio as a printed page, shown against a gray, black or colored background. As a result of consistent usage computer users are now familiar with this representation of a simple stream of pages. In the same way the use of scroll bars and “page up” and “page down” keys has become a part of the baseline knowledge that new staff may be expected to already understand. These commonly understood representations and methods of interaction do not, however, extend to a more complex collection of documents that is more than a simple, ordered, sequence of pages. 
     BRIEF SUMMARY 
     One embodiment is a method of presenting documents using a binder file stored on a computer-readable storage medium where the documents in the binder file are presentable within a graphical interface that appears as a notebook binder. The method includes opening a printer driver; selecting a binder file from an interface of the printer driver; selecting a section of the selected binder file from the interface of the printer driver; and adding the document to the selected binder file with an indicator for the document specifying the selected section. 
     Another embodiment is a computer readable storage medium having processor-executable instructions, the processor-executable instructions when installed onto a system enable the system to perform actions. The actions include displaying a printer driver interface; presenting a list containing at least one binder file within a first region of the printer driver interface for selection by a user; presenting, upon selection of a one of the at least one binder file, a list containing at least one section of the selected binder file within a second region of the printer driver interface for selection by the user; and adding, upon selection of a one of the at least one section, the document to the selected binder file with an indicator for the document specifying the selected section. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Non-limiting and non-exhaustive embodiments of the present invention are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified. 
       For a better understanding of the present invention, reference will be made to the following Detailed Description, which is to be read in association with the accompanying drawings, wherein: 
         FIG. 1  is a schematic representation of one embodiment of an environment in which the invention can be employed; 
         FIG. 2  is a schematic conceptualization of one embodiment of a binder file, according to the invention; 
         FIG. 3  is a schematic representation of elements of one embodiment of a system for management and display of content of a binder file, according to the invention; 
         FIG. 4  is a schematic representation of one embodiment of a printer driver interface for adding a document to a binder file, according to the invention; and 
         FIG. 5  is a schematic representation of one embodiment of a method of adding a document to a binder file, according to the invention; 
     
    
    
     DETAILED DESCRIPTION 
     The methods, systems, and devices described herein may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Accordingly, the methods, systems, and devices described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense. The methods described herein can be performed using any type of computing device that includes a processor or any combination of computing devices where each device performs at least part of the process. 
     Suitable computing devices typically include mass memory and typically include communication between devices. The mass memory illustrates a type of computer-readable media, namely computer storage media. Computer storage media may include volatile, nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computing device. 
     Methods of communication can include both wired and wireless (e.g., RF, optical, or infrared) communications methods and such methods provide another type of computer readable media; namely communication media. Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, data signal, or other transport mechanism and includes any information delivery media. The terms “modulated data signal,” and “carrier-wave signal” includes a signal that has one or more of its characteristics set or changed in such a manner as to encode information, instructions, data, and the like, in the signal. By way of example, communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media. 
       FIG. 1  illustrates one embodiment of an environment for the invention. In  FIG. 1 , a network environment is illustrated, but it will be understood that the invention is also applicable to unnetworked computing devices as well. It will be understood that the network environment can be a local area network, a wide area network, or any combination thereof. It will also be understood that the network can include devices, other than those illustrated, coupled to the network and that there may be multiple devices of each type illustrated connected to the network. The illustrated environment includes a network  100  to which is attached, either directly or through other devices, one or more computing devices  104  (e.g., computers, workstations, and the like), one or more printers  102 , and one or more servers  106 . Other devices can optionally be attached to the network such as personal data assistants (PDA&#39;s), cameras, cellular telephones, portable storage devices (e.g., compact discs, DVDs, memory sticks, flash drives, or other optical or magnetic storage media), and the like. Any of these devices can be connected directly to the network or via another device such as a computing device  104 , printer  102 , or server  106 . A computing device  104  typically includes a display  108  and one or more input devices  110 , such a keyboard, mouse, trackball, and the like. The computing device will also typically include internal components, such as a processor, a mass memory, and one or more components for reading portable computer-readable media, as described above. 
     Storage and presentation of related documents together is one method of increasing efficiency. In the office and other environments, physical documents are often collected into physical binders (using, for example, a ring-binder, lever-arch binder, comb- or ring-binding) for storage and reference. Often the documents within the binder are divided into sections, where each section contains different classes (e.g., different subject matter or different type) of document. As an example a home user may file utility bills into a binder with electricity in one section, telephone bills into another section, and so on. Similarly, an accounts clerk may file invoices relating to different suppliers or different date ranges into separate sections. To provide a clear demarcation between the sections, and to allow for easy navigation when searching for a document within the binder, dividers may be used between the sections. Such dividers may be made from a heavier or stiffer medium than that on which the regular pages are printed, may be colored and may include a tab that extends beyond the edges of the pages of the documents within the binder. Each of these characteristics enables the division between sections to be found more easily and quickly. 
     Electronic documents are increasingly ubiquitous in business environments. When multiple documents are accessed together they can be organized in a variety of ways, including storage in a hierarchy of directories or folders on a computer, or by a conduit into a content management system running at the organization or department level. In at least some circumstances, there is value in maintaining a single file that contains a hierarchical document structure in a way that is easy to transfer between users while making it difficult to accidentally separate the constituent documents. Such a file will be referred to herein as a ‘binder file’. The binder file format is described in the U.S. Provisional Patent Application 61/241,722 entitled “System and Method for Providing a Representation of Hierarchical Structures of Documents”, filed on even date herewith, and incorporated herein by reference. 
     In at least some embodiments, the file with a binder format can be used to store multiple ‘documents’ within ‘sections’ within a single ‘binder’ file.  FIG. 2  conceptually illustrates this concept with a binder file  200  containing multiple sections  202  with documents  204  distributed within the sections. It will be understood the three level hierarchy of document/section/binder is not exclusive and that the binder display metaphor may be extended to other depths, for example, by the depiction of sections and subsections. 
     As illustrated in  FIG. 3 , the binder file  200  can be created and modified using a binder management application  302 . The binder file  200  can be displayed on a computing device  104  using a binder display application  304 . It will be understood that the binder management application  302  and binder display application  304  can be components of a single software application or can be separate applications or even divided among any number of different application. Moreover, the binder management application  302  and binder display application  304  may reside on the same computing device or may reside on different devices. For example, a binder file  200  may be generated using the binder management application  302  on one computing device or using an external server and then imported to another computing device or server for display using the binder display application  304 . In some instances, components of either or both of the binder management application and binder display application may reside on different computing devices or servers. 
     In some embodiments, a binder file may be created as a single process from a nominated set of documents. In other embodiments, a binder file may be maintained as a dynamic file that can be modified over time, with new documents being added, removed, or modified. At least a portion of the value to a user of maintaining such a binder file is in providing a useful interface to maintain, search, and read all of the constituent documents within the binder file. But that value could be outweighed if the method of adding new documents is too onerous. It is beneficial if new documents can be added efficiently and easily to the correct location within the binder file from a variety of document sources (e.g., applications such word processors, spreadsheets, document readers, computer aided design programs, e-mail programs, and the like.) 
     Within the binder file each document and section has metadata associated with it. Additional metadata may also be associated with the binder file as a whole. The specific set of metadata used may vary from one embodiment to another or may be configured by a user of an embodiment. For example, the metadata may include one more of the following: an identifier for each document (e.g., a number or a title for each document); an indicator in which section a document belongs; a locator for each document designating a defined position within a section; a label for each section (and possibly additional identification such as a color); or the order of sections within the binder. Other metadata may also be included for one or more (or even each) document, section, or binder such as creator or author name(s); creation date; identification of the source document from which this document within the binder was imported (as a directory/file path or as an identifier within a content management system or other infrastructure repository); the time/date at which the document or section was last modified; the time/date at which the document or section was created or added to the binder; a time/date in the future by which some activity must be performed; a table of contents for the binder; binder name; the storage location of one or more copies of the binder file (e.g., to allow for automatic updating of the copies when the binder file is altered); alternate document or section titles; recipient name(s) or title(s); keyword(s); and other items such as those described by the Dublin Core Metadata Initiative or that may be desirable for a specific use case. 
     There are a number of different methods for associating metadata with a document, section, or file. For example, metadata items may be generated automatically at the time of creation or editing of the binder, section or document. Metadata items may be automatically derived from a precursor representation of a document at the time that the binder is created or a document is added to an existing binder. Metadata items may be entered manually by a computer user or derived from some other external source. It will be understood that these methods may be used exclusively or in combination for any particular set of metadata or any particular metadata item. 
     In at least some embodiments, a user creates or opens a document in the software that they would normally use to do so. The document may be a file in its own right, such as a DOC file in Microsoft Word or a PDF file in Adobe Acrobat; or it may be an email message opened in a mail program, a web page opened in an internet browser, or a view opened in an infrastructure program such as IBM Lotus Notes. 
     When the user wishes to add the document to a pre-existing binder file, the user selects a specific printer driver that allows the user to select which binder file the document should be added to and which section within that binder the document should be added into. Additional options similar to those in many printer drivers may also be configured (such as the page size and orientation, whether fonts should be embedded in the created document, scaling of the pages of the document, and the like.) When the user approves the options as set the printer driver will add the new document to the selected section within the binder file after any other documents that may already be present within that section or at a position within the section selected by the user. Metadata associate with the document may be generated and added to the binder file automatically, by manual entry, or a combination of both automatic and manual entry. 
     The process of insertion of the new document into an existing section within a hierarchical collection of documents stored in a single file, by a tool that is accessible from the majority of applications used for document creation, editing and viewing on common operating systems is one feature of this invention. The use of a printer driver as that tool is a pragmatic way to deliver the functionality. It will be understood that documents may also be inserted into a binder by alternative methods, such as an application natively supporting such functionality, provision of an application-specific add-in to save or export a document into a binder, or by a tool that enables scanning of printed documents into a binder (with or without optical character recognition). 
     In at least some embodiments, the printer driver also allows the user to create a new binder. In at least some embodiments, the printer driver allows the user to provide at least some metadata such as a name for the binder. In at least some embodiments, the printer driver also allows the user to create a new section within an existing binder, to provide metadata such as a name for the section, and optionally to specify where the new section should be added within the pre-existing sequence of sections. In at least some embodiments, the printer driver also allows the user to select the position of the new document within the sequence of documents already present within the section selected. 
     In at least some embodiments, a menu of the application in which the document is created or modified includes a menu item to allow the document to be added to a binder file. Selection of the menu item will initiate the printer driver. Alternatively or additionally, selection of a menu item, such as “Print” will initiate an interface with a list containing one or more printers (if available), one or more applications (e.g., Adobe PDF) if available, and a binder option. Selection of the binder option will initiate the printer driver for the binder file application. 
       FIG. 4  illustrates one embodiment of a printer driver interface  400  to allow addition of the document into a binder file. The printer driver interface  400  provides a list of available binder files  402 . The interface may optionally provide a mechanism to allow the user to select the directory or folder within the operating system filing system in which the binder that is to be added to is located. The user can then select a binder file within that directory or folder. 
     Upon selection of a binder file, the printer driver interface  400  can provide a list of sections  404  within the binder file. The user can select the section within the binder that the new document is to be appended to. The printer driver interface  400  may also provide a section  406  where metadata information can be added, for example, a title of the document. In some embodiments, the title of the document may be initially extracted from the document or from the filename of the document. Section  406  may allow the user to modify this initial title. It will be understood that the printer driver interface may include additional sections that allow for entry of other metadata. 
     In other embodiments, the printer driver interface manages all binder files centrally in such a way that the user sees only a single library of binders and is not therefore required to select a folder or directory in which the desired binder file is located. In at least some embodiments, the printer driver interface can include an option to create a new binder. In at least some embodiments, the printer driver interface can include an option to create a new section within a binder. In at least some embodiments, the printer driver interface can include an option to define the position of the new document within the sequence of any pre-existing documents. 
       FIG. 5  schematically illustrates one embodiment of a method of adding a new document  502  to a binder file  500  to create a modified binder file  500 ′ that includes the new document. Metadata  504  is included with the new document  502  in the modified binder file  500 . The metadata for the file may be generated automatically or manually or any combination thereof. For example, metadata such as the time and date of addition to the binder can be automatically generated by the application. Metadata, such as creation date, creator(s), title, and location of the source document can be automatically generated from the document file itself. Metadata, such as the section into which the document is placed or the document title, may be manually entered by the user. 
     The above specification, examples and data provide a description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention also resides in the claims hereinafter appended.