Abstract: Embodiments of the present disclosure are directed to archiving content items of a cloud-based collaboration environment. According to one embodiment, a method for applying activity-based legal holds to archived content in a cloud-based collaboration environment can comprise receiving a request to apply a legal hold to a user of the cloud-based collaboration environment, wherein the set of content items are stored in an archive, identifying, by the processor of the cloud-based collaboration environment, the set of content items based on activity of the user and applying a retention marker identifying the legal hold to each content item of the identified set of content items.

Abstract: Archiving content items of a cloud-based collaboration environment can comprise receiving a request to create an archive and creating an internal platform user. The internal platform user is not associated with an actual user of the cloud-based collaboration environment. An archive folder associated with an archive folder identifier and comprising a container for archived content can be created, the internal platform user can be assigned as an owner of the archive folder, the archive folder can be marked as an archive and the archive folder identifier can be returned in response to the request to create an archive.

Abstract: Methods, systems, and computer program products for a content management system. Embodiments operate within or in conjunction with such a content management system. The content management system stores content objects for access by various collaborators, including extra-system collaborators. A user of the content management system configures extra-enterprise shared link URLs that permit the extra-system collaborators to access shared content objects over an Internet connection. A shared link event graph data structure is formed based on access requests over the extra-enterprise shared link URLs. An interactive user interface module is generated by processing a shared link report query over the shared link event graph data structure to select a subject set of the extra-enterprise shared link URLs, and to generate a data set of the interactive user interface module based at least in part on results from the query. A user interacts with the interactive user interface module to generate insights.

Abstract: Methods, systems, and computer program products for a content management system. Embodiments operate within or in conjunction with such a content management system. The content management system stores content objects for access by various collaborators, including extra-system collaborators. A user of the content management system configures extra-enterprise shared link URLs that permit the extra-system collaborators to access shared content objects over an Internet connection. A shared link event graph data structure is formed based on access requests over the extra-enterprise shared link URLs. An interactive user interface module is generated by processing a shared link report query over the shared link event graph data structure to select a subject set of the extra-enterprise shared link URLs, and to generate a data set of the interactive user interface module based at least in part on results from the query. A user interacts with the interactive user interface module to generate insights.

Abstract: Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.

Abstract: Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.

Abstract: Methods, systems, and computer program products for a content management system. Embodiments operate within or in conjunction with such a content management system. The content management system stores content objects for access by various collaborators, including extra-system collaborators. A user of the content management system configures extra-enterprise shared link URLs that permit the extra-system collaborators to access shared content objects over an Internet connection. A shared link event graph data structure is formed based on access requests over the extra-enterprise shared link URLs. An interactive user interface module is generated by processing a shared link report query over the shared link event graph data structure to select a subject set of the extra-enterprise shared link URLs, and to generate a data set of the interactive user interface module based at least in part on results from the query. A user interacts with the interactive user interface module to generate insights.

Abstract: Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.

Abstract: Systems and methods for maintaining and updating file system shadows by a synchronization client of a cloud-based platform. In some embodiments, an executor of the synchronization client can execute an action on an item in the local file system which changes the state of the item from an old state to a new state. The synchronization client updates the file system shadows with the new state of the item via an interface to facilitate generation of a synchronization event for the change to the item, that would otherwise go undetected if the change to the item was immediately reversed. In some embodiments, methods for providing shadow consistency and enhancing concurrent access to shadows are implemented by the synchronization client in maintaining and updating the file system shadows.

Abstract: Systems and methods for document management classification, capture and search are disclosed. In one embodiment, a system for document management may include a document taxonomy library comprising a plurality of document taxonomies; a document create module comprising a document metadata repository and a document template/clause repository; a document capture module comprising a metadata repository, an image repository, and a document capture workflow; and a document communicate module comprising an extracted metadata repository. In one embodiment, the document create module creates a document using a document taxonomy from the document taxonomy library, the document metadata repository, and the template clause/repository; the document capture module captures metadata from the document based on a document taxonomy associated with the document; and the document communicate module stores extracted metadata from the document in the extracted metadata repository.

Abstract: Enterprise administrators in a cloud-based environment including a cloud-based server and a repository can selectively impose permissions on items (e.g., files and folders) marked for synchronization (“sync items”). The sync items can be synchronized with the client devices of users by downloading the items along with the permission attributes from the cloud-based server. However, the permissions on those sync items means that any unpermitted changes to the local copies of the sync items do not get uploaded to the cloud-based server. A synchronization client on the client devices detects any changes made locally to the sync items that are not consistent with the permission attributes, and repairs those changes so that the sync items are restored to their most recent states. This ensures that any unauthorized changes made to sync items remain local and do not propagate by the synchronization process to other users.

Abstract: Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.

Abstract: Techniques for monitoring local and/or remote file systems by a synchronization component (e.g., client/server) of a cloud-based platform are disclosed. In some embodiments, a method of building synchronization events by a synchronization component (e.g., a synchronization server/client) includes obtaining a set of items that have been changed and their new states and retrieving last known states of the set of items that are stored in a reference snapshot inside a filesystem scanner. The method further includes generating differences between the new states and the last known states of the set of items as item changes and utilizing information provided by the item changes to translate the item changes into synchronization events for execution on the opposing file system. A method of handling failed synchronization events by a synchronization component of the cloud-based platform by collapsing a subsequent event with the failed synchronization event is also disclosed.

Abstract: Enterprise administrators in a cloud-based environment including a cloud-based server and a repository can selectively impose permissions on items (e.g., files and folders) marked for synchronization (“sync items”). The sync items can be synchronized with the client devices of users by downloading the items along with the permission attributes from the cloud-based server. However, the permissions on those sync items means that any unpermitted changes to the local copies of the sync items do not get uploaded to the cloud-based server. A synchronization client on the client devices detects any changes made locally to the sync items that are not consistent with the permission attributes, and repairs those changes so that the sync items are restored to their most recent states. This ensures that any unauthorized changes made to sync items remain local and do not propagate by the synchronization process to other users.

Abstract: Enterprise administrators in a cloud-based environment including a cloud-based server and a repository can selectively impose permissions on items (e.g., files and folders) marked for synchronization (“sync items”). The sync items can be synchronized with the client devices of users by downloading the items along with the permission attributes from the cloud-based server. However, the permissions on those sync items means that any unpermitted changes to the local copies of the sync items do not get uploaded to the cloud-based server. A synchronization client on the client devices detects any changes made locally to the sync items that are not consistent with the permission attributes, and repairs those changes so that the sync items are restored to their most recent states. This ensures that any unauthorized changes made to sync items remain local and do not propagate by the synchronization process to other users.

Abstract: A new cultivar of Panicum plant named ‘Noneulby’ that is characterized by its compact, slightly broad and upright plant habit, its average of 76 cm in height and 61 cm in width in the landscape, its foliage that is blue in color, its flowers that are silver in color and changing to purple in color, and its flowers that are held partially above the foliage (about 1/3).

Abstract: A new cultivar of Panicum plant named ‘Nonlufht’ that is characterized by its plant height of 1.98 m (to top of inflorescence) and plant width of 1.83 m (at the widest point), its vase-shape with arching foliage at the top with a tight base, its green foliage, and its silver flowers.

Abstract: A new cultivar of Panicum plant named ‘Nondee’ that is characterized by its rounded and upright plant habit with nonlodging clumping foliage with upright flowering spikes above foliage, its average of 61 cm in foliage height, 1.2 m in inflorescence height and 1.2 m in spread in the landscape, its foliage that green in color and becomes flushed with purple in autumn, its flowering period from August to October in Michigan, and its flowers that are maroon-purple in color.

Abstract: A new cultivar of Panicum plant named ‘Nontlobg’ that is characterized by its average plant height of 2.1 m and plant width of 0.9 m in width, its upright, vase-shaped, and tight plant habit, its narrow base, its broad, green foliage, and its flowers that are rose in color that turn silvery in color.

Abstract: A new cultivar of Panicum plant named ‘Nonesory’ that is characterized by its average of 0.91 m in height (including inflorescences) and 0.69 m in spread as grown in the landscape for 3 years, its compact and vase shaped plant habit with nonlodging clumping foliage with upright flowering spikes above foliage, its foliage that green in color, its flowering period from August to October in Michigan, and its flowers that are deep rose in color.