A variety of knowledge can be contained in digital documents stored on document storage services. Examples of document storage services include cloud-based services such as Box, Dropbox, Google Drive, Sharepoint, etc.
An individual or a team of individuals, e.g., an enterprise team working on a project, may access documents scattered among multiple disparate document storage services. For example, an individual or team of individuals preparing a business proposal may access relevant knowledge contained in documents stored on Box, and documents stored on Dropbox, and documents stored on Google Drive, etc.
An individual accessing documents scattered among multiple disparate document storage services must often go through an arduous and time-consuming process of logging onto each document storage service, often multiple times, and presenting the proper credentials to each document storage service. In addition, documents scattered among multiple disparate document storage services may have unknown and disparate naming conventions and directory structures which can complicate efforts to find needed documents.
In general, in one aspect, the invention relates to a knowledge cloud organizer. A knowledge cloud organizer according to the invention can include: a document selector that enables user-selection of a set of documents scattered among a set of disparate document storage services for inclusion in a document integration, and that determines a set of document integration parameters for each document selected for the document integration; and a knowledge cloud access portal that in response to the document integration parameters generates a visual depiction of one or more of the documents included in the document integration such that the visual depiction enables user access to one or more of the documents included in the visual depiction.
In general, in another aspect, the invention relates to a method for organizing a knowledge cloud. The method can include: obtaining a user-selection of a set of documents scattered among a set of disparate document storage services for inclusion in a document integration; determining a set of document integration parameters for each document selected for the document integration; and generating a visual depiction of one or more of the documents included in the document integration in response to the document integration parameters such that the visual depiction enables user access to one or more of the documents included in the visual depiction.
Other aspects of the invention will be apparent from the following description and the appended claims.
Embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements.
Reference will now be made in detail to the various embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Like elements in the various figures are denoted by like reference numerals for consistency. While described in conjunction with these embodiments, it will be understood that they are not intended to limit the disclosure to these embodiments. On the contrary, the disclosure is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the disclosure as defined by the appended claims. Furthermore, in the following detailed description of the present disclosure, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be understood that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, have not been described in detail so as not to unnecessarily obscure aspects of the present disclosure.
The documents 1-n can include any type of digital documents in any format, e.g., industry standard formats. Examples of the documents 1-n include text files, e.g., word files, image files, e.g., jpeg, tiff, etc., PDF files, video/movie files, data files, planning/organization files, financial files, etc.
The document storage services 1-m can include any selection and arrangement of document storage services including so-called cloud-based services e.g., Dropbox, Box, Sharepoint, Google Drive, etc., accessible via a network 140, using e.g., Internet protocols.
The document integration 104 can be based on a team, a project, an organization, etc. In one or more embodiments, the document selector 102 generates a user interface 114 that enables a user to specify a team name, team identifier, etc., for the document integration 104, and identify one or more individuals for inclusion in the team, and enable browsing of the document storage services 1-m and individual selection of the documents 1-n for inclusion in the document integration 104 for a specified team.
The document selector 102 determines a respective set of document integration parameters 1-n for each document 1-n selected for the document integration 104. For example, the document integration parameters 1 correspond to the document 1, the document integration parameters 2 correspond to the document 2, etc.
The document integration parameters 1-n can include document names and types, document creation parameters, document ownership parameters, document modification parameters, document size parameters, document sharing information, document version parameters, keywords, etc. The document integration parameters 1-n include identifications of the document storage services 1-m where the respective documents 1-n are stored along corresponding credentials for accessing the document storage services 1-m.
For example, when a user via the user interface 114 selects the document 1 for inclusion in the document integration 104, the document selector 102 can obtain document name and type, creation, modification, etc., parameters for the document 1 from the document storage service 1 and include such parameters in the document integration parameters 1 along with a set of local parameters, e.g., team identifier, and credentials for accessing the document 1 on the document storage service 1. Likewise, when a user selects the document 2 for inclusion in the document integration 104, the document selector 102 can obtain document name and type, etc. parameters from the document storage service 2 and include such parameters in the document integration parameters 2 along with local parameters and credentials for accessing the document 2 on the document storage service 2.
The document integration parameters 1-n can include any selection and arrangement of any kinds of documents stored on any selection and arrangement of the disparate document storage services 1-m. The document integration parameters 1-n can be stored in a database of the knowledge cloud organizer 100.
The knowledge cloud organizer 100 includes a knowledge cloud access portal 106 that generates a visual depiction 112 of one or more of the documents 1-n included in the document integration 104 in response to the document integration parameters 1-n. The visual depiction 112 can depict the documents 1-n using document names, icons, versions, activities, types, sizes, etc.
The knowledge cloud organizer 100 provides smart search and sort functions that enable a user to search for documents in the document integration 104 by matching a set of search terms to any combination of the document integration parameters 1-n so that only matching documents appear in the visual depiction 112. A user can sort the matching documents in the visual depiction 112 by any of the document integration parameters 1-n. For example, a user can search for documents in the document integration 104 by entering search terms that match to document names, user names, document activities, dates, document types, etc., and sort the results by document name, user name, dates, document type, document size, etc. A smart search can include user-selectable operators for combining search terms to yield exact matches, near matches, etc.
The visual depiction 112 enables user access to one or more of the documents 1-n included in the document integration 104. In one or more embodiments, the visual depiction 112 enables user-access by identifying on which of the document storage services 1-m each document included in the document integration 104 is stored. For example, the visual depiction 112 can identify the document storage services 1-m using a unique name, acronym, abbreviation, etc., associated with each document storage service 1-m. The visual depiction 112 can identify the document storage services 1-m using a unique icon associated with each document storage service 1-m.
In one or more embodiments, the visual depiction 112 enables user-access by including a document storage service link, e.g., a URL, for each document 1-n included in the document integration 104. For example, the visual depiction 112 can include a link to the document storage service 1 for the document 1 including a respective set of security credentials for accessing the document 1 from the document storage service 1. Likewise, the visual depiction 112 can include a link to the document storage service 2 for the document 2 including a respective set of security credentials for accessing the document 2 from the document storage service 2.
In one or more embodiments, the visual depiction 112 includes a timeline of a series activities involving the documents 1-n included in the document integration 104. Examples of activities that can be depicted in a timeline include document creation, document modification, document accesses, etc. A timeline in the visual depiction 112 can be zoomable under user-control.
For example, the document integration parameters 1 correspond to an xls document named Knowledge graph created on Aug. 8, 2018 by Jason, modified on Aug. 12, 2018 by Ted, and stored on G Drive (Google Drive) with Credentials A. Likewise, the document integration parameters 2 correspond to a keynote document named Knowledge graph Presentation created on Aug. 10, 2018 by Ted, modified on Aug. 10, 2018 by Myla, and stored on Box with Credentials B.
A set of credentials in the document integration parameters 1-4 can include, e.g., a login user name and password for the respective document storage service 1-m. A set of credentials in the document integration parameters 1-4 can include a security token for accessing the respective document storage service 1-m. A set of credentials in the document integration parameters 1-4 can include a set of application programming interface (API) parameters, procedures, directory structure parameters, etc., for accessing the respective document storage service 1-m.
The knowledge cloud access portal 106 generates a visual depiction 512 of the matching documents found by the smart search engine 508. The visual depiction 512 can depict the matching documents using document names, icons, versions, activities, types, sizes, etc. The visual depiction 512 can enable user access to the matching documents as previously described.
In one or more embodiments, links to the specified matching documents are embedded in the fields 620. For example, when a user selects, e.g., clicks, on “Knowledge graph.xls” the knowledge cloud organizer 100 generates an access to Google Drive with the Credentials A listed in the document integration parameters 1 (
In some embodiments, the disabled search term “inventory” can be merely dimmed so that it can easily be reenabled by a user to reinclude it in a subsequent search.
In one or more embodiments, the knowledge cloud organizer 100 automatically updates the matching documents depicted in the visual depiction 512 in response to actuations made via the user interface elements 800-802.
At step 910, a user-selection is obtained of a set of documents scattered among a set of disparate document storage services for inclusion in a document integration. Step 910 can include selecting a team identifier, organization identifier, etc., for a document integration. Step 910 can include selecting a set of individuals to be included a specified team. Step 910 can include browsing one or more of a set of disparate document storage services and selecting among the documents on the disparate document storage services for inclusion in a document integration.
At step 920, a set of document integration parameters are determined for each document included in a document integration. Step 920 can include obtaining a set of parameters for a document included in a document integration from a document storage service where it is stored. Step 920 can include obtaining a set of local parameters for a document included in a document integration.
At step 930, a visual depiction is generated of one or more of the documents included in a document integration in response to the document integration parameters. A visual depiction at step 930 enables user access to one or more of the documents included in the visual depiction. A visual depiction at step 930 can identify the document storage services where documents are stored. A visual depiction at step 930 can include links with credentials to the document storage services where the documents are stored. A visual depiction at step 930 can depict a timeline of activities pertaining to the documents, e.g., a zoomable timeline.
The computer processor(s) 1002 may be an integrated circuit for processing instructions. For example, the computer processor(s) may be one or more cores or micro-cores of a processor. The computing system 1000 may also include one or more input device(s), e.g., a touchscreen, keyboard 1010, mouse 1012, microphone, touchpad, electronic pen, or any other type of input device. Further, the computing system 1000 may include one or more monitor device(s) 1008, such as a screen (e.g., a liquid crystal display (LCD), a plasma display, touchscreen, cathode ray tube (CRT) monitor, projector, or other display device), external storage, input for an electric instrument, or any other output device. The computing system 1000 may be connected to, e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, mobile network, or any other type of network) via a network adapter 1018.
While the foregoing disclosure sets forth various embodiments using specific diagrams, flowcharts, and examples, each diagram component, flowchart step, operation, and/or component described and/or illustrated herein may be implemented, individually and/or collectively, using a range of processes and components.
The process parameters and sequence of steps described and/or illustrated herein are given by way of example only. For example, while the steps illustrated and/or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various example methods described and/or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments may be devised which do not depart from the scope of the invention as disclosed herein.