COLLABORATION SESSIONS IN A WORKSPACE ON A CLOUD-BASED CONTENT MANAGEMENT SYSTEM

BACKGROUND

Online social networking sites are intended to provide a convenient way for members of the social networking service to interact and build social relationships. Often, a social networking site will provide an area for a social networking member to create a personal profile as well as an area for friends and other social networking members to leave comments for the owner of the profile. Each member can maintain his own profile and comments area and decide who can view the profile and leave comments.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of a web-based content management system with a collaboration environment that provides discussion workspaces linked to workspaces containing work items are illustrated in the figures. The examples and figures are illustrative rather than limiting.

FIG. 1 illustrates an example diagram of a system where a host server supports discussion workspaces linked to folders or workspaces in an online collaboration environment.

FIG. 2 depicts an example diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting for organizing work items and workspaces.

FIG. 3 depicts a block diagram illustrating an example of components in the host server of a web-based collaboration environment that provides discussion workspaces.

FIG. 4 depicts a screenshot of an example user interface that shows a tab for accessing a discussion workspace.

FIG. 5 depicts a screenshot of an example user interface that shows a field for entering a topic in a discussion workspace.

FIG. 6 depicts a screenshot of an example user interface that shows a comment field in a discussion workspace.

FIG. 7 depicts a screenshot of an example user interface that shows a comment field for responding to a comment in a discussion workspace.

FIG. 8 depicts a screenshot showing an example user interface for engaging in discussions on work items with collaborators in an online or web-based collaboration environment.

FIGS. 9A and 9B depict a flow diagram illustrating an example process of providing a discussion workspace linked to a workspace containing work items.

FIG. 10 depicts a flow diagram illustrating an example process of providing a discussion workspace linked to a workspace within a workspace.

FIG. 11 shows a screenshot of an example user interface showing an event stream in a discussion workspace.

FIG. 12 shows a screenshot of another example user interface showing an event stream in a discussion workspace.

FIG. 13 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

FIG. 14 shows an example of a folder-file hierarchy layout of folder/workspaces and their associated discussion workspaces.

DETAILED DESCRIPTION

A system is described for generating a discussion workspace in a web-based content management system with a collaboration environment, where the discussion workspace is linked to a workspace or folder that contains work items. Collaborators with permissions to participate in the discussion workspace can start a topic of online discussion and/or leave comments for other collaborators of the workspace.

Various aspects and examples of the invention will now be described. The following description provides specific details for a thorough understanding and enabling description of these examples. One skilled in the art will understand, however, that the invention may be practiced without many of these details. Additionally, some well-known structures or functions may not be shown or described in detail, so as to avoid unnecessarily obscuring the relevant description.

The terminology used in the description presented below is intended to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific examples of the technology. Certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.

FIG. 1 illustrates an example diagram of a system where a host server 100 supports discussion workspaces linked to folders or workspaces containing work items in a content management system with an online collaboration environment for users 108 associated with the respective workspaces. The content management system can generally be a cloud-based service.

The client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100. Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between or among the devices 102 and/or the host server 100.

For example, the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g. an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc. In one embodiment, the client devices 102 and host server 100 are coupled via a network 106. In some embodiments, the devices 102 and host server 100 may be directly connected to one another.

The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.

Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used in the disclosed technology by various users or collaborators (e.g., collaborators 108) for accessing, through network 106, a web-based content management system with a collaboration environment or online collaboration platform (e.g., hosted by the host server 100).

The collaboration platform or environment hosts workspaces with work items stored in the data repository 130 that one or more users can access (e.g., view, edit, update, revise, comment, add to discussions, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., device 102). The digital content can include .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc.

The data repository 130 is a database that can be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc. The data repository 130 can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.

A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. In general, the content management system permits a user to group stored files in a hierarchical manner, such that a workspace made up of a group of files can be contained within another workspace, such as a folder. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example. The workspace can also include an online discussion area for collaborators to engage in an online discussion.

In general, a workspace can be associated with a set of users or collaborators (e.g., collaborators 108) which have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users. Each user may have their own set of access rights to every piece of content in the workspace, or each user may have different access rights to different pieces of content. Access rights may be specified by a user associated with a work space and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.

In general, the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such that each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a work space for other users to access (e.g., for viewing, editing, commenting, discussing, signing-off, or otherwise manipulating). The user can log in to the online platform and upload the document (or any other type of work item) to an existing work space or to a new work space. The document can be shared with existing users or collaborators in a work space.

A diagrammatic illustration of the online collaboration environment and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of FIG. 2.

In one embodiment, discussions among collaborators of a workspace or folder can be linked to the particular workspace or folder, and collaborators can create topics for discussion and comment on those topics.

Functions and techniques disclosed for implementing discussions in the online platform linked to a work space can be performed by the host server 100 of the collaboration platform. Functions and techniques performed by the host server 100 and the related components therein are described, respectively, in detail with further reference to the example of FIG. 3.

In one embodiment, client devices 102 communicate with the host server 100 over network 106. In general, network 106, over which the client devices 102 and the host server 100 communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.

The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).

In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1×RTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.

FIG. 2 depicts an example diagram of a web-based or online collaboration platform deployed in an enterprise or other organizational setting 250 for organizing workspaces 205, 225, 245 which include work items 215, 235, 255 and for providing a discussion workspace area 217, 237, 257 linked to the respective workspaces 205, 225, 245.

The web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting.

When deployed in an organizational setting, multiple workspaces (e.g., workspace A, B C) can be created to support different projects or a variety of work flows. Each workspace can have its own associated work items. For example, work space A 205 and discussion workspace 217 can be associated with work items 215, work space B 225 and discussion workspace 237 can be associated with work items 235, and work space N 245 and discussion workspace 237 can be associated with work items 255. The work items 215, 235, and 255 may be unique to each work space but need not be. For example, a particular document can be associated with only one work space (e.g., work space A 205) or it may be associated with multiple work spaces (e.g., work space A 205 and work space B 225, etc.).

In general, each work space has a set of users or collaborators associated with it. For example, work space A 205 is associated with multiple users or collaborators 206. In some instances, work spaces deployed in an enterprise may be department specific. For example, work space B may be associated with department 210 and some users shown as example user A 208, and workspace N 245 can be associated with departments 212 and 216 and users shown as example user B 214.

Each user associated with a work space can generally access the work items associated with the work space. The level of access will depend on permissions associated with the specific work space, and/or with a specific work item. Permissions can be set for the work space or set individually on a per work item basis. For example, the creator of a work space (e.g., one of user A 208 who creates work space B) can set one permission setting applicable to all work items 235 for other associated users and/or users associated with the affiliate department 210, for example. Creator user A 208 may also set different permission settings for each work item, which may be the same for different users, or varying for different users.

In one embodiment, a first type of permission level, e.g. an editor, can allow a user to have full read and write access to a workspace such that the user can view and download contents of the workspace as well as upload new content to the workspace. A second type of permission level, e.g. a viewer, can allow a user to have full read access to a workspace such that the user can view and download contents of the workspace but not upload or edit contents of the workspace. A third type of permission level, e.g. an uploader, can allow a user to have limited write access to contents of a workspace such that the user can see items in the workspace but not download or view the items, while being permitted to upload new content to the workspace.

In one embodiment, the ability of a user associated with a workspace to contribute to a discussion workspace linked to that workspace or to invite others to join the workspace can be tied to the permission level of the user. For instance, an editor may be permitted to participate in the discussion workspace and invite other collaborators, while a viewer may only be allowed to participate in the discussion workspace, and an uploader may not be permitted to perform either action. Alternatively, separate discussion permission and/or invitation permission can be assigned by a creator or administrator of a workspace to individuals associated with the workspace. In some instances, discussion permission and/or invitation permission can be associated with the workspace or the items in the workspace or can be based upon any other criteria.

FIG. 3 shows a block diagram of an example host server 100 of a web-based collaboration environment that provides discussion workspaces linked to the workspaces in the collaboration environment.

The host server 100 of the web-based or online content management system with a collaboration environment can include, for example, a network interface 302, a discussion workspace engine 310, user interface module 320, a collaboration manager 330, a comments module 340, an activity detector 350, and an event stream module 360. The event stream module 360 can include a tracking module 365. The discussion workspace engine 310 can include a discussion workspace module 312, a discussion topic module 314, and a thread manager 316. Additional or fewer components/modules/engines can be included in the host server 100 and each illustrated component.

The network interface 302 can be a networking module that enables the host server 100 to mediate data in a network with an entity that is external to the host server 100, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 302 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, or engine can be centralized or its functionality distributed. The module, manager, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all media that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all media that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable media include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.

One embodiment of the host server 100 includes a discussion workspace engine 310 that generates the discussion workspaces that enable collaborators to conduct online discussions. Discussion workspaces are intended to facilitate discussions relating to work items contained in the linked workspaces, but discussions need not be limited in such a manner.

In one embodiment, the workspaces in the web-based content management system with collaboration environment function similarly to folders in a folder-file hierarchy system where a user places related files or work items inside a folder or workspace, and multiple files and/or folders can be placed inside another folder or workspace, resulting in a folder tree organizational structure. Most users are familiar with the concept of a folder-file hierarchy system because many personal computers use the folder-file hierarchy system for organizing files. Thus, by mapping the concept of a collaborative workspace to the common mental model of folders, the learning gap for users of the collaboration environment is easily bridged.

In one embodiment, the discussion workspace engine 310 includes a discussion workspace module 312 that creates a separate discussion workspace for each folder workspace in the web-based collaboration environment. Further, the discussion workspace module 312 links each discussion workspace with its respective folder workspace so that users of a particular workspace find it intuitive to engage in communications in the linked discussion workspace regarding the items contained in the folder workspace. However, users are not limited to discussing only items in the associated workspace.

FIG. 14 shows an example of a folder-file hierarchy layout of folder/workspaces and their associated discussion workspaces. The discussion workspaces are organized using the same folder-file hierarchy as the folder/workspaces. For example, folder/workspace A contains subfolder/workspace B and subfolder/workspace C. This hierarchy is paralleled by the discussion workspaces where discussion workspace A contains discussion workspace B and discussion workspace C. Further, folder/workspace A is associated with discussion workspace A, as shown by the dotted line connecting the two. Additionally, subfolder/workspace B is associated with discussion workspace B, and subfolder/workspace C is associated with discussion workspace C, also shown by dotted lines connecting the associated folder/workspaces and discussion workspaces. Thus, discussions relating to files A1 and A2 in folder/workspace A can take place in discussion workspace A; discussions relating to files B1 and B2 in subfolder/workspace B can take place in discussion workspace B; and discussions relating to files C1 and C2 in folder/workspace C can take place in discussion workspace C.

In one embodiment, the folder workspaces in the web-based collaboration environment and the linked discussion workspaces created by the discussion workspace module 312 can be presented to a user by the user interface module 320 as neighboring tabs on a web-browser screen. An example is shown in FIG. 4 where the contents of the folder entitled ‘Company Community Files’ is shown under the ‘files and folders’ tab 410, and next to the ‘files and folders’ tab 410 is the ‘discussions’ tab 412 that provides access to the linked discussion workspace. The user interface module 320 presents the comments submitted by collaborators of the workspace in the discussion area, and discussion topics submitted by collaborators can be used by collaborators to organize the displayed comments.

In one embodiment, discussions that take place in a discussion workplace that is linked to a child folder in the collaboration environment are also visible in the discussion workplace linked to the parent folder. So in the example layout shown in FIG. 14, discussions in discussion workspace B relating to files B1 and B2 in child folder/workspace B and in discussion workspace C relating to files C1 and C2 in child folder/workspace C are also shown in the parent discussion workspace A.

In one embodiment, the discussion workspace engine 310 includes a discussion topic module 314 that allows a user to create a new discussion topic. In one embodiment, prior to starting a new discussion in the discussion workspace, a user creates a new discussion topic and then enters his comments for communicating with his collaborators. Subsequent comments from other users associated with the workspace, also known as collaborators, can be replies to the first comment or new comments.

In one embodiment, the discussion workspace engine 310 includes a thread manager 316 that allows a user to reply to, edit, or delete a comment in a discussion workspace. Generally, the author of the comment, creator of the workspace, or designated administrator can edit or delete a comment.

In one embodiment, the host server 100 includes a collaborator manager 330 that tracks the permission levels of users. The term collaborator can refer to users who are given permission by a creator or administrator of a workspace to join that workspace. As discussed above, each collaborator of a workspace can be assigned a particular permission level or a default permission level. In one embodiment, when a collaborator of a workspace creates a sub-workspace within a parent workspace, the sub-workspace inherits each of the collaborators of the parent workspace, along with the permission levels of the collaborators in the parent workspace.

In one embodiment, the host server 100 includes a comments module 340 that creates a comments area linked with each file that is uploaded to the web-based content management system. Similar to the comments in the discussion workspace described above, comments associated with a file are limited to those with permission to leave a comment. Also, comments associated with a file can be maintained by the thread manager 316 which enables replies, editing, and deleting of file comments.

In one embodiment, the host server 100 includes an activity detector 350 that can detect an activity occurring in the web-based collaboration environment. Detected activities can be shown in an event stream in the linked discussion workspace. Activities can include any action related to a workspace, such as adding, deleting, or modifying a work item in the workspace or folder; adding, deleting, or modifying collaborators in the workspace; previewing or commenting on a work item; sharing a work item; emailing a link to a work item; adding, deleting, or modifying comments in the discussion workspace; and creating a discussion topic in the discussion workspace. In one embodiment, actions can be detected in real time or in near real time, and the event stream can be updated in real time or in near real time.

In one embodiment, the host server 100 includes an event stream module 360 that can receive detected activities with respect to work items in a workspace from the activity detector 350 and present the activities in an event stream in the associated discussion workspace. In one embodiment, activities that occur with respect to a child folder in the collaboration environment are also entered into the event stream of the parent folder. In one embodiment, the event stream module 360 can also send an email to collaborators notifying them of detected activities.

In one embodiment, the event stream module 360 includes the tracking module 365 which can track users of the web-based collaboration platform. In one embodiment, the tracking module 365 keeps track of when a user logs into the collaboration platform. When a user logs into the collaboration platform, the event stream module 360 sends a notification to the user about the latest new discussion topics or threads that have been started or discussion replies that have been generated since the last time the user logged into the collaboration platform. In some instances, the tracking module 365 marks a discussion as new until the user has read a discussion reply.

In one embodiment, the tracking module 365 keeps track of when a user goes to a specific folder where there is a discussion. When the user goes to that folder, the event stream module 360 sends a notification to the user about the latest new discussion topics or threads that have been started or discussion replies that have been generated since the last time the user visited that specific folder. In some instances, the tracking module 365 marks a discussion as new until the user has read a discussion reply.

In one embodiment, the tracking module 365 can track when a user has registered mobile device, and the event stream module 360 can send push notifications of detected activities, such as creation of a new discussion topic or a new discussion reply. Push notification is described in more detail in U.S. application Ser. No. 13/152,982, entitled, “REAL TIME NOTIFICATION OF ACTIVITIES THAT OCCUR IN A WEB BASED COLLABORATION ENVIRONMENT”, filed Jun. 3, 2011 and is incorporated herein in its entirety.

FIG. 4 depicts a screenshot showing an example user interface 400 for use in accessing the discussion workspace of a workspace in a web-based collaboration environment.

In the example of FIG. 4, the folder-file hierarchy of stored information in the content management system 130 of the user is shown as item 402. Here, the root folder is called “All Files”, and the root folder contains a folder or workspace called ‘Company Community Files’. The screen shot shows the contents 420 of this folder under the tab 410 called ‘Files and folders’, namely four folders or workspaces. The collaborators 440 of the “Company Community Files” workspace are shown on the right. The user is shown to be the owner, and the other collaborators may have different access permissions. The button 450 can be used by the user to invite further collaborators to join the workspace.

The ‘discussions’ tab 412 shown next to the ‘Files and Folders’ tab 410 indicates that one discussion has been started. The discussions under this tab are linked to the ‘Files and folders’ workspace. Any collaborator 440 can go to the ‘discussions’ tab 412 to start or join a discussion about any item in the linked ‘Files and folders’ workspace, provided the collaborator has the appropriate permission level to participate in a discussion. The linked discussion workspace is intended primarily for online conversations relating to the contents of the ‘company Community Files’ folder, although other comments can also be left as part of the ongoing discussion.

If the account holder of the displayed folder tree is only engaged in a small number of collaborations, the discussions can all be accessed and easily managed through the single, centralized ‘discussions’ tab 412.

In another scenario, if the account holder has a large number of ongoing collaborations, the online discussions can be filtered and more manageably organized by maintaining focused communications in each of the discussion workspaces linked to a specific sub-folder. In the example of FIG. 4, clicking on the sub-folder ‘Soccer League Sign-Ups’ would show the files and folders contained in this sub-folder under its own ‘files and folders’ tab. And next to the ‘files and folders’ tab would be a ‘discussions’ tab that is linked to the ‘Soccer League Sign-Ups’ workspace. Thus, the discussions related to this second-level folder can be focused just on work items in this workspace. By linking discussion workspaces to folders or hierarchical workspaces, discussions are automatically organized in the same manner as the folder workspaces are organized.

FIG. 5 shows an example screenshot of the discussion workspace 500 when a user/collaborator clicks on tab 412. The ongoing discussion topic 510 is called “This is a great new interface!” Users/collaborators can provide comments on this topic in the “Enter your comment” field 520. Users/collaborators can also start a new topic of discussion in the “Enter a topic title here” field 530 and clicking on the button “Create Topic” 532.

FIG. 6 shows an example screenshot of the discussion workspace 600 when a user/collaborator has entered a comment. When a user/collaborator clicks on the comment button 602 associated with a discussion topic, all previous comments in the discussion under that topic are displayed, and the “Enter your comment” field is shown. In the example of FIG. 6, the comment 606 “Well, let's hear it!” has been entered. After entering a comment, the user/collaborator clicks on the “Add Comment” button 604 to add the comment to the online discussion. In one embodiment, comments and topics can be received and shown in the discussion workspace in real time or in near real time.

FIG. 7 shows an example screenshot of the discussion workspace 700 when a user/collaborator clicks on the reply button 702 associated with a previous comment in a discussion. A new comment field 704 appears that is indented to show the level of the comment. Once the user/collaborator enters his comment in field 704, clicking the button ‘Add Comment’ 706 will add the comment to the discussion.

FIG. 8 shows another example screenshot of the discussion workspace 800 that has two discussions shown under the topics 805 and 825. Further comments in the two discussions can be entered in the comment field 815 and 835, respectively.

FIG. 9 is a flow diagram illustrating an example process 900 of providing a discussion workspace. At block 905, the system receives user input to create a new workspace/folder. In order to send the request to create the new workspace/folder, the user should have an access permission level that allows him to do so. Then at block 910, the system creates the new workspace/folder specified by the user along with a new discussion workspace linked to the new workspace/folder.

Then at block 915, the system allows the user to invite collaborators to the new workspace/folder. Any users invited to join the new workspace/folder can also join the discussion workspace, and vice versa. The user who created the new workspace/folder can set the permission level of each new user/collaborator invited to join.

Next, at block 920, the system also allows authorized user/collaborators to invite other user/collaborators to join the new workspace/folder and the linked discussion workspace and to set the permission level of each new user/collaborator invited to join.

Because the workspace/folder is new, no discussions yet exist in the discussion workspace. At block 925, the system allows authorized collaborators to start new topics in the discussion workspace. Although the discussion workspace is intended to facilitate communications among collaborators relating to the work items in the linked new workspace/folder, user/collaborators are not restricted by the system to comments that do so.

At block 930, the system allows authorized user/collaborators to make a comment under any topic that has been started. Then at block 935, the system allows authorized user/collaborators to respond to any comments that are in the ongoing dialogues in the discussion workspace. And at block 940, the system allows a comment author to edit or delete any of his comments in the discussion workspace.

The process continues at block 945 where actions related to work items in the linked workspace/folder are detected, and the detected actions are part of an event stream that is shown in the discussion workspace at block 950. At block 952, email notification of detected actions, such as the creation of a new discussion topic or thread or the addition of a new discussion reply, can be sent to collaborators.

At decision block 955, the system determines if there any child workspace/folders within the current workspace/folder. If there are no child workspace/folders (block 955—No), the process ends at block 999. If there are child workspace/folders (block 955—Yes), at block 960, the event stream from the discussion workspace linked to the child workspace/folder is included in the event stream of the current workspace/folder.

FIG. 10 is a flow diagram illustrating an example process 1000 of providing a discussion workspace for a workspace within a workspace. In one embodiment, the workspace within a workspace is a sub-folder of a parent folder.

At block 1005, the system receives user input to create a new workspace within an existing workspace. If the user is authorized to crate the new workspace, at block 1010, the system creates the new workspace and a discussion workspace linked to the new workspace within a workspace.

At block 1025, the system carries over collaborators from the parent workspace and provides inherited access permissions. Thus, if a collaborator is assigned a permission level that allows him to took at all files and participate in discussions in the parent workspace/folder, the same permissions would apply to the collaborators in the child workspace/folder. The process then continues to block 915 in FIG. 9A.

FIG. 11 shows a screenshot of an example user interface showing an event stream in a discussion workspace. The event stream 1110 shows activities performed by collaborators relating to the work items in the linked workspace/folder, for example, updating and downloading work items. The example event stream activities include information about the collaborator who performed the activity, the type of activity, the time and date of the activity, and the work item (e.g. file) on which the action was performed. However, the activities in the event stream can be adjusted to include more information, for example, more details about the activity such as the names of the items updated or downloaded, or the creator of the work item.

The event stream 1110 lists activities in strict chronological order, listing the most recent activity first. However, the event stream can be customized by the user or the owner/administrator of the workspace. For example, event stream activities can be organized according to the type of activities, and within each type of activity, the event stream can provide a chronological listing of activities.

In addition to the event stream, collaborators can still maintain an online discussion by using the add topic field 1120 and adding a comment or replying to an ongoing discussion.

FIG. 12 shows a screenshot of another example user interface showing an event stream in a discussion workspace. The event stream 1220 shows example activities such as previewing a work item from a shared link. Additionally, there is an idea/link field 1210 shown in FIG. 12. The idea/link field 1210 gives a user/collaborator a way to share an idea or a link as part of an online discussion by entering it in the field. In one embodiment, the idea/link field 1210 can replace the add topic field described above.

FIG. 13 shows a diagrammatic representation of a machine 1300 in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed

In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.

The network interface device enables the machine 1300 to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.

Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.

CONCLUSION

Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense (i.e., to say, in the sense of “including, but not limited to”), as opposed to an exclusive or exhaustive sense. As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements. Such a coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

The above Detailed Description of examples of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific examples for the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. While processes or blocks are presented in a given order in this application, alternative implementations may perform routines having steps performed in a different order, or employ systems having blocks in a different order. Some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples. It is understood that alternative implementations may employ differing values or ranges.

The various illustrations and teachings provided herein can also be applied to systems other than the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the invention.

Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts included in such references to provide further implementations of the invention.

These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.

While certain aspects of the invention are presented below in certain claim forms, the applicant contemplates the various aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as a means-plus-function claim under 35 U.S.C. §112, sixth paragraph, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶ will begin with the words “means for.”) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention.

COLLABORATION SESSIONS IN A WORKSPACE ON A CLOUD-BASED CONTENT MANAGEMENT SYSTEM

Information

Publication Number

Date Filed

Date Published

Inventors

CPC

US Classifications

International Classifications

Abstract

Description

Claims

CROSS-REFERENCES TO RELATED APPLICATIONS

Provisional Applications (1)