Opening network-enabled electronic documents

BACKGROUND

Currently, users may open network-enabled electronic documents by selecting links. Some links cause a specific software application associated with the electronic document to load the electronic document. Some other links cause a network browser to render the electronic document.

Assume, for example, that a sales manager wants to enable his or her salesmen to be able to open an electronic document to record their sales. The sales manager may send an email to the salesmen with two links to the electronic document: one for opening the electronic document using a specific software application associated with the electronic document; and one for opening the electronic document with a network browser.

SUMMARY

System(s), method(s), and/or technique(s) (“tools”) are described that enable a user to open a network-enabled electronic document in either a specific software application associated with the electronic document or a network browser. In some cases the tools do so using a single link. On selection of the link, if the user's computing device has access to the specific software application, the tools may load the electronic document using that application. Or, if the user's computing device does not have access to the specific software application, the tools may render the electronic document with a network browser. In so doing, the tools may make the document available to a larger set of potential users through their browsers, allow users the convenience of accessing the document within a browser, optimize users' experience in working with the document through a specific software application, or provide a simpler opening procedure.

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 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.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates an exemplary operating environment in which various embodiments of the tools may operate.

<figref idrefs="DRAWINGS">FIG. 2</figref> is an exemplary process illustrating some ways in which the tools open a network-enabled electronic document in either a specific software application associated with the electronic document or a network browser when the electronic document is selected with a link in a document library.

<figref idrefs="DRAWINGS">FIG. 3</figref> is an exemplary process illustrating some ways in which the tools open an electronic document responsive to a user selecting the electronic document with a link in a webpage, an email, or another document.

<figref idrefs="DRAWINGS">FIG. 4</figref> is an exemplary process describing ways in which the tools determine whether to open in a network browser or a specific software application.

<figref idrefs="DRAWINGS">FIG. 5</figref> shows an exemplary flow diagram with actions and/or communications between elements of <figref idrefs="DRAWINGS">FIG. 1</figref>.

The same numbers are used throughout the disclosure and figures to reference like components and features.

DETAILED DESCRIPTION

Overview

The following document describes tools capable of enabling a user to open a network-enabled electronic document in either a specific software application associated with the electronic document or a network browser. The tools may decide between these options based on: whether the user's computing device has access to the specific software application or a version of that application capable of fully implementing the electronic document's functions; a pre-selected setting or default; or the user's selection, among others.

An environment in which the tools may enable these and other actions is set forth below in a section entitled Exemplary Operating Environment. This section is followed by another section describing exemplary ways in which the tools open a network-enabled electronic document responsive to the electronic document being selected with a link in a document library, entitled Selecting an Electronic Document with a Link in a Document Library. Another section follows and describes exemplary ways in which the tools open a network-enabled electronic document responsive to the electronic document being selected with other types of links, entitled Selecting an Electronic Document with a Link in a Webpage, Email, or Document. A final section, entitled Determining Where to Open Electronic Documents, sets forth an exemplary process by which the tools may determine whether to open an electronic document in a network browser or a specific software application. These section titles are provided for the reader's convenience and do not alter or limit the scope of the entitled sections.

Exemplary Operating Environment

Before describing the tools in detail, the following discussion of an exemplary operating environment is provided to assist the reader in understanding one way in which various inventive aspects of the tools may be employed. The environment described below constitutes but one example and is not intended to limit application of the tools to any one particular operating environment. Other environments may be used without departing from the spirit and scope of the claimed subject matter.

<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates one such operating environment generally at <b>100</b> comprising a client computing device <b>102</b> having one or more client processor(s) <b>104</b> and client computer-readable media <b>106</b>. The client computing device is shown with a desktop computer icon but may be another type of computing device, such as a smart phone, laptop, or personal digital assistant. The client processors are capable of accessing and/or executing the computer-readable media. The client computer-readable media comprises or has access to a network browser <b>108</b>, which is a module, program, or other entity capable of interacting with a network-enabled entity, a detection module <b>110</b>, and a specific software application <b>112</b>.

The detection module is capable of detecting whether or not the client computing device has access to the specific software application and, in some cases, the specific software application's version and capabilities. It may be part of or separate from the network browser and comprise script and/or an ActiveX module. The specific software application is capable of opening a specific type of electronic document, such as an Excel™ application that is capable of editing Excel™-type spreadsheet electronic documents or an Infopath™ application that is capable of editing Infopath™-form types of electronic documents. The specific software application may also comprise or be affected by a document loading module <b>114</b>, which is capable of causing an electronic document to be loaded and opened within the specific software application.

The operating environment also comprises a network <b>116</b> and server(s) <b>118</b> (“servers”). The network enables communication between the client and the servers, and may comprise a global or local wired or wireless network, such as the Internet or a company's intranet.

The servers comprise a single server or multiple servers, such as a server farm, though the servers may also comprise additional server or non-server entities capable of communicating with other entities or of governing the individual servers. The servers are shown with three separate servers <b>118</b><i>a</i>, <b>118</b><i>b</i>, and <b>118</b><i>c </i>operating serially or in parallel to service requests.

The servers comprise servers' processors <b>120</b> and server computer-readable media <b>122</b>. The server processors are capable of accessing and/or executing the server computer-readable media. The server computer-readable media comprises or has access to a request handler <b>124</b>, and a network electronic document application <b>126</b>. The request handler is capable of receiving or intercepting requests, such as requests generated responsive to a user selecting to open an electronic document. The network electronic document application is capable of servicing an electronic document, such as by creating and providing HTML (“HyperText Markup Language”) enabling the network browser to render the electronic document and receiving and saving edits to the electronic document.

Selecting an Electronic Document with a Link in a Document Library

The following discussion describes exemplary ways in which the tools open a network-enabled electronic document in either a specific software application associated with the electronic document or a network browser responsive to the electronic document being selected with a link in a document library. A document library may comprise, for example, a web page containing a collection of electronic documents and a way in which to select a link to each of these documents. This discussion refers to particular elements, such as elements of operating environment <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, though other elements and environments may be used.

When a user selects a link, such as a hyperlink in a document library to open an electronic document, the tools determine whether or not a specific software application associated with the electronic document is available on or accessible by the user's computing device (e.g., it is installed). The tools also determine whether or not the specific software application is of a version compatible with the electronic document. If both of these are true, the tools may load the electronic document on the user's computing device with the specific software application. In some cases there is an indication (e.g., a previously selected setting) indicating that the electronic document should only be opened in the network browser. In these cases the tools may forgo these actions and immediately open the electronic document in the network browser.

If the specific software application associated with the electronic document is not accessible or is accessible but of an incompatible version, the tools may also open the electronic document with the user's network browser. To do so, the tools may, in some cases, cause the network browser to navigate to a page with appropriate query parameters sufficient to cause the browser to open the electronic document on that page.

The tools may behave in either of these manners regardless of whether the user is selecting to create a new electronic document or is selecting an existing electronic document. Also, when the user is done with the electronic document, the tools may return the user to the page that was used to open the document (e.g., the document library page or other page through which the link was selected). An exemplary process performing some of the above actions is set forth immediately below.

<figref idrefs="DRAWINGS">FIG. 2</figref> is an exemplary process <b>200</b> illustrating some ways in which the tools open a network-enabled electronic document selected with a link in a document library. The process is illustrated as a series of blocks representing individual operations or acts performed by elements of operating environment <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, such as detection module <b>110</b> and request handler <b>124</b>. This and other processes disclosed herein may be implemented in any suitable hardware, software, firmware, or combination thereof, in the case of software and firmware, these processes represent a set of operations implemented as computer-executable instructions stored in computer-readable media and executable by one or more processors.

Block <b>202</b> receives a selection through a link to a document library for a network-enabled electronic document. A user, for instance, may click on an icon (e.g., a button graphic) associated with, or text for, a universal resource locator (URL) to select the electronic document in the document library.

Block <b>204</b> determines whether the electronic document is accessible through the document library, such as by being on a shared enterprise server (e.g., a SharePoint™ server). If yes, the tools proceed to block <b>206</b>. If no, the tools proceed to block <b>212</b>.

Block <b>206</b> determines whether the document library has a previously selected or default setting indicating that the electronic document should be opened in the network browser regardless of whether or not the specific software application associated with the electronic document is accessible and of a compatible version. If yes (it does have a setting), the tools proceed to block <b>208</b>. If no, the tools proceed to block <b>210</b>.

Block <b>208</b> redirects the network browser to a page on which the electronic document may be opened. Here the tools redirect the network browser to a dynamic server-generated browser page that is capable of opening the electronic document. This dynamic server-generated browser page may be generated using asp, aspx, jsp, php, and cgi technologies, for example, which permit the document to be displayed as part of the dynamic server-generated browser page. Here the tools use a URL having the URL for the electronic document along with query parameters. These query parameters indicate whether the document library is set for the electronic document to be opened in the browser even if the specific software application is accessible. These query parameters may contain an encoded server-relative path to the electronic document's file and an encoded absolute path to the page that was used to open the file. The absolute path parameter may later be used by the network browser to navigate back to that page when the electronic document is closed.

Block <b>210</b> determines whether the user has a right to open the electronic document in the specific software application. The tools may determine this based on a security setting in the file for the electronic document, which may be referenced in the path of the request. If no, the tools proceed to block <b>208</b> and redirect the network browser. If yes, the tools proceed to block <b>212</b>.

Block <b>212</b> determines if the specific software application associated with the network-enable electronic document is accessible and, in some cases, whether it is of a compatible version. Here block <b>212</b> determines whether or not a document loading module associated with the specific software application is installed (e.g., an ActiveX module) on the user's computing device. If yes, the tools proceed to block <b>214</b>. If no, the tools proceed to block <b>208</b>.

Block <b>214</b> opens the electronic document with the specific software application. Here the tools use the document loading module to open the electronic document in the specific software application. The document loading module may receive, as a parameter, the URL for the electronic document. With this parameter, the specific software application requests the file for the electronic document in such a way that the server can distinguish the request from a network browsers request. In one particular embodiment, the server distinguishes the request with a translate F HTTP header, receives the file, and opens the electronic document.

Selecting an Electronic Document with a Link in a Webpage, Email, or Document

The following discussion describes exemplary ways in which the tools open a network-enabled electronic document in either a specific software application associated with the electronic document or a network browser responsive to the electronic document being selected with a link in a webpage, email, or document. This discussion refers to particular elements, such as elements of operating environment <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, though other elements and environments may be used.

When a user selects a link to open an electronic document through a webpage, email, document (e.g., a word-processing document), or the like, the tools determine whether or not a specific software application associated with the electronic document is accessible by the user's computing device (e.g., it is installed) and is of a version compatible with the electronic document.

If these are both true, the tools cause the specific software application to open the electronic document. If these are not both true, the tools cause the network browser to open the electronic document. To open the electronic document using the network browser, the tools cause the network browser to navigate to a page with appropriate query parameters sufficient to cause the browser to open the electronic document on that page.

The tools may behave in either of these manners regardless of whether the user is selecting a new or existing electronic document. When the user is done with the electronic document, the tools may return the user to the document library page or other page through which the user selected the link. An exemplary process performing some of the above actions is set forth immediately below.

<figref idrefs="DRAWINGS">FIG. 3</figref> is an exemplary process <b>300</b> illustrating some ways in which the tools open an electronic document responsive to a user selecting the electronic document with a link in a webpage, an email, or another document. The process is illustrated as a series of blocks representing individual operations or acts performed by elements of operating environment <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, such as detection module <b>110</b> and request handler <b>124</b>.

Block <b>302</b> receives a selection through a link in a webpage, email, or other document and for a network-enabled electronic document. A user, for instance, may click on a universal resource locator (URL) link in an email to select the electronic document.

Block <b>304</b> determines whether or not the user has a right to open the electronic document at least in the network browser. The tools may do so through information in the file for the electronic document, such as security settings and the identity of the user or machine through which the user selected the link. If block <b>304</b> determines that the user does not have this right, the tools may end the process and/or provide an error message (not shown).

Block <b>306</b> determines whether or not the electronic document should only be opened in the network browser. The tools may determine that the electronic document should be loaded in the network browser even if the user's computing device has access to the specific software application based on a default setting or a previously selected setting. If yes (it should be opened in the network browser), the tools proceed to block <b>308</b>. If no, the tools proceed to block <b>310</b>.

Block <b>308</b> renders the electronic document through the network browser. The tools may do so using a server having software tailored to the electronic document, such as an electronic-form-ready server for an electronic-form type of electronic document or a spreadsheet-ready server for an electronic document comprising spreadsheets.

Block <b>310</b> determines whether the user has a right to open the electronic document in the specific software application. The tools may determine this based on a security setting in the file for the electronic document, which may be referenced in the path of the request. If yes, the tools proceed to block <b>312</b>. If no, the tools proceed to block <b>308</b> and render the electronic document.

Block <b>312</b> determines whether an identifier for the specific software application is present and, if so, whether it indicates a version equal to or greater than the electronic document's version. The tools may do so based on query parameters in the header. These query parameters may include those noted as part of process <b>200</b> above. If no, the tools proceed to block <b>308</b> and render the electronic document. If yes, the tools proceed to block <b>314</b>.

Block <b>314</b> opens the electronic document with the specific software application. The tools may receive, as a parameter, the URL for the electronic document. The tools may then return the electronic document's content such that it will be opened by the specific software application. Or it may then compute a URL for a redirect to the specific software application or append query parameters to the URL for the selected link. These parameters may include those noted as part of process <b>200</b>. This URL or appended URL is used by the tools to launch the specific software application either with a <b>302</b> redirect to the appended URL or by passing the URL to the document loading module.

Determining where to Open Electronic Documents

The following discussion describes these and alternative ways in which the tools determine where to open a network-enabled electronic document. By way of example, this discussion refers to particular elements, such as elements of operating environment <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, processes <b>200</b> and <b>300</b>, and flow diagram <b>500</b> of <figref idrefs="DRAWINGS">FIG. 5</figref>.

<figref idrefs="DRAWINGS">FIG. 4</figref> is an exemplary process <b>400</b> illustrated as a series of blocks representing individual operations or acts performed by elements of operating environment <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>, such as detection module <b>110</b> and request handler <b>124</b>.

Block <b>402</b> intercepts a request generated by a user selecting a link to open an electronic document. The link may be to open an electronic document in a document library as set forth in process <b>200</b> or a link in a webpage, email, or other document as set forth in process <b>300</b>. In some cases selection of this link, if it were not intercepted, would cause the specific software application to open the electronic document. In some others, if it were not intercepted, this selection would cause the network browser to open the electronic document.

This link may include information indicating what version or capabilities are needed in a specific software application associated with the requested electronic document to enable the functionality of the electronic document. Alternatively or conjunctively, the detection module may inspect the contents of the electronic document to determine the document's version or capabilities.

<figref idrefs="DRAWINGS">FIG. 5</figref> is an exemplary flow diagram showing actions and/or communications between elements of <figref idrefs="DRAWINGS">FIG. 1</figref>. Here the request generated by selection of the link is intercepted from network browser <b>108</b> (on client computing device <b>102</b>) by request handler <b>124</b> over communications network <b>116</b>. Communications over the communications network are shown with arrows over a dashed line. This interception is marked with arrow <b>1</b>.

Block <b>404</b> determines whether or not the user's computing device has access to a specific software application associated with the requested electronic document or whether the electronic document was previously selected to be opened only in a network browser. Block <b>404</b> may also determine the capabilities of the specific software application and/or its version.

Here the request handler asks detection module <b>110</b> whether the user's computing device has access to the specific software application and for its version. The detection module receives this query for information from the request handler, shown at arrow <b>2</b>. The detection module determines whether the user's client computing device has access to the specific software application (e.g., it is installed) and, if it does, the application's version. The detection module then provides this information, shown at arrow <b>3</b>, which is received by the request handler. This communication between the request handler and the detection module may be indirect, such as through the network browser.

Block <b>404</b> may decide whether or not to make this determination based on the request having information indicating that the requested electronic document may possibly be opened using remote resources (e.g., network electronic document application <b>126</b>) or local resources (e.g., specific software application <b>112</b>). In some cases this information is a particular extension in a URL for the request, such as an “.xls” extension for a spreadsheet type of electronic document or an “.xml” extension for an electronic-form type of electronic document. In some other cases, this information is or is derived from meta-information promoted from the document to a filing system or document library.

Block <b>404</b> may also determine that the electronic document was previously selected to be opened only in the network browser based on having information indicating that the requested electronic document's URL comprises a particular parameter. This permits designers or other users of an electronic document to ensure that the electronic document is only opened in the network browser even if the user's client computing device has access to the specific software application associated with that electronic document.

Process <b>400</b> proceeds to block <b>406</b> if the user's client computing device does not have access (and/or an appropriate version or capabilities) to the specific software application or is previously set to be opened by the network browsers. Alternatively, an additional selection may be requested from the user, such as a dialog box asking whether or not the user wishes to open the electronic document in either the network browser or the specific software application (not shown). A user's selection to open the electronic document in the network browser may be determinative. Otherwise, the process proceeds to block <b>408</b>.

Block <b>406</b> causes the electronic document to be opened in a network browser. If the request would have caused the electronic document to be opened in the specific software application—if it were not intercepted—the request handler alters the request effective to enable the network browser to handle the request. This dynamic alteration to the request causes data to be sent to the user's client computing device using a different format than were it not altered. Here the request handler alters the request and submits it to the network electronic document application effective to cause the network electronic document application to send data in a format acceptable for direct rendering in the network browser (e.g., HTML), rather than in the format used by the specific software application (e.g., the format corresponding to the physical file for the electronic document). This is shown in <figref idrefs="DRAWINGS">FIG. 5</figref> at arrows <b>4</b><i>a </i>and <b>5</b><i>a. </i>

Block <b>408</b> causes a specific software application associated with the selected electronic document to open the electronic document. The request handler may instruct the detection module or document loading module <b>114</b> to request a physical file (e.g., a non-rendering file) for the electronic document in a format usable by the specific software application. This is shown at arrow <b>4</b><i>b</i>. The request handler may do so by dynamically altering the request from the user's selection and sending this altered request to the detection module or document loading module and telling it to make a request using this altered request. The request handler alters the user's request by appending query parameters to it (such as those noted in process <b>200</b> or <b>300</b> above).

Here the detection module receives these instructions and makes a request for a physical file. The detection module makes the request of the network electronic document application, though it may make the request of any source (local or remote) capable of supplying the physical file (arrow <b>5</b><i>b</i>). This physical file is effective to enable the specific software application to open the electronic document on the user's client computing device. In response, the network electronic document application provides the physical file to the detection module at arrow <b>6</b><i>b. </i>

The detection module receives the physical file and causes the document loading module to load the physical file and the specific software application effective to cause the specific software application to open the electronic document. This is shown at arrows <b>7</b><i>b </i>and <b>8</b><i>b</i>. The document loading module may know to cause the specific software application to load the physical file based on information provided in the physical file, such as its format being compatible with the specific software application but not with the network browser.

In cases where the link is selected by the user through the network browser, such as in a webpage, the tools may remain or return to that webpage. For instance, if a user selects a link in a webpage opened in the network browser, the tools may open the electronic document with the specific software application or within the webpage.

Each of the above acts, includes blocks of process <b>200</b>, <b>300</b>, and <b>400</b>, may all be performed without user interaction other than the user's selection of a link to open an electronic document. This enables a user, with as little as one selection of one link, to open an electronic document in either a network browser or a specific software application, as appropriate. A user may not need, for example, to know whether his or her client computing device has access to the specific software application, that the specific software application is of an appropriate version or capabilities, or that the electronic document should be opened in the network browser even if the user's device has an appropriate specific software application installed.

CONCLUSION

The above-described systems, methods, and/or techniques enable a user to open a network-enabled electronic document in either a specific software application associated with the electronic document or a network browser. In some cases the user may do so through selection of a single link. Although the systems and methods have been described in language specific to structural features and/or methodological acts, it is to be understood that the systems and methods defined in the appended claims are not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed systems and methods.