As digital content has become dominantly used in enterprise settings or other environments as the preferred mechanism for project, task, and work flow management, the technology surrounding streamlined collaboration and editing of digital content among groups of users has become an area of active development.
In content management for enterprise settings or similar environments, numerous users are editing, sharing and accessing digital content and files in a shared online work space; as such, content management, version control, and permission tracking are examples of issues that need to be addressed.
The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.
Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.
Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.
Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.
Embodiments of the present disclosure include systems and methods for the central management and control of user-contributed content in a web-based collaborative environment and management console provided therefor.
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 and/or notification server 150. Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 102 and/or the host server 100 and/or notification server 150.
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, host server 100, and notification server 150 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, administrator users 185 or collaborators (e.g., collaborators 108) for accessing, through network 106, a web-based collaboration environment or online collaboration platform (e.g., hosted by the host server 100 with notification capabilities (e.g., real time or near real time) enabled through the optional notification server 150).
The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, 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. A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user (author or creator of the content) or an administrative user 185, or a general collaborator 175, for example.
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 be 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 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, signing-off, or otherwise manipulating). The user can login 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.
Administrative user(s) 185 can be associated with a single work space or multiple work spaces. Administrative users 185 may be users having administrative rights to content contributed by other users in a given workspace or across multiple work spaces. For example, an administrative user 185 may be a department manager in an enterprise or similar organization who oversees several projects and assigns/monitors tasks performed by several collaborators. An administrative user 185, may, manage, edit, access content provided by other users through the collaboration platform. Administrative users 185 may also manage collaborative users 175, for example, by monitoring, reviewing their work items, work status, assignments, and/or change/assign/edit permissions of the collaborative users 175 with respect to documents and work items in one or more work space. Further use cases can include eDiscovery applications using account-wide search enabled for administrative users.
A diagrammatic illustration of the online collaboration environment and the relationships between workspaces and users/collaborators/administrators are illustrated with further reference to the example of
In one embodiment, the host server 100 of the online or web-based collaboration environment provides enhanced mechanisms for centralized management and control of user-contributed content by a user who can play an administrative/management role with respect to some workspaces but not in others. The web-based collaboration environment can provide a user interface having a segmented view between a management console and a user console.
For workspaces which the user is an administrator or manager, the user can, through the management console activated in the user interface through the collaborative environment, access, manage, edit, and/or monitor content provided by other users (e.g., content relating to a given project, within a certain department, topic, organization, or enterprise). The administrative user can also, through the management console, track, monitor users or collaborators across one or more workspaces in the online collaboration environment.
For workspace which the user is not an administrator, the user may access the user console through the same interface to access the associated content and/or interact with the associated collaborators. The segmented view in a common user interface allows, for example, a user to manage multiple affiliations and associated content/collaborators, either with a given work space in the collaboration environment, or with multiple enterprises/organizations, through the web-based collaboration environment.
Note that through the user interface, the administrative user can also access a non-management console view to access his/her own content in a separate work space or context in which he/she may not play an administrative or management role, either in the web-based work space or in an actual physical enterprise/environment.
In other words, the segmented administrator and user views enable the decentralization and management of roles by a user using a single account. In this manner, the user need not establish multiple accounts (e.g., different log-in information) for different affiliations and/or to access different work items with different work space affiliations. For example, a given administrator can login to the collaboration environment using a single account to access a project for which he/she is managing (and also managing the associated content and other users) and at the same time, using that same account to access projects or work spaces where the user is just a contributor or collaborator, and not managing the content, project, or other users. The projects accessed through the segmented views may have the same or different enterprise organization affiliations.
Functions and techniques disclosed for centrally managing and controlling user-contributed content and other users via a management console are further described with reference to the components illustrated in the example of
In one embodiment, client devices 102 communicate with the host server 100 and/or notification server 150 over network 106. In general, network 106, over which the client devices 102, the host server 100, and/or notification server 150 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, text messaging (SMS), 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, 1xRTT, 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.
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 formal or informal setting, such as a group of users with no-specific (common) formal organizational or enterprise affiliation.
When deployed in a 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 associate work items. For example, work space A 205 may be associated with work items 215, work space B 225 can be associated with work items 235, and work space N 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 word 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 some instances, a given work space (e.g., work space A 205) may have an administrative user (e.g., administrative user 285) who manages the associated work items (e.g., work items 215) contributed or provided by other users (e.g., users 206) and/or the affiliated users. The administrator 285 may also manage multiple work spaces (e.g., work spaces A, B, etc) and/or the contributing/associated users, etc. Through the collaboration environment, a user with an administrative role can access and manage an aggregate of content provided by the other users. The administrative user can also manage other users and user groups through the collaboration environment, via a management console.
In each work space A, B . . . N, when an action is performed on a work item by a given user or any other activity is detected in the work space, other users in the same work space may be notified (e.g., in real time or in near real time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, or modifying collaborators in the work space, uploading, downloading, adding, deleting a work item in the work space, creating a discussion topic in the work space.
Such notifications can be sent to relevant users and/or any administrators to notify them of actions surrounding such activities.
Example user interfaces for accessing the collaborative environment or platform and the central management and content control mechanisms are illustrated with references to the example screenshots of
Each of users 316, 318, and 320 can individually use multiple different devices to access and/or manipulate work items 324 in the work space 302 with which they are associated with. For example users 316, 318, 320 can be collaborators on a project to which work items 324 are relevant. Since the work items 324 are hosted by the collaboration environment (e.g., a cloud-based environment), each user can access the work items 324 anytime, and from any physical location using any device (e.g., including devices they own or any shared/public/loaner device). The admin user 318 can access the work items in the work space 302 provided by other users (e.g., user 316 and/or creator 320), and/or edit or perform other actions in accordance with admin rights via a management console through the collaboration work space. Tasks, jobs in the work space 302 can also be managed by the admin user 318 (e.g., monitor progress, assign tasks, review comments, review revisions, etc.) through the management console.
The host server 400 of the web-based or online collaboration environment can generally be a cloud-based service. The host server 400 can include, for example, a network interface 402, an access type detector 405, a notification engine 415 having a notification server manager 416 and/or a management console feed generator 418. The host server 400 can further include a management console/user console agent 455 having a verification module 456, a content manager 458 having a search/filter agent 459, a user/task manager 460 having a status monitor agent 461 and/or a user manager 462. Additional or less components/modules/engines can be included in the host server 400 and each illustrated component.
The network interface 402 can be a networking module that enables the host server 400 to mediate data in a network with an entity that is external to the host server 400, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 402 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, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, 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 mediums that are statutory (e.g., in the United States, under 35 U.S.C. §101), and to specifically exclude all mediums 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 mediums 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 400 includes the access type detector 405 which can receive, detect, process, identify, a user request and categorize it as either an administrative request or a general user request.
An administrative request includes a request from a user with management or other administrative roles, either in the collaborative environment online or in the physical organization or enterprise. The access request can be received from a user (e.g., through UI features in a user interface, such as that one shown in the examples of
Administrative requests include those by an administrative user to centrally manage or control an aggregate of content provided by other users, such as users in one or more work spaces in the online environment, which can correspond to users which share a common affiliation in real life (e.g., collaborators in the same project, belonging to the same department, major, organization, sub-organization, sub-group, enterprise, local office of a company, common seniority, etc.). Administrative requests include a request from a user to view, edit, organize, or otherwise access an aggregate of content provided by or contributed by other users.
A general user request can include requests to upload the user's own content (authored or created content), edit uploaded content, review, or edit content provided by other collaborators. In response to detecting an administrative request, the system can initially verify that that the user has permission to manage or access the aggregated content provided by other users in a given setting (e.g., in a specific work space, group of work spaces, or content associated with a physical organization, enterprise, or other types of groups).
For example, the request, once categorized as a general user request or as a administrator request, can be passed on to the management console/user console agent 455. If the request is detected as an admin request, the verification module 456 can determine, verify, confirm, whether the user has administrative rights to manage content or an aggregate of content provided by the other users in a given setting. The verification module 456 can verify such rights based on identification of the user using the user's login credentials and user data stored for the user in the system (e.g., repository 130 of the example of
Administrative rights may be assigned by management of a given enterprise, with which the work space is relevant, or any other user or member of the web-based collaboration environment or real-life organization or group of affiliated people. Administrative rights may be assigned by the admin user him/herself. Alternatively or in addition, administrative rights may be assigned to one or more users by a collaborator in a given work space. In general, the user and the other users are affiliated with a common organization and the administrative user in the online platform also assumes an administrative role in the common organization. Such rights and relationships can be indicated in user profiles stored in the system.
When admin rights have been confirmed or verified for a user, the management console/user console agent 455 can depict, in a user interface, for the user to access the web-based collaboration environment, a view providing access to an aggregate of content provided by the other users. Via the view (e.g., a ‘management console’), the user is able to selectively access a subset of the aggregate of the content by applying filtering mechanisms through the user interface to manage the content (e.g., via the content manager module 458).
The view depicted in the management console can include the aggregate of content provided by the other users presented as a list of files or folders for the administrative user to view, access, monitor, review, or edit, for example, as shown in the panel 604 in the example screenshot of
Examples of the filtering and search mechanisms are shown in the example screenshots of
The management console also further includes group management features which allow the user to manage user groups among the other users, for example, via the user/tasks manager module 460 or the user manager module 462 therein. The user can also, through the management console, manage one or more of the other users that provided the content, for example, by changing or updating access permissions of the individual work items in the aggregate set of content. The screenshot of
In addition, the management console allows users to assign tasks in a work space to other users (e.g., another user or collaborator in a work space), for example, facilitated by the user/task manager 460. In one embodiment, through the status monitor agent 461, the administrative user is able to monitor the status of individual work items or assigned tasks. The administrative user may also be able to perform changing or updating access permissions of the individual work items in the aggregate set of content.
One embodiment of the host server 400 includes a notification engine 455. The notification engine 455, can for example, update a feed stream in the management console for the administrative user, for example, via the management console feed generator 418. In some instances, the feed stream can be optionally updated in real time or near real time relative to when the action relative to a work item, work space, or user is performed, initiated, saved, shared, and/or completed. For real-time updating, the notification engine 455 can utilize another server, or another engine in the same server which provides push functionality.
The notification engine 455 can generally notify users, which can be collaborators of the user who performed the activity in the work space, in addition to one or more administrator users, via one or more of many mechanisms, including but not limited to, email, SMS, voice-message, text-based message, RSS, feed, etc., as described in detail with further reference to related co-pending U.S. patent application Ser. No. 13/152,982 filed on Jun. 3, 2011. The contents of which are incorporated herein by reference in its entirety.
In one embodiment, the notification is depicted through a web-browser used by the other user (e.g., another collaborator or one or more administrative users) to access the web-based collaboration environment, for access in real time or near real time, or in delay time to when the activity was performed by the user. When notifying a user in real time through a web-browser, the notification engine 415 can utilize a push-enabled service to ensure real time notification. In one embodiment, the notification is sent by a component or another server which implements push technology.
The push-enabled service can be implemented via long poll or HTTP streaming, for example, by the notification server 500 or another component, device which may be internal to or external to the host server 400. In addition, the host server 400 could utilize other push servers including third party push servers to implement push technology including but not limited to mobile platform push systems and services (e.g., via smart phones or tablets or other portable devices such as iPhone, Android phones, Blackberry, iPad, Galaxy or other tablets, etc.) The host server 400 can send a notification server an identification of the recipient or administrative user to be notified and indicator of the activity to notify the recipient of.
In general, recipients, including recipients who are administrative users, of an activity notification are selected based on criteria. The activities which an administrative user is notified of can also be determined by system-managed criteria. The criteria may be determined, for example, based on a work space in which the activity was performed in the online collaboration platform. Specifically, the criteria, is in one embodiment, determined based on permissions configured for the workspace, as managed, tracked, updated, implemented, revised, based on the permissions manager 435.
For example, the workspace can be associated with an enterprise and in such an instance, the criteria can specify that the recipient that is selected is an employee of the enterprise and is therefore an administrative user. Enterprise associations and affiliations can be managed by the organization tracker 440, for example; in some embodiments, enterprises and/or enterprise accounts can specifically be managed, tracked, monitored by the enterprise tracker 441.
Permissions for the workspace can be configured by a creator or administrative user of the workspace. Administrator designations are also tracked and stored in the permissions manager 435. The collaboration manager 438 can determine, track, and implement relationships, roles, and/or access levels of multiple users/collaborators. For example, users may be a general user, a creator of the work space, a creator of a work item, or an administrative user. The permissions for a work space can be configured by a user, creator, or the administrative user and is generally managed by the collaborations manager 438.
The criteria that are determined by work space permissions can be managed by the work space manager 436 in the permissions manager 435. A recipient selection criteria for recipients of notifications or other access rights can generally be based on user affiliation with the workspace, including, one or more of, member, invited collaborator and collaborator in the workspace. Such user affiliation can be tracked and managed by, for example, the collaboration manger 438 of the permissions manager 435.
In one embodiment, the criteria are determined based on permissions associated with a work item on which the activity was performed in relation to in the workspace. Permissions associated with work items can be managed, tracked, updated, revised, or implemented, in one embodiment, by the work item manager 442. For example, the permissions associated with the work item can be set by, a creator of the work item or an administrative user of the work space. Each work space can include multiple work items where each of multiple work items has individually configurable permissions. The individually configured permissions can be determined by user roles and rights (e.g., as managed by the collaborations manager 438). The work item manager 442 can communicate with the collaboration manager 438 in setting, configuring, or re-configuring permissions associated with work items.
In process 502, it is verified that a user has permission to view and/or manage the aggregate of the content provided by the other users. In process 504, it is detected that the management console is selected in a user interface by the user. In process 506, a view providing access to an aggregate of content provided by the other users is depicted in a user interface for the user to access the web-based collaboration environment.
In process 508, filtering mechanisms are applied through the user interface to manage the content. The filters selected can include, by way of example but not limitation, search term, keyword, time, time range, user, owner, collaborator, date range, type of access, type of content, etc. In process 512, the administrative user can selectively access a subset of the aggregate of the content. Note that in some instances, separate permission settings or levels can be set for permission to view content, manage content, and/or aggregate content. In other words, administrative users can have rights to view users' content but not to filter and aggregate, or administrative users can have permission to view users' content. These permissions can vary based on use case, company requirements, and can be customized on a case by case basis.
In process 514, the administrative user can selectively access individual work items in the aggregate of the selection of content. One embodiment includes process 516, where, the user exports or downloads a subset of the content based on the applied filters. Similarly, in process 510, filtering mechanisms can be applied through the user interface to select or manage one or more of the other users that provided the set of the aggregate of the content.
Screenshot 600 illustrates the management console view when the ‘admin console’ tab 602 is selected. Under this view, which is accessible to the administrative user, the files and folders panel 604 showing a hierarchy of aggregated content among multiple users can be accessed and used to selectively view content (e.g., shown in window 612). Alternatively, the user can, through user interface 600 select the ‘my account’ tab 608 and access his/her own account and the associated content and collaborators which can be independent of work spaces and content which the user has admin rights for.
Screenshot 700 depicts another example view of the management console showing panel 702 which allows the admin user to view the files in a selected folder of aggregated content from multiple users. Similarly, screenshots 800 and 900 depict additional examples of features provided to an admin user through the management console to access, edit, share, view, or otherwise manipulate content, files, or folders.
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 2800 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.
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, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” 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; the coupling of 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, shall 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 embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
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 disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.
These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure 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 disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.
While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, 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, ¶6 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 disclosure.
This application claims the benefit of U.S. Patent Application No. 61/538,782 entitled “CENTRAL MANAGEMENT AND CONTROL OF USER-CONTRIBUTED CONTENT IN A WEB-BASED COLLABORATION ENVIRONMENT AND MANAGEMENT CONSOLE THEREFOR” which was filed on Sep. 23, 2011, the contents of which are all incorporated by reference herein. This application is further related to U.S. patent application Ser. No. 13/152,982 entitled “Real Time Notification Of Activities that Occur In A Web-Based Collaboration Environment”, which was filed on Jun. 3, 2011, the contents of which are all incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
858619 | O'Farrell | Jul 1907 | A |
5787175 | Carter | Jul 1998 | A |
5799320 | Klug | Aug 1998 | A |
5848415 | Guck | Dec 1998 | A |
5999908 | Abelow | Dec 1999 | A |
6016467 | Newsted et al. | Jan 2000 | A |
6034621 | Kaufman | Mar 2000 | A |
6073161 | DeBoskey et al. | Jun 2000 | A |
6098078 | Gehani et al. | Aug 2000 | A |
6233600 | Salas et al. | May 2001 | B1 |
6260040 | Kauffman et al. | Jul 2001 | B1 |
6289345 | Yasue | Sep 2001 | B1 |
6292803 | Richardson et al. | Sep 2001 | B1 |
6336124 | Alam et al. | Jan 2002 | B1 |
6345386 | Delo et al. | Feb 2002 | B1 |
6370543 | Hoffert et al. | Apr 2002 | B2 |
6374260 | Hoffert et al. | Apr 2002 | B1 |
6385606 | Inohara et al. | May 2002 | B2 |
6396593 | Laverty et al. | May 2002 | B1 |
6515681 | Knight | Feb 2003 | B1 |
6539381 | Prasad et al. | Mar 2003 | B1 |
6584466 | Serbinis et al. | Jun 2003 | B1 |
6636872 | Heath et al. | Oct 2003 | B1 |
6654737 | Nunez | Nov 2003 | B1 |
6662186 | Esquibel et al. | Dec 2003 | B1 |
6687878 | Eintracht et al. | Feb 2004 | B1 |
6714968 | Prust | Mar 2004 | B1 |
6735623 | Prust | May 2004 | B1 |
6742181 | Koike et al. | May 2004 | B1 |
6760721 | Chasen et al. | Jul 2004 | B1 |
6947162 | Rosenberg et al. | Sep 2005 | B2 |
6952724 | Prust | Oct 2005 | B2 |
6996768 | Elo et al. | Feb 2006 | B1 |
7020697 | Goodman et al. | Mar 2006 | B1 |
7039806 | Friedman et al. | May 2006 | B1 |
7069393 | Miyata et al. | Jun 2006 | B2 |
7130831 | Howard et al. | Oct 2006 | B2 |
7133834 | Abelow | Nov 2006 | B1 |
7149787 | Mutalik et al. | Dec 2006 | B1 |
7152182 | Ji et al. | Dec 2006 | B2 |
7155483 | Friend et al. | Dec 2006 | B1 |
7165107 | Pouyoul et al. | Jan 2007 | B2 |
7222078 | Abelow | May 2007 | B2 |
7275244 | Charles Bell et al. | Sep 2007 | B1 |
7296025 | Kung et al. | Nov 2007 | B2 |
7346778 | Guiter et al. | Mar 2008 | B1 |
7353252 | Yang et al. | Apr 2008 | B1 |
7386535 | Kalucha et al. | Jun 2008 | B1 |
7401117 | Dan et al. | Jul 2008 | B2 |
7543000 | Castro et al. | Jun 2009 | B2 |
7581221 | Lai et al. | Aug 2009 | B2 |
7620565 | Abelow | Nov 2009 | B2 |
7647559 | Yozell-Epstein et al. | Jan 2010 | B2 |
7650367 | Arruza | Jan 2010 | B2 |
7661088 | Burke | Feb 2010 | B2 |
7665093 | Maybee et al. | Feb 2010 | B2 |
7676542 | Moser et al. | Mar 2010 | B2 |
7698363 | Dan et al. | Apr 2010 | B2 |
7734600 | Wise et al. | Jun 2010 | B1 |
7756843 | Palmer | Jul 2010 | B1 |
7774412 | Schnepel | Aug 2010 | B1 |
7814426 | Huesken et al. | Oct 2010 | B2 |
7886287 | Davda | Feb 2011 | B1 |
7886295 | Burger et al. | Feb 2011 | B2 |
7890964 | Vogler-Ivashchanka et al. | Feb 2011 | B2 |
7937663 | Parker et al. | May 2011 | B2 |
7958453 | Taing | Jun 2011 | B1 |
7979296 | Kruse et al. | Jul 2011 | B2 |
7996374 | Jones et al. | Aug 2011 | B1 |
8027976 | Ding et al. | Sep 2011 | B1 |
RE42904 | Stephens, Jr. | Nov 2011 | E |
8065739 | Bruening et al. | Nov 2011 | B1 |
8090361 | Hagan | Jan 2012 | B2 |
8103662 | Eagan et al. | Jan 2012 | B2 |
8117261 | Briere et al. | Feb 2012 | B2 |
8140513 | Ghods et al. | Mar 2012 | B2 |
8151183 | Chen et al. | Apr 2012 | B2 |
8185830 | Saha et al. | May 2012 | B2 |
8214747 | Yankovich et al. | Jul 2012 | B1 |
8230348 | Peters et al. | Jul 2012 | B2 |
8326814 | Ghods et al. | Dec 2012 | B2 |
8347276 | Schadow | Jan 2013 | B2 |
8358701 | Chou et al. | Jan 2013 | B2 |
8370803 | Holler et al. | Feb 2013 | B1 |
8429540 | Yankovich et al. | Apr 2013 | B1 |
8464161 | Giles et al. | Jun 2013 | B2 |
8515902 | Savage | Aug 2013 | B2 |
8549066 | Donahue et al. | Oct 2013 | B1 |
8549511 | Seki et al. | Oct 2013 | B2 |
8583619 | Ghods et al. | Nov 2013 | B2 |
8607306 | Bridge et al. | Dec 2013 | B1 |
8719445 | Ko | May 2014 | B2 |
8745267 | Luecke et al. | Jun 2014 | B2 |
8868574 | Kiang et al. | Oct 2014 | B2 |
8892679 | Destagnol et al. | Nov 2014 | B1 |
8914900 | Smith et al. | Dec 2014 | B2 |
8918387 | Sokolov | Dec 2014 | B1 |
8949939 | Peddada | Feb 2015 | B2 |
8959579 | Barton et al. | Feb 2015 | B2 |
8990955 | Hymel et al. | Mar 2015 | B2 |
20010027492 | Gupta | Oct 2001 | A1 |
20020091738 | Rohrabaugh et al. | Jul 2002 | A1 |
20020099772 | Deshpande et al. | Jul 2002 | A1 |
20020116544 | Barnard et al. | Aug 2002 | A1 |
20020133509 | Johnston et al. | Sep 2002 | A1 |
20020147770 | Tang | Oct 2002 | A1 |
20020194177 | Sherman et al. | Dec 2002 | A1 |
20030041095 | Konda et al. | Feb 2003 | A1 |
20030084306 | Abburi et al. | May 2003 | A1 |
20030093404 | Bader et al. | May 2003 | A1 |
20030108052 | Inoue et al. | Jun 2003 | A1 |
20030110264 | Whidby et al. | Jun 2003 | A1 |
20030115326 | Verma et al. | Jun 2003 | A1 |
20030135536 | Lyons | Jul 2003 | A1 |
20030135565 | Estrada | Jul 2003 | A1 |
20030154306 | Perry | Aug 2003 | A1 |
20030204490 | Kasriel | Oct 2003 | A1 |
20030217171 | Von Stuermer et al. | Nov 2003 | A1 |
20040021686 | Barberis | Feb 2004 | A1 |
20040088647 | Miller et al. | May 2004 | A1 |
20040098361 | Peng | May 2004 | A1 |
20040103147 | Flesher et al. | May 2004 | A1 |
20040111415 | Scardino et al. | Jun 2004 | A1 |
20040117438 | Considine et al. | Jun 2004 | A1 |
20040122949 | Zmudzinski et al. | Jun 2004 | A1 |
20040128359 | Horvitz et al. | Jul 2004 | A1 |
20040177138 | Salle et al. | Sep 2004 | A1 |
20040181579 | Huck et al. | Sep 2004 | A1 |
20040196307 | Zak et al. | Oct 2004 | A1 |
20040201604 | Kraenzel et al. | Oct 2004 | A1 |
20040230624 | Frolund et al. | Nov 2004 | A1 |
20040246532 | Inada | Dec 2004 | A1 |
20040267836 | Armangau et al. | Dec 2004 | A1 |
20050005276 | Morgan | Jan 2005 | A1 |
20050010860 | Weiss et al. | Jan 2005 | A1 |
20050022229 | Gabriel et al. | Jan 2005 | A1 |
20050028006 | Leser et al. | Feb 2005 | A1 |
20050050228 | Perham et al. | Mar 2005 | A1 |
20050063083 | Dart et al. | Mar 2005 | A1 |
20050097225 | Glatt et al. | May 2005 | A1 |
20050108406 | Lee et al. | May 2005 | A1 |
20050114305 | Haynes et al. | May 2005 | A1 |
20050114378 | Elien et al. | May 2005 | A1 |
20050138118 | Banatwala et al. | Jun 2005 | A1 |
20050182966 | Pham et al. | Aug 2005 | A1 |
20050198299 | Beck et al. | Sep 2005 | A1 |
20050198452 | Watanabe | Sep 2005 | A1 |
20050234864 | Shapiro | Oct 2005 | A1 |
20050234943 | Clarke | Oct 2005 | A1 |
20050261933 | Magnuson | Nov 2005 | A1 |
20060005163 | Huesken et al. | Jan 2006 | A1 |
20060026535 | Hotelling et al. | Feb 2006 | A1 |
20060036568 | Moore et al. | Feb 2006 | A1 |
20060041603 | Paterson et al. | Feb 2006 | A1 |
20060047804 | Fredricksen et al. | Mar 2006 | A1 |
20060053088 | Ali et al. | Mar 2006 | A1 |
20060070083 | Brunswig et al. | Mar 2006 | A1 |
20060075071 | Gillette | Apr 2006 | A1 |
20060117247 | Fite et al. | Jun 2006 | A1 |
20060123062 | Bobbitt et al. | Jun 2006 | A1 |
20060168550 | Muller et al. | Jul 2006 | A1 |
20060174051 | Lordi et al. | Aug 2006 | A1 |
20060174054 | Matsuki | Aug 2006 | A1 |
20060179070 | George et al. | Aug 2006 | A1 |
20060242204 | Karas et al. | Oct 2006 | A1 |
20060259524 | Horton | Nov 2006 | A1 |
20060265719 | Astl et al. | Nov 2006 | A1 |
20060271510 | Harward et al. | Nov 2006 | A1 |
20070016680 | Burd et al. | Jan 2007 | A1 |
20070038934 | Fellman | Feb 2007 | A1 |
20070079242 | Jolley et al. | Apr 2007 | A1 |
20070100830 | Beedubail et al. | May 2007 | A1 |
20070115845 | Hochwarth et al. | May 2007 | A1 |
20070124460 | McMullen et al. | May 2007 | A1 |
20070124781 | Casey et al. | May 2007 | A1 |
20070126635 | Houri | Jun 2007 | A1 |
20070130143 | Zhang et al. | Jun 2007 | A1 |
20070130163 | Perez et al. | Jun 2007 | A1 |
20070198609 | Black et al. | Aug 2007 | A1 |
20070208878 | Barnes-Leon et al. | Sep 2007 | A1 |
20070214180 | Crawford | Sep 2007 | A1 |
20070220016 | Estrada et al. | Sep 2007 | A1 |
20070220590 | Rasmussen et al. | Sep 2007 | A1 |
20070240057 | Satterfield et al. | Oct 2007 | A1 |
20070250762 | Mansfield | Oct 2007 | A1 |
20070256065 | Heishi et al. | Nov 2007 | A1 |
20070266304 | Fletcher et al. | Nov 2007 | A1 |
20070282848 | Kiilerich et al. | Dec 2007 | A1 |
20070283443 | McPherson et al. | Dec 2007 | A1 |
20070288290 | Motoyama et al. | Dec 2007 | A1 |
20080005195 | Li | Jan 2008 | A1 |
20080016146 | Gan et al. | Jan 2008 | A1 |
20080021959 | Naghi et al. | Jan 2008 | A1 |
20080028323 | Rosen et al. | Jan 2008 | A1 |
20080040173 | Aleong et al. | Feb 2008 | A1 |
20080040503 | Kleks et al. | Feb 2008 | A1 |
20080059656 | Saliba et al. | Mar 2008 | A1 |
20080063210 | Goodman et al. | Mar 2008 | A1 |
20080065881 | Dawson et al. | Mar 2008 | A1 |
20080077631 | Petri | Mar 2008 | A1 |
20080091763 | Devonshire et al. | Apr 2008 | A1 |
20080091790 | Beck | Apr 2008 | A1 |
20080104277 | Tian | May 2008 | A1 |
20080114720 | Smith et al. | May 2008 | A1 |
20080133674 | Knauerhase et al. | Jun 2008 | A1 |
20080140732 | Wilson et al. | Jun 2008 | A1 |
20080147790 | Malaney et al. | Jun 2008 | A1 |
20080151817 | Fitchett et al. | Jun 2008 | A1 |
20080154873 | Redlich et al. | Jun 2008 | A1 |
20080182628 | Lee et al. | Jul 2008 | A1 |
20080183467 | Yuan et al. | Jul 2008 | A1 |
20080184130 | Tien et al. | Jul 2008 | A1 |
20080194239 | Hagan | Aug 2008 | A1 |
20080215883 | Fok et al. | Sep 2008 | A1 |
20080222654 | Xu et al. | Sep 2008 | A1 |
20080243855 | Prahlad et al. | Oct 2008 | A1 |
20080250333 | Reeves et al. | Oct 2008 | A1 |
20080250348 | Alimpich et al. | Oct 2008 | A1 |
20080271095 | Shafton | Oct 2008 | A1 |
20080276158 | Lim et al. | Nov 2008 | A1 |
20090015864 | Hasegawa | Jan 2009 | A1 |
20090019093 | Brodersen et al. | Jan 2009 | A1 |
20090019426 | Baeumer et al. | Jan 2009 | A1 |
20090030710 | Levine | Jan 2009 | A1 |
20090044128 | Baumgarten et al. | Feb 2009 | A1 |
20090049131 | Lyle et al. | Feb 2009 | A1 |
20090119322 | Mills et al. | May 2009 | A1 |
20090125469 | McDonald et al. | May 2009 | A1 |
20090132651 | Roger et al. | May 2009 | A1 |
20090138808 | Moromisato et al. | May 2009 | A1 |
20090150417 | Ghods et al. | Jun 2009 | A1 |
20090150627 | Benhase et al. | Jun 2009 | A1 |
20090164438 | Delacruz | Jun 2009 | A1 |
20090171983 | Samji et al. | Jul 2009 | A1 |
20090193107 | Srinivasan et al. | Jul 2009 | A1 |
20090193345 | Wensley et al. | Jul 2009 | A1 |
20090198772 | Kim et al. | Aug 2009 | A1 |
20090210459 | Nair et al. | Aug 2009 | A1 |
20090214115 | Kimura et al. | Aug 2009 | A1 |
20090235167 | Boyer et al. | Sep 2009 | A1 |
20090235181 | Saliba et al. | Sep 2009 | A1 |
20090235189 | Aybes et al. | Sep 2009 | A1 |
20090249224 | Davis et al. | Oct 2009 | A1 |
20090254589 | Nair et al. | Oct 2009 | A1 |
20090260060 | Smith et al. | Oct 2009 | A1 |
20090265430 | Bechtel et al. | Oct 2009 | A1 |
20090276771 | Nickolov et al. | Nov 2009 | A1 |
20090282212 | Peterson | Nov 2009 | A1 |
20090282483 | Bennett | Nov 2009 | A1 |
20090300356 | Crandell | Dec 2009 | A1 |
20090300527 | Malcolm et al. | Dec 2009 | A1 |
20090327358 | Lukiyanov et al. | Dec 2009 | A1 |
20090327961 | De Vorchik et al. | Dec 2009 | A1 |
20100011447 | Jothimani | Jan 2010 | A1 |
20100017262 | Iyer et al. | Jan 2010 | A1 |
20100036929 | Scherpa et al. | Feb 2010 | A1 |
20100042720 | Stienhans et al. | Feb 2010 | A1 |
20100057560 | Skudlark et al. | Mar 2010 | A1 |
20100057785 | Khosravy et al. | Mar 2010 | A1 |
20100076946 | Barker et al. | Mar 2010 | A1 |
20100082634 | Leban | Apr 2010 | A1 |
20100088150 | Mazhar et al. | Apr 2010 | A1 |
20100092126 | Kaliszek et al. | Apr 2010 | A1 |
20100093310 | Gbadegesin et al. | Apr 2010 | A1 |
20100107225 | Spencer et al. | Apr 2010 | A1 |
20100151431 | Miller | Jun 2010 | A1 |
20100153835 | Xiong et al. | Jun 2010 | A1 |
20100162365 | Del Real | Jun 2010 | A1 |
20100162374 | Nair | Jun 2010 | A1 |
20100179940 | Gilder et al. | Jul 2010 | A1 |
20100185463 | Noland et al. | Jul 2010 | A1 |
20100185932 | Coffman et al. | Jul 2010 | A1 |
20100191689 | Cortes et al. | Jul 2010 | A1 |
20100198783 | Wang et al. | Aug 2010 | A1 |
20100198871 | Stiegler et al. | Aug 2010 | A1 |
20100198944 | Ho et al. | Aug 2010 | A1 |
20100205537 | Knighton et al. | Aug 2010 | A1 |
20100218237 | Ferris et al. | Aug 2010 | A1 |
20100223378 | Wei | Sep 2010 | A1 |
20100229085 | Nelson et al. | Sep 2010 | A1 |
20100235526 | Carter et al. | Sep 2010 | A1 |
20100235539 | Carter et al. | Sep 2010 | A1 |
20100241972 | Spataro et al. | Sep 2010 | A1 |
20100250120 | Waupotitsch et al. | Sep 2010 | A1 |
20100251340 | Martin et al. | Sep 2010 | A1 |
20100262582 | Garcia-Ascanio et al. | Oct 2010 | A1 |
20100267588 | Nelson et al. | Oct 2010 | A1 |
20100274765 | Murphy et al. | Oct 2010 | A1 |
20100274772 | Samuels | Oct 2010 | A1 |
20100281118 | Donahue et al. | Nov 2010 | A1 |
20100290623 | Banks et al. | Nov 2010 | A1 |
20100318893 | Matthews et al. | Dec 2010 | A1 |
20100322252 | Suganthi et al. | Dec 2010 | A1 |
20100325155 | Skinner et al. | Dec 2010 | A1 |
20100325527 | Estrada et al. | Dec 2010 | A1 |
20100325559 | Westerinen et al. | Dec 2010 | A1 |
20100325655 | Perez | Dec 2010 | A1 |
20100332401 | Prahlad et al. | Dec 2010 | A1 |
20100332962 | Hammer et al. | Dec 2010 | A1 |
20100333116 | Prahlad et al. | Dec 2010 | A1 |
20110001763 | Murakami | Jan 2011 | A1 |
20110016409 | Grosz et al. | Jan 2011 | A1 |
20110022559 | Andersen et al. | Jan 2011 | A1 |
20110022812 | Van Der Linden et al. | Jan 2011 | A1 |
20110040812 | Phillips | Feb 2011 | A1 |
20110041083 | Gabai et al. | Feb 2011 | A1 |
20110047413 | McGill et al. | Feb 2011 | A1 |
20110047484 | Mount et al. | Feb 2011 | A1 |
20110052155 | Desmarais et al. | Mar 2011 | A1 |
20110054968 | Galaviz | Mar 2011 | A1 |
20110055299 | Phillips | Mar 2011 | A1 |
20110055721 | Jain et al. | Mar 2011 | A1 |
20110061045 | Phillips | Mar 2011 | A1 |
20110061046 | Phillips | Mar 2011 | A1 |
20110065082 | Gal et al. | Mar 2011 | A1 |
20110066951 | Ward-Karet et al. | Mar 2011 | A1 |
20110083167 | Carpenter et al. | Apr 2011 | A1 |
20110093567 | Jeon et al. | Apr 2011 | A1 |
20110099006 | Sundararaman et al. | Apr 2011 | A1 |
20110113320 | Neff et al. | May 2011 | A1 |
20110119313 | Sung et al. | May 2011 | A1 |
20110137991 | Russell | Jun 2011 | A1 |
20110142410 | Ishii | Jun 2011 | A1 |
20110145744 | Haynes et al. | Jun 2011 | A1 |
20110161289 | Pei et al. | Jun 2011 | A1 |
20110167125 | Achlioptas | Jul 2011 | A1 |
20110167353 | Grosz et al. | Jul 2011 | A1 |
20110167435 | Fang | Jul 2011 | A1 |
20110185292 | Chawla et al. | Jul 2011 | A1 |
20110202424 | Chun et al. | Aug 2011 | A1 |
20110202599 | Yuan et al. | Aug 2011 | A1 |
20110208958 | Stuedi et al. | Aug 2011 | A1 |
20110209064 | Jorgensen et al. | Aug 2011 | A1 |
20110213765 | Cui et al. | Sep 2011 | A1 |
20110219419 | Reisman | Sep 2011 | A1 |
20110225417 | Maharajh et al. | Sep 2011 | A1 |
20110238458 | Purcell et al. | Sep 2011 | A1 |
20110238621 | Agrawal | Sep 2011 | A1 |
20110239135 | Spataro et al. | Sep 2011 | A1 |
20110246294 | Robb et al. | Oct 2011 | A1 |
20110246950 | Luna et al. | Oct 2011 | A1 |
20110252320 | Arrasvuori et al. | Oct 2011 | A1 |
20110252339 | Lemonik et al. | Oct 2011 | A1 |
20110258461 | Bates | Oct 2011 | A1 |
20110258561 | Ladouceur et al. | Oct 2011 | A1 |
20110277027 | Hayton et al. | Nov 2011 | A1 |
20110282710 | Akkiraju et al. | Nov 2011 | A1 |
20110289433 | Whalin et al. | Nov 2011 | A1 |
20110296022 | Ferris et al. | Dec 2011 | A1 |
20110313803 | Friend et al. | Dec 2011 | A1 |
20110320197 | Conejero et al. | Dec 2011 | A1 |
20120064879 | Panei | Mar 2012 | A1 |
20120072436 | Pierre et al. | Mar 2012 | A1 |
20120079095 | Evans et al. | Mar 2012 | A1 |
20120089659 | Halevi et al. | Apr 2012 | A1 |
20120096521 | Peddada | Apr 2012 | A1 |
20120110005 | Kuo et al. | May 2012 | A1 |
20120110436 | Adler, III et al. | May 2012 | A1 |
20120110443 | Lemonik et al. | May 2012 | A1 |
20120117626 | Yates et al. | May 2012 | A1 |
20120124306 | Abercrombie et al. | May 2012 | A1 |
20120124547 | Halbedel | May 2012 | A1 |
20120134491 | Liu | May 2012 | A1 |
20120136936 | Quintuna | May 2012 | A1 |
20120144283 | Hill et al. | Jun 2012 | A1 |
20120150888 | Hyatt et al. | Jun 2012 | A1 |
20120151551 | Readshaw et al. | Jun 2012 | A1 |
20120158908 | Luna et al. | Jun 2012 | A1 |
20120159178 | Lin et al. | Jun 2012 | A1 |
20120159310 | Chang et al. | Jun 2012 | A1 |
20120173612 | Vegesna-Venkata et al. | Jul 2012 | A1 |
20120173625 | Berger | Jul 2012 | A1 |
20120179981 | Whalin et al. | Jul 2012 | A1 |
20120185355 | Kilroy | Jul 2012 | A1 |
20120185913 | Martinez et al. | Jul 2012 | A1 |
20120192055 | Antebi et al. | Jul 2012 | A1 |
20120192086 | Ghods et al. | Jul 2012 | A1 |
20120203908 | Beaty et al. | Aug 2012 | A1 |
20120214444 | McBride et al. | Aug 2012 | A1 |
20120218885 | Abel et al. | Aug 2012 | A1 |
20120221789 | Felter | Aug 2012 | A1 |
20120226767 | Luna et al. | Sep 2012 | A1 |
20120233155 | Gallmeier et al. | Sep 2012 | A1 |
20120233205 | McDermott | Sep 2012 | A1 |
20120233543 | Vagell et al. | Sep 2012 | A1 |
20120240061 | Hillenius et al. | Sep 2012 | A1 |
20120257249 | Natarajan | Oct 2012 | A1 |
20120259964 | Lin et al. | Oct 2012 | A1 |
20120266203 | Elhadad et al. | Oct 2012 | A1 |
20120284638 | Cutler et al. | Nov 2012 | A1 |
20120284664 | Zhao | Nov 2012 | A1 |
20120291011 | Quine | Nov 2012 | A1 |
20120296790 | Robb | Nov 2012 | A1 |
20120309540 | Holme et al. | Dec 2012 | A1 |
20120311157 | Erickson et al. | Dec 2012 | A1 |
20120317239 | Mulder et al. | Dec 2012 | A1 |
20120317487 | Lieb et al. | Dec 2012 | A1 |
20120328259 | Seibert et al. | Dec 2012 | A1 |
20120331177 | Jensen | Dec 2012 | A1 |
20120331441 | Adamson | Dec 2012 | A1 |
20130007245 | Malik et al. | Jan 2013 | A1 |
20130007471 | Grab et al. | Jan 2013 | A1 |
20130007894 | Dang et al. | Jan 2013 | A1 |
20130014023 | Lee et al. | Jan 2013 | A1 |
20130042106 | Persaud et al. | Feb 2013 | A1 |
20130055127 | Saito et al. | Feb 2013 | A1 |
20130067232 | Cheung et al. | Mar 2013 | A1 |
20130073403 | Tuchman et al. | Mar 2013 | A1 |
20130080919 | Kiang et al. | Mar 2013 | A1 |
20130117337 | Dunham | May 2013 | A1 |
20130117376 | Filman et al. | May 2013 | A1 |
20130124638 | Barreto et al. | May 2013 | A1 |
20130138608 | Smith | May 2013 | A1 |
20130138615 | Gupta et al. | May 2013 | A1 |
20130159411 | Bowen | Jun 2013 | A1 |
20130163289 | Kim et al. | Jun 2013 | A1 |
20130167253 | Seleznev et al. | Jun 2013 | A1 |
20130185347 | Romano | Jul 2013 | A1 |
20130185558 | Seibert et al. | Jul 2013 | A1 |
20130191339 | Haden et al. | Jul 2013 | A1 |
20130198600 | Lockhart et al. | Aug 2013 | A1 |
20130212486 | Joshi et al. | Aug 2013 | A1 |
20130218978 | Weinstein et al. | Aug 2013 | A1 |
20130239049 | Perrodin et al. | Sep 2013 | A1 |
20130246932 | Zaveri et al. | Sep 2013 | A1 |
20130262210 | Savage et al. | Oct 2013 | A1 |
20130262862 | Hartley | Oct 2013 | A1 |
20130268480 | Dorman | Oct 2013 | A1 |
20130268491 | Chung 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 |
20130282830 | Besen et al. | Oct 2013 | A1 |
20130305039 | Gauda | Nov 2013 | A1 |
20130326344 | Masselle et al. | Dec 2013 | A1 |
20140032489 | Hebbar et al. | Jan 2014 | A1 |
20140032616 | Nack | Jan 2014 | A1 |
20140033277 | Xiao et al. | Jan 2014 | A1 |
20140033291 | Liu | Jan 2014 | A1 |
20140052939 | Tseng et al. | Feb 2014 | A1 |
20140068589 | Barak | Mar 2014 | A1 |
20140150023 | Gudorf et al. | May 2014 | A1 |
20140156373 | Roberts et al. | Jun 2014 | A1 |
20140172595 | Beddow et al. | Jun 2014 | A1 |
20140344456 | Buzbee et al. | Nov 2014 | A1 |
20140359286 | Wen et al. | Dec 2014 | A1 |
20150019723 | Kweon et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
2724521 | Nov 2009 | CA |
101997924 | Mar 2011 | CN |
102264063 | Nov 2011 | CN |
0921661 | Jun 1999 | EP |
1349088 | Oct 2003 | EP |
1528746 | May 2005 | EP |
2372574 | Oct 2011 | EP |
2610776 | Jul 2013 | EP |
2453924 | Apr 2009 | GB |
2471282 | Dec 2010 | GB |
09-101937 | Apr 1997 | JP |
2003273912 | Sep 2003 | JP |
2004310272 | Nov 2004 | JP |
2008250944 | Oct 2008 | JP |
20020017444 | Mar 2002 | KR |
20040028036 | Apr 2004 | KR |
20050017674 | Feb 2005 | KR |
20060070306 | Jun 2006 | KR |
20060114871 | Nov 2006 | KR |
20070043353 | Apr 2007 | KR |
20070100477 | Oct 2007 | KR |
20100118836 | Nov 2010 | KR |
20110074096 | Jun 2011 | KR |
20110076831 | Jul 2011 | KR |
WO-0007104 | Feb 2000 | WO |
WO-0219128 | Mar 2002 | WO |
WO-2004097681 | Nov 2004 | WO |
WO-2006028850 | Mar 2006 | WO |
WO-2007024438 | Mar 2007 | WO |
WO-2007035637 | Mar 2007 | WO |
WO-2007113573 | Oct 2007 | WO |
WO-2008076520 | Jun 2008 | WO |
WO-2011109416 | Sep 2011 | WO |
WO-2012167272 | Dec 2012 | WO |
WO-2013009328 | Jan 2013 | WO |
WO-2013013217 | Jan 2013 | WO |
WO-2013041763 | Mar 2013 | WO |
WO-2013166520 | Nov 2013 | WO |
Entry |
---|
Nancy Conner, “Google Apps: The Missing Manual”, published by O'Reilly Media, May 27, 2008. |
Nancy Conner, “Google Apps: The Missing Manual”, published by O'Reilly Media May 27, 2008. |
International Search Report and Written Opinion for PCT/US2008/012973 dated Apr. 30, 2009, pp. 1-11. |
Supplementary European Search Report European Application No. EP 08 85 8563 dated Jun. 20, 2011 pp. 1-5. |
International Search Report and Written Opinion for PCT/US2011/039126 mailed on Oct. 6, 2011, pp. 1-13. |
Partial International Search Report for PCT/US2011/041308 dated Feb. 27, 2012, pp. 1-2. |
International Search Report and Written Opinion for PCT/US2011/056472 mailed on Jun. 22, 2012, pp. 1-12. |
Langfeld L. et al., “Microsoft SharePoint 2003 Unleashed,” Chapters 11 and 15, Jun. 2004, pp. 403-404, 557-561, 578-581. |
International Search Report and Written Opinion for PCT/US2011/041308 Mailed Jul. 2, 2012, pp. 1-16. |
International Search Report and Written Opinion for PCT/US2011/060875 Mailed Oct. 30, 2012, pp. 1-10. |
“Understanding Metadata,” National Information Standards Organization, NISO Press, 2004, 20 pages. |
International Search Report and Written Opinion for PCT/US2012/056955, Applicant: Box, Inc., Mailed Mar. 27, 2013, pp. 1-11. |
International Search Report and Written Opinion for PCT/US2011/047530, Applicant: Box, Inc., Mailed Mar. 22, 2013, pp. 1-10. |
International Search Report and Written Opinion for PCT/US2012/065617, Applicant: Box, Inc., Mailed Mar. 29, 2013, 9 pages. |
International Search Report and Written Opinion for PCT/US2012/067126, Applicant: Box, Inc., Mailed Mar. 29, 2013, 10 pages. |
International Search Report and Written Opinion for PCT/US2012/063041, Applicant: Box, Inc., Mailed Mar. 29, 2013, 12 pages. |
International Search Report and Written Opinion for PCT/US2011/057938, Applicant: Box, Inc., Mailed Mar. 29, 2013, 10 pages. |
Parr, “Google Docs Improves Commenting, Adds E-mail Notifications,” Apr. 16, 2011, mashable.com, pp. 1-6. |
“Microsoft Office SharePoint 2007 User Guide,” Feb. 16, 2010, pp. 1-48. |
Lars, “35 Very Useful Online Tools for Improving your project Management and Team Collaboration,” Apr. 31, 2010, tripwiremagazine.com, pp. 1-32. |
Internet Forums, http://web.archive.org/web/20100528195550/http://en.wikipedia.org/wiki/Internet—forums, Wikipedia, May 30, 2010, pp. 1-20. |
Yahoo! Groups, http://web.archive.org/web/20090320101529/http://en.wikipedia.org/wiki/Yahoo!—Groups, Wikipedia, Mar. 20, 2009, pp. 1-6. |
Wiki, http://web.archive.org/web/20100213004936/http://en.wikipedia.org/wiki/Wiki, Feb. 13, 2010, pp. 1-16. |
Cisco, “FTP Load Balancing on ACE in Routed Mode Configuration Example,” DocWiki, Jun. 2011, 7 pages. |
Palmer, “Load Balancing FTP Servers,” BlogNav, Oct. 2008, 2 pages. |
Wayback, “Wayback machine,” Wayback, Jun. 1, 2011, 1 page. |
Google Docs, http://web.Archive.org/web/20100413105758/http://en.wikipedia.org/wiki/Google—docs, Apr. 13, 2010, 6 pages. |
Gedymin, “Cloud computing with an emphasis on Google App Engine,” Master Final Project, Sep. 2011, 146 pages. |
Exam Report for GB1316533.7, Applicant: Box, Inc. Mailed Oct. 8, 2013, 9 pages. |
Exam Report for GB1316532.9, Applicant: Box, Inc. Mailed Oct. 31, 2013, 10 pages. |
Exam Report for GB1310666.1, Applicant: Box, Inc. Mailed Aug. 30, 2013, 10 pages. |
Exam Report for GB1309209.3, Applicant: Box, Inc. Mailed Oct. 30, 2013, 11 pages. |
“QuickOffice,” Wikipedia Article (old revision), published May 9, 2012, Wikipedia Foundation, 2 pages. |
“Quickoffice Enhances Android Mobile office Application for Improved Productivity on latest Smartphone and Table Devices,” QuickOffice Press Release, Nov. 21, 2011, QuickOffice Inc., 2 pages. |
“PaperPort,” Wikipedia article (old revision), published May 19, 2012, Wikipedia Foundation, 2 pages. |
“PaperPort Professional 14,” PC Mag. Com review, published Feb. 2012, Ziff Davis, Inc., 8 pages. |
“Conceptboard”, One-Step Solution for Online Collaboration, retrieved from websites http://conceptboard.com and https://www.youtube.com/user/ConceptboardApp?feature=watch, printed on Jun. 13, 2013, 9 pages. |
“How-to Geek, How to Sync Specific Folders With Dropbox,” downloaded from the internet http://www.howtogeek.com, Apr. 23, 2013, 5 pages. |
Exam Report for EP13158415.3, Applicant: Box, Inc. Mailed Jun. 4, 2013, 8 pages. |
Exam Report for GB1300188.8, Applicant: Box, Inc. Mailed May 31, 2013, 8 pages. |
Exam Report for GB1306011.6, Applicant: Box, Inc. Mailed Apr. 18, 2013, 8 pages. |
International Search Report and Written Opinion for PCT/US2010/070366, Applicant: Box, Inc., Mailed Apr. 24, 2013, 10 pages. |
International Search Report and Written Opinion for PCT/US2013/020267, Applicant: Box, Inc., Mailed May 7, 2013, 10 pages. |
International Search Report and Written Opinion for PCT/US2013/023889, Applicant: Box, Inc., Mailed Jun. 24, 2013, 13 pages. |
International Search Report and Written Opinion for PCT/US2013/029520, Applicant: Box, Inc., Mailed Jun. 26, 2013, 10 pages. |
International Search Report and Written Opinion for PCT/US2013/034662, Applicant: Box, Inc., Mailed May 31, 2013, 10 pages. |
International Search Report and Written Opinion for PCT/US2013/035404, Applicant: Box, Inc., Mailed Jun. 26, 2013, 13 pages. |
Exam Report for EP13168784.0, Applicant: Box, Inc. Mailed Nov. 21, 2013, 7 pages. |
Exam Report for EP13185269.1, Applicant: Box, Inc. Mailed Jan. 28, 7 pages. |
Exam Report for GB1311417.8, Applicant: Box, Inc. Mailed Dec. 20, 2013, 5 pages. |
Exam Report for GB1312095.1, Applicant: Box, Inc. Mailed Dec. 12, 2013, 7 pages. |
Exam Report for GB1312874.9, Applicant: Box, Inc. Mailed Dec. 20, 2013, 11 pages. |
Exam Report for GB1316971.9, Applicant: Box, Inc. Mailed Nov. 26, 2013, 10 pages. |
Exam Report for GB1317600.3, Applicant: Box, Inc. Mailed Nov. 21, 2013, 8 pages. |
Exam Report for GB1318373.6, Applicant: Box, Inc. Mailed Dec. 17, 2013, 4 pages. |
Exam Report for GB1320902.8, Applicant: Box, Inc. Mailed Dec. 20, 2013, 4 pages. |
Patent Court Document of Approved Judgment for GB0602349.3 and GB0623571.7; Mar. 3, 2009, 17 pages. |
Exam Report for GB1308842.2, Applicant: Box, Inc. Mailed Mar. 10, 2014, 4 pages. |
Exam Report for GB1314771.5, Applicant: Box, Inc. Mailed Feb. 17, 2014, 7 pages. |
Partial Search Report for EP131832800, Applicant: Box, Inc. Mailed May 8, 2014, 5 pages. |
Search Report for EP141509422, Applicant: Box, Inc. Mailed May 8, 2014, 7 pages. |
Tulloch et al., “Windows Vista Resource Kit,” Apr. 8, 2007, Microsoft Press, XP055113067, 6 pages. |
“Revolving sync conflicts; frequently asked questions,” Microsoft Tech Support, Jul. 16, 2012, retrieved from the Internet: http://web.archive.org/web, 2 pages. |
Pyle et al., “How to enable Event logging for Offline Files (Client Side Caching) in Windows Vista,” Feb. 18, 2009, retrieved from the internet: http://blogs.technet.com, 3 pages. |
Duffy, “The Best File-Syncing Services,” pcmag.com, retrieved from the internet: http://www.pcmag.com, Sep. 28, 2012, 7 pages. |
“Troubleshoot sync problems,” Microsoft Tech Support: May 2, 2012, retrieved from the internet, http://web. Archive.org/web, 3 pages. |
Exam Report for GB1318792.7, Applicant: Box, Inc. Mailed May 22, 2014, 2 pages. |
Exam Report for EP13177108.1, Applicant: Box, Inc. Mailed May 26, 2014, 6 pages. |
Exam Report for GB1410569.6 Applicant: Box, Inc. Mailed Jul. 11, 2014, 9 pages. |
Sommerer, “Presentable Document Format: Improved On-demand PDF to HTML Conversion,” retrieved from the internet, http://research.microsoft.com, Nov. 2004, 8 pages. |
Extended Search Report for EP131832800, Applicant: Box, Inc. Mailed Aug. 25, 2014, 7 pages. |
Extended Search Report for EP141509422, Applicant: Box, Inc. Mailed Aug. 26, 2014, 12pages. |
Search Report for EP 13189144.2 Applicant: Box, Inc. Mailed Sep. 1, 2014, 9 pages. |
Exam Report for GB1312874.9 Applicant: Box, Inc. Mailed Sep. 26, 2014, 2 pages. |
Exam Report for GB1415126.0 Applicant: Box, Inc. Mailed Oct. 2, 2014, 8 pages. |
Exam Report for GB1415314.2 Applicant: Box, Inc. Mailed Oct. 7, 2014, 6 pages. |
Exam Report for GB1309209.3 Applicant: Box, Inc. Mailed Oct. 7, 2014, 3 pages. |
Exam Report for GB1315232.7 Applicant: Box, Inc. Mailed Oct. 9, 2014, 5 pages. |
Exam Report for GB1318789.3 Applicant: Box, Inc. Mailed Oct. 30, 2014, 6 pages. |
Microsoft Windows XP Professional Product Documentation: How Inheritance Affects File and Folder Permissions, Apr. 11, 2014, 2 pages. |
Exam Report for GB1317393.5 Applicant: Box, Inc. Mailed Nov. 7, 2014, 6 pages. |
Exam Report for GB1311417.8 Applicant: Box, Inc. Mailed Nov. 7, 2014, 2 pages. |
Exam Report for GB1311421.0 Applicant: Box, Inc. Mailed Nov. 7, 2014, 4 pages. |
“Average Conversion Time for a D60 RAW file?” http://www.dpreview.com, Jul. 22, 2002, 4 pages. |
Burns, “Developing Secure Mobile Applications for Android,” Oct. 2008, Version 1.0, 1-28 pages. |
Comes, “MediaXchange User's Manual,” Version 1.15.15, Feb. 1, 2009, pp. 1-90. |
Exam Report for GB1312264.3, Applicant: Box, Inc. Mailed Mar. 24, 2014, 7 pages. |
John et al., “Always Sync Support Forums—View topic—Allway sync funny behavior,” Allway Sync Support Forum at http://sync-center.com, Mar. 28, 2011, XP055109680, 2 pages. |
Search Report for EP 11729851.3, Applicant: Box, Inc. Mailed Feb. 7, 2014, 9 pages. |
Search Report for EP14151588.2, Applicant: Box, Inc. Mailed Apr. 15, 2014, 12 pages. |
Search Report for EP14153783.7, Applicant: Box, Inc. Mailed Mar. 24, 2014, 7 pages. |
Search Report for EP13187217.8, Applicant: Box, Inc. Mailed Apr. 15, 2014, 12 pages. |
Rao, “Box Acquires Crocodoc to Add HTML5 Document Converter and Sleek Content Viewing Experience to Cloud Storage Platform,” retrieved from the internet, http://techcrunch.com, May 9, 2013, 8 pages. |
Walker, “PDF.js project meeting notes,” retrieved from the internet, http://groups.google.com, May 15, 2014, 1 page. |
Sommerer, “Presentable Document Format: Improved On-demand PDF to HTML Conversion,” retrieved from the internet, http://research.microsoft.com, 8 pages. |
“Tulsa TechFest 2012—Agenda,” retrieved from the website, http://web.archive.org, Oct. 2, 2012, 2 pages. |
Delendik, “Evolving with Web Standards—The Story of PDF.JS,” retrieved from the internet, http://people.mozilla.org, Oct. 12, 2012, 36 pages. |
Delendik, “My PDF.js talk slides from Tulsa TechFest,” retrieved from the internet, http://twitter.com, Oct. 12, 2012, 2 pages. |
Cohen, “Debating the Definition of Cloud Computing Platforms,” retrieved from the internet, http:://forbes.com, Feb. 3, 2014, 7 pages. |
Exam Report for GB1316685.5 Applicant: Box, Inc. Mailed Feb. 17, 2015, 5 pages. |
Exam Report for EP 13185269.1, Applicant: Box, Inc. Mailed Feb. 13, 2015, 8 pages. |
Exam Report for GB1316532.9 Applicant: Box, Inc. Mailed Mar. 27, 2015, 6 pages. |
Burney, “How to Move Document from Your Computer to Your iPad and Back Again,” May 31, 2011, 3 pages. |
User's Guide for SMART Board Software for Windows, published Dec. 2004, 90 pages. |
Zambonini et al., “Automated Measuring of Interaction with User Interfaces,” Published as WO2007113573 Oct. 2007, 19 pages. |
Exam Report for GB1309209.3 Applicant: Box, Inc. Mailed Jan. 19, 2015, 6 pages. |
“Agilewords—How to Request Approval,” YouTube, http://www.youtube.com/watch?v=3-Ov3DYNN3Q, Jan. 31, 2011, 2 pages. |
“Agilewords—Features, Powerful Features Yet Simple,” Jun. 1, 2011, http://web.archive.org/web/20110601223756/http://agilewords.com/product/features, 3 pages. |
Number | Date | Country | |
---|---|---|---|
20130080919 A1 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
61538782 | Sep 2011 | US |