Intelligent and paperless office

The claimed subject matter provides a system and/or a method that facilitates collecting and organizing electronic documents. An interface component can receive a document. A manager component can automatically file the document into a category based at least in part upon a portion of static metadata associated with the document and a portion of metadata dynamically generated from an inference related to the portion of static metadata associated with the document.

BACKGROUND

Technological advances in computer hardware, software and networking have lead to increased demand for electronic information exchange rather than through conventional techniques such as paper and telephone correspondence, for example. Such electronic communication can provide split-second, reliable data transfer between essentially any two locations throughout the world. Many industries and consumers are leveraging such technology to improve efficiency and decrease cost through web-based (e.g., on-line) services. For example, consumers can purchase goods, review bank statements, research products and companies, obtain real-time stock quotes, download brochures, etc. with the click of a mouse and at the convenience of home.

As the amount of available electronic data grows, it becomes more important to store and/or utilize such data in a manageable manner that facilitates user-friendly and quick data searches and retrieval. Generally, various companies, enterprises, businesses, and the like include a tremendous amount of data, metadata, etc. For example, office productivity tools (e.g., word processing, spread sheets, presentation software, mail applications, contact applications, networks, instant messaging applications, etc.) can include a wealth of information about the user itself as well as a user's contact lists and/or interaction with contacts.

In general, companies, businesses, and enterprises can employ vast numbers of internal and/or external communications and information transfer. For example, internal and/or external communications and information transfer can include, but are not limited to electronic mail (email), fax, mail, handwritten notes, whiteboards, Internet Protocol (IP) telephony, web mail, web-browsing, text messaging over a network of two or more computers (or network connectable, processor-based devices), and the like. Such communications, whether internal, external, or both, can further generate an overwhelming amount of physical paper. The use of physical paper has been noted to contribute to the declination of the environment since large amounts of trees are lumbered for paper creation. In addition to its ill affects towards the environment, physical paper can be costly, unorganized, inefficient, and space-consuming.

SUMMARY

The following presents a simplified summary of the innovation in order to provide a basic understanding of some aspects described herein. This summary is not an extensive overview of the claimed subject matter. It is intended to neither identify key or critical elements of the claimed subject matter nor delineate the scope of the subject innovation. Its sole purpose is to present some concepts of the claimed subject matter in a simplified form as a prelude to the more detailed description that is presented later.

The subject innovation relates to systems and/or methods that facilitate implementing a paperless environment with automatic document filing. A manager component can detect a document within an office environment and automatically file or store the document based on at least in part upon a portion of static metadata associated with the document and a portion of metadata dynamically generated from an inference related to the portion of static metadata and/or content or context associated with the document. In general, the document can be evaluated in which a tag can be appended to the document for identification or description. Moreover, the manager component can evaluate static metadata in order to infer and create additional metadata (e.g., dynamically generated metadata based on the static metadata and/or the content of the document), wherein at least one of the static metadata or the generated metadata can be utilized to automatically file the document. The manager component can further file or store the document utilizing the tag (e.g., including the any suitable combination of static metadata, generated metadata, etc.), wherein a collection of documents with substantially similar tags can be organized into a virtual file stack. The manager component can evaluate a plurality of documents, regardless of format, in order to identify a topic, category, content, context, subject, etc. in which to appropriately sort or file such document. Thus, the manager component drastically improves efficiency with the reduction (and possible elimination) of physical paper. In addition, the manager component can further provide automatic notification to an entity to which the document relates based on the evaluated content, context, and/or purpose of the document.

Upon the detection of a document, the manager component can generate a document-descriptive tag that can be utilized to sort and file the document automatically. Generally, the document can be any suitable document (independent of format) related to an office environment or network such as an attachment, an email, a word processor document, a presentation document, a scanned document, a fax, a spreadsheet, a drawing, a figure, a graphic, a portion of audio, a portion of text, a portion of a graphic, a portion of video, a portable document format (PDF), etc. Furthermore, the manager component can utilize a uniform component that implements a standardized convention in relation with file names, storage locations, document format, document file types, and the like. In another aspect in accordance with the subject innovation, an adviser component can generate suggestive data in connection with file locations, virtual file stack references, file names, and the like. In other aspects of the claimed subject matter, methods are provided that facilitate automatically detecting and filing a portion of incoming data based on content.

DETAILED DESCRIPTION

Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical disks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick, key drive . . . ). Additionally it should be appreciated that a carrier wave can be employed to carry computer-readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN). Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter. Moreover, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs.

Now turning to the figures,FIG. 1illustrates a system100that facilitates implementing a paperless environment with automatic document filing. The system100can include a manager component102that can automatically sort and/or file a portion of data received via the interface component106to result in auto-filed data104. In general, the manager component102can evaluate the portion of data in order to identify a category or a location in which to store and/or file. For example, the portion of data (e.g., a document, etc.) can be stored in a structure, a data store, a hard drive, a network drive, and/or any suitable data storage device or system. In a specific example, the manager component102can evaluate the portion of data and tag such portion of data with category-specific or location-specific data, wherein such tag can be utilized for filing and/or storing such data and/or future data. In general, the manager component102can examine a portion of static metadata related to a document (e.g., a portion of data) and infer and generate additional metadata based on the portion of static metadata and/or the content of the document. By utilizing at least one of the static metadata, the generated metadata, the content of the document, the context of the document, or any suitable combination thereof, the manager component can automatically tag and file the document (e.g., portion of data). Moreover, the manager component102can inspect at least one of content or context of a document in order to sort and file such documents. For organization, the system100can tag the document with metadata that describes the document to enable efficient and track-able filing. In another aspect in accordance with the subject innovation, the document can be filed into categories or locations based on the tag to create virtual file (e.g., data, etc.) stacks. Thus, rather than having mounds of physical paper stacks, the subject innovation can create virtual file stacks based on evaluated and identified categories.

It is to be appreciated the portion of data can be a document associated with an office environment. For example, the document can be any suitable electronic document (regardless of format or file type) such as, but is not limited to, an attachment, an email, a word processor document, a presentation document, a scanned document, a fax, a spreadsheet, a drawing, a figure, a graphic, a portion of audio, a portion of text, a portion of a graphic, a portion of video, a portable document format (PDF), etc. In general, it is to be appreciated that the system100can be utilized with any suitable electronic data that can be included on physical paper. It is to be appreciated that the system100can automatically file or sort a plurality of documents based on their respective content or substance rather than file type or format. Thus, the claimed subject matter allows an office environment to reduce and/or eliminate the use of physical paper by automatically filing and/or storing electronic portions of data (e.g., documents, attachments, etc.).

For example, an office environment can include numerous incoming or outgoing documents (e.g., portions of data) that can be extremely difficult to track, store, and/or organize. A first document can relate to Client A and billing (e.g., substance, content, context, etc.), wherein such document can be automatically filed and/or stored based on such gathered information. A virtual file stack can be created with a reference tag of Client A and billing to allow such document to be efficiently accessed. A second document can be identified and evaluated to ascertain content associated with Client B. A virtual file stack can be generated for Client B in which the second document can be tagged and filed accordingly. A third document can be received that relates to Client A and billing which can then be stored and/or filed into the virtual file stack. By creating virtual file stacks based on the identified content or context, the documents can be efficiently stored/filed and managed without using physical paper.

As previously discussed, the manager component102can evaluate static metadata related to a document, wherein the static metadata can be, but is not limited to being, date, author, origin, source, device source, location, title, name of author, type of document, physical origin, language of the document, size of document, information within the document, name of the file, amount of reviewers of the document, amount of authors, amount of people that contributed, order of modification of the document, and/or any other suitable data statically related to the document. Utilizing such static metadata, the manager component102can infer and generate additional metadata in order to identify a content, a context, a purpose, a detail of the document, etc. For instance, by inferring, generating, and tagging the document with additional metadata, the document type, context, purpose, or content can be identified. For instance, by evaluating the static metadata of the document such as title, authors, language, format, etc., the manager component102can determine the document is a resume, a recipe, a time sheet, a bill, a check, a pay stub, etc.

It is to be appreciated that the manager component102can dynamically generate metadata based upon at least one of the static metadata associated with the document and/or a content related to the document. In one example, a document type/purpose and/or department affiliation can be determined by inferring information from static metadata such as identifying author and/or reviewer affiliation. Dynamically generated metadata can add more information by evaluating the content of a document. For instance, the manager component102can employ machine learning techniques to identify characteristics that a secretary and/or admin can gather by viewing the document (e.g., looking at a document and adding extra database fields, etc.). In another example, a resume can be the document, in which the manager component102can extract degree, years of experience, expertise, awards, spoken languages, references, etc. by evaluating static metadata, content, and the like. In another example, a purchase order can be the document, wherein the manager component102can identify such document as a purchase order by evaluating static metadata, content, etc. such as, product information, critical updates, departments, etc. Where the document is a specification, the manager component102can infer key players, dependencies, parts, etc.

In accordance with another aspect of the subject innovation, the manager component102can provide automatic notification to an entity. For example, based on the identified content (e.g., examining static metadata, generating additional metadata based on content and/or static metadata), the manager component102can notify an entity (e.g., department, manager, user, worker, group of people, an email alias, a machine, a voicemail, an email, an instant messenger address, a server, a network, etc.) based on the document being relevant to such entity. For example, the manager component102can identify the document as being a resume and notify a human resource department of such document.

In addition, the system100can include any suitable and/or necessary interface component106(herein referred to as “interface106”), which provides various adapters, connectors, channels, communication paths, etc. to integrate the manager component102into virtually any operating and/or database system(s) and/or with one another. In addition, the interface106can provide various adapters, connectors, channels, communication paths, etc., that provide for interaction with the manager component102, the auto-filed data104, a portion of data associated with an office environment, and any other device and/or component associated with the system100.

FIG. 2illustrates a system200that facilitates automatically detecting and filing a portion of incoming data based on content. The system200can include the manager component102that can dynamically file and/or store a portion of data related to a document into a structure which enables the generation of auto-filed data104. The manager component102can receive and/or identify a portion of data to incorporate (e.g., file, store, sort, etc.) into a structure, wherein such structure can be dynamically created, user-defined, pre-existing, etc. For instance, the system200can be employed in an office environment (e.g., a business, a company, a corporation, a partnership, a small business, an entity, a home office, etc.) in which data can be automatically filed based on content or context into an existing data structure (e.g., a network, a hard drive, a file storage system, a file folder directory structure, a file hierarchy, a schema, a data structure, etc.). In another example, the manager component102can dynamically create the structure as data is received and evaluated (e.g., dynamically, in real time, etc.). In still another example, the manager component102can incorporate a user preference and/or suggestion as the structure is dynamically created (e.g., prompts, pop-ups, user-defined settings, etc.). It is to be appreciated that the system200can utilize any suitable structure in connection with automatically filing and/or storing data.

The manager component102can include an evaluation component202that can examine a portion of received and/or identified data in order to ascertain content or context of such data. The evaluation component202can identify content or context of the office environment data in order to accurately stack, sort, and/or file the data. The evaluation component202can examine at least one of a source that transmitted the document, a target (e.g., the receiver or intended recipient, etc.) of the document, a substance of the document, metadata related to the document, properties of the document, received file type, received file name, a title of the document, and/or any other suitable data associated with the document. In addition, the evaluation component202can examine at least one of a portion of static metadata related to a document or a portion of automatically generated metadata (e.g., generated based on evaluating the static metadata, etc.). Moreover, the evaluation component202can utilize various conversion techniques in order to convert the data into suitable data format for evaluation. For instance, the data conversion technique can be, but not limited to being, text translation, scanned document conversion (e.g., text conversion, image conversion, etc.), image conversion, audio conversion, video translation, etc. For example, the document can be received as an audio file (e.g., which could be transcribed and stored on paper) that can be converted into text and evaluated for automatic filing/storing. In another example, a document can be scanned in which the evaluation component202can convert the scanned document into text or images to base the automatic filing.

The manager component102can further include a tag component204that can append the document or the portion of data with a tag for identification. The tag component204can generate a tag that describes the data based on at least one of a portion of content, the portion of static metadata, or the portion of generated metadata, wherein the content, context, purpose, or “gist” can be determined by the evaluation component202. For instance, the tag can be metadata, a hypertext markup language (HTML) tag, a keyword, a portion of static metadata, a portion of generated metadata, and/or any suitable combination thereof. In general, the tag component204can employ any suitable tag that describes and/or identifies a document. A sort component206can file and store the document based on the tag appended thereto by the tag component204. The sort component206can examine a tagged portion of data and file such document into a structure (e.g., a schema, a data structure, a file structure, a file folder directory, etc.).

FIG. 3illustrates a system300that facilitates tracking automatic filing and storing of documents. The system300can include the manager component102that can employ document evaluation and tagging for a paperless office environment with automatic filing and storage of data. In particular, the manager component102can receive a portion of data via the interface106and append an identifying tag to the portion of data, wherein such data can be filed and/or stored based on the tag. The portion of data can be stored and/or filed in accordance with a structure (e.g., pre-defined, dynamically created, etc.). Moreover, the manager component102can detect a portion of data within an office environment that can be automatically filed and/or stored. For instance, a first email attachment can be received and automatically filed. When a second email is received with the same attachment, the manager component102can ascertain that such document has been automatically stored and/or filed previously. In a similar example, the same attachment can be received via a scanning copy machine, in which the manager component102can ascertain that such document has been previously stored and/or filed. In yet another example, the attachment can be received in a disparate format or file type but with the same content, wherein the manager component102can ascertain that such content has been previously stored and/or filed from the first email attachment. Thus, the system300allows an office environment to be less redundant and wasteful by eliminating physical paper.

The manager component102can receive a portion of data such as, but not limited to, an electronic document, an attachment, an email, a word processing document, a portion of an image, a portion of audio, a portion of video, a scanned document, etc. The portion of data can be associated with a network302, wherein the network302can be related to an office environment. For example, the manager component102can dynamically detect a document within the network302in which such document can be automatically filed and stored based upon content or context of such document. It is to be appreciated that the manager component102can dynamically file and store the document within the network302, in a separate data store (as depicted and discussed below), and/or any suitable combination thereof. Moreover, it is to be appreciated and understood that the network302can include a structure (e.g., file structure, schema, a data structure, a file folder hierarchical storage system, etc.) associated with the office environment in which the data (e.g., a document) can be automatically filed and stored in accordance with.

The manager component102can utilize a log component304that can track various data related to the system300. In particular, the log component304can track and/or monitor data related to the network302, documents, attachments, locations, categories, tags, automatic filing details (e.g., time, location, content, context, etc.), automatic storing details (e.g., time, location, location in structure, etc.), static metadata, generated metadata created by evaluating the static metadata (e.g., utilizing inference techniques, etc.), etc. It is to be appreciated that the log component304can be a stand-alone component, incorporated into the manager component102, incorporated into the network302, and/or any combination thereof.

The manager component102can further utilize a search component306that facilitates querying any data associated with the system300. The search component306can allow a user and/or any component to query to system300in relation to data automatically filed or stored, tags associated with the automatic filing or storing, location of data, categories utilized for filing or storing, structure in which data is stored or filed, static metadata, generated metadata, etc. For example, a user can query the system300to identify a particular document that had been automatically filed in the past. In another example, the system300can be queried to identify categories that have been created to which data is being filed and/or stored. In still another example, the system300can be queried to locate a specific virtual file stack. It is to be appreciated that a plurality of searches and/or queries can be implemented by the search component306and the above examples are not to be limiting on the claimed subject matter. Moreover, it is to be appreciated that the search component306is depicted as a stand-alone component, but the search component306can be incorporated into the manager component102, the network302, and/or any combination thereof.

The system300can further include a data store308that can include any suitable data related to the manager component102, the network302, the auto-filed data104, the log component304, the search component306, etc. For example, the data store308can include, but not limited to including, data related to the network302, documents, email, email attachments, tags, a structure for data to be stored or file (e.g., a file storage system, a file folder directory, a hierarchy of data stores, an organization of data containers based on an office environment, etc.), tagging settings, filing settings/options, storing options/settings, naming conventions (discussed in more detail below), tagging criteria, logged data, historic data related to searches, historic data related to automatically filed or stored data, conversion techniques, static metadata, generated metadata, inference techniques, and/or any other suitable data related to automatically filing or storing a portion of data associated with the network302.

It is to be appreciated that the data store308can be, for example, either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM). The data store308of the subject systems and methods is intended to comprise, without being limited to, these and any other suitable types of memory. In addition, it is to be appreciated that the data store308can be a server, a database, a hard drive, a pen drive, an external hard drive, a portable hard drive, and the like.

FIG. 4illustrates a system400that facilitates employing uniformity to a portion of automatically filed data within a network. The system400can include the manager component102that can receive a document related to a network302, wherein the document can be evaluated and tagged with context, type, purpose, or content identifying metadata for automatic filing and/or storing. For instance, an incoming email with a word processing document attachment can be automatically detected, evaluated, tagged, and sorted into a location or category within a structure. The static metadata can be evaluated by the manager component102in order to create additional metadata that further identifies the document. For instance, a first portion of metadata, a second portion of metadata, and a third portion of metadata can be evaluated to infer that the document relates to a slide show presentation. Typically, the attachment would be manually evaluated, printed, and physically filed. The system400enables the attachment to be automatically filed and/or stored in a virtual file stack based on identified content, type, purpose, and/or context of the attachment. Thus, the system400drastically reduces or eliminates the amount of physical paper utilized within the network302.

The manager component102can utilize a uniform component402that employs a standardized convention in connection with at least one of a file name, a virtual file stack name, file type, or a name related to a structure into which items/data can be filed or stored. In particular, the uniform component402can ensure data automatically filed and/or stored is consistent in terms of naming conventions (e.g., file name, file location name, virtual file stack name, etc.). The uniform component402can enforce a standardized naming convention based on user-defined criteria, pre-established criteria utilized within the network302, dynamically identified criteria based on incoming documents that are automatically filed/stored, and/or any other suitable combination thereof.

For instance, an office environment can include a network drive (e.g., shared hard drive, etc.) that is accessible to employees and hosts data related to the office. The network drive can include a naming convention for documents in connection with any data stored thereon. The uniform component402can employ such existing naming conventions with incoming data that is automatically filed and/or stored. Moreover, it is to be appreciated that the uniform component402can initiate a user-defined naming convention in order to update the existing naming convention.

FIG. 5illustrates a system500that facilities enhancing automatic paperless sorting with suggested filing locations/categories. The system500can include the manager component102that can automatically file or store data into a virtual file stack utilizing a metadata tag in order to optimize an office environment. The system500can include an adviser component502that can provide a portion of suggestive data for a document in accordance with filing and/or storing. In general, the suggestive data can relate to a virtual file stack location, a storage location within a structure, a reference name for the document, a tag for the document, etc. For instance, the adviser component502can dynamically provide suggestive data for a document upon discovery, wherein the suggestive data can be a portion of a graphic. In one specific example, the portion of graphic can be a virtual sticker that can display suggestive data for informative purposes or confirmation purposes.

For example, a document can be detected and evaluated in which the adviser component502can display suggestive data in accordance with potential filing and/or storing (based on static metadata, generated metadata, any combination thereof, etc.). The suggestive data can allow a user to approve or confirm the suggestions, wherein the user can further manually edit such suggestions. Thus, a file storage location can be suggested as well as a file reference name, wherein the user can confirm the storage location and manually edit or change the suggested file reference name. It is to be appreciated that any suitable suggestion related to the automatic filing or storing can be implemented by the adviser component502and the above example is not to be limiting on the subject innovation.

FIG. 6illustrates a system600that employs intelligence to facilitate implementing a paperless environment with automatic document filing. The system600can include the manager component102, auto-filed data104, and the interface106. It is to be appreciated that the manager component102, auto-filed data104, and the interface106can be substantially similar to respective components, interfaces, and data described in previous figures. The system600further includes an intelligent component602. The intelligent component602can be utilized by the manager component102to facilitate automatically filing and/or storing data related to an office environment. For example, the intelligent component602can infer additional metadata for a document by evaluating static metadata related to a document, content of a document, content of data, purpose of a document, context of data, tag structures for data, conversion of data into schema, file locations within a structure, storage locations within a structure, virtual file stacks, naming conventions, suggestive data for filing, suggestive data for storing, etc.

The manager component102can further utilize a presentation component604that provides various types of user interfaces to facilitate interaction between a user and any component coupled to the manager component102. As depicted, the presentation component604is a separate entity that can be utilized with the manager component102. However, it is to be appreciated that the presentation component604and/or similar view components can be incorporated into the manager component102and/or a stand-alone unit. The presentation component604can provide one or more graphical user interfaces (GUIs), command line interfaces, and the like. For example, a GUI can be rendered that provides a user with a region or means to load, import, read, etc., data, and can include a region to present the results of such. These regions can comprise known text and/or graphic regions comprising dialogue boxes, static controls, drop-down-menus, list boxes, pop-up menus, as edit controls, combo boxes, radio buttons, check boxes, push buttons, and graphic boxes. In addition, utilities to facilitate the presentation such as vertical and/or horizontal scroll bars for navigation and toolbar buttons to determine whether a region will be viewable can be employed. For example, the user can interact with one or more of the components coupled and/or incorporated into the manager component102.

The user can also interact with the regions to select and provide information via various devices such as a mouse, a roller ball, a keypad, a keyboard, a pen and/or voice activation, for example. Typically, a mechanism such as a push button or the enter key on the keyboard can be employed subsequent entering the information in order to initiate the search. However, it is to be appreciated that the claimed subject matter is not so limited. For example, merely highlighting a check box can initiate information conveyance. In another example, a command line interface can be employed. For example, the command line interface can prompt (e.g., via a text message on a display and an audio tone) the user for information via providing a text message. The user can then provide suitable information, such as alpha-numeric input corresponding to an option provided in the interface prompt or an answer to a question posed in the prompt. It is to be appreciated that the command line interface can be employed in connection with a GUI and/or API. In addition, the command line interface can be employed in connection with hardware (e.g., video cards) and/or displays (e.g., black and white, and EGA) with limited graphic support, and/or low bandwidth communication channels.

FIG. 7illustrates a method700that facilitates automatically organizing electronic documents associated with an office network. At reference numeral702, a document can be received. For example, the document can be any suitable electronic document (regardless of file type or format) related to an office environment such as, but is not limited to being, an attachment, an email, a word processor document, a presentation document, a scanned document, a fax, a spreadsheet, a drawing, a figure, a graphic, a portion of audio, a portion of text, a portion of a graphic, a portion of video, a portable document format (PDF), etc. For example, a document can be received via a scanning device that can scan a physical piece of paper to create an electronic copy.

At reference numeral704, the document can be analyzed to identify at least one of a substance of the document, a content of the document, a portion of static metadata related to the document, or a portion of generated metadata created by inferring the portion of static metadata. Static metadata related to a document can be evaluated in order to generate additional metadata that can provide a context, content, type, or purpose of the document. In other words, the static metadata can be examined to infer additional metadata that further clarifies the documents content/context. Various intelligence or machine learning can be employed in order to dynamically evaluate a document to ascertain content or context of the document. Thus, an email can be evaluated in order to determine the email relates to particular subject, topic, category, etc. At reference numeral706, the document can be tagged based on the identified content. For instance, the tag can be metadata, a hypertext markup language (HTML) tag, a keyword, etc. In general, the tag can describe and/or identify a document.

At reference numeral708, the document can be filed into a location based on the analysis. The document can be filed or stored into a structure associated with an office environment, wherein the structure can be a schema, a data structure, a file structure, a file folder directory, etc. It is to be appreciated and understood that the structure can be dynamically created, user-defined, pre-existing, etc. In another example, the document can be stored into a virtual file stack that can include documents with substantially similar content.

FIG. 8illustrates a method800for uniformly managing and filing incoming documents based on content. At reference numeral802, an incoming document can be automatically detected. The incoming document can be targeted for a network associated with an office environment. For instance, the incoming document can be received or detected via email, fax, scanning/copying device, a download, a network, the Internet, etc. For example, an email with a document attachment targeted for an employee in an office environment can be automatically detected. At reference numeral804, metadata for the incoming document can be evaluated and additional metadata can be evaluated. Machine learning, inference techniques, intelligence, and the like can be utilized to generate additional metadata based on the static metadata and/or ascertain content, purpose, context, etc. of the incoming document, wherein various aspects/metadata of the document can be examined (e.g., date, author, origin, source, device source, location, title, name of author, type of document, physical origin, language of the document, size of document, information within the document, name of the file, amount of reviewers of the document, amount of authors, amount of people that contributed, order of modification of the document, and/or any other suitable data statically related to the document etc.).

At reference numeral806, a decision is made whether the document has been already filed based on the evaluated content or context of such document. If the document has been already filed (e.g., YES), the method800can return to reference numeral802to continue automatic detection of incoming documents. If the document has not been already filed (e.g., NO), the method800can continue to reference numeral808. At reference numeral808, the document can be tagged based on at least one of the evaluation of the document or a user-defined rule. For instance, a user may edit automatic filing or storing options with a defined rule that stores or files a document regardless of content identified.

At reference numeral810, the incoming document can be filed with a standardized convention. For instance, the standardized convention can relate to naming the document, location of the document, a virtual file stack name, a name reference related to a structure in which the document is stored, etc. By employing the standardized conventions, the documents automatically filed and stored can be easily accessed, queried, etc in an efficient manner.

In order to provide additional context for implementing various aspects of the claimed subject matter,FIGS. 9-10and the following discussion is intended to provide a brief, general description of a suitable computing environment in which the various aspects of the subject innovation may be implemented. For example, a manager component that automatically files and stores an electronic document based on metadata (e.g., static, additional metadata created based on static metadata, etc.), as described in the previous figures, can be implemented in such suitable computing environment. While the claimed subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a local computer and/or remote computer, those skilled in the art will recognize that the subject innovation also may be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks and/or implement particular abstract data types.

Moreover, those skilled in the art will appreciate that the inventive methods may be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based and/or programmable consumer electronics, and the like, each of which may operatively communicate with one or more associated devices. The illustrated aspects of the claimed subject matter may also be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. However, some, if not all, aspects of the subject innovation may be practiced on stand-alone computers. In a distributed computing environment, program modules may be located in local and/or remote memory storage devices.

FIG. 9is a schematic block diagram of a sample-computing environment900with which the claimed subject matter can interact. The system900includes one or more client(s)910. The client(s)910can be hardware and/or software (e.g., threads, processes, computing devices). The system900also includes one or more server(s)920. The server(s)920can be hardware and/or software (e.g., threads, processes, computing devices). The servers920can house threads to perform transformations by employing the subject innovation, for example.

One possible communication between a client910and a server920can be in the form of a data packet adapted to be transmitted between two or more computer processes. The system900includes a communication framework940that can be employed to facilitate communications between the client(s)910and the server(s)920. The client(s)910are operably connected to one or more client data store(s)950that can be employed to store information local to the client(s)910. Similarly, the server(s)920are operably connected to one or more server data store(s)930that can be employed to store information local to the servers920.

With reference toFIG. 10, an exemplary environment1000for implementing various aspects of the claimed subject matter includes a computer1012. The computer1012includes a processing unit1014, a system memory1016, and a system bus1018. The system bus1018couples system components including, but not limited to, the system memory1016to the processing unit1014. The processing unit1014can be any of various available processors. Dual microprocessors and other multiprocessor architectures also can be employed as the processing unit1014.

The system memory1016includes volatile memory1020and nonvolatile memory1022. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer1012, such as during start-up, is stored in nonvolatile memory1022. By way of illustration, and not limitation, nonvolatile memory1022can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory1020includes random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM).

Computer1012can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s)1044. The remote computer(s)1044can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer1012. For purposes of brevity, only a memory storage device1046is illustrated with remote computer(s)1044. Remote computer(s)1044is logically connected to computer1012through a network interface1048and then physically connected via communication connection1050. Network interface1048encompasses wire and/or wireless communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ring and the like. WAN technologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).

Communication connection(s)1050refers to the hardware/software employed to connect the network interface1048to the bus1018. While communication connection1050is shown for illustrative clarity inside computer1012, it can also be external to computer1012. The hardware/software necessary for connection to the network interface1048includes, for exemplary purposes only, internal and external technologies such as, modems including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.

There are multiple ways of implementing the present innovation, e.g., an appropriate API, tool kit, driver code, operating system, control, standalone or downloadable software object, etc. which enables applications and services to use the advertising techniques of the invention. The claimed subject matter contemplates the use from the standpoint of an API (or other software object), as well as from a software or hardware object that operates according to the advertising techniques in accordance with the invention. Thus, various implementations of the innovation described herein may have aspects that are wholly in hardware, partly in hardware and partly in software, as well as in software.