Patent Application
20120278281
When users send files that are attached to an electronic message, they create multiple copies of a given file. Not only does a copy of the attachment exist in each user's mailbox, the attachment is often stored in other locations as well. When a user replies with changes to the attachment they create yet another copy and version of the attachment.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
A link to a shared version of a local file is inserted into metadata of the local file. The local file may be a copy of a shared file and/or a local file that is designated to be shared. For example, when a local file is uploaded to a shared location for collaboration, a link to the shared location is automatically inserted into metadata of the local file. A local copy of a shared file may be created by downloading the shared file to a local data store. A link to the shared location is automatically inserted into the locally stored. When the local file is opened, the link within the metadata may be used to access the version of the local file at the shared location. Changes made to the local file and/or shared version of the file may also be synchronized.
Referring now to the drawings, in which like numerals represent like elements, various embodiment will be described. In particular,
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Other computer system configurations may also be used, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Distributed computing environments may also be used where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Referring now to
A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 10. The computer 100 further includes a mass storage device 14 for storing an operating system 16, messaging application(s) 24, Web browser 25, and sharing manager 26 which will be described in greater detail below.
The mass storage device 14 is connected to the CPU 5 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media provide non-volatile storage for the computer 100. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, the computer-readable media can be any available media that can be accessed by the computer 100.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, 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. Computer storage media includes, but is not limited to, RAM, ROM, Erasable Programmable Read Only Memory (“EPROM”), Electrically Erasable Programmable Read Only Memory (“EEPROM”), flash memory or other solid state 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 the computer 100.
Computer 100 operates in a networked environment using logical connections to remote computers through a network 18, such as the Internet. The computer 100 may connect to the network 18 through a network interface unit 20 connected to the bus 12. The network connection may be wireless and/or wired. The network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The computer 100 may also include an input/output controller 22 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIG. 1). Similarly, an input/output controller 22 may provide input/output to a display screen 23, a printer, or other type of output device.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 9 of the computer 100, including an operating system 16 suitable for controlling the operation of a computer, such as the WINDOWS PHONE 7®, WINDOWS 7®, or WINDOWS SERVER® operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 9 may also store one or more program modules. In particular, the mass storage device 14 and the RAM 9 may store one or more application programs, such as one or more messaging application(s) 24 and one or more document application(s) 25. File application(s) 25 may be many different type of applications, such as a word processing application, a presentation application, a photo program, a spreadsheet application, and the like.
A user interface 15 is used by a user to interact with applications and files. Messaging application(s) 24 may be one or more different messaging applications. For example, computing device 100 may include an email application, an Instant Messaging (IM) application, an SMS, MMS application, a real-time information network (e.g. Twitter® interface), a social networking application, and the like. According to an embodiment, messaging application 24 is an email application, such as MICROSOFT OUTLOOK®. The messaging application(s) may be client based and/or web based. For example, a network based message service 17 may be used, such as: MICROSOFT WINDOWS LIVE or some other network based service.
Network share 27 is configured to store content (e.g. files, spreadsheets, Web content, and the like) that are accessible to one or more users through IP network 18. For example, network share 27 may store content that is accessible by users located at one or more locations.
Sharing manager 26 is configured to automatically insert a link to a file at a shared location in response to a local file being shared and/or a local version of a shared file being created. For example, in response to detecting when a local file, such as local file 19, is shared (e.g. at network share 27), sharing manager 26 inserts metadata into the local file that includes a link to shared version of the file at the shared location. Similarly, in response to a file at shared location 27 being downloaded and a local copy of the shared file being created, sharing manager 26 inserts metadata into the local copy of the shared file that includes a link to shared version of the file at the shared location. Sharing manager 26 may be located externally from an application, e.g. messaging application 24 or file application 25, as shown or may be a part of an application. Further, all/some of the functionality provided by sharing manager 26 may be located internally/externally from an application.
Sharing manager 26 is configured to insert metadata including a link within a local file. The term “link” refers to an address that represents a location of content. For example, a link may be in the form of a Uniform Resource Locator (URL) that specifies a network location of where the content is stored. Selecting the link generally retrieves the content that is pointed to by the link. Sharing manager 26 creates a link to the shared version of the local file at the shared location and inserts the metadata including the link into the local file. For example, when a local file is uploaded to a shared location for collaboration and/or downloaded to create a local copy of the shared file, sharing manager 26 automatically inserts the created link to the shared location and metadata into the local file. The local file that is uploaded/downloaded may be many different type of files (e.g. word processing documents, pictures, web content, spreadsheets, and the like). When the local file is opened, the link within the metadata may be used to retrieve the version of the local file at the shared location. Changes made to the local file and/or shared version of the file may also be synchronized. More details regarding the sharing manager are disclosed below.
The computing devices may be any type of computing device that is configured to perform the operations relating to sharing files. For example, some of the computing devices may be: mobile computing devices (e.g. cellular phones, tablets, smart phones, laptops, and the like); desktop computing devices and servers. Some computing devices may be arranged to provide an online service (e.g. messaging service 240 that is configured for sending and receiving electronic messages, a document service 250 that is configured for interacting with documents, and the like), some may be arranged as data shares, some may be arranged in local networks, some may be arranged in networks accessible through the Internet, and the like.
The computing devices are coupled through network 18. Network 18 may be many different types of networks. For example, network 18 may be an IP network, a carrier network for cellular communications, and the like. Generally, network 18 is used to transmit data between computing devices, such as computing device 1, computing device 2, network share 230, messaging service 240, and document service 250.
Computing device 1 includes application 212, user interface 216 and local file 218. As illustrated, computing device 1 is used by a user to interact with applications, local files that are stored local to computing device 1 and shared files that are stored in a shared location (e.g. shared file(s) 232).
User interface (UI) 216 is used to interact with applications and content, such as application 212 and shared files and/or local files. One or more user interfaces of one or more types may be used to interact with the content. For example, UI 216 may include the use of a context menu, a menu within a menu bar, a menu item selected from a ribbon user interface, a graphical menu, and the like. Generally, UI 216 is configured such that a user may easily interact with content. For example, a user may simply select an option within UI 216 to create a shared version of a local file (e.g. local file 218) at shared location 230. UI 216 may also be used to display information relating to shared files. For example, upon detection of a link to a shared file that is within metadata of a local file, UI 216 may display a selectable option to allow a user to view the shared version of the local file. UI 216 may also be used to set/change permissions that are to be associated with the shared attachment. For example, UI 216 may be used to change read/write permissions for one or more users of the shared document.
Application 212 may be a client based application, such as a document application, an email application, an Instant Messaging Application, a social media application, and the like. Generally, application 212 is used to share a local file at a shared location and interact with the local/shared files. A network based application, such as messaging service 240 and/or document service 250 may be used in addition to application 212 or instead of one or more of the applications. For example, a web interface may be used to access an online service, such as messaging service 240 and/or document service 250.
Messaging service 240 may be used to process electronic messages between one or more computing devices, such as computing device 1 and computing device 2. Messaging service 240 may be configured to process different message types, such as SMS, MMS, email, messages for social networks and the like. Messaging service 240 may be configured with the functionality of sharing manager 26 and one or more message types may be used to communicate the electronic messages including links to shared content that are related to attachments that were designated to be shared.
Document service 250 may by one or more computing devices, such as computing device 1 and computing device 2, to interact with documents, such as shared file(s) 232. Document service 250 may be configured to interact with one or more types of documents, such as word-processing documents, spreadsheet documents, photos, and the like. Document service 250 may be configured with the functionality of sharing manager 26.
Computing device 2 includes one or more applications, such as a web browser 222 that may be configured to access an online service, such as messaging service 240 and document service 250. For example, web browser 222 may be used to access an electronic message through an email messaging service and then access a shared version of a local file 232 stored at shared location 230.
One or more network shares (e.g. shared location 230) may be used to store shared file(s) that are shared between users and/or accessed remotely, such as attachments that were initially included within an electronic message and were selected to be shared and local files that were designated to be shared. The shared content may be any type of content that can be shared (e.g. files such as word processing documents, spreadsheets, slides, website content and the like). Shared location 230 is accessible by the computing devices that interact with the shared file(s) 232. The shared location may be associated with an online service that supports online access/interaction with content (e.g. messaging service 240, document service 250).
According to an embodiment, sharing manager 26 is configured to detect any attachments to an electronic message and to provide an option to automatically upload the attachments to a shared location and permission the attachments for sharing between users. The attachments may be to any type of content, such as word processing documents, spreadsheets, slides, website content and the like. Generally, the attachment may be to any type of content that is accessible by a computing device. Sharing manager 26 inserts metadata into the local file that is not uploaded that includes a link to the shared location.
Sharing manager 26 is also configured to present one or more selectable options that when selected open the shared file from shared location 230. For example, when local file 218 is opened that has metadata that includes a link to a shared version of the local file at shared location 230, an option may be displayed to a user that when selected opens up the shared version of the local file from the shared location 230.
Sharing manager 26 detects when a local file is uploaded to a shared location and/or when local version of a shared file is created (e.g. a shared file 232 is downloaded to computing device 1). In response to the local file being shared and/or a local copy of a shared file being created, sharing manager 26 creates a link to the shared version of the local file that is stored at the shared location. According to an embodiment, the link is a URL to the shared file. Sharing manager 26 inserts metadata including the link into the local file such that the local file remains associated with the shared version of the local file. The metadata may be placed at different locations within the local file. According to an embodiment, the metadata is inserted into a file header of the local file.
Sharing manager 26 may also be configured to automatically permission the file at the shared network location. The permissions to be set for a file may be predetermined. For example, all files that are shared may be initially set for read/write access or read access or write access. Permissions may be set based on the type of file (e.g. word processing documents may be set to read/write whereas photos or pictures may be set to read only). The default permissions may be set by a user. According to an embodiment, sharing manager 26 is configured to present an option to change the default permissions. For example, a user may select a change permissions option to modify the permissions for one or more of the files for one or more of the users.
Sharing manager 26 may also be configured to synchronize changes made to either the shared file at shared location 230 and/or changes made to the local file 218. For example, a user may make one or more changes to local file 218 while they are not connected to shared location 230. When connection is restored, sharing manager 26 may synchronize the changes to shared file 232 at shared location 232. According to an embodiment, a cached version of the shared file is stored locally in a cache and changes are applied to the cached version. The cached version of the shared file is synchronized with the version stored at the shared location.
The electronic message may be accessed a number of ways. For example, a web browser may access an electronic mail service, an email application on a computing device may be configured to receive emails from one or more different services, and the like.
When electronic message 300 is created and/or received, one or more files may be attached to the message. The attachments may be to any type of content, such as word processing documents, spreadsheets, slides, websites and the like.
When an attachment is detected for the electronic message, an upload option 320 may be presented with the display of electronic message 300. Upload option may include one or more options. For example, a single selectable option may be displayed to upload an attachment or one or more other options may be included in an upload option menu for setting other options (e.g. changing shared location, changing permissions, including attachment with/without link to shared content, and the like).
As illustrated, message 300 includes attached file 310 that is a copy of local file 330. In response to attached file being shared, local file 330 is updated to include metadata 345. Metadata 345 includes a link to the shared version of the local file that is uploaded to the shared location. According to an embodiment, each version of the local file has metadata inserted to include the link. In the current example, metadata 345 is inserted into both local file 330 and attached file 310. In this way, if either one of the local files (attached file 310, local file 330) is opened, the link in the metadata may be used to access the shared version of the local file.
As illustrated, document application window 400 shows local file 410 being opened by a document editing application (e.g. a word processing application). In response to opening local file 410, a determination is made as to whether local file is shared by accessing metadata within the local file. According to an embodiment, the metadata is stored within the header of the local file and includes a link to the shared version of the local file. User interface 420 may be displayed in response to different events and determinations. For example, user interface 420 may be displayed each time local file 410 is opened. User interface 420 may be displayed in response to a determination that a more recent version of the local file is stored at the shared location.
After a start block, process 500 moves to operation 510, where a determination is made that a local file is shared. The determination may be made using different methods. For example, the determination that the local file is shared may be made in response to: a user selecting a sharing option relating to the local file; a search is performed in one or more shared locations for a shared version of the local file; a user may specify that a shared version of the local file exists, and the like.
Flowing to operation 520, a link to the shared version of the local file is created. According to an embodiment, the link is a URL to the shared version of the local file at the shared location.
Moving to operation 530, metadata is inserted into the local file. The metadata includes the link to the shared version and may include other information relating to the sharing of the local file (e.g. sharing permissions). According to an embodiment, the metadata is inserted into a header of the local file. The metadata may be stored in other ways. For example, a metadata store may be maintained that stores the metadata including the link separately from (but associated with) the local file.
Flowing to operation 540, a cached version of the local file may be optionally created. The cached version may be the shared version of the local file that is stored at the shared location and/or the cached version may be the local file that is stored locally. Instead of directly interacting with the shared version of the local file, the cached version may be accessed and changed.
Transitioning to operation 550, the local file may be synchronized with the shared version of the local file such that each version includes recent changes. According to an embodiment, the cached version of the local file is synchronized with the shared version at the shared location in response to network connectivity being restored to the shared location and/or in response to a user input requesting synchronization.
The process then flows to an end block and returns to processing other actions.
After a start block, process 600 moves to operation 610, where a shared file is accessed. The shared file may be accessed from a variety of locations such as a network share and/or some other network location.
Moving to operation 620, a local copy of the shared file is created. For example, a user may download a copy of the shared file to a local data store.
Flowing to operation 630, a link to the shared version of the local file is created. According to an embodiment, the link is a URL to the shared version of the local file at the shared location.
Moving to operation 640, metadata is inserted into the local file. The metadata includes the link to the shared version and may include other information relating to the sharing of the local file (e.g. sharing permissions). According to an embodiment, the metadata is inserted into a header of the local file. The metadata may be stored in other ways. For example, a metadata store may be maintained that stores the metadata including the link separately from (but associated with) the local file.
Flowing to operation 650, a cached version of the local file may be optionally created. The cached version may be the shared version of the local file that is stored at the shared location and/or the cached version may be the local file that is stored locally. Instead of directly interacting with the shared version of the local file, the cached version may be accessed and changed.
Transitioning to operation 660, the local file may be synchronized with the shared version of the local file such that each version includes recent changes. According to an embodiment, the cached version of the local file is synchronized with the shared version at the shared location in response to network connectivity being restored to the shared location and/or in response to a user input requesting synchronization.
The process then flows to an end block and returns to processing other actions.
After a start operation, process 700 flows to operation 710 where a determination is made that a local file is opened that is associated with a shared version. According to an embodiment, the local file is examined to determine whether or not the local file is associated with metadata that includes a link to a shared version of the local file.
Moving to operation 720, a determination may/may not be made to determine when the local file is different from the shared file (i.e. the shared version has been more recently updated). This determination may be used to determine when to display a user interface and/or when to perform a synchronization.
Transitioning to operation 730, a user interface may be displayed to open the shared version of the local file. For example, when the shared version of the local file is more recent than the local file, then the user interface may be displayed such that the user can access the shared version of the local file. The user interface may also be displayed whenever a local file is opened that is being shared. This helps to ensure that changes are made to a single instance of the file.
Flowing to operation 740, the shared file is opened when the user selects the option within the displayed user interface.
The process then flows to an end block and returns to processing other actions.
The above specification, examples and data provide a complete 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 resides in the claims hereinafter appended.
