Managing projects in a content management system

Description

BACKGROUND

There are many software applications that assist users in managing projects. Often these software applications are complicated and difficult to use. Many times several different software applications are required to manage the various tasks, documents types, schedules, communications, and other project related activities and files. Using these existing systems to manage a project can be difficult to learn, burdensome to use, and time consuming for the user.

SUMMARY

Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims, or can be learned by the practice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readable storage media for managing projects in a content management system. For example, the content management system can create a project folder (e.g., shared folder) for managing data associated with a project. The project folder can be shared with content management system users (e.g., project members) who are contributors to the project. The content management system can store project data (e.g., content items, communications, comments, tasks, etc.) related to the project in the project folder. When the project folder is selected by a user, the content management system can generate a project folder view that presents the project data associated with the project folder and/or project in a convenient and easy to access graphical user interface. The content management system can aggregate project data from various content items associated with the project and present the project data in a single graphical user interface.

Disclosed are systems, methods, and non-transitory computer-readable storage media for managing tasks in a content management system. For example, the content management system can collect, aggregate, and/or store task data assigned to a user from across projects and/or content items. The user can select to view tasks for a particular project and/or from across all projects. The content management system can generate a single graphical user interface for presenting the task data associated with the user. The content management system can generate a graphical user interface the allows the user to move tasks from one task status graphical element (e.g., task status container) to another task status graphical element to change the status of a task associated with the user. Thus, the user can quickly and easily view the tasks assigned to the user and update the status of tasks in an easy to use graphical user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the disclosure will become apparent by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only example embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 shows an example configuration of devices and a network in accordance with some embodiments;

FIG. 2 is a block diagram of an example system for managing project data in a content management system;

FIG. 3 illustrates an example graphical user interface for presenting project folders;

FIG. 4 illustrates an example graphical user interface for presenting a project folder view;

FIG. 5 illustrates an example graphical user interface for adding a new content item to a project;

FIG. 6 illustrates an example graphical user interface for presenting a view of a content item added to the selected project folder;

FIG. 7 illustrates an example text that includes special expressions;

FIG. 8 illustrates an example graphical user interface presenting a content item that was added to the selected project folder;

FIG. 9 illustrates an example graphical user interface for presenting a description of the selected project;

FIG. 10 illustrates an example graphical user interface for presenting tasks associated with the selected project;

FIG. 11 illustrates an example graphical user interface for presenting tagged project data;

FIG. 12 illustrates an example graphical user interface for presenting comments associated with a project;

FIG. 13 illustrates an example graphical user interface presenting recently accessed content items;

FIG. 14 illustrates an example graphical user interface for presenting tasks associated with a particular user of a content management system;

FIG. 15 illustrates an example graphical user interface for creating a new task;

FIG. 16 illustrates an example graphical user interface presenting a newly created task;

FIG. 17 illustrates an example graphical user interface presenting a column view of tasks associated with the user;

FIG. 18 illustrates an example graphical interface for changing the state of a task;

FIG. 19 is an example process for managing projects in a content management system;

FIG. 20 is an example process for managing tasks in content management system;

FIG. 21A shows an example possible system embodiment for implementing various embodiments of the present technology; and

FIG. 21B shows an example possible system embodiment for implementing various embodiments of the present technology.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure.

The disclosed technology addresses the need in the art for an easy, simple, and convenient way for users to manage project data. By organizing project data into a shared project folder managed by the content management system described herein, users are able to access all project data for a specific project at a single location. Moreover, the content management system can generate and present project data by generating a graphical user interface that aggregates project data from across content items stored in the shared folder and/or associated with the project so that the user does not have to run multiple software applications or interact with multiple user interfaces to view the project data. Additionally, since the content management system synchronizes the project folder with the computing devices associated with members/users of the project, project members can access project data through the content management system's servers or on the local file system of the users' devices (e.g., when the user's device is not connected to the network). The technology disclosed herein improves the efficiency of both user device and content management system server devices by reducing the number of software applications a user previously had to install on the user's device to perform project management tasks. Moreover, by storing all project data in a centralized location (e.g., instead of at different locations), the user device and/or the content management system servers are required to do less processing to find, aggregate, process, and present data (e.g., content items, comments, tasks, etc.) associated with a project.

With respect to implementing various embodiments of the disclosed technology, an example system configuration 100 is shown in FIG. 1, wherein electronic devices communicate via a network for purposes of exchanging content and other data. The system can be configured for use on a wide area network such as that illustrated in FIG. 1. However, the present principles are applicable to a wide variety of network configurations that facilitate the intercommunication of electronic devices. For example, each of the components of system 100 in FIG. 1 can be implemented in a localized or distributed fashion in a network.

In system 100, a user can interact with content management system 106 (e.g., an online synchronized content management system) through client devices 102₁, 102₂, . . . , 102_n(collectively “102”) connected to network 104 by direct and/or indirect communication. Content management system 106 can include a single computing device (e.g., a server) or multiple computing devices (e.g., multiple servers) that are configured to perform the functions and/or operations necessary to provide the services described herein. Content management system 106 can support connections from a variety of different client devices, such as: desktop computers; mobile computers; mobile communications devices, e.g. mobile phones, smart phones, tablets; smart televisions; set-top boxes; and/or any other network enabled computing devices. Client devices 102 can be of varying type, capabilities, operating systems, etc. Furthermore, content management system 106 can concurrently accept connections from and interact with multiple client devices 102.

A user can interact with content management system 106 via a client-side application installed on client device 102_i. In some embodiments, the client-side application can include a content management system specific component. For example, the component can be a stand-alone application, one or more application plug-ins, and/or a browser extension. However, the user can also interact with content management system 106 via a third-party application, such as a web browser, that resides on client device 102_iand is configured to communicate with content management system 106. In either case, the client-side application can present a user interface (UI) for the user to interact with content management system 106. For example, the user can interact with the content management system 106 via a client-side application integrated with the file system or via a webpage displayed using a web browser application.

Content management system 106 can enable a user to store content items, as well as perform a variety of content management tasks, such as retrieve, modify, browse, and/or share the content items. Furthermore, content management system 106 can enable a user to access the content from multiple client devices 102. For example, client device 102_ican upload content to content management system 106 via network 104. Later, the same client device 102_ior some other client device 102_jcan retrieve the content from content management system 106.

To facilitate the various content management services, a user can create an account with content management system 106. User account database 150 can maintain the account information. User account database 150 can store profile information for registered users. In some cases, the only personal information in the user profile can be a username and/or email address. However, content management system 106 can also be configured to accept additional user information such as birthday, address, billing information, etc.

User account database 150 can include account management information, such as account type (e.g. free or paid), usage information, (e.g. file edit history), maximum storage space authorized, storage space used, content storage locations, security settings, personal configuration settings, content sharing data, etc. Account management module 124 can be configured to update and/or obtain user account details in user account database 150. The account management module 124 can be configured to interact with any number of other modules in content management system 106.

An account can be used to store content items, such as digital data, documents, text files, audio files, video files, etc., from one or more client devices 102 authorized on the account. The content items can also include collections for grouping content items together with different behaviors, such as folders, playlists, albums, etc. For example, an account can include a public folder that is accessible to any user. The public folder can be assigned a web-accessible address. A link to the web-accessible address can be used to access the contents of the public folder. In another example, an account can include: a photos collection that is intended for photos and that provides specific attributes and actions tailored for photos; an audio collection that provides the ability to play back audio files and perform other audio related actions; or other special purpose collection. An account can also include shared collections or group collections that are linked with and available to multiple user accounts. The permissions for multiple users may be different for a shared collection.

The content items can be stored in content storage 160. Content storage 160 can be a storage device, multiple storage devices, or a server. Alternatively, content storage 160 can be a cloud storage provider or network storage accessible via one or more communications networks. Content management system 106 can hide the complexity and details from client devices 102 so that client devices 102 do not need to know exactly where or how the content items are being stored by content management system 106. In some embodiments, content management system 106 can store the content items in the same collection hierarchy as they appear on client device 102_i. However, content management system 106 can store the content items in its own order, arrangement, or hierarchy. Content management system 106 can store the content items in a network accessible storage (NAS) device, in a redundant array of independent disks (RAID), etc. Content storage 160 can store content items using one or more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4, HFS/HFS+, BTRFS, and so forth.

Content storage 160 can also store metadata describing content items, content item types, and the relationship of content items to various accounts, collections, or groups. The metadata for a content item can be stored as part of the content item or can be stored separately. In one variation, each content item stored in content storage 160 can be assigned a system-wide unique identifier.

Content storage 160 can decrease the amount of storage space required by identifying duplicate content items or duplicate segments of content items. Instead of storing multiple copies, content storage 160 can store a single copy and then use a pointer or other mechanism to link the duplicates to the single copy. Similarly, content storage 160 can store content items more efficiently, as well as provide the ability to undo operations, by using a content item version control that tracks changes to content items, different versions of content items (including diverging version trees), and a change history. The change history can include a set of changes that, when applied to the original content item version, produce the changed content item version.

Content management system 106 can be configured to support automatic synchronization of content items from one or more client devices 102. The synchronization can be platform agnostic. That is, the content items can be synchronized across multiple client devices 102 of varying type, capabilities, operating systems, etc. For example, client device 102_ican include client software, which synchronizes, via a synchronization module 132 at content management system 106, content in client device 102_i's file system with the content in an associated user account. In some cases, the client software can synchronize any changes to content in a designated collection and its sub-collections, such as new, deleted, modified, copied, or moved content items or collections. The client software can be a separate software application, can integrate with an existing content management application in the operating system, or some combination thereof. In one example of client software that integrates with an existing content management application, a user can manipulate content items directly in a local collection, while a background process monitors the local collection for changes and synchronizes those changes to content management system 106. Conversely, the background process can identify content items that have been updated at content management system 106 and synchronize those changes to the local collection. The client software can provide notifications of synchronization operations, and can provide indications of content statuses directly within the content management application. Sometimes client device 102_imay not have a network connection available. In this scenario, the client software can monitor the linked collection for content item changes and queue those changes for later synchronization to content management system 106 when a network connection is available. Similarly, a user can manually start, stop, pause, or resume synchronization with content management system 106.

A user can view or manipulate content via a web interface generated and served by user interface module 122. For example, the user can navigate in a web browser to a web address provided by content management system 106. Changes or updates to content in the content storage 160 made through the web interface, such as uploading a new version of a content item, can be propagated back to other client devices 102 associated with the user's account. For example, multiple client devices 102, each with their own client software, can be associated with a single account and content items in the account can be synchronized between each of the multiple client devices 102.

Content management system 106 can include a communications interface 120 for interfacing with various client devices 102, and can interact with other content and/or service providers 109₁, 109₂, . . . , 109_n(collectively “109”) via an Application Program Interface (API). Certain software applications can access content storage 160 via an API on behalf of a user. For example, a software package, such as an app running on a smartphone or tablet computing device, can programmatically make calls directly to content management system 106, when a user provides credentials, to read, write, create, delete, share, or otherwise manipulate content. Similarly, the API can allow users to access all or part of content storage 160 through a web site.

Content management system 106 can also include authenticator module 126, which can verify user credentials, security tokens, API calls, specific client devices, and so forth, to ensure only authorized clients and users can access content items. Further, content management system 106 can include analytics module 134 module that can track and report on aggregate file operations, user actions, network usage, total storage space used, as well as other technology, usage, or business metrics. A privacy and/or security policy can prevent unauthorized access to user data stored with content management system 106.

Content management system 106 can include sharing module 130 for managing sharing content publicly or privately. Sharing content publicly can include making the content item accessible from any computing device in network communication with content management system 106. Sharing content privately can include linking a content item in content storage 160 with two or more user accounts so that each user account has access to the content item. The sharing can be performed in a platform agnostic manner. That is, the content can be shared across multiple client devices 102 of varying type, capabilities, operating systems, etc. The content can also be shared across varying types of user accounts.

In some embodiments, content management system 106 can be configured to maintain a content directory identifying the location of each content item in content storage 160. The content directory can include a unique content entry for each content item stored in the content storage.

A content entry can include a content path that can be used to identify the location of the content item in a content management system. For example, the content path can include the name of the content item and a folder hierarchy associated with the content item. For example, the content path can include a folder or path of folders in which the content item is placed as well as the name of the content item. Content management system 106 can use the content path to present the content items in the appropriate folder hierarchy.

A content entry can also include a content pointer that identifies the location of the content item in content storage 160. For example, the content pointer can include the exact storage address of the content item in memory. In some embodiments, the content pointer can point to multiple locations, each of which contains a portion of the content item.

In addition to a content path and content pointer, a content entry can also include a user account identifier that identifies the user account that has access to the content item. In some embodiments, multiple user account identifiers can be associated with a single content entry indicating that the content item has shared access by the multiple user accounts.

To share a content item privately, sharing module 130 can be configured to add a user account identifier to the content entry associated with the content item, thus granting the added user account access to the content item. Sharing module 130 can also be configured to remove user account identifiers from a content entry to restrict a user account's access to the content item.

To share content publicly, sharing module 130 can be configured to generate a custom network address, such as a uniform resource locator (URL), which allows any web browser to access the content in content management system 106 without any authentication. To accomplish this, sharing module 130 can be configured to include content identification data in the generated URL, which can later be used to properly identify and return the requested content item. For example, sharing module 130 can be configured to include the user account identifier and the content path in the generated URL. Upon selection of the URL, the content identification data included in the URL can be transmitted to content management system 106 which can use the received content identification data to identify the appropriate content entry and return the content item associated with the content entry.

In addition to generating the URL, sharing module 130 can also be configured to record that a URL to the content item has been created. In some embodiments, the content entry associated with a content item can include a URL flag indicating whether a URL to the content item has been created. For example, the URL flag can be a Boolean value initially set to 0 or false to indicate that a URL to the content item has not been created. Sharing module 130 can be configured to change the value of the flag to 1 or true after generating a URL to the content item.

In some embodiments, sharing module 130 can also be configured to deactivate a generated URL. For example, each content entry can also include a URL active flag indicating whether the content should be returned in response to a request from the generated URL. For example, sharing module 130 can be configured to only return a content item requested by a generated link if the URL active flag is set to 1 or true. Thus, access to a content item for which a URL has been generated can be easily restricted by changing the value of the URL active flag. This allows a user to restrict access to the shared content item without having to move the content item or delete the generated URL. Likewise, sharing module 130 can reactivate the URL by again changing the value of the URL active flag to 1 or true. A user can thus easily restore access to the content item without the need to generate a new URL.

While content management system 106 is presented with specific components, it should be understood by one skilled in the art, that the architectural configuration of system 106 is simply one possible configuration and that other configurations with more or fewer components are possible.

FIG. 2 is a block diagram of an example system 200 for managing project data in a content management system. For example, system 200 can correspond to system 100 of FIG. 1, described above. As described above, system 200 can include content management system 106.

In some implementations, content management system 106 can include project module 202. For example, project module 202 can be a software module installed and/or running on content management system 106. Project module 202 can manage project folders and project data associated with projects. Project module 202 can generate a project folder view (e.g., graphical user interface) for presenting project data to a user (e.g., project member). Project module 202 can, for example, store content items and/or project data associated with a project in project folder 204 in content storage 160.

In some implementations, content management system 106 can include comments database 206. For example, comments database 206 can be stored in project folder 204 or stored separately from projects folder 204. Comments database 206 can store comments associated with a particular project or many different projects. For example, project module 202 can read content items, including content item metadata, stored in project folder 204 and extract comments (e.g., messages from one user to another user) from the content items. Project module can determine various attributes (e.g., project identifier, author identifier, recipient identifier, tags, source content item identifier, etc.) for each comment. Project module 202 can then store the comments in association with the determined attributes in comments database 206 so that project module 202 can later locate comments based on the comment attributes.

In some implementations, project module 202 can analyze a comment to determine attributes for the comment. For example, project module 202 can determine a source content item attribute based on the content item identifier corresponding to the content item in which the comment was found. Similarly, project module 202 can determine a project identifier attribute for a comment based on the project folder where the corresponding content item is stored. For example, when a user adds a comment to a content item stored in project folder 204 corresponding to “Project Widget”, then project module 202 can determine the project attribute for the comment to be “Project Widget”.

Project module 202 can determine an author identifier for the comment based on the user identifier associated with the user who wrote the comment. For example, each user of content management system 106 can be assigned a user identifier. When a user edits a content item managed by content management system 106, content management system 106 can store metadata for the content item that identifies the user who made the changes to the content item and what changes (e.g., edits, comments, etc.) were made to the content item. Thus, project module 202 can determine the author identifier attribute based on the user identifier stored in the content item metadata.

In some implementations, project module can determine comment attributes based on special expressions included in a comment. For example, project module 202 can analyze the comments to determine whether a comment includes expressions (e.g., prefixes, tags, symbols, etc.) that indicate attributes for the comment. For example, content management system 106 can define a user identifier prefix (e.g., the “at” symbol “@”) that when added to a comment indicates a recipient identifier attribute will follow. For example, a user can input a comment that includes “@kevin” to address the comment to a project member named Kevin. Thus, when project module 202 analyzes a comment and finds the string “@kevin”, project module 202 can determine that the recipient attribute for the comment includes the user “Kevin.”

Similarly, content management system 106 can define a content item prefix (e.g., the plus “+” character) that when added to a comment indicates a content item identifier attribute will follow. For example, a user can input a comment that includes “+overview.pdf” to create a link to a content item in the comment. When project module 202 analyzes a comment and finds the string “+overview.pdf”, project module 202 can determine that a linked content item attribute for the comment includes the content item “overview.pdf” Project module 202 can, for example, convert a content item identifier prefixed with the content item prefix into a link so that a user can access the content item through the link embedded in the comment.

In some implementations, content management system 106 can define a tag prefix (e.g., the hash “#” character) that when added to a comment indicates a tag attribute will follow. For example, a user can input a comment that includes “#engineering” to tag the comment with a subject, classification, or some other information. When project module 202 analyzes a comment and finds the string “#engineering”, project module 202 can determine that a tag attribute for the comment includes the tag “engineering.” Project module 202 can, for example, use tags to organize comments, tasks, or other project data, as described below.

In some implementations, content management system 106 can define a task prefix (e.g., opening and closing square brackets “[ ]”) In that when added to the beginning of a comment indicates that the comment should be converted into a task. For example, a user can input a comment that includes “[=]” If at the beginning of the comment to indicate that the comment should be converted into a task. When project module 202 analyzes a comment and finds the string “[ ]” If followed by a comment and/or comment attributes, project module 202 can convert the comment into a task. Project module 202 can treat the comment attributes as task attributes and store the task and task attributes in task database 208 in addition to or instead of storing the comment that generated the task in comments database 206. For example, task database 208 can be stored in projects folder 204 or stored separately from project folder 204.

In some implementations, project module 202 can generate various project folder views based on the comments, tasks, and/or attributes stored in comments database 206 and/or tasks database 208. For example, project module 202 can generate the graphical user interfaces described below by filtering, sorting, aggregating, and/or otherwise organizing the comments and/or tasks in comments database 206 and/or tasks database 208 based on the comment attributes and/or task attributes, as described in detail below.

In some implementations, system 200 can include client device 240. For example, client device 240 can correspond to client device 102_idescribed above. Client device 240 can, for example, be a laptop computer, tablet computer, smart phone, wearable device, and/or any other computing device. Although FIG. 2 illustrates a system 200 having only one client device 240 (e.g., client device 102_i), system 200 can include many client devices 240 (e.g., client devices 102_i-102_n) that interact with content management system 106 and/or project module 202 to manage projects. For example, each member of a project may have a different client device 240 that communicates with content management system 106 to access project data managed by content management system 106 and/or project module 202.

In some implementations, client device 240 can include content management system (CMS) client 242. For example, CMS client 242 can be a native application of client device 240. For example, a native software application can be an application that is built specifically for the hardware and/or software configuration of client device 240. Thus, the graphical user interfaces (and other functionality) of CMS client 242 described below can be implemented using instructions, application programming interfaces (APIs), and other technologies native to client device 240. To generate the various graphical user interfaces below and/or implement various features described herein, CMS client 242 can request project data (e.g., project content items, project member identifiers, comments, tasks, etc.) from project module 202 over a network connection (e.g., through network 104). Project module 202 can obtain project data from project folder 204, comments database 206, and/or tasks database 208 and send the project data to CMS client 242. CMS client 242 can then present the project data on various graphical user interfaces generated by CMS client 242.

Alternatively, CMS client 242 can be a web client executed by a web browser running on client device 240. Thus, the graphical user interfaces (and other functionality) of CMS client 240 can be implemented using instructions, APIs, and other technologies that are not native to client device 240. For example, CMS client 240 can be built as a web application using non-native web code or instructions. CMS client 240 can be served to a web browser on client device 240 and the web browser can execute CMS client 240 to present the graphical user interfaces (and other functionality) to the user, as described in detail below. To generate the various graphical user interfaces below and/or implement various features described herein, CMS client 242 (e.g., the web browser) can request various project folder views (e.g., graphical user interfaces, web pages, etc.) from project module 202. Project module 202 can generate the project folder views (e.g., the graphical user interfaces described below) for presenting project data (e.g., project content items, project member identifiers, comments, tasks, etc.) and send the project views to CMS client 242 over a network connection (e.g., through network 104). For example, project module 202 can obtain project data from project folder 204, comments database 206, and/or tasks database 208, generate the project folder views based on the project data, and send the project folder views to CMS client 242. CMS client 242 can then present the project folder views on a display of client device 240.

In some implementations, client device 240 can include CMS daemon 244. For example, CMS daemon 244 can be a client of content management system 106 that maintains synchronization of data between content management system 106 and client device 240. For example, client device 240 can include managed content 250. Managed content 250 can be a portion of the file system on client device 240 managed by content management system 106 and/or CMS daemon 244. CMS daemon 244 and/or content management system 106 can synchronize content items stored in managed content 250 with content items stored in content storage 160. In particular, when the user of client device 240 is a member of a project corresponding to project folder 204, CMS daemon 244 and/or content management system 106 can synchronize project folder 204 and project folder 252 so that project folder 204 and project folder 252 include the same project content items and/or project data (e.g., comments, tasks, etc.). Thus, a user of client device 240 can access project data stored in project folder 204/252 through CMS client 242 or through the local file system (e.g., project folder 252) on client device 240.

FIG. 3 illustrates an example graphical user interface 300 for presenting project folders. For example, CMS client 242 can present graphical user interface (GUI) 300 on a display of client device 240. In some implementations, GUI 300 can include side panel 301 presenting various graphical elements for viewing content management system data associated with a content management system user. While side panel 301 is not represented in each figure described below, side panel 301 can be presented along with each graphical user interface described herein. In the example illustrated by FIG. 3, the user has selected graphical element 302 to view content associated with a company that the user works for and/or for which a business account has been established in content management system 106. Upon receiving the selection of graphical element 302, CMS client 242 can present company folder view 303. In other examples, the user can select other graphical elements to view non-business (e.g., personal) folders and/or non-business project folders.

In some implementations, folder view 303 can include project folders. For example, folder view 303 can present project folder 304 and/or project folder 308. A user can cause content management system 106 to create a new project folder (e.g., project folder 304) by selecting graphical element 314. Project folders 304 and/or 308 can be shared folders accessible by other users of content management system 106. For example, most projects include a team of people that perform various tasks to accomplish the goals of the project. Thus, project folders 304 and/or 308 can be shared with other users (e.g., project members) of content management system 106. The members of each project can be represented in areas 306 and/or 310 by graphical elements (e.g., images, initials, avatars, etc.). These project members can access project folders 304 and/or 308 respectively to view project content items and other project data for the projects corresponding to project folders 304 and/or 308. A user can select a project folder to view details about the corresponding project. For example, the user can select project folder 304 (e.g., select a project) to cause CMS client 242 to present GUI 400 of FIG. 4.

FIG. 4 illustrates an example graphical user interface 400 for presenting a project folder view. For example, CMS client 242 can present GUI 400 on a display of client device 240 in response to the user selecting project folder 304. GUI 400 can present project folder view 402 that presents various content items, comments, tasks, tags and/or other project data. For example, a user can select graphical element 404 to cause CMS client 242 to present project data view 405 that includes content items and/or folders associated with the selected project (e.g., “Project Widget”) in project folder view 402. For example, CMS client 242 can obtain the content item information and/or project information presented in project data view 405 from project folder 204 through project module 202 or locally from project folder 252, as described above.

In some implementations, project data view 405 can include project configuration panel 406. For example, project configuration panel 406 can include graphical representations 408 of project members. Graphical representations 408 can include photographs of members' faces, initials, avatars, and/or some other visual representation that users can recognize to identify members of the selected project. In some implementations, project configuration panel 406 can include graphical element 410 for adding new members to the project. For example, a user (e.g., project manager) can select graphical element 410 to cause CMS client 242 to present graphical user interfaces for selecting and/or adding content management system users to the selected project.

In some implementations, project data view 405 can include representations of folders within project folder 304. For example, project data view 405 can include graphical elements 414, 416 and/or 418 representing various sub-folders of project folder 304. A user can select a sub-folder (e.g., graphical element 414) to view content items stored in the selected sub-folder.

In some implementations, project data view 405 can include graphical element 420 for adding new content items to the project (e.g., project folder). In the description herein, the terms “project” and “project folder” can be used interchangeably since the project folder is a representation of a corresponding project and is used to contain, manage, and/or organize project data. For example, a user can select graphical element 420 to cause CMS client 242 to present GUI 500 of FIG. 5 for adding a new content item to the project.

FIG. 5 illustrates an example graphical user interface 500 for adding a new content item to a project. For example, in response to receiving a user selection of graphical element 420, CMS client 242 can present graphical element 502 (e.g., a popup, a menu, etc.) on a display of client device 240.

In some implementations, graphical element 502 can present options for adding new content items to the selected project. For example, graphical element 502 can include graphical element 504 for uploading a file to the selected project. A user can select graphical element 504 to cause CMS client 242 to present a file browser that allows the user to select a content item to upload to the selected project folder managed by content management system 106. Graphical element 502 can include graphical element 506 for creating a new folder in the selected project. A user can select graphical element 506 to cause CMS client 242 to present a new folder dialog box that allows the user to create and name a new folder within the selected project folder managed by content management system 106. Graphical element 502 can include graphical elements 508 and/or 510 for creating a new content item of a particular type in the selected project. A user can select graphical element 508 or 510 to cause CMS client 242 to present a new content item dialog box that allows the user to create and name a new content item of a specific type within the selected project folder managed by content management system 106. Graphical element 502 can include graphical element 512 for adding a link to a content item in the selected project. A user can select graphical element 512 to cause CMS client 242 to present a dialog box that allows the user to specify a link to a content item to add to the selected project folder managed by content management system 106. After the user has added a new content item, folder, or link to the selected project folder, CMS client 242 can present the new content item, folder, or linked content item, as illustrated by FIG. 6.

FIG. 6 illustrates an example graphical user interface 600 for presenting a view of a content item added to the selected project folder. For example, GUI 600 can be presented by CMS client 242 on a display of client device 240. GUI 600 can include graphical element 602 for returning to a project folder view. For example, the user can select graphical element 602 to cause CMS client 242 to present GUI 400, GUI 800, etc., on a display of client device 240.

In some implementations, GUI 600 can include content area 604. For example, content area 604 can present the content of a selected, newly added, or newly created content item in project folder 304. Content area 604 can present a static preview (e.g., image) of content. Content area 604 can provide an editor interface for editing or modifying the content of the corresponding content item.

In some implementations, GUI 600 can include comments area 608 where a user can add or view comments on the content item. For example, the user can select area 608 to invoke a text input area. The user can provide textual input to create a comment and the comment can be presented in comments area 608. For example, the user can create or view comment entry 610. Comment entry 610 can include a graphical representation 612 of the user who created comment entry 610. Comment entry 610 can include textual comment data 614. In some implementations, the user can provide text input that includes special expressions or characters that can be interpreted by CMS client 242 and/or project module 202. As described above, special characters can be input by the user to add a user identifier or a content item identifier to the comment. Special characters can be input by the user to create a task based on a comment, as described with reference to FIG. 7 below.

FIG. 7 illustrates an example text 700 that includes special expressions. For example, as the user provides text input to generate comment 700, the user can type in special characters and/or special expressions that CMS client 242 and/or project module 202 can interpret to have special meaning. FIG. 7 illustrates how CMS client 242 and/or project module 202 react to detecting special characters and/or special expressions in comments, content, tasks, or any other textual data managed by content management system 106.

As illustrated FIG. 7, the user has provided text input 710 and included task prefix 712 (e.g., “H”) at the beginning of text input 710. CMS client 242 and/or project module 202 can interpret task prefix 712 as an indication that the user wishes text input 710 to be automatically converted by CMS client 242 and/or project module 202 into a task for the corresponding project.

Additionally, text input 710 includes user identifier prefix 714 (e.g., “@”) followed by the first few characters of a user identifier. CMS client 242 and/or project module 202 can interpret the identifier prefix 714 as an indication that the user wishes to insert a user identifier into text input 710. When CMS client 242 and/or project module 202 detects user identifier prefix 714, CMS client 242 can present suggestion 716 including suggestions for content management system user identifiers that match the characters that follow user identifier prefix 714. In the example of FIG. 7, user identifier prefix 714 is followed by the characters “Ke” and CMS client 242 has found a user identifier “Kevin Holm” that matches the characters “Ke.” CMS client 242 can present the user identifier “Kevin Holm” in suggestion 716 and the user can select suggestion 716 to have the suggested user identifier added to text input 710. While FIG. 7 illustrates only one suggested user identifier, CMS client 242 can present multiple user identifiers when multiple user identifiers match the sequence of characters following user identifier prefix 714.

In some implementations, the user can continue providing text input to text input 710 to generate text input 720. As illustrated by FIG. 7, after the user selects user identifier suggestion 716, user identifier prefix 714 can be removed (e.g., replaced) by the selected user identifier 722.

Additionally, the user can provide text input for linking a content item to text input 720. For example, the user can provide text input 720 including a content item identifier prefix 724 (e.g., “+”) followed by a few characters of a content item identifier. When CMS client 242 and/or project module 202 detects the content item identifier prefix 724, CMS client 242 can present suggestion 726 including suggestions for content item identifiers that match the characters that follow content item identifier prefix 724. In the example of FIG. 7, content item identifier prefix 724 is followed by the characters “mo” and CMS client 242 has found the content item “Mockup.jpeg” that matches the characters “mo.” CMS client 242 can present the content item identifier “Mockup.jpeg” in suggestion 726 and the user can select suggestion 726 to cause CMS client 242 to add a link to Mockup.jpeg to text input 720. While FIG. 7 illustrates only one suggested content item, CMS client 242 can present multiple content items when multiple content item identifiers match the sequence of characters following content item identifier prefix 724.

In some implementations, the user can continue providing text input to text input 720 to generate text input 730. As illustrated by FIG. 7, after the user selects content item suggestion 724, CMS client 242 can replace content item identifier prefix 714 with a link 732 to the selected content item 726.

Additionally, the user can provide text input for adding a tag to text input 730. For example, the user can provide text input 730 including a tag prefix 734 (e.g., “#”) followed by a few characters of a tag (e.g., subject, classification, descriptive word or phrase, etc.).

When CMS client 242 detects that the user is finished with text input 730 (e.g., the user submits the comment, closes the corresponding content item, a threshold period of time has elapsed since last input, etc.), CMS client 242 and/or project module 202 can process the comment (or text input) to determine the various attributes of the comment and/or to determine whether to convert the comment into a task. CMS client 242 and/or project module 202 can then store the comment or task and associated attributes (e.g., project identifier attribute, author identifier attribute, source content item attribute, recipient user attribute, linked content item attribute, tag attribute, etc.) in the appropriate database (e.g., comment database 206, task database 208).

FIG. 8 illustrates an example graphical user interface 800 presenting a content item that was added to the selected project folder. For example, GUI 800 can be presented by CMS client 242 on a display of client device 240 in response to the user selecting graphical element 602 of FIG. 6. In this example, the user has selected an option from graphical element 502 to add a content item 802 to the selected project folder. When content item 802 is added to the project folder, CMS client 242 and/or project module 202 can read content item 802 and extract comments, tasks, tags, and other project data from the content item. CMS client 242 can add the comments and tasks to comment database 206 and/or tasks database 208, respectively, along with the corresponding attribute data, as described above.

FIG. 9 illustrates an example graphical user interface 900 for presenting a description of the selected project. For example, the user can select graphical element 902 to present an informational project data view 903 (e.g., Wiki page, overview, etc.) describing the project, project members, important documents, and/or other information. Project data view 903 can present a content item 904 (e.g., file, document, web page, etc.) generated by one or more of the project members.

In some implementations, a project member can edit content item 904 from within project data view 903 by providing textual input, adding graphics, and/or other content. For example, a project member can edit content item 904 by adding text to content item 904 and CMS client 242 (or project module 202) can interpret special characters, patterns, or expressions in the text as described with reference to FIG. 7. For example, a user who is editing content item 904 can provide string 906 as input. String 906 can include the content item link prefix “+” followed by the characters “jou”. CMS client 242 can detect the content item link prefix and, in response to detecting the prefix, determine content items that have identifiers that include the characters following the prefix (e.g., “jou”). CMS client 242 can then present the determined content items as suggestions in graphical element 908 on GUI 900. The user can select one of the suggested content items to cause CMS client 242 to add a link to the content item in content item 904.

In some implementations, graphical element 908 can include a selectable item for creating a new content item having an identifier that matches the characters that follow the content item prefix. When the user selects to create a new content item, CMS client 242 can insert a link to the new content item in content item 904 presented in project data view 903.

FIG. 10 illustrates an example graphical user interface 1000 for presenting tasks associated with the selected project. For example, GUI 1000 can be presented by CMS client 242 in response to receiving a user selection of graphical element 1002 presented in project folder view 402. GUI 1000 can include, for example, project data view 1003 that provides a GUI for managing tasks associated with the currently selected project. For example, tasks can be created at the project level and/or the content item level. Project data view 1003 can present tasks according to whether the task is a project level task or a content item (e.g., file) level task. For example, project level tasks can be presented at the top of project data view 1003 and content item level tasks can be presented below the project level tasks. Other implementations may reverse the order of presentation of the tasks. CMS client 242 can obtain the task information presented in project data view 1003 from task database 208 through project module 202, as described above.

In some implementations, project data view 1003 can include graphical element 1004 and graphical element 1006 for creating a new project level task. For example, the user can select graphical element 1004 (e.g., a text input control) and enter text to describe a new project level task. The user can type text that includes the special characters, patterns, or expressions described above with reference to FIG. 7 to add links to content items, mention other users (e.g., project members) of content management system 106, and/or tag the new task. When other users are mentioned in a task, project module 202 can assign the task to the mentioned user, for example. When the user is done providing text input to graphical element 1004, the user can select graphical element 1006 (e.g., a button) to cause CMS client 242 and/or project module 202 to create the new project level task. When the project level task is created, project module 202 can store the project level task and task attributes (as described above) in task database 208. For example, CMS client 242 can send the description for the new project level task to project module 202 so that project module 202 can determine the attributes of the task and store the task in task database 208.

In some implementations, project data view 1003 can present graphical representations of tasks associated with the selected project. Project data view 1003 can include task 1008. For example, task 1008 can be a project level task created based on user input to graphical element 1004 and graphical element 1006. Project data view 1003 can include tasks 1010, 1012, and/or 1014. Tasks 1010, 1012, and/or 1014 can be content level tasks created when a project member creates a task within or with reference to a project content item.

Each task 1008-1014 can include various attributes. For example, task 1008 can include a task description. The task description can be a textual explanation of task 1008. Task 1008 can include recipient attribute 1020. For example, when a project member is at ‘@’ mentioned in a task, CMS client 242 and/or project module 202 can determine that the mentioned project member has been assigned the task. Task 1008 can include content item attribute 1022. For example, when a project content item is plus ‘+’ mentioned in a task, CMS client 242 and/or project module 202 can create a link to the mentioned content item in the task and determine that the mentioned content item is related to (e.g., is an attribute of) the task. Task 1008 can include tag attribute 1024. When task 1008 includes a tag prefix (e.g., ‘#’ character), CMS client 242 and/or project module 202 can determine a tag attribute for the task based on the string that immediately follows the tag prefix. Task 1008 can include author or creator attribute 1026. For example, CMS client 242 can determine which project member created the corresponding task, as described above. Each content item task 1010, 1012, and/or 1014 can include text or other graphical representation of the content item from within which the corresponding task was created. For example, content item tasks 1010, 1012, and/or 1014 can include source content item attributes 1011, 1013 and/or 1015 respectively. For example,

Each of the tasks presented by project data view 1003 can be generated by different project members and/or from within different project content items or different project user interfaces. For example, task 1004 can be generated from within project folder view 402 and/or project data view 1003 while task 1010 can be generated from within a project content item (e.g., content item 802). As another example, task 1010 can be generated from within a content item “Design.pdf” while task 1014 can be generated from within content item “Schedule.url.” Task 1010 can be generated by project member “Ben Berliner” while task 1012 was generated by project member “Phil Bowman.”

In some implementations, a user can select a task to change the state of the selected task. For example, the user can select a checkbox associated with a task to indicate that the task has been completed. When the user selects the checkbox, CMS client 242 can change the state of the corresponding task to completed and remove the task from project data view 1003.

In some implementations, a user can select a task to modify attributes of the task. For example, the user can select the text description of the task to cause CMS client 242 to present a task editing graphical user interface (e.g., graphical element 1502 of FIG. 15). The user can provide input to cause CMS client 242 to change various attributes of the selected task. CMS client 242 can then send the updated task information to project module 202 for storage in task database 208 and present the updated task information in project data view 1003.

FIG. 11 illustrates an example graphical user interface 1100 for presenting tagged project data. For example, GUI 1100 can be presented by CMS client 242 in response to the user selecting graphical element 1102 presented in project folder view 402. For example, in response to receiving a user selection of graphical element 1102, CMS client 242 can present project data view 1103 that includes representations of tagged project data. CMS client 242 can obtain the tagged project data from comments database 206, tasks database 208, and/or project folder 204 through project module 202. Alternatively, CMS client 242 can obtain the tagged project data from local project folder 252 on client device 240.

In some implementations, project data view 1103 can present tagged project data organized by tag. For example, a tag can be a string preceded (e.g., prefixed) by a special character or expression. As described above, the prefix for a tag can be the hash character ‘#’. Example tags can include “#engineering,” “#planning,” and/or “#design.” CMS client 242 can request tagged project data from project module 202. In response to the request, project module 202 can search comments database 206, tasks database 208, and/or project folder 204 for tagged data (e.g., comments, tasks, content items, etc.) and generate a collection of tagged data. In some implementations, the collection of tagged data can be organized or sorted by tag. For example, all “#engineering” tags can be grouped together in the collection. All “#planning” tags can be grouped together in the collection. Alternatively, CMS client 242 can sort the tagged data upon receipt of the collection of tagged data from project module 202. After generating the collection of tagged data, project module 202 can send the collection of tagged project data to CMS client 242 for presentation in project data view 1103.

In some implementations, CMS client 242 can present the tagged project data organized into groups or sections according to the tags associated with the project data, as illustrated by FIG. 11. For example, project data view 1103 can present a group or section 1110 of “#engineering” tags that include tagged project data 1112 and/or 1114. CMS client 242 can include project data 1112 and/or 1114 in section 1110 when CMS client 242 determines that project data 1112 and/or 1114 includes the “#engineering” tag. Similarly, data view 1103 can present a group or section 1120 of “#planning” tags that include tagged project data 1122. CMS client 242 can include project data 1122 in section 1120 when CMS client 242 determines that project data 1122 includes the “#planning” tag.

In some implementations, project data view 1103 can include tagged data of various types and/or from various project members. For example, project data view 1103 can include task 1112 and comment 114 that both include the “#engineering” tag. Project data view 1103 can include comment 114 created by project member “Ben Berliner” that includes the “#engineering” tag and task 1122 created by project member “Phil Bowman” that includes the “#planning” tag. Thus, project data view 1103 can include tags from across project content items, comments, tasks, and/or project members.

FIG. 12 illustrates an example graphical user interface 1200 for presenting comments associated with a project. For example, GUI 1200 can be presented by CMS client 242 in response to the user selecting graphical element 1202 presented in project folder view 402. For example, in response to receiving a user selection of graphical element 1202, CMS client 242 can present project data view 1203 that includes representations of comments associated with the selected project. CMS client 242 can obtain the comments from comments database 206 through project module 202. Alternatively, CMS client 242 can obtain the comments from local project folder 252 on client device 240.

In some implementations, project data view 1203 can include comments associated with various project content items. For example, project data view 1203 can include comments 1210, 1212 and/or 1214. Comments 1210, 1212 and/or 1214 can be presented, for example, ordered by when the corresponding comment was generated or created. For example, if comment 1210 is the most recent (e.g., newest) comment, comment 1210 can be presented at the top of project data view 1203. Comments 1212 and 1214 can be listed below comment 1210 in time order from newest to oldest. In some implementations, comments can be presented in time order where the comment at the bottom of project data view 1203 is the newest and increasingly older comments are presented toward the top of project data view 1203. Each comment 1210, 1212 and/or 1214 can include an identifier (e.g., graphical element 1216, text 1218) for author of the comment, an indication 1220 of when the comment was created, an identifier 1222 for the content item in which the comment was created, and/or text 1224 representing the comment.

FIG. 13 illustrates an example graphical user interface 1300 presenting recently accessed content items. For example, GUI 1300 can be presented by CMS client 242 in response to receiving user input selecting graphical element 1302 presented in project data view 1303. To generate GUI project data view 1303, CMS client 242 can receive project data from project module 202 indicating times (e.g., timestamps) at which project content items stored in project folder 204 were accessed (e.g., viewed, modified, created, moved, etc.). For example, the timestamps can be determined based on file system data and/or a change log that tracks changes to content items in the project folder. Since project folder 204 is synchronized with project folder 252 on client device 240, the timestamp associated with a content item may represent times at which the corresponding content item was accessed on client device 240. Alternatively, CMS client 242 can determine times (e.g., timestamps) at which project content items stored in project folder 252 were accessed (e.g., viewed, modified, created, moved, etc.). Since project folder 252 is synchronized with project folder 204 on content management system 106, the timestamp associated with a content item may represent times at which the corresponding content item was accessed on content management system 106 or another client device similar to client device 240 (not shown) that has been synchronized with project.

In some implementations, project data view 1303 can include graphical representations of recently accessed project content items. For example, project data view 1303 can include graphical representation 1310 and/or graphical representation 1320 of recently accessed project content items. For example, project data view 1303 can present time ordered representations of recently accessed project content items. CMS client 242 can, for example, generate project data view 1303 by presenting a representation of the most recently accessed project content item (e.g., representation 1310) at the top of project data view 1303 and less and less recent project content items (e.g., representation 1320) in time order below the most recently accessed project content item. A user can scroll project data view 1303 upward to view content items that were accessed in the more distant past, for example.

Each content item representation (e.g., representation 1310, representation 1320, etc.) in project data view 1303 can present an identifier (e.g., name, directory, path, etc.) for the corresponding project content item. Each content item representation in project data view 1303 can present an indication of when the corresponding project content item was last accessed.

In some implementations, each content item representation in project data view 1303 can present a representation of the contents of the corresponding project content item. For example, representation 1310 can include content representation 1312. Representation 1320 can include content representation 1322. For example, content representation 1312/1322 can be a static preview image of the content of the corresponding content item. Alternatively, content representation 1312/1322 can be an editable or modifiable representation of the corresponding content item. In some implementations, the user can provide input to content representation 1312/1322 to scroll, zoom, print, or perform some other action with respect to the content presented in content representation 1312/1322. In some implementations, the user can select content representation 1312/1322 or corresponding content item identifier to open the corresponding content item in an editor application for the selected content item.

FIG. 14 illustrates an example graphical user interface 1400 for presenting tasks associated with a particular user of content management system 106. For example, GUI 1400 can be presented by CMS client 242 on a display of client device 240 in response to the user selecting graphical element 1404 from task menu 1402. For example, task menu 1402 can be presented in side panel 301 on GUI 1400 and/or any of the other graphical user interfaces described herein.

In some implementations, GUI 1400 can present user task view 1420. For example, user task view 1420 can present tasks associated with a specific user. For example, if the user “Phil Bowman” (e.g., as indicated by graphical element 1414) is using client device 240 and/or CMS client 242 and has logged into content management system 106, user task view 1420 can present tasks associated with (e.g., created by, assigned to, etc.) the user “Phil Bowman.” CMS client 242 can obtain task information describing tasks associated with the user for presentation in user task view 1420 from tasks database 208 through project module 202, for example. Alternatively, CMS client 242 can obtain task information describing tasks associated with the user locally from managed content 250 on client device 240.

In some implementations, the tasks in user task view 1420 can be presented in a list view as illustrated by GUI 1400 and indicated by graphical element 1412. For example, user task view 1420 can present tasks arranged or prioritized by due date. User task view 1420 can filter tasks by due date. For example, user task view 1420 can present tasks that are due within the next 7 days, 10 days, 2 weeks, etc. User task view 1420 can present tasks that are incomplete and/or in progress.

In some implementations, user task view 1420 can present tasks from across different projects. For example, when the user selects graphical element 1404, CMS client 242 can present tasks associated with the user and from various projects managed by content management system 106. For example, user task view 1420 can present tasks 1442 and 1444 associated with the particular user and from project 1440 (e.g., “Project Widget”). User task view 1420 can present tasks 1452 and 1454 associated with the particular user and project 1450 (e.g., “Project Awesome”). User task view 1420 can present task 1462 associated with the particular user and project 1460 (e.g., “Project Opie”). As described above, the user can select a task or task checkbox to change the state of the corresponding task.

In some implementations, user task view 1420 can present tasks associated with a particular project. For example, the user can select graphical element 1406 to cause user task view 1420 to filter tasks by project. In other words, when graphical element 1406 is selected, user task view 1420 can present tasks associated with a project associated with graphical element 1406 while hiding (e.g., not showing, filtering out, etc.) tasks associated with other projects. Thus, when CMS client 242 receives a selection of graphical element 1406, CMS client 242 can generate and present user task view 1420 that includes tasks 1442 and 1444 associated with project 1440 while hiding tasks 1452, 1454, and 1462 associated with projects 1450 and 1460. Similarly, when CMS client 242 receives a selection of graphical element 1408, CMS client 242 can present user task view 1420 that includes tasks associated with project 1450 and hides tasks associated with project 1440 and 1460. When CMS client 242 receives a selection of graphical element 1410, CMS client 242 can present user task view 1420 that includes tasks associated with project 1460 and hides tasks associated with project 1440 and 1450.

FIG. 15 illustrates an example graphical user interface 1500 for creating a new task. For example, GUI 1500 can correspond to GUI 1400 of FIG. 14. CMS client 242 can present GUI 1500 in response to the user selecting graphical element 1501 presented in user task view 1420, for example. In response to receiving the user selection of graphical element 1501, CMS client 242 can present graphical element 1502 (e.g., a window, a popup, a dialog box) on GUI 1500.

In some implementations, graphical element 1502 can include input controls for defining a new task. The input controls can include text input boxes, pull down menus, calendar controls, and/or other well-known user input controls. The text input controls can receive text input including the special characters, expressions, prefixes, etc., described above with reference to FIG. 7 and CMS client 242 can interpret, translate, or convert the prefixed text into task attributes, as described above. When the user provides text input into the text controls, CMS client 242 can present suggestions for users, project members, content items, etc., based on the text input, as described above with reference to FIG. 7.

In some implementations, graphical element 1502 can include input control 1504 for describing the new task. For example, the user can provide text input to input control 1504 to provide a title, subject, and/or description of the new task. Graphical element 1502 can include input control 1506 for associating the new task with a project. For example, the user can provide text input to input control 1506 to provide an identifier for a project with which the new task is associated. Graphical element 1502 can include input control 1508 for specifying a due date for the new task. For example, the user can provide text input to input control 1506 to specify a date when the task is due for completion. Alternatively, input control 1506 can present a calendar representation that allows the user to select a due date from the calendar representation.

In some implementations, graphical element 1502 can include input control 1510 for assigning the task to a user of content management system 106. For example, the user can provide text input to input control 1510 specifying the name of a user to whom the task is assigned. Graphical element 1502 can include input control 1512 for providing details about the task. For example, the user can provide text input to input control 1512 to provide a summary description of the task, indicate related content items, indicate related users or project members, and/or include tags or any other information relevant to the new task. Graphical element 1502 can include input control 1514 for indicating a current state or status of the new task. For example, the user can provide text input specifying the current status of the new task. When input control 1514 is a pull down menu control, the user can select the current status of the task from a set of predefined statuses (e.g., to do, in progress, completed, etc.). When the user is done defining the task in graphical element 1502, the user can select graphical element 1516 (e.g., a button) to cause CMS client 242 to save the new task in project folder 252 and/or in task database 208 through project module 202.

FIG. 16 illustrates an example graphical user interface 1600 presenting a newly created task. For example, GUI 1600 can correspond to GUI 1400 of FIG. 14. CMS client 242 can present GUI 1600 in response to the user selecting graphical element 1516 to save a new task. For example, GUI 1600 can present task 1602 associated with project 1460 as defined based on the user input received by graphical element 1502.

FIG. 17 illustrates an example graphical user interface 1700 presenting a column view of tasks associated with the user. For example, CMS client 242 can present a columnar representation of user task view 1420 in response to the user selecting graphical element 1704. The user can, for example, switch between a list view and task view of user by selecting graphical element 1412 (e.g., for list view) and/or graphical element 1704 (e.g., for column view), respectively.

When presenting a column view of user tasks on user task view 1420, CMS client 242 can present graphical elements 1710, 1720, and/or 1730 representing respective task states. Each graphical element 1710, 1720, and/or 1730 can define an area (e.g., columns, rows, sections, etc.). A task can be presented within the area of a graphical element 1710, 1720, and/or 1730 when the current state of the task corresponds to the task state represented by the corresponding graphical element 1710, 1720, and/or 1730. For example, graphical element 1710 can represent a “to do” state indicating that corresponding tasks 1712, and/or 1714 have not yet been started. Graphical element 1720 can represent a “in progress” state indicating that corresponding task 1722 has been started but not yet completed. Graphical element 1730 can represent a “completed” state indicating that corresponding task 1732 has been completed. Other graphical elements may be presented representing other task states.

In some implementations, a user can provide input to user task view 1420 to change the state of a task. For example, the user can select the checkbox within task 1714 to indicate that task 1714 has been completed. Upon receiving the user input indicating that task 1714 has been completed, CMS client 242 can present a representation 1732 of task 1714 that indicates that task 1714 has been completed within the area defined by graphical element 1730. For example, CMS client 242 can remove task 1714 from graphical element 1710 and present task 1714 (now task 1732) within the area defined by graphical element 1730.

FIG. 18 illustrates an example graphical interface 1800 for changing the state of a task. For example, GUI 1800 can correspond to GUI 1700 of FIG. 17 described above.

In some implementations, a user can change the state of a task by dragging and dropping tasks into the areas defined by graphical elements 1710, 1720, and/or 1730. For example, the user can select and drag task 1802 from graphical element 1710 into graphical element 1720 to cause CMS client 242 to change the state of task 1802 from “to do” to “in progress.” Similarly, the user can select and drag task 1804 from graphical element 1720 into graphical element 1730 to cause CMS client 242 to change the state of task 1802 from “in progress” to “completed.” The user can select and drag task 1810 from graphical element 1710 into graphical element 1730 to cause CMS client 242 to change the state of task 1810 from “to do” to “completed,” as indicated by task 1730. The user can also provide input to change task states by moving tasks from graphical elements 1730 and/or 1720 to graphical elements 1710 and 1720, for example. When the user changes the state of a task, CMS client 242 can send the updated task information, including the changed task state, to project module 202 for storage in task database 208 managed by content management system 106.

Example Processes

FIG. 19 is an example process 1900 for managing projects in a content management system. For example, process 1900 can be performed by CMS client 242 and/or project module 202 to manage project data and present graphical user interfaces that allow a user (e.g., project member) to view and manage project data within a single project management application and/or graphical user interface. The steps below are described with reference to a computing device that performs operations described at each step. The computing device can correspond to a server corresponding to content management system 106 and/or client device 240. The steps can be performed by project module 202 and/or CMS client 242.

At step 1902, a computing device can store a project folder corresponding to a project. For example, the project folder can be a shared folder. The computing device can share the shared folder members (e.g., users) of the project who are collaborating on project tasks, content items, etc., to achieve a project goal. The computing device can create the project folder in response to receiving input from a user of content management system 106 to create a new shared folder managed by content management system 106.

At step 1904, the computing device can store content items in the project folder. For example, the computing device can store a content item in the project folder in response to a user uploading a content item to the project. The computing device can store a content item in the project folder in response to a user creating a new content item in the project or project folder view, as described above. The computing device can store a content item in the project folder in response to a user moving a content item into the project folder using standard file system operations. The computing device can store a content item in the project folder in response to a user linking to or mentioning a content item in a comment, task, or other interaction with CMS client 242.

At step 1906, the computing device can store project data associated with the project. For example, the content items stored in the project folder can include comments, tasks, tags and other project data. The computing device can read the content items to determine comments, tasks, and/or tags included in the project content items and store the comments, tasks, and/or tags in project databases and/or the project folder, as described above. The computing device can store comments, tasks, and/or tag created externally to project content items. For example, the computing device can store comments, tasks, and/or tags created by a user in any of the graphical user interfaces described above.

At step 1908, the computing device can receive a user selection of a project folder. For example, the user can select a project folder from GUI 300 of FIG. 3.

At step 1910, the computing device can obtain project data associated with the project corresponding to the selected project folder. For example, the computing device can obtain project data (e.g., tasks, comments, tags, etc.) from various databases, described above. The computing device can obtain the project data from the project folder stored on a server of content management system 106 or on client device 240. The computing device can obtain the project data from within content items associated with the project and/or stored in the project folder.

At step 1912, the computing device can generate a project folder view. For example, in response to receiving the selection of the project folder and/or obtaining the project data, the computing device can present a project folder view that presents the project data as described above with reference to the graphical user interfaces of FIG. 4 to FIG. 13.

At step 1914, the computing device can cause a client device to present the project folder view. For example, when the computing device is a server of content management system 106 and CMS client 242 is a web browser, the server can send a web page to CMS client 242 to cause CMS client 242 to present the project folder view on a display of client device 240. When the computing device is a server of content management system 106 and CMS client 242 is a native browser, the server can send a project data to CMS client 242 to cause CMS client 242 to present the project folder view in a native GUI of CMS client 242 on a display of client device 240. Alternatively, CMS client 242 on client device 240 can obtain project data from a local synchronized version of the project folder and present the project folder view based on the local project data.

FIG. 20 is an example process 2000 for managing tasks in content management system. For example, process 2000 can be performed by CMS client 242 and/or project module 202 to manage user task data and present graphical user interfaces that allow a user (e.g., project member) to view and manage task data. The steps below are described with reference to a computing device that performs operations described at each step. The computing device can correspond to a server corresponding to content management system 106 and/or client device 240. The steps can be performed by project module 202 and/or CMS client 242, for example.

At step 2002, a computing device can store tasks associated with one or more projects. For example, the computing device can store tasks in a task database, as described above. The computing device can store tasks in one or more project folders, as described above.

At step 2004, the computing device can receive a request for task data associated with a particular user. For example, project module 202 can receive from CMS client 242 a request for task data associated with a particular user.

At step 2006, the computing device can determine tasks associated with the particular user. For example, project module 202 can search task database 208 for tasks assigned to and/or created by the particular user.

At step 2008, the computing device can generate a user task view. For example, the user task view can include tasks associated with the particular user, as determined at step 2006. The tasks can be organized in a list view and/or grouped by project, as illustrated by FIG. 14 and FIG. 16. The tasks can be organized in a column view and/or grouped by task state, as illustrated by FIG. 17 and FIG. 18.

At step 2010, the computing device can apply filters to tasks associated with the particular user. For example, step 2008 can be an optional step that applies project filters, time filters, and/or task state filters to tasks associated with the particular user. For example, the computing device can apply a project filter based on a selected project such that tasks not associated with the selected project are filtered out of (e.g., hidden from) the user task view. The computing device can apply a time filter based on a configured amount of time (e.g., 7 days, 2 weeks, one month, etc.) such that tasks that have due dates that are not within the configured amount of time from the present time are filtered out of (e.g., hidden from) the user task view. The computing device can apply a task state filter that filters out tasks from the user task view that are completed or are in some other state.

At step 2012, the computing device can cause a client device to present the user task view on a display of the client device. For example, when the computing device is a server of content management system 106 and CMS client 242 is a web browser, the server can send a web page to CMS client 242 to cause CMS client 242 to present the user task view on a display of client device 240. When the computing device is a server of content management system 106 and CMS client 242 is a native browser, the server can send user task data to CMS client 242 to cause CMS client 242 to present the user task data in a native GUI of CMS client 242 on a display of client device 240. Alternatively, CMS client 242 on client device 240 can obtain user task from managed content 250.

FIG. 21A and FIG. 21B show example possible system embodiments. The more appropriate embodiment will be apparent to those of ordinary skill in the art when practicing the present technology. Persons of ordinary skill in the art will also readily appreciate that other system embodiments are possible.

FIG. 21A illustrates a conventional system bus computing system architecture 2100 wherein the components of the system are in electrical communication with each other using a bus 2105. Example system 2100 includes a processing unit (CPU or processor) 2110 and a system bus 2105 that couples various system components including the system memory 2115, such as read only memory (ROM) 2120 and random access memory (RAM) 2125, to the processor 2110. The system 2100 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 2110. The system 2100 can copy data from the memory 2115 and/or the storage device 2130 to the cache 2112 for quick access by the processor 2110. In this way, the cache can provide a performance boost that avoids processor 2110 delays while waiting for data. These and other modules can control or be configured to control the processor 2110 to perform various actions. Other system memory 2115 may be available for use as well. The memory 2115 can include multiple different types of memory with different performance characteristics. The processor 2110 can include any general purpose processor and a hardware module or software module, such as module 12132, module 22134, and module 32136 stored in storage device 2130, configured to control the processor 2110 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 2110 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing device 2100, an input device 2145 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 2135 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 2100. The communications interface 2140 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 2130 is a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 2125, read only memory (ROM) 2120, and hybrids thereof.

The storage device 2130 can include software modules 2132, 2134, 2136 for controlling the processor 2110. Other hardware or software modules are contemplated. The storage device 2130 can be connected to the system bus 2105. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 2110, bus 2105, display 2135, and so forth, to carry out the function.

FIG. 21B illustrates a computer system 2150 having a chipset architecture that can be used in executing the described method and generating and displaying a graphical user interface (GUI). Computer system 2150 is an example of computer hardware, software, and firmware that can be used to implement the disclosed technology. System 2150 can include a processor 2110, representative of any number of physically and/or logically distinct resources capable of executing software, firmware, and hardware configured to perform identified computations. Processor 2110 can communicate with a chipset 2160 that can control input to and output from processor 2110. In this example, chipset 2160 outputs information to output 2165, such as a display, and can read and write information to storage device 2170, which can include magnetic media, and solid state media, for example. Chipset 2160 can also read data from and write data to RAM 2175. A bridge 2180 for interfacing with a variety of user interface components 2185 can be provided for interfacing with chipset 2160. Such user interface components 2185 can include a keyboard, a microphone, touch detection and processing circuitry, a pointing device, such as a mouse, and so on. In general, inputs to system 2150 can come from any of a variety of sources, machine generated and/or human generated.

Chipset 2160 can also interface with one or more communication interfaces 2190 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 2110 analyzing data stored in storage 2170 or 2175. Further, the machine can receive inputs from a user via user interface components 2185 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 2110.

It can be appreciated that example systems 2100 and 2150 can have more than one processor 2110 or be part of a group or cluster of computing devices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

Any of the steps, operations, functions, or processes described herein may be performed or implemented by a combination of hardware and software modules, alone or in combination with other devices. In an embodiment, a software module can be software that resides in memory of a client device and/or one or more servers of a content management system and perform one or more functions when a processor executes the software associated with the module. The memory can be a non-transitory computer-readable medium.

In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.

Claims

1. A method comprising: causing, by a content management system, display of a graphical user interface on an authorized client device, the graphical user interface comprising a project view, the project view presenting project data corresponding to a project managed by the content management system;receiving, by the content management system via the graphical user interface, a request to add a content item to the project;based on the request, adding, by the content management system, the content item to the project, wherein adding the content item to the project comprises: analyzing the content item to identify one or more of comments, tasks, or tags contained in the content item,extracting the one or more of the comments, the tasks, or the tags from the content item, andstoring the one or more of the comments, the tasks, or the tags in association with the project, andupdating the project view to include at least one of the comments, the tasks, or the tags from the content item.
2. The method of claim 1, wherein receiving, by the content management system via the graphical user interface, the request to add the content item to the project comprises: causing display of a graphical element via the graphical user interface, the graphical element comprising an option for adding a link to the content item; andreceiving, via the graphical element, the link to the content item.
3. The method of claim 1, further comprising: receiving, by the content management system, a further request to view the content item;responsive to receiving the request, generating, by the content management system, a further graphical user interface for presenting the content item, the further graphical user interface comprising a comments area that includes the comments extracted from the content item; andcausing, by the content management system, display of the further graphical user interface.
4. The method of claim 3, further comprising: receiving, by the content management system, a further comment via the comments area of the graphical user interface; andstoring, by the content management system, the further comment in association with the project.
5. The method of claim 4, further comprising: analyzing, by the content management system, the further comment;based on the analyzing, detecting, by the content management system, a first indication to generate a new task and a second indication comprising an assignment of the new task; andbased on the detecting, creating, by the content management system, the new task,assigning, by the content management system, the new task in accordance with the assignment, andstoring, by the content management system, the new task in association with the project.
6. The method of claim 1, further comprising: receiving, by the content management system, a further request to view a plurality of comments associated with the project;identifying, by the content management system, the plurality of comments associated with the project, wherein the plurality of comments comprise the comments associated with the content item and at least one second comment associated with a second content item that is associated with the project; andcausing, by the content management system, display of the plurality of comments associated with the project.
7. The method of claim 1, further comprising: receiving, by the content management system, a further request to view a plurality of tasks associated with the project;identifying, by the content management system, the plurality of tasks associated with the project, wherein the plurality of tasks comprise the tasks associated with the content item and at least one second task associated with a second content item that is associated with the project; andcausing, by the content management system, display of the plurality of tasks associated with the project.
8. A non-transitory computer readable medium comprising one or more sequences of instructions, which, when executed by a processor, causes a content management system to perform operations comprising: receiving, by the content management system, a request to add a content item to a project of a plurality of projects managed by the content management system;based on the request, adding, by the content management system, the content item to the project, wherein adding the content item to the project comprises: identifying the project of the plurality of projects indicated in the request,analyzing the content item to identify one or more of comments, tasks, or tags contained in the content item,extracting the one or more of the comments, the tasks, or the tags from the content item, andstoring the one or more of the comments, the tasks, or the tags in association with the project, andgenerating a project view that includes at least one of the comments, the tasks, or the tags from the content item.
9. The non-transitory computer readable medium of claim 8, wherein receiving, by the content management system, the request to add the content item to the project comprises: causing display of a graphical element via a graphical user interface, the graphical element comprising an option for adding a link to the content item; andreceiving, via the graphical element, the link to the content item.
10. The non-transitory computer readable medium of claim 8, further comprising: receiving, by the content management system, a further request to view the content item;responsive to receiving the request, generating, by the content management system, a graphical user interface for presenting the content item, the graphical user interface comprising a comments area that includes the comments extracted from the content item; andcausing, by the content management system, display of the graphical user interface.
11. The non-transitory computer readable medium of claim 10, further comprising: receiving, by the content management system, a further comment via the comments area of the graphical user interface; andstoring, by the content management system, the further comment in association with the project.
12. The non-transitory computer readable medium of claim 11, further comprising: analyzing, by the content management system, the further comment;based on the analyzing, detecting, by the content management system, a first indication to generate a new task and a second indication comprising an assignment of the new task; andbased on the detecting, creating, by the content management system, the new task,assigning, by the content management system, the new task in accordance with the assignment, andstoring, by the content management system, the new task in association with the project.
13. The non-transitory computer readable medium of claim 8, further comprising: receiving, by the content management system, a further request to view a plurality of comments associated with the project;identifying, by the content management system, the plurality of comments associated with the project, wherein the plurality of comments comprise the comments associated with the content item and at least one second comment associated with a second content item that is associated with the project; andcausing, by the content management system, display of the plurality of comments associated with the project.
14. The non-transitory computer readable medium of claim 8, further comprising: receiving, by the content management system, a further request to view a plurality of tasks associated with the project;identifying, by the content management system, the plurality of tasks associated with the project, wherein the plurality of tasks comprise the tasks associated with the content item and at least one second task associated with a second content item that is associated with the project; andcausing, by the content management system, display of the plurality of tasks associated with the project.
15. A system comprising: a processor; anda memory having programming instructions stored thereon, which, when executed by the processor, causes the system to perform operations comprising: receiving a request to add a content item to a project;based on the request, adding the content item to the project, wherein adding the content item to the project comprises: analyzing the content item to identify one or more of comments, tasks, or tags contained in the content item,extracting the one or more of the comments, the tasks, or the tags from the content item, andstoring the one or more of the comments, the tasks, or the tags in association with the project, andgenerating a project view that includes at least one of the comments, the tasks, or the tags from the content item.
16. The system of claim 15, wherein receiving the request to add the content item to the project comprises: causing display of a graphical element via a graphical user interface, the graphical element comprising an option for adding a link to the content item; andreceiving, via the graphical element, the link to the content item.
17. The system of claim 15, wherein the operations further comprise: receiving a further request to view the content item;responsive to receiving the request, generating a graphical user interface for presenting the content item, the graphical user interface comprising a comments area that includes the comments extracted from the content item; andcausing display of the graphical user interface.
18. The system of claim 17, wherein the operations further comprise: receiving a further comment via the comments area of the graphical user interface; andstoring the further comment in association with the project.
19. The system of claim 18, wherein the operations further comprise: analyzing the further comment;based on the analyzing, detecting a first indication to generate a new task and a second indication comprising an assignment of the new task; andbased on the detecting, creating the new task,assigning the new task in accordance with the assignment, andstoring the new task in association with the project.
20. The system of claim 15, wherein the operations further comprise: receiving a further request to view a plurality of comments associated with the project;identifying the plurality of comments associated with the project, wherein the plurality of comments comprise the comments associated with the content item and at least one second comment associated with a second content item that is associated with the project; andcausing display of the plurality of comments associated with the project.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. application Ser. No. 17/302,370, filed Apr. 30, 2021, which is a continuation of U.S. application Ser. No. 16/525,811, filed Jul. 30, 2019, now U.S. Pat. No. 11,017,354, issued May 25, 2021, which is a continuation of U.S. application Ser. No. 15/395,220, filed Dec. 30, 2016, now U.S. Pat. No. 10,402,786, issued Sep. 3, 2019, which are incorporated by reference in their entireties.

US Referenced Citations (386)

Number	Name	Date	Kind
5634129	Dickinson et al.	May 1997	A
6370567	Ouchi	Apr 2002	B1
6505236	Pollack et al.	Jan 2003	B1
6839741	Tsai et al.	Jan 2005	B1
6970906	Parsons et al.	Nov 2005	B1
7039678	Halahmi et al.	May 2006	B1
7062532	Sweat et al.	Jun 2006	B1
7543237	Kontny et al.	Jun 2009	B2
7546317	Kaptelinin	Jun 2009	B1
7689510	Lamkin et al.	Mar 2010	B2
7693958	Teodosiu et al.	Apr 2010	B2
7774710	Krishnan et al.	Aug 2010	B2
7865394	Calloway et al.	Jan 2011	B1
7970850	Callanan et al.	Jun 2011	B1
8015491	Shaver et al.	Sep 2011	B2
8117271	McConn et al.	Feb 2012	B2
8122015	Liu et al.	Feb 2012	B2
8122051	Spring et al.	Feb 2012	B2
8161120	Tan et al.	Apr 2012	B2
8214747	Yankovich et al.	Jul 2012	B1
8245141	Fuller et al.	Aug 2012	B1
8250150	Beck et al.	Aug 2012	B2
8316128	Beck et al.	Nov 2012	B2
8332357	Chung	Dec 2012	B1
8341532	Ryan et al.	Dec 2012	B2
8392472	Gupta et al.	Mar 2013	B1
8438185	Teranishi et al.	May 2013	B2
8533268	Vernon et al.	Sep 2013	B1
8543926	Giles et al.	Sep 2013	B2
8584022	O'Shaughnessy et al.	Nov 2013	B1
8639552	Chen et al.	Jan 2014	B1
8666991	Peters	Mar 2014	B2
8700719	Covitz et al.	Apr 2014	B1
8713106	Spataro et al.	Apr 2014	B2
8745222	Chi et al.	Jun 2014	B2
8793324	Schabes et al.	Jul 2014	B1
8819587	Shrum et al.	Aug 2014	B1
8892679	Destagnol et al.	Nov 2014	B1
8918365	Skrenta	Dec 2014	B2
8924876	Joyce et al.	Dec 2014	B1
8930412	Nelson et al.	Jan 2015	B2
8977662	Hilliar	Mar 2015	B1
8977722	Tsao	Mar 2015	B2
8990151	Savage et al.	Mar 2015	B2
9002962	Lynch et al.	Apr 2015	B2
9166954	Swineford et al.	Oct 2015	B2
9230241	Singh et al.	Jan 2016	B1
9235268	Arrasvuori et al.	Jan 2016	B2
9240962	Jung et al.	Jan 2016	B2
9251360	Meyer et al.	Feb 2016	B2
9252973	Lin et al.	Feb 2016	B1
9298355	Beausoleil et al.	Mar 2016	B1
9300609	Beausoleil et al.	Mar 2016	B1
9395892	Beausoleil et al.	Jul 2016	B1
9395893	Beausoleil et al.	Jul 2016	B1
9477760	Xie et al.	Oct 2016	B2
9542391	Eisner et al.	Jan 2017	B1
9584565	Ho et al.	Feb 2017	B1
9588979	Cueto et al.	Mar 2017	B2
9641488	Mityagin et al.	May 2017	B2
9747297	Penangwala et al.	Aug 2017	B2
9773051	Smith	Sep 2017	B2
9978040	Lee et al.	May 2018	B2
9990365	Kilpatrick et al.	Jun 2018	B1
10320727	Mesters et al.	Jun 2019	B1
10402786	Lo et al.	Sep 2019	B2
10719807	Newhouse et al.	Jul 2020	B2
10796012	Birkel et al.	Oct 2020	B2
10970656	Newhouse et al.	Apr 2021	B2
11017354	Lo	May 2021	B2
20020120485	Kirkconnell-Ewing et al.	Aug 2002	A1
20020138582	Chandra et al.	Sep 2002	A1
20030009536	Henderson et al.	Jan 2003	A1
20030018622	Chau	Jan 2003	A1
20030046134	Frolick et al.	Mar 2003	A1
20030065722	Ieperen	Apr 2003	A1
20030131062	Miyashita et al.	Jul 2003	A1
20030135565	Estrada	Jul 2003	A1
20030163490	Kitamura	Aug 2003	A1
20040083480	Dodge et al.	Apr 2004	A1
20040117445	Lee et al.	Jun 2004	A9
20040141508	Schoeneberger et al.	Jul 2004	A1
20040162878	Lewis et al.	Aug 2004	A1
20040187140	Aigner et al.	Sep 2004	A1
20040225647	Connelly et al.	Nov 2004	A1
20040230599	Moore et al.	Nov 2004	A1
20040236639	Candadai et al.	Nov 2004	A1
20050022931	Min et al.	Feb 2005	A1
20050028008	Kumar	Feb 2005	A1
20050091289	Shappell et al.	Apr 2005	A1
20050097440	Lusk et al.	May 2005	A1
20050108293	Lipman et al.	May 2005	A1
20050151756	Miyamoto et al.	Jul 2005	A1
20050172226	Kobashi et al.	Aug 2005	A1
20050182773	Feinsmith	Aug 2005	A1
20050198125	Macleod et al.	Sep 2005	A1
20050198299	Beck et al.	Sep 2005	A1
20050222931	Mamou et al.	Oct 2005	A1
20050223024	Hyun et al.	Oct 2005	A1
20050223315	Shimizu et al.	Oct 2005	A1
20060004685	Pyhalammi et al.	Jan 2006	A1
20060020904	Aaltonen et al.	Jan 2006	A1
20060026213	Yaskin et al.	Feb 2006	A1
20060064434	Gilbert et al.	Mar 2006	A1
20060080432	Spataro et al.	Apr 2006	A1
20060101443	Nasr	May 2006	A1
20060136821	Barabe et al.	Jun 2006	A1
20060265377	Raman et al.	Nov 2006	A1
20070033088	Aigner et al.	Feb 2007	A1
20070050324	Trinkel et al.	Mar 2007	A1
20070067726	Flynt et al.	Mar 2007	A1
20070100829	Allen et al.	May 2007	A1
20070101294	Fong et al.	May 2007	A1
20070150551	Krishnan et al.	Jun 2007	A1
20070179958	Chen et al.	Aug 2007	A1
20070276795	Poulsen et al.	Nov 2007	A1
20070277098	Shahar et al.	Nov 2007	A1
20070288839	Kurosawa et al.	Dec 2007	A1
20080028323	Rosen et al.	Jan 2008	A1
20080036794	Weiser et al.	Feb 2008	A1
20080077614	Roy et al.	Mar 2008	A1
20080091761	Tsao	Apr 2008	A1
20080120382	Heidloff et al.	May 2008	A1
20080140732	Wilson et al.	Jun 2008	A1
20080177994	Mayer	Jul 2008	A1
20080195659	Rawle	Aug 2008	A1
20080201422	Peccora et al.	Aug 2008	A1
20080256458	Aldred et al.	Oct 2008	A1
20080288453	Smetters et al.	Nov 2008	A1
20080320397	Do et al.	Dec 2008	A1
20090013043	Tan	Jan 2009	A1
20090044146	Patel et al.	Feb 2009	A1
20090064284	Poston et al.	Mar 2009	A1
20090131116	Tsuchiya et al.	May 2009	A1
20090138808	Moromisato et al.	May 2009	A1
20090172281	Jogand-Coulomb et al.	Jul 2009	A1
20090177754	Brezina et al.	Jul 2009	A1
20090235182	Kagawa et al.	Sep 2009	A1
20090249244	Robinson et al.	Oct 2009	A1
20090282421	Jaffer et al.	Nov 2009	A1
20090307605	Ryan et al.	Dec 2009	A1
20090307622	Jalon et al.	Dec 2009	A1
20090319694	Slezak et al.	Dec 2009	A1
20090327405	Fitzgerald et al.	Dec 2009	A1
20090327936	Wong et al.	Dec 2009	A1
20100024011	Fukuoka	Jan 2010	A1
20100070448	Omoigui	Mar 2010	A1
20100082713	Frid-Nielsen et al.	Apr 2010	A1
20100095198	Bultrowicz et al.	Apr 2010	A1
20100138503	Ishikawa et al.	Jun 2010	A1
20100151431	Miller et al.	Jun 2010	A1
20100180196	Matsusaka	Jul 2010	A1
20100211621	Hariharan et al.	Aug 2010	A1
20100241711	Ansari et al.	Sep 2010	A1
20100250497	Redlich et al.	Sep 2010	A1
20100262435	Smith et al.	Oct 2010	A1
20100287221	Battepati et al.	Nov 2010	A1
20100293021	Van et al.	Nov 2010	A1
20100299763	Marcus et al.	Nov 2010	A1
20100317420	Hoffberg	Dec 2010	A1
20110014524	Skotheim et al.	Jan 2011	A1
20110022662	Barber-Mingo et al.	Jan 2011	A1
20110054968	Galaviz	Mar 2011	A1
20110066948	Tsao	Mar 2011	A1
20110069643	Yoakum et al.	Mar 2011	A1
20110083090	Gwiazda et al.	Apr 2011	A1
20110119101	Drury	May 2011	A1
20110119353	Tsao	May 2011	A1
20110145245	Choi et al.	Jun 2011	A1
20110154209	Fan et al.	Jun 2011	A1
20110173081	Crucs	Jul 2011	A1
20110185015	Stolper	Jul 2011	A1
20110202430	Narayanan et al.	Aug 2011	A1
20110214088	Sandru et al.	Sep 2011	A1
20110249024	Arrasvuori et al.	Oct 2011	A1
20110252375	Chaudhri	Oct 2011	A1
20110258554	Sidenur et al.	Oct 2011	A1
20110258561	Ladouceur et al.	Oct 2011	A1
20110276897	Crevier et al.	Nov 2011	A1
20110289054	Johnson et al.	Nov 2011	A1
20120036016	Hoffberg et al.	Feb 2012	A1
20120054639	Shi et al.	Mar 2012	A1
20120079389	Tsao	Mar 2012	A1
20120089565	Jackson	Apr 2012	A1
20120089610	Agrawal et al.	Apr 2012	A1
20120110515	Abramoff et al.	May 2012	A1
20120124092	Teranishi et al.	May 2012	A1
20120136936	Quintuna	May 2012	A1
20120143917	Prabaker et al.	Jun 2012	A1
20120151379	Schultz et al.	Jun 2012	A1
20120158461	Aldrey et al.	Jun 2012	A1
20120182384	Anderson et al.	Jul 2012	A1
20120185800	Hart et al.	Jul 2012	A1
20120192086	Ghods et al.	Jul 2012	A1
20120221520	Garrett et al.	Aug 2012	A1
20120278388	Kleinbart et al.	Nov 2012	A1
20120284290	Keebler et al.	Nov 2012	A1
20120284638	Cutler et al.	Nov 2012	A1
20120287020	Utsuki et al.	Nov 2012	A1
20120290531	Kallakuri et al.	Nov 2012	A1
20120290935	Ihara et al.	Nov 2012	A1
20120290951	Utsuki et al.	Nov 2012	A1
20120296946	Goto	Nov 2012	A1
20120297341	Glazer et al.	Nov 2012	A1
20120311060	Beck et al.	Dec 2012	A1
20120311492	Omholt et al.	Dec 2012	A1
20120317239	Mulder et al.	Dec 2012	A1
20120331108	Ferdowsi et al.	Dec 2012	A1
20130013560	Goldberg et al.	Jan 2013	A1
20130014023	Lee et al.	Jan 2013	A1
20130024788	Olsen et al.	Jan 2013	A1
20130031147	Ghods et al.	Jan 2013	A1
20130054613	Bishop	Feb 2013	A1
20130073971	Huang et al.	Mar 2013	A1
20130074191	Ben-Reuven	Mar 2013	A1
20130080919	Kiang et al.	Mar 2013	A1
20130086506	Molander et al.	Apr 2013	A1
20130091440	Kotler et al.	Apr 2013	A1
20130110641	Ormont et al.	May 2013	A1
20130117060	Henriksen	May 2013	A1
20130117376	Filman et al.	May 2013	A1
20130124638	Barreto et al.	May 2013	A1
20130132814	Mangini et al.	May 2013	A1
20130138506	Zhu et al.	May 2013	A1
20130138608	Smith	May 2013	A1
20130138723	Ku et al.	May 2013	A1
20130173798	Micucci et al.	Jul 2013	A1
20130179799	Savage	Jul 2013	A1
20130191339	Haden et al.	Jul 2013	A1
20130198600	Lockhart et al.	Aug 2013	A1
20130205251	Cisler et al.	Aug 2013	A1
20130212112	Blom et al.	Aug 2013	A1
20130218596	Gome et al.	Aug 2013	A1
20130218829	Martinez	Aug 2013	A1
20130227015	Mihara et al.	Aug 2013	A1
20130246901	Massand	Sep 2013	A1
20130254699	Bashir et al.	Sep 2013	A1
20130262210	Savage et al.	Oct 2013	A1
20130268895	Yamaki et al.	Oct 2013	A1
20130275398	Dorman et al.	Oct 2013	A1
20130275429	York et al.	Oct 2013	A1
20130275509	Micucci et al.	Oct 2013	A1
20130297317	Lee et al.	Nov 2013	A1
20130297680	Smith et al.	Nov 2013	A1
20130297700	Hayton et al.	Nov 2013	A1
20130305165	Zuber et al.	Nov 2013	A1
20130311557	Motes et al.	Nov 2013	A1
20130346394	Ludvigsen et al.	Dec 2013	A1
20140006784	Walker et al.	Jan 2014	A1
20140012836	Bercovici et al.	Jan 2014	A1
20140013246	Beechuk et al.	Jan 2014	A1
20140025509	Reisz et al.	Jan 2014	A1
20140029751	Swineford et al.	Jan 2014	A1
20140047560	Meyer et al.	Feb 2014	A1
20140067934	Ware et al.	Mar 2014	A1
20140068401	Kirigin	Mar 2014	A1
20140082073	Wable et al.	Mar 2014	A1
20140082101	Wable et al.	Mar 2014	A1
20140089406	Gniffke et al.	Mar 2014	A1
20140108085	Henriksen	Apr 2014	A1
20140132702	Leibovich et al.	May 2014	A1
20140133632	Wakai et al.	May 2014	A1
20140136989	Choi et al.	May 2014	A1
20140156416	Goenka et al.	Jun 2014	A1
20140156806	Karpistsenko et al.	Jun 2014	A1
20140164535	Lynch et al.	Jun 2014	A1
20140165006	Chaudhri et al.	Jun 2014	A1
20140172925	Goldbrenner et al.	Jun 2014	A1
20140172997	Chan et al.	Jun 2014	A1
20140181013	Micucci et al.	Jun 2014	A1
20140181213	Hunter et al.	Jun 2014	A1
20140181697	Kirigin	Jun 2014	A1
20140188790	Hunter et al.	Jul 2014	A1
20140189818	Meyer	Jul 2014	A1
20140195885	Thiruvidam et al.	Jul 2014	A1
20140200944	Henriksen	Jul 2014	A1
20140201126	Zadeh et al.	Jul 2014	A1
20140208220	Watal	Jul 2014	A1
20140210756	Lee et al.	Jul 2014	A1
20140215551	Allain et al.	Jul 2014	A1
20140215568	Kirigin et al.	Jul 2014	A1
20140222701	Loh et al.	Aug 2014	A1
20140222917	Poirier	Aug 2014	A1
20140229839	Lynch et al.	Aug 2014	A1
20140237464	Waterman et al.	Aug 2014	A1
20140280602	Quatrano	Sep 2014	A1
20140281870	Vogel et al.	Sep 2014	A1
20140282188	Hathaway et al.	Sep 2014	A1
20140282222	Eim et al.	Sep 2014	A1
20140289351	Chen et al.	Sep 2014	A1
20140289360	Mahkovec et al.	Sep 2014	A1
20140289645	Megiddo et al.	Sep 2014	A1
20140289658	Gelernter et al.	Sep 2014	A1
20140294167	Kim et al.	Oct 2014	A1
20140297759	Mody	Oct 2014	A1
20140298207	Ittah et al.	Oct 2014	A1
20140304618	Carriero et al.	Oct 2014	A1
20140304836	Velamoor et al.	Oct 2014	A1
20140316898	Russell et al.	Oct 2014	A1
20140317544	Wang	Oct 2014	A1
20140325016	Chen et al.	Oct 2014	A1
20140330776	Chen	Nov 2014	A1
20140344739	Yoon	Nov 2014	A1
20140359023	Homsany	Dec 2014	A1
20140359085	Chen	Dec 2014	A1
20140359465	Litan et al.	Dec 2014	A1
20140365263	Honeyman et al.	Dec 2014	A1
20140365432	Jain et al.	Dec 2014	A1
20140372539	Zaveri	Dec 2014	A1
20140372923	Rossi et al.	Dec 2014	A1
20140378063	Nathwani et al.	Dec 2014	A1
20140379647	Smith et al.	Dec 2014	A1
20140380232	Sarnoff et al.	Dec 2014	A1
20150006596	Fukui et al.	Jan 2015	A1
20150019480	Maquaire et al.	Jan 2015	A1
20150019654	Wheeler et al.	Jan 2015	A1
20150026260	Worthley et al.	Jan 2015	A1
20150026604	Mulukuri et al.	Jan 2015	A1
20150032692	Litzenberger	Jan 2015	A1
20150032829	Barshow et al.	Jan 2015	A1
20150033305	Shear et al.	Jan 2015	A1
20150058751	Tseng	Feb 2015	A1
20150074044	Metreveli et al.	Mar 2015	A1
20150074520	Muto et al.	Mar 2015	A1
20150082224	Hathaway et al.	Mar 2015	A1
20150095799	Tsao	Apr 2015	A1
20150100889	Tuchman et al.	Apr 2015	A1
20150120835	Schroeder	Apr 2015	A1
20150120859	Kondo et al.	Apr 2015	A1
20150127628	Rathod et al.	May 2015	A1
20150134751	Meyers, Jr. et al.	May 2015	A1
20150134808	Fushman et al.	May 2015	A1
20150135097	Carriero et al.	May 2015	A1
20150135300	Ford	May 2015	A1
20150148093	Huang et al.	May 2015	A1
20150149177	Kalns et al.	May 2015	A1
20150149929	Shepherd et al.	May 2015	A1
20150156274	Alten et al.	Jun 2015	A1
20150169566	Yang et al.	Jun 2015	A1
20150186538	Yan et al.	Jul 2015	A1
20150188960	Alhaidar et al.	Jul 2015	A1
20150200885	Sharp et al.	Jul 2015	A1
20150200945	Edson et al.	Jul 2015	A1
20150213037	Baldwin et al.	Jul 2015	A1
20150213397	Arena	Jul 2015	A1
20150286371	Degani et al.	Oct 2015	A1
20150288775	Larabie-Belanger	Oct 2015	A1
20150304265	Vincent et al.	Oct 2015	A1
20150341399	Lee	Nov 2015	A1
20150358303	Hui et al.	Dec 2015	A1
20150379455	Munzer	Dec 2015	A1
20160028796	Garcia et al.	Jan 2016	A1
20160034844	Kofman	Feb 2016	A1
20160085421	Feeney	Mar 2016	A1
20160094495	Ahuja et al.	Mar 2016	A1
20160127452	Newman et al.	May 2016	A1
20160140139	Torres et al.	May 2016	A1
20160179754	Borza et al.	Jun 2016	A1
20160247245	Baic et al.	Aug 2016	A1
20160259508	Eccleston et al.	Sep 2016	A1
20160277537	Liang et al.	Sep 2016	A1
20160283085	Beausoleil et al.	Sep 2016	A1
20160283502	Beausoleil et al.	Sep 2016	A1
20160283567	Beausoleil et al.	Sep 2016	A1
20160285702	Beausoleil et al.	Sep 2016	A1
20160285795	Beausoleil et al.	Sep 2016	A1
20160285796	Beausoleil et al.	Sep 2016	A1
20160285797	Beausoleil et al.	Sep 2016	A1
20160285817	Beausoleil et al.	Sep 2016	A1
20160285818	Beausoleil et al.	Sep 2016	A1
20160285890	Beausoleil et al.	Sep 2016	A1
20160314473	Engles et al.	Oct 2016	A1
20160371395	Dumant et al.	Dec 2016	A1
20170006102	Mody et al.	Jan 2017	A1
20170046531	Roberts	Feb 2017	A1
20170104743	Larabie-Belanger	Apr 2017	A1
20170139557	Heo et al.	May 2017	A1
20170192656	Pedrick et al.	Jul 2017	A1
20170220605	Nivala et al.	Aug 2017	A1
20170220657	Nivala et al.	Aug 2017	A1
20170249070	Chen et al.	Aug 2017	A1
20170269805	DeMaris et al.	Sep 2017	A1
20170285928	Beausoleil et al.	Oct 2017	A1
20170371891	Yazganarikan	Dec 2017	A1
20180143975	Casal et al.	May 2018	A1
20180189735	Lo et al.	Jul 2018	A1

Foreign Referenced Citations (70)

Number	Date	Country
2016201019	Oct 2016	AU
2016201472	Oct 2016	AU
2016201472	Dec 2016	AU
2017201395	Mar 2017	AU
2016201019	Apr 2017	AU
2017204625	Jul 2017	AU
2016235983	Oct 2017	AU
2016236015	Oct 2017	AU
2016235985	Jun 2018	AU
2016235984	Oct 2018	AU
1527226	Sep 2004	CN
101689188	Mar 2010	CN
102224497	Oct 2011	CN
102375858	Mar 2012	CN
103282937	Sep 2013	CN
107431631	Dec 2017	CN
107438840	Dec 2017	CN
2884408	Jun 2015	EP
3073674	Sep 2016	EP
3251290	Dec 2017	EP
3251305	Dec 2017	EP
3251288	Sep 2019	EP
3073673	Jul 2020	EP
3251289	Sep 2020	EP
S61279916	Dec 1986	JP
2000060803	Feb 2000	JP
2000105731	Apr 2000	JP
2001202405	Jul 2001	JP
2001229282	Aug 2001	JP
2002244988	Aug 2002	JP
2002297883	Oct 2002	JP
2003108503	Apr 2003	JP
2003256323	Sep 2003	JP
2003316629	Nov 2003	JP
2004013267	Jan 2004	JP
2004046796	Feb 2004	JP
2004355417	Dec 2004	JP
2004362118	Dec 2004	JP
2005346704	Dec 2005	JP
2006092074	Apr 2006	JP
2006155550	Jun 2006	JP
2006189958	Jul 2006	JP
2007072523	Mar 2007	JP
2007323561	Dec 2007	JP
2009069899	Apr 2009	JP
2010079889	Apr 2010	JP
2013161481	Aug 2013	JP
2013175059	Sep 2013	JP
2014134961	Jul 2014	JP
2014164717	Sep 2014	JP
2015032092	Feb 2015	JP
2015056096	Mar 2015	JP
2016099894	May 2016	JP
6028118	Oct 2016	JP
2016181250	Oct 2016	JP
2016184404	Oct 2016	JP
2017084356	May 2017	JP
2017182790	Oct 2017	JP
WO-2007058207	May 2007	WO
WO-2010102296	Sep 2010	WO
2011098749	Aug 2011	WO
WO-2013033144	Mar 2013	WO
WO-2014200634	Dec 2014	WO
WO-2015080798	Jun 2015	WO
WO-2016085822	Jun 2016	WO
WO-2016153676	Sep 2016	WO
WO-2016153735	Sep 2016	WO
WO-2016153736	Sep 2016	WO
WO-2016153737	Sep 2016	WO
WO-2016168748	Oct 2016	WO

Non-Patent Literature Citations (166)

Entry
Non-Final Office Action from U.S. Appl. No. 17/360,738, dated Jun. 9, 2023, 17 pages.
Advisory Action from U.S. Appl. No. 15/055,566, dated Jan. 24, 2022, 3 pages.
Advisory Action from U.S. Appl. No. 15/055,566, dated Nov. 23, 2020, 4 pages.
Advisory Action from U.S. Appl. No. 14/725,982, dated Apr. 23, 2020, 5 pages.
Advisory Action from U.S. Appl. No. 15/624,615, dated Aug. 28, 2019, 2 pages.
Advisory Action from U.S. Appl. No. 15/859,028, dated Feb. 3, 2021, 4 pages.
Advisory Action from U.S. Appl. No. 15/859,028, dated Jun. 25, 2020, 3 pages.
Advisory Action from U.S. Appl. No. 16/911,926, dated Aug. 24, 2021, 3 pages.
Anzures-Garcia M., et al., “Service-Based Layered Architectural Model for Building Collaborative Applications in Heterogeneous Environments”, IEEE, 2009, 12 pages.
Bachpalle S.D., et al., “Data Security Approach for Online Social Network”, IEEE, Jul. 8, 2014, 6 pages.
Beliz System, “Making Documents on Google Drive,” Digital Documents Laboratories, Jul. 18, 2014, Retrieved from: https://watasu.com/dedoken/cloud/page2.html , 9 pages.
Board Opinion for Chinese Application No. 201680013779.8 dated Aug. 19, 2020, 10 pages.
Brady T., et al., “Creating Value by Delivering Integrated Solutions,” 2005, International Journal of Project Management, pp. 360-365.
Brief Communication of Oral Proceedings for European Application No. 17804403.8, dated May 11, 2021, 10 pages.
Chronaki C.E., et al., “WebOnCOLL: Medical Collaboration in Regional Healthcare Networks,” IEEE, Dec. 1997, vol. 1 (4), 13 pages.
Communication pursuant to Article 94(3) EPC for European Application No. 16720200.1 dated Sep. 30, 2019, 5 pages.
Communication Pursuant to Rules 161(1) and 162 EPC for European Application No. 17804403.8 dated Aug. 6, 2019, 3 pages.
Communication under Rule 71(3) EPC for European Application No. 16711411.5 dated Oct. 18, 2019, 7 pages.
Communication pursuant to Article 94(3) EPC for EP Application No. 19195083.1, dated Mar. 31, 2021, 6 pages.
Communication Pursuant to Article 94(3) EPC for European Application No. 17804403.8 dated May 7, 2020, 7 pages.
Communication Pursuant to Article 94(3) EPC for European Application No. 17805064.7 dated Nov. 5, 2019, 4 pages.
Communication Pursuant to Article 94(3) EPC for European Application No. 18766090.7 dated Aug. 30, 2021, 7 pages.
Communication Pursuant to Article 94(3) EPC for European Application No. 19195083.1 dated Jun. 7, 2022, 4 pages.
Communication Pursuant to Article 94(3) EPC for European Application No. 20167778.8 dated Jul. 29, 2021, 9 pages.
Communication Pursuant to Article 94(3) for EP Application No. 19182606.4 dated Mar. 16, 2021, 7 pages.
Communication under Rule 71(3) EPC for European Application No. 16711412.3 dated Nov. 13, 2019, 7 pages.
Communication under Rule 71 (3) EPC of intention to grant for European Application No. 20167778.8 dated Dec. 19, 2022, 79 pages.
Communication under Rule 71(3) EPC for European Application No. 16161853.3 dated Feb. 4, 2020, 7 pages.
Communication under rule 71(3) EPC Intention to Grant for European Application No. 16711412.3 dated Mar. 27, 2020, 7 pages.
Communication under Rule 71(3) EPC of Intention to Grant for European Application No. 16720200.1 dated Jun. 12, 2020, 136 pages.
Communication under Rule 71(3) EPC of Intention to Grant for European Application No. 16720200.1 dated Sep. 4, 2020, 70 pages.
Corrected Notice of Allowability for U.S. Appl. No. 15/624,615 dated Feb. 6, 2020, 2 pages.
Crucial Works Inc, “Sharing Folders,” Apps x Support, Jan. 29, 2013, Retrieved from: https://web.archive.org/web/20130129101828/ http://www.appsupport.jp/drive/share-folder on Aug. 29, 2017, 8 pages.
Decision to Refuse European Patent Application No. 17804403.8 dated Jul. 1, 2021, 12 pages.
Decision to Refuse European Patent Application No. 17805064.7 dated Feb. 12, 2021, 32 pages.
Examination Report No. 1, for Australian Application No. 2017385025, dated Nov. 28, 2019, 5 pages.
Examination Report No. 1, for Australian Application No. 2017385026, dated Nov. 28, 2019, 6 pages.
Examination Report No. 1, for Australian Application No. 2018397276, dated Sep. 9, 2020, 4 pages.
Examination Report No. 2, for Australian Application No. 2017385025, dated Apr. 30, 2020, 5 pages.
Examination Report No. 2, for Australian Application No. 2017385026, dated Apr. 30, 2020, 5 pages.
Examination Report No. 2, for Australian Application No. 2018397276, dated Jan. 7, 2021, 4 pages.
Examination Report No. 3, for Australian Application No. 2017385025, dated Aug. 4, 2020, 5 pages.
Examination Report No. 3, for Australian Application No. 2017385026, dated Aug. 4, 2020, 6 pages.
Examination Report No. 4, for Australian Application No. 2017385025, dated Nov. 2, 2020, 4 pages.
Examination Report No. 4, for Australian Application No. 2017385026, dated Nov. 20, 2020, 5 pages.
Extended European Search Report for Application No. 19195083.1 dated Oct. 31, 2019, 8 pages.
Extended European Search Report for EP Application No. 16161853.3 dated Aug. 18, 2016, 3 pages.
Extended European Search Report for EP Application No. 16161962.2 dated Aug. 24, 2016, 3 pages.
Extended European Search Report for EP Application No. 19182606.4 dated Aug. 8, 2019, 9 pages.
Extended European Search Report for European Application No. 20167778.8 dated Jul. 7, 2020, 10 pages.
Extended European Search Report for European Application No. 21160648.8 dated Jun. 17, 2021, 12 pages.
Extended European Search Report for European Application No. 21196029.9 dated Dec. 14, 2021, 9 pages.
Final Office Action for U.S. Appl. No. 14/725,958 dated Feb. 5, 2020, 26 pages.
Final Office Action from U.S. Appl. No. 16/911,926, dated Jun. 14, 2022, 16 pages.
Final Office Action from U.S. Appl. No. 14/725,982, dated Feb. 19, 2020, 16 pages.
Final Office Action from U.S. Appl. No. 15/055,566, dated Oct. 13, 2021, 24 pages.
Final Office Action from U.S. Appl. No. 15/055,566, dated Sep. 29, 2020, 27 pages.
Final Office Action from U.S. Appl. No. 15/476,688, dated Apr. 16, 2020, 25 pages.
Final Office Action from U.S. Appl. No. 15/476,755, dated Apr. 16, 2020, 29 pages.
Final Office Action from U.S. Appl. No. 15/859,028, dated Apr. 15, 2020, 21 pages.
Final Office Action from U.S. Appl. No. 15/859,028, dated Nov. 27, 2020, 24 pages.
First Examination Report for Australian Application No. 2020277236 dated Feb. 10, 2022, 3 pages.
Freedman V., et al., “A Collaborative Extensible User Environment for Simulation and Knowledge Management,” IEEE, 2015, pp. 280-286.
Froese T., “The impact of emerging information technology on project management for construction,” Automation in Construction, 2010, vol. 19(5), pp. 531-538.
Google Inc., “View and Create Documents on Android,” Mar. 19, 2015, Wayback Machine, Google Docs, downloaded from https://web.archive.org/web/20150319022434/ https://support.google.com/docs/answer/3420399?hl=en , May 30, 2016, 3 pages.
Hoomey, Estyle Inc., “Google Drive How to Use Leverage Surgery “Spreadsheet” that can be Used in Excel Instead!,” Nov. 9, 2013, retrieved from https://web.archive.org/web/20131109104805/ http:/1hoomey.net/googledrive-study-4 on Jun. 30, 2016, 18 pages.
Hoomey, Estyle Inc., “How to Use Google Drive's ‘Spread Sheet’ that is Usable instead of Excel,” Nov. 9, 2013, retrieved from https://web.archieve.org/web/20131109104805/ http://hoomey.net/googledrive-study-4 , on Sep. 15, 2017, 9 pages.
Intention to Grant for European Application No. 191 82606.4 dated Dec. 6, 2022, 77 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US16/19052, dated Oct. 5, 2017, 7 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US16/20117, dated Oct. 5, 2017, 8 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US16/20124, dated Oct. 5, 2017, 8 pages.
International Preliminary Report on Patentability for PCT Application No. PCT/US16/20132, dated Oct. 5, 2017, 8 pages.
International Search Report & Written Opinion for Application No. PCT/US2018/04780 dated Oct. 15, 2018, 16 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US16/19052, dated Nov. 7, 2016, 9 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US16/20117, dated May 13, 2016, 10 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US16/20124, dated May 24, 2016, 10 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US16/20132, dated May 24, 2016, 9 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2017/061204 dated Dec. 21, 2017, 9 pages.
International Search Report and Written Opinion for PCT Application No. PCT/US2017/061206 dated Jan. 3, 2018, 11 pages.
“Intralinks VIA,” 2015, Retrieved from https://www.intralinks.com/sites/default/files/file_attach/intralinks_via_brochure.pdf , 13 pages.
Iwashi, “How to Use Google Documents,” Wind-Mill Iwashi Blog, Dec. 17, 2014, retrieved from http://wind-mill.co.jp/iwashiblog/2014/12/google-document/ , Mar. 27, 2019, 12 pages.
Kaizu T., “Customize Explorer's New Menu on Window,” Tech Tips, published on Apr. 4, 2003, 14 pages.
Kappes G., et al., “Virtualization-Aware Access Control for Multitenant Filesystems,” MSST, Jun. 2-6, 2014, pp. 1-6.
Mislove A., et al., “POST: A Secure, Resilient, Cooperative Messaging System,” Conference: Proceedings of HotOS'03: 9th Workshop on Hot Topics in Operating Systems, Lihue (Kauai), Hawaii, USA, May 18-21, 2003, 6 pages.
Non-Final Office Action from U.S. Appl. No. 14/725,942, dated Sep. 27, 2019, 26 pages.
Non-Final Office Action from U.S. Appl. No. 14/725,958, dated Sep. 27, 2019, 25 pages.
Non-Final Office Action from U.S. Appl. No. 14/725,982, dated Sep. 20, 2019, 13 pages.
Non-Final Office Action from U.S. Appl. No. 15/055,566, dated Jul. 8, 2022, 23 pages.
Non-Final Office Action from U.S. Appl. No. 15/055,566, dated Mar. 5, 2020, 25 pages.
Non-Final Office Action from U.S. Appl. No. 15/055,566, dated Mar. 31, 2021, 32 pages.
Non-Final Office Action from U.S. Appl. No. 15/476,688, dated Nov. 18, 2019, 23 pages.
Non-Final Office Action from U.S. Appl. No. 15/476,715, dated Oct. 4, 2019, 25 pages.
Non-Final Office Action from U.S. Appl. No. 15/476,755, dated Nov. 29, 2019, 23 pages.
Non-Final Office Action from U.S. Appl. No. 15/624,615, dated Oct. 2, 2019, 12 pages.
Non-Final Office Action from U.S. Appl. No. 15/859,028, dated Jan. 3, 2020, 20 pages.
Non-Final Office Action from U.S. Appl. No. 15/859,028, dated Jul. 30, 2020, 23 pages.
Non-Final Office Action from U.S. Appl. No. 16/525,811, dated Aug. 20, 2020, 7 pages.
Non-Final Office Action from U.S. Appl. No. 16/858, 120, dated Oct. 6, 2020, 8 pages.
Non-Final Office Action from U.S. Appl. No. 16/911,926, dated Dec. 21, 2022, 16 pages.
Non-Final Office Action from U.S. Appl. No. 16/911,926, dated Nov. 29, 2021, 16 pages.
Non-Final Office Action from U.S. Appl. No. 17/220,369, dated Sep. 16, 2021, 11 pages.
Non-Final Office Action from U.S. Appl. No. 17/302,370, dated Sep. 2, 2022, 7 pages.
Non-Final Office Action from U.S. Appl. No. 17/805,361, dated Nov. 18, 2022, 14 pages.
Notice of Reasons for Refusal for Japanese Application No. 2018-190286 dated Oct. 4, 2019, 5 pages.
Notice of Acceptance for Australian Application No. 2018397276 dated Jun. 28, 2021, 3 pages.
Notice of Allowance from U.S. Appl. No. 14/725,905, dated Oct. 2, 2019, 15 pages.
Notice of Allowance from U.S. Appl. No. 14/725,942, dated Mar. 10, 2021, 6 pages.
Notice of Allowance from U.S. Appl. No. 14/725,942, dated Sep. 16, 2020, 5 pages.
Notice of Allowance from U.S. Appl. No. 14/725,958, dated Mar. 10, 2021, 6 pages.
Notice of Allowance from U.S. Appl. No. 14/725,958, dated Sep. 17, 2020, 12 pages.
Notice of Allowance from U.S. Appl. No. 14/725,982, dated Mar. 7, 2022, 6 pages.
Notice of Allowance from U.S. Appl. No. 14/725,982, dated Mar. 25, 2022, 3 pages.
Notice of Allowance from U.S. Appl. No. 14/726, 103, dated Sep. 16, 2019, 2 pages.
Notice of Allowance from U.S. Appl. No. 15/476,688, dated Apr. 30, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,715, dated Aug. 6, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,715, dated May 13, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,742, dated Aug. 21, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,742, dated Feb. 8, 2021, 10 pages.
Notice of Allowance from U.S. Appl. No. 15/476,742, dated Jul. 1, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,742, dated Mar. 3, 2021, 3 pages.
Notice of Allowance from U.S. Appl. No. 15/476,755, dated Feb. 10, 2021, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,755, dated Mar. 8, 2021, 3 pages.
Notice of Allowance from U.S. Appl. No. 15/476,755, dated May 20, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/476,755, dated Sep. 3, 2020, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/624,615, dated Dec. 30, 2019, 9 pages.
Notice of Allowance from U.S. Appl. No. 15/859,028, dated Apr. 6, 2021, 11 pages.
Notice of Allowance from U.S. Appl. No. 15/859,028, dated Sep. 10, 2021, 12 pages.
Notice of Allowance from U.S. Appl. No. 16/525,811, dated Feb. 26, 2021, 10 pages.
Notice of Allowance from U.S. Appl. No. 16/858, 120, dated Jan. 22, 2021, 10 pages.
Notice of Allowance from U.S. Appl. No. 17/220,369, dated Mar. 25, 2022, 11 pages.
Notice of Allowance from U.S. Appl. No. 15/055,566, dated Nov. 18, 2022, 17 pages.
Notice of Allowance from U.S. Appl. No. 15/395,220, dated May 20, 2019, 7 pages.
Notice of Allowance from U.S. Appl. No. 17/302,370, dated Jan. 25, 2023, 9 pages.
Notice of Allowance from U.S. Appl. No. 14/725,905, dated Jan. 10, 2020, 2 pages.
Notice of Reasons for Refusal for Japanese Application No. 2018-190286 dated Feb. 26, 2021, 7 pages.
Notice of Reasons for Refusal for Japanese Application No. 2018-190286 dated Jun. 29, 2020, 8 pages.
Notice of Reasons for Refusal for Japanese Application No. 2019-508896 dated Jan. 5, 2021, 21 pages.
Notice of Reasons for Refusal for Japanese Application No. 2019-508896 dated May 8, 2020, 24 pages.
Notice of Reasons for Refusal for Japanese Application No. 2020-523702 dated Jun. 25, 2021, 12 pages.
Notification of the First Office Action and Search Report for Chinese Application No. 201680013771.1 dated Dec. 4, 2019, 12 pages.
Notification of Reason(s) for Refusal for Japanese Application No. 2019-508895 dated Aug. 21, 2020, 7 pages.
Office Action for Australian Application No. 2016235984 dated Mar. 22, 2018, 3 pages.
Office Action for Japanese Application No. 2017-544960 dated Mar. 16, 2018, 10 pages. (English Translation only).
Office Action for U.S. Appl. No. 14/725,942 dated Feb. 5, 2020, 25 pages.
Office Action for U.S. Appl. No. 15/476,742 dated Feb. 5, 2020, 23 pages.
Opposition—Decision Issued for Australian Application No. 2017385025, dated Jun. 30, 2021, 10 pages.
Pundir A K.,“Towards a Complexity Framework for Managing Projects,” Dec. 31, 2007, 7 pages.
Shimada H., “Online Storage Service Having Documents-Editing Functions: Introduction to Google Drive for a Person that Missed the Wave,” ITmedia Inc., Feb. 7, 2014, retrieved from internet URL: https://web.archive.org/web/20140207083317/ and https://www.atmarkit.co.jp/ait/articles/1303/13/news105.html , on May 27, 2016, 21 pages.
Shultz G., “Take Control of Your Windows 7 Open With Menus.” Jan. 12, 2012, TechRepublic, https://www.techrepublic.com/blog/windows-and-office/take-control-of-your-windows-7-open-with-menus/ , 11 pages.
Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 17805064.7 dated Apr. 21, 2020, 9 pages.
Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 18766090.7, dated Dec. 22, 2022, 11 pages.
Technology for Teachers and Students, “Microsoft OneDrive and SkyDrive Tutorial,” retrieved from https://www.youtube.com/watch?v=RZoYvmi9L9E , Feb. 2, 2014, 1 page.
Voida S., et al., “Share and Share Alike: Exploring the User Interface Affordances of File Sharing,” Proceedings of the ACM Conference on Human Factors in Computing Systems (CHI 2006), Apr. 22-27, 2006, ACM, 10 pages.
White C., “5 Unusual Ways to Use Dropbox You Might Not Have Thought of,” Dec. 18, 2010, retrieved from http://mashable.com/2010/12/18/dropbox-uses/ , on Sep. 15, 2017, 3 pages.
Wikihow, “How to Use Facebook,” 2013, retrieved from http://www.wikihow.com/Use-Facebook , on Sep. 15, 2017, 8 pages.
Wikihow, “How to Use Facebook(With Cheat Sheet)”, 2013, retrieved from http://www.wikihow.com/Use-Facebook on Mar. 28, 2019, 7 pages.
Yoshida H., “Word 2007 & Excel 2007 Masterbook,” Japan, Daily Communication, May 30, 2009, first edition, 3 pages.
Communication under Rule 71 (3) EPC of Intention to Grant for European Application No. 19195083.1 dated Mar. 23, 2023, 72 pages.
Result of Consultation for European Application No. 18766090.7 dated Apr. 28, 2023, 15 pages.
Notice of Allowance from U.S. Appl. No. 17/805,361, dated May 24, 2023, 12 pages.
Wang F., et al., “Web-based Collaborative Information Integration for Scientific Research,” IEEE 23rd International Conference on Data Engineering, 2007, pp. 1232-1241.
Notice of Allowance from U.S. Appl. No. 17/302,370, dated Jul. 26, 2023, 8 pages.
Notice of Allowance from U.S. Appl. No. 17/302,370, dated Nov. 21, 2023, 9 pages.
Non-Final Office Action from U.S. Appl. No. 16/911,926, dated Aug. 24, 2023, 16 pages.
Notice of Reasons for Refusal for Japanese Application No. 2022-118838 dated Sep. 25, 2023, 8 pages.
Notification of the First Office Action and Search Report for Chinese Application No. 202110775690.8 dated Jan. 30, 2024, 20 pages.

Related Publications (1)

	Number	Date	Country
	20230222448 A1	Jul 2023	US

Continuations (3)

	Number	Date	Country
Parent	17302370	Apr 2021	US
Child	18188257		US
Parent	16525811	Jul 2019	US
Child	17302370		US
Parent	15395220	Dec 2016	US
Child	16525811		US

Managing projects in a content management system

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Disclaimer

Term Extension

Abstract