Abstract:
Architecture that provides a technique whereby version information is tracked and presented for a given document, in the document. The version information can be presented or accessed using a dropdown user interface (UI) navigation model which employs animation to assist users in tracking which user is making a change and when the change is made. Moreover, a user can select a specific version item to navigate back to the content associated with changes made, as part of collaboration, for example. The dropdown menu includes elements that comprise user tiles, user name, last saved date, and so on. Additionally, a user can jump between documents within a single UI. In an email embodiment, users communicating via email as part of the collaboration can be presented with a side-by-side view of the messages communicated during the collaboration, and the corresponding change to the document content.

Description:
BACKGROUND 
     Collaboration is a widely-used technique for providing increased productivity and effectiveness in corporate environments. However, problems exist at least with knowing the version of the content (in the document) on which work is being performed is an important aspect of collaboration. For example, consider that a single document is the focus of collaboration sharing among a group of users. In this typical case, each user can make updates to the document and the updates will then be merged into the single document. However, the timing of the updates can pose problems as well as who made the updates to a given piece of content. Generally, the chronology of the updates needs to be tracked so that the final version contains all the updates and when made in the proper order. Moreover, this becomes particularly problematic when using email for sending the document updates. 
     SUMMARY 
     The following presents a simplified summary in order to provide a basic understanding of some novel embodiments described herein. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later. 
     The disclosed architecture provides a technique whereby version information is tracked and presented for a given document, in the document. The version information can be presented or accessed using a dropdown user interface (UI) navigation model which employs animation to assist users in tracking which user is making a change and when the change is made. Moreover, a user can select a specific version item to navigate back to the content associated with changes made, as part of collaboration, for example. The dropdown menu includes elements that comprise user tiles, user name, last saved date, and so on. Additionally, a user can jump between documents within a single UI. 
     To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of the various ways in which the principles disclosed herein can be practiced and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  illustrates a computer-implemented versioning system in accordance with the disclosed architecture. 
         FIG. 2  illustrates an alternative embodiment of a versioning system that employs email in combination with document collaboration. 
         FIG. 3  illustrates an exemplary system that employs the version information in the document. 
         FIG. 4  illustrates an exemplary presentation technique  400  for the version information. 
         FIG. 5  illustrates a computer-implemented versioning method in accordance with the disclosed architecture. 
         FIG. 6  illustrates further aspects of the method of  FIG. 5 . 
         FIG. 7  illustrates a block diagram of a computing system that executes versioning in accordance with the disclosed architecture. 
     
    
    
     DETAILED DESCRIPTION 
     The disclosed architecture assists collaboration on a document by multiple users that make incremental changes to document content. Version history information is presented, and when an item of version history is selected, the associated change is emphasized (e.g., highlighted) in the document. 
     In an email embodiment, users communicating via email as part of the collaboration can be presented with a side-by-side view of the messages communicated during the collaboration, and the corresponding change to the document content. For example, if six emails were employed on collaboration of a document and six corresponding changes to the document content were made, selection of the fourth item of version information in the document will activate presentation of the associated fourth email message to assist in providing additional context as to why the change was made. 
     Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding thereof. It may be evident, however, that the novel embodiments can be practiced without these specific details. In other instances, well known structures and devices are shown in block diagram form in order to facilitate a description thereof. The intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claimed subject matter. 
       FIG. 1  illustrates a computer-implemented versioning system  100  in accordance with the disclosed architecture. The system  100  includes an application user interface  102  (e.g., a word processor, spreadsheet, etc.) that enables the presentation and edit of content  104  of a document  106  of an application (e.g., a word processor, spreadsheet, etc.). A versioning component  108  tracks and presents version information  110  of the document  106  based on edits made to the content  104  as part of collaboration of multiple users. The version information  110  is presented as part of (e.g., in) the document  106 . 
     The collaboration can be performed in combination with a viewing window  112  that presents an edit and corresponding version information in association with user identity information of a user that made the edit. The viewing window  112  can be a user interface of a messaging application (e.g., email) that processes messages communicated between the users in combination with the collaboration. The messages are presented concurrently with the document  106 , where concurrency is in a messaging user interface of the messaging application (e.g., email). The version information  110  or portions thereof can be propagated into the message during the collaboration. The state of user interaction with the document content  104  is animated as part of the version information  110 . 
     The version information  110  includes at least one of document name, version count, identity information of a user that made the edit, date, time, chronological information relative to other edits, or sharing information. The version information  110  can be presented in the document  106  as a dropdown menu, for example, via which different versions of the document  106  can be selected for presentation. The edit of a given user is emphasized in the document  106  in response to selection of the user in the dropdown menu. 
     The viewing window  112  can be presented in combination with the application UI in a common (or single) user interface. 
       FIG. 2  illustrates an alternative embodiment of a versioning system  200  that employs email in combination with document collaboration. The system  200  includes the application user interface  102  of an application  202  (e.g., word processing application) that enables presentation and edit of the content  104  (e.g., text, media, links, etc.) of the document  106  during collaboration by multiple users. A messaging component  204  (e.g., email application) processes and presents message(s)  206  (or dialog) in a messaging UI  208 , the message(s)  206  being communicated between the users during the collaboration. The versioning component  108  presents the version information  110  in the document  106  based on edits made to the content  104  by the users. 
     The document  106  and messaging component  204  are presented concurrently during the collaboration to show dialog (messages) between the collaboration users and edits inserted by the collaboration users into the document  106 . The version information  110  or portions thereof is propagated into the message (message(s)  206 ) during the collaboration. The version information  110  can include one or more of state (e.g., “User 1  is editing the document”) of user interaction with the content, document name (e.g., Doc 1 ), version count (e.g., three versions), identity information of a user (e.g., User 1  made the edit) that made the edit, date, time, chronological information (e.g., “the latest”) relative to other edits, and/or sharing information (e.g., “three users are sharing Doc 1 ”). The version information  110  can be presented in the document  106  via a dropdown menu via which different versions of the document  106  can be selected for presentation. The edit of a given user is emphasized (e.g., highlighted, circumscribed by a box, differentiating font, differentiating style, etc.) in the document  106  in response to selection of the user in the dropdown menu. The collaboration can be initiated via the messaging component  204  and navigation is facilitated between the messaging component (e.g., messaging UI  208 ) and the document  106 . Note also that the messaging UI  208  and the application UI  102  can be presented side-by-side as a common (or single) user interface  210 . 
       FIG. 3  illustrates an exemplary system  300  that employs the version information  110  in the document  106 . Here, the messaging UI  208  shows two messages for a first user (USER 1 ) and a second user (USER 2 ). The first user makes edits (NEW TEXT 1 ) into the document content  104  (also referred to as the ORIGINAL TEXT 1 ). This editing event is recorded and presented in the version information  110  with the timestamp at which time and date the editing occurred, by which user, and with the chronological information (e.g., latest), version count information (e.g., two versions), document name (DOC 1 ), and location of the shared media (e.g., shared on drive-X with three people), for example. Portions of the version information  110  (as previously described) can be presented in a dropdown menu  302 , as is illustrated in  FIG. 4 . Once the edit by the first user has been made, a notification  304  can be inserted back into the message UI  208  in association with the dialog of the first user. If there are no edits yet made to the document  106 , the version information  110  can be made unelectable (inaccessible) since no other version information is available. 
       FIG. 4  illustrates an exemplary presentation technique  400  for the version information  110 . Here, the dropdown menu  302  expands to four document versions: the latest version, the original version, and two intermediate versions (by User 2  and User 4 ). The corresponding edits of the users are shown in the content  104 . State (e.g., draft—you are editing . . . ) of the editing by the first user can be part of the animation of the portion  402  of the version information  110 . If a user selects a second portion  404  of the version information  110  the corresponding edits in the content can also be emphasized (e.g., highlighted). Additionally, the associated message in the message UI  208  (of  FIG. 3 ) can be annotated or selected to draw attention of the viewer to the associated message(s). 
     Included herein is a set of flow charts representative of exemplary methodologies for performing novel aspects of the disclosed architecture. While, for purposes of simplicity of explanation, the one or more methodologies shown herein, for example, in the form of a flow chart or flow diagram, are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation. 
       FIG. 5  illustrates a computer-implemented versioning method in accordance with the disclosed architecture. At  500 , a document is presented for collaboration by multiple users. At  502 , edits applied to the document (e.g., as part of the collaboration) are associated with different corresponding version information. At  504 , the version information is presented in the document as facilitated in execution by a processor. At  506 , the version information is updated based on new edits to the document. 
       FIG. 6  illustrates further aspects of the method of  FIG. 5 . Note that the arrowing indicates that each block represents a step that can be included, separately or in combination with other blocks, as additional aspects of the method represented by the flow chart of  FIG. 5 . At  600 , the document and communications dialog are presented in a common user interface between which navigation is facilitated. At  602 , the version information is presented as an accumulated list of selectable document versions. At  604 , the version information is presented as including at least one of document name, version count, identity information (e.g., name, alias, etc.) of a user that made the edit, date, time, chronological information relative to other edits, or sharing information. At  606 , visual emphasis is applied to an edit of a user based on selection of selected document version in the version information. 
     As used in this application, the terms “component” and “system” are intended to refer to a computer-related entity, either hardware, a combination of software and tangible hardware, software, or software in execution. For example, a component can be, but is not limited to, tangible components such as a processor, chip memory, mass storage devices (e.g., optical drives, solid state drives, and/or magnetic storage media drives), and computers, and software components such as a process running on a processor, an object, an executable, a data structure (stored in volatile or non-volatile storage media), a module, a thread of execution, and/or a program. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. The word “exemplary” may be 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. 
     Referring now to  FIG. 7 , there is illustrated a block diagram of a computing system  700  that executes versioning in accordance with the disclosed architecture. In order to provide additional context for various aspects thereof,  FIG. 7  and the following description are intended to provide a brief, general description of the suitable computing system  700  in which the various aspects can be implemented. While the description above is in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that a novel embodiment also can be implemented in combination with other program modules and/or as a combination of hardware and software. 
     The computing system  700  for implementing various aspects includes the computer  702  having processing unit(s)  704 , a computer-readable storage such as a system memory  706 , and a system bus  708 . The processing unit(s)  704  can be any of various commercially available processors such as single-processor, multi-processor, single-core units and multi-core units. Moreover, those skilled in the art will appreciate that the novel methods can be practiced with other computer system configurations, including minicomputers, mainframe computers, as well as personal computers (e.g., desktop, laptop, etc.), hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices. 
     The system memory  706  can include computer-readable storage (physical storage media) such as a volatile (VOL) memory  710  (e.g., random access memory (RAM)) and non-volatile memory (NON-VOL)  712  (e.g., ROM, EPROM, EEPROM, etc.). A basic input/output system (BIOS) can be stored in the non-volatile memory  712 , and includes the basic routines that facilitate the communication of data and signals between components within the computer  702 , such as during startup. The volatile memory  710  can also include a high-speed RAM such as static RAM for caching data. 
     The system bus  708  provides an interface for system components including, but not limited to, the system memory  706  to the processing unit(s)  704 . The system bus  708  can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), and a peripheral bus (e.g., PCI, PCIe, AGP, LPC, etc.), using any of a variety of commercially available bus architectures. 
     The computer  702  further includes machine readable storage subsystem(s)  714  and storage interface(s)  716  for interfacing the storage subsystem(s)  714  to the system bus  708  and other desired computer components. The storage subsystem(s)  714  (physical storage media) can include one or more of a hard disk drive (HDD), a magnetic floppy disk drive (FDD), and/or optical disk storage drive (e.g., a CD-ROM drive DVD drive), for example. The storage interface(s)  716  can include interface technologies such as EIDE, ATA, SATA, and IEEE 1394, for example. 
     One or more programs and data can be stored in the memory subsystem  706 , a machine readable and removable memory subsystem  718  (e.g., flash drive form factor technology), and/or the storage subsystem(s)  714  (e.g., optical, magnetic, solid state), including an operating system  720 , one or more application programs  722 , other program modules  724 , and program data  726 . 
     The one or more application programs  722 , other program modules  724 , and program data  726  can include the entities and components of the system  100  of  FIG. 1 , the entities and components of the system  200  of  FIG. 2 , the entities and components the system  300  of  FIG. 3 , the entities and components of the technique  400  of  FIG. 4 , and the methods represented by the flowcharts of  FIGS. 5 and 6 , for example. 
     Generally, programs include routines, methods, data structures, other software components, etc., that perform particular tasks or implement particular abstract data types. All or portions of the operating system  720 , applications  722 , modules  724 , and/or data  726  can also be cached in memory such as the volatile memory  710 , for example. It is to be appreciated that the disclosed architecture can be implemented with various commercially available operating systems or combinations of operating systems (e.g., as virtual machines). 
     The storage subsystem(s)  714  and memory subsystems ( 706  and  718 ) serve as computer readable media for volatile and non-volatile storage of data, data structures, computer-executable instructions, and so forth. Such instructions, when executed by a computer or other machine, can cause the computer or other machine to perform one or more acts of a method. The instructions to perform the acts can be stored on one medium, or could be stored across multiple media, so that the instructions appear collectively on the one or more computer-readable storage media, regardless of whether all of the instructions are on the same media. 
     Computer readable media can be any available media that can be accessed by the computer  702  and includes volatile and non-volatile internal and/or external media that is removable or non-removable. For the computer  702 , the media accommodate the storage of data in any suitable digital format. It should be appreciated by those skilled in the art that other types of computer readable media can be employed such as zip drives, magnetic tape, flash memory cards, flash drives, cartridges, and the like, for storing computer executable instructions for performing the novel methods of the disclosed architecture. 
     A user can interact with the computer  702 , programs, and data using external user input devices  728  such as a keyboard and a mouse. Other external user input devices  728  can include a microphone, an IR (infrared) remote control, a joystick, a game pad, camera recognition systems, a stylus pen, touch screen, gesture systems (e.g., eye movement, head movement, etc.), and/or the like. The user can interact with the computer  702 , programs, and data using onboard user input devices  730  such a touchpad, microphone, keyboard, etc., where the computer  702  is a portable computer, for example. These and other input devices are connected to the processing unit(s)  704  through input/output (I/O) device interface(s)  732  via the system bus  708 , but can be connected by other interfaces such as a parallel port, IEEE 1394 serial port, a game port, a USB port, an IR interface, short-range wireless (e.g., Bluetooth) and other personal area network (PAN) technologies, etc. The I/O device interface(s)  732  also facilitate the use of output peripherals  734  such as printers, audio devices, camera devices, and so on, such as a sound card and/or onboard audio processing capability. 
     One or more graphics interface(s)  736  (also commonly referred to as a graphics processing unit (GPU)) provide graphics and video signals between the computer  702  and external display(s)  738  (e.g., LCD, plasma) and/or onboard displays  740  (e.g., for portable computer). The graphics interface(s)  736  can also be manufactured as part of the computer system board. 
     The computer  702  can operate in a networked environment (e.g., IP-based) using logical connections via a wired/wireless communications subsystem  742  to one or more networks and/or other computers. The other computers can include workstations, servers, routers, personal computers, microprocessor-based entertainment appliances, peer devices or other common network nodes, and typically include many or all of the elements described relative to the computer  702 . The logical connections can include wired/wireless connectivity to a local area network (LAN), a wide area network (WAN), hotspot, and so on. LAN and WAN networking environments are commonplace in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which may connect to a global communications network such as the Internet. 
     When used in a networking environment the computer  702  connects to the network via a wired/wireless communication subsystem  742  (e.g., a network interface adapter, onboard transceiver subsystem, etc.) to communicate with wired/wireless networks, wired/wireless printers, wired/wireless input devices  744 , and so on. The computer  702  can include a modem or other means for establishing communications over the network. In a networked environment, programs and data relative to the computer  702  can be stored in the remote memory/storage device, as is associated with a distributed system. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used. 
     The computer  702  is operable to communicate with wired/wireless devices or entities using the radio technologies such as the IEEE 802.xx family of standards, such as wireless devices operatively disposed in wireless communication (e.g., IEEE 802.11 over-the-air modulation techniques) with, for example, a printer, scanner, desktop and/or portable computer, personal digital assistant (PDA), communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This includes at least Wi-Fi (or Wireless Fidelity) for hotspots, WiMax, and Bluetooth™ wireless technologies. Thus, the communications can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies called IEEE 802.11x (a, b, g, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wire networks (which use IEEE 802.3-related media and functions). 
     The illustrated and described aspects can be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in local and/or remote storage and/or memory system. 
     What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and/or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.