Techniques for Managing Persistent Document Collections
Various technologies and techniques are disclosed for creating and managing persistent document collections. A data store is used for storing one or more persistent document collections. A content management application is used for managing documents for users, for creating one or more persistent document collections of a sub-set of the documents upon user request, and for storing the one or more persistent document collections in the data store. Users can create one or more persistent document collections from a sub-set of the documents. Users can also modify the one or more persistent document collections. A requested portion of one or more persistent document collections can be output upon request from an external application so that the external application can download one or more of the documents that are represented by the persistent document collection for further modification by the user.
Latest Microsoft Patents:
- APPLICATION SINGLE SIGN-ON DETERMINATIONS BASED ON INTELLIGENT TRACES
- SCANNING ORDERS FOR NON-TRANSFORM CODING
- SUPPLEMENTAL ENHANCEMENT INFORMATION INCLUDING CONFIDENCE LEVEL AND MIXED CONTENT INFORMATION
- INTELLIGENT USER INTERFACE ELEMENT SELECTION USING EYE-GAZE
- NEURAL NETWORK ACTIVATION COMPRESSION WITH NON-UNIFORM MANTISSAS
This application is a continuation of, claims the benefit of and priority to, previously filed U.S. patent application Ser. No. 15/453,320 entitled “Techniques for Managing Persistent Document Collections” filed on Aug. 3, 2017, which is a continuation of, claims the benefit of and priority to, previously filed U.S. patent application Ser. No. 14/736,839 entitled “Techniques for Managing Persistent Document Collections” filed on Jun. 11, 2015, which is a continuation of, claims the benefit of and priority to, previously filed U.S. patent application Ser. No. 14/602,822 entitled “Techniques for Managing Persistent Document Collections” filed on Jan. 22, 2015, which is a continuation of, claims the benefit of and priority to, previously filed U.S. patent application Ser. No. 12/336,554 entitled “Techniques for Managing Persistent Document Collections” filed on Dec. 17, 2008, and issued on Feb. 24, 2015 as U.S. Pat. No. 8,965,926, the subject matter of which are hereby incorporated by reference in their entireties.
BACKGROUNDMany document management applications such as MICROSOFT® Office SharePoint Server enable users to organize documents in a series of lists or libraries. Such document management applications can typically be accessed through a web browser or a rich client interface, and make it easy for organizations to share documents with various team members. When adding a new document through the document management application, the user typically selects which list or library to add the document to. Other users can then find that document by accessing that library specifically, or by performing one or more query searches across libraries to locate one or more documents of interest.
If the user wants to work with the same set of documents over a period of time, he or she typically has two options. The first option is that the user can perform the search multiple times to keep re-locating the documents. The second option is that the user can keep track of which varying libraries actually contain the documents that he or she is interested in working with. And then each time the user is ready to work with those documents, he/she must navigate to those respective libraries one by one to access the respective document of interest.
SUMMARYVarious technologies and techniques are disclosed for creating and managing persistent document collections. In one implementation, a system for creating and managing persistent document collections is described. The system includes a data store is used for storing one or more persistent document collections. The system also includes a content management application that is used for managing documents for users, for creating one or more persistent document collections of a sub-set of the documents upon user request, and for storing the one or more persistent document collections in the data store.
In another implementation, a method is disclosed for enabling users to create and manage one or more persistent document collections. Documents that are managed by a content management application are displayed for user review. An add selection is received from a user which specifies at least one of the documents to add to a persistent document collection. The user can optionally specify additional attributes about the persistent document collection, such as storage space to allocate, etc. The persistent document collection is then created and stored in a data store.
In yet another implementation, techniques are described for a content management application that also allows external applications to access and manage documents contained in one or more persistent document collections. Users can create one or more persistent document collections from a sub-set of the documents. Users can also modify the one or more persistent document collections. A requested portion of one or more persistent document collections can be output upon request from an external application so that the external application can download one or more of the documents that are represented by the persistent document collection for further modification by the user.
This Summary was 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.
The technologies and techniques herein may be described in the general context as an application that manages persistent document collections, but the technologies and techniques also serve other purposes in addition to these. In one implementation, one or more of the techniques described herein can be implemented as features within a content management application such as MICROSOFT® Office SharePoint Server, or from any other type of program or service that manages documents for multiple users. In another implementation, one or more of the techniques described herein are implemented as features with other applications that interact with content management applications.
In one implementation, techniques are described for enabling users to create persistent document collections. The term “persistent document collection” as used herein is meant to include a group of one or more documents that are identified by a name or other identifier, and that get stored so that one or more users can access the underlying documents through the assigned grouping at later points in time. In another implementation, one or more of these persistent document collections can be accessed by one or more external applications to allow the user to work with them further from those external applications, or to allow those externals applications to perform other operations independently of the user. The term “external application” as used herein is meant to include an application that is separate from the document management application that created the persistent document collection(s).
Once created, the persistent document collection(s) are then stored in one or more data stores, such as data store 104. Depending on the implementation used, the content management application 102 handles interactions with the data store 104 and/or user interface 106 handles interactions with the data store 104. For example, when content management application 102 is a web application that resides on a web server, and with user interface 106 being displayed to the user in a web browser, then content management application 102 may handle interactions with the data store 104 directly. In other implementations, user interface 106 may contain logic for interacting directly with the data store 104, such as when user interface and content management application 102 are contained as part of the same executable file on a client computer. In either scenario, by storing the document collection(s) that get created by the user, the same and/or other users are able to access this grouping of documents more easily on later interactions with the content management application 102.
Turning now to
Yet another non-limiting example of an attribute that can be specified for a persistent document collection includes which one or more external applications should be allowed to access this persistent document collection. These are just a few non-limiting examples of the types of attributes that can be assigned to one or more persistent document collections. In other implementations, fewer and/or additional attributes could be used.
The persistent document collection is then stored in a data store (stage 210) so that the user who created it or other users with appropriate security permissions can access it later. The steps can be repeated to allow more documents to be added at a later time to this persistent document collection or a different persistent document collection (stage 212).
A list of documents that are part of a persistent document collection are displayed (stage 222), such as on a computer screen of a user. The user is able to specify a remove selection to remove selected document(s) from the persistent document collection, and the content management application processes the user selection when it is received to remove the document from the specified persistent document collection (stage 224). Alternatively or additionally, the user is also able to select one or more of the documents to view, and the content management application displays the contents of the selected document(s) in a user interface of the user when such a selection is received from the user (stage 226).
Turning now to
Turning now to
As shown in
Additionally, device 500 may also have additional features/functionality. For example, device 500 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in
Computing device 500 includes one or more communication connections 514 that allow computing device 500 to communicate with other computers/applications 515. Device 500 may also have input device(s) 512 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 511 such as a display, speakers, printer, etc. may also be included. These devices are well known in the art and need not be discussed at length here.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. All equivalents, changes, and modifications that come within the spirit of the implementations as described herein and/or by the following claims are desired to be protected.
For example, a person of ordinary skill in the computer software art will recognize that the examples discussed herein could be organized differently on one or more computers to include fewer or additional options or features than as portrayed in the examples.
Claims
1. A data processing system comprising:
- a processor; and
- a memory in communication with the processor, the memory storing executable instructions that when executed by the processor, cause the data processing system to perform functions of: managing documents for a plurality of users; receiving user input from a client-side web browser associated with one of the plurality of users; creating a persistent document collection upon receiving the user input from the client-side web browser, the persistent document collection comprising one or more documents; assigning a first attribute to the persistent document collection, the first attribute specifying an external application that can access the persistent document; assigning a second attribute to the persistent document collection, the second attribute specifying an amount of disk space to allocate to the persistent document collection; and storing the one or more persistent document collections in the memory, in storage space allocated to the one or more persistent document collections; wherein the persistent document collection enables one of the plurality of users to access the one or more documents.
2. The data processing system of claim 1, wherein the executable instructions, when executed by the processor, further cause the device to perform functions of:
- receiving a request from the external application for information regarding a portion of the persistent document collection; and
- in response to the request from the external application, retrieving the information from the memory and providing the information to the external application.
3. The data processing system of claim 2, wherein the information that is provided to the external application is used by the external application to allow management of the portion of the persistent document collection.
4. The data processing system of claim 2, wherein the executable instructions, when executed by the processor, further cause the device to perform functions of:
- in response to the request from the external application, enabling downloading of one or more documents in the portion of the persistent document collection by the external application.
5. The data processing system of claim 4, wherein the executable instructions, when executed by the processor, further cause the device to perform functions of:
- enabling modifying of the one or more documents in the portion of the persistent document collection by the external application.
6. The data processing system of claim 5, wherein modifying of the one or more documents includes removing a first document from the portion of the persistent document collection or updating a second document using a revised version of the second document, the revised version of the second document belonging to the persistent document collection.
7. The data processing system of claim 6, wherein the executable instructions, when executed by the processor, further cause the device to perform functions of:
- synchronizing one or more documents represented by the portion of the persistent document collection with the one or more documents downloaded to a computer by the external application.
8. A method for creating and managing persistent document collections, the method comprising:
- managing documents for a plurality of users;
- receiving user input from a client-side web browser associated with one of the plurality of users;
- creating a persistent document collection upon receiving the user input from the client-side web browser, the persistent document collection comprising one or more documents;
- assigning a first attribute to the persistent document collection, the first attribute specifying an external application that can access the persistent document;
- assigning a second attribute to the persistent document collection, the second attribute specifying an amount of disk space to allocate to the persistent document collection; and
- storing the one or more persistent document collections in the memory, in storage space allocated to the one or more persistent document collections;
- wherein the persistent document collection enables one of the plurality of users to access the one or more documents.
9. The method of claim 8, further comprising:
- receiving a request from the external application for information regarding a portion of the persistent document collection; and
- in response to the request from the external application, retrieving the information from the memory and providing the information to the external application.
10. The method of claim 9, wherein the information that is provided to the external application is used by the external application to allow management of the portion of the persistent document collection.
11. The method of claim 9, further comprising:
- in response to the request from the external application, enabling downloading of one or more documents in the portion of the persistent document collection by the external application.
12. The method of claim 11, further comprising:
- enabling modifying of the one or more documents in the portion of the persistent document collection by the external application.
13. The method of claim 12, wherein modifying of the one or more documents includes removing a first document from the portion of the persistent document collection or updating a second document using a revised version of the second document, the revised version of the second document belonging to the persistent document collection.
14. A non-transitory computer readable medium on which are stored instructions that, when executed, cause a programmable device to:
- manage documents for a plurality of users;
- receive user input from a client-side web browser associated with one of the plurality of users;
- create a persistent document collection upon receiving the user input from the client-side web browser, the persistent document collection comprising one or more documents;
- assign a first attribute to the persistent document collection, the first attribute specifying an external application that can access the persistent document;
- assign a second attribute to the persistent document collection, the second attribute specifying an amount of disk space to allocate to the persistent document collection; and
- store the one or more persistent document collections in the memory, in storage space allocated to the one or more persistent document collections;
- wherein the persistent document collection enables one of the plurality of users to access the one or more documents.
15. The non-transitory computer readable medium of claim 14, wherein the instructions further cause the programmable device to:
- receive a request from the external application for information regarding a portion of the persistent document collection; and
- in response to the request from the external application, retrieve the information from the memory and providing the information to the external application.
16. The non-transitory computer readable medium of claim 15, wherein the information that is provided to the external application is used by the external application to allow management of the portion of the persistent document collection.
17. The non-transitory computer readable medium of claim 15, wherein the instructions further cause the programmable device to:
- in response to the request from the external application, enabling downloading of one or more documents in the portion of the persistent document collection by the external application.
18. The non-transitory computer readable medium of claim 17, wherein the instructions further cause the programmable device to:
- enabling modifying of the one or more documents in the portion of the persistent document collection by the external application.
19. The non-transitory computer readable medium of claim 18, wherein modifying of the one or more documents includes removing a first document from the portion of the persistent document collection or updating a second document using a revised version of the second document, the revised version of the second document belonging to the persistent document collection.
20. The non-transitory computer readable medium of claim 15, wherein the instructions further cause the programmable device to:
- synchronizing one or more documents represented by the portion of the persistent document collection with the one or more documents downloaded to a computer by the external application.
Type: Application
Filed: Apr 25, 2019
Publication Date: Aug 15, 2019
Applicant: MICROSOFT TECHNOLOGY LICENSING, LLC (Redmond, WA)
Inventors: Ethan GUR-ESH (Seattle, WA), Nathan FINK (Seattle, WA), Dustin FRIESENHAHN (Bellevue, WA), Nithya RAMKUMAR (Redmond, WA), Maura J. FITZGERALD (Swampscott, MA)
Application Number: 16/395,177