Abstract: A metadata-driven file system prioritizes the distribution of files across different storage devices based on arbitrary file metadata matching to different file usage scenarios defined within one or more workflows or taxonomies. The file metadata may be tagged with different key-value pairs from the defined workflows or taxonomies. Upon receiving a file or file access request, the metadata-driven file system matches the file metadata to a key-value pair combination of the taxonomy, and stores the file to a storage device that is selected using a storage rule that is defined for the matching key-value pair combination. The taxonomy may be defined with other programmatic file operations that the metadata-driven file system may perform against files with matching metadata.

Abstract: Disclosed is a collaboration system that synchronizes what is seen and heard by all participants to a conference such that participant input provided during the conference are seen and heard with respect to the same state of a presented asset. Additionally, the collaboration system may monitor the conference, may extract a first participant contribution prior to presentation of a first asset in the conference and a second participant contribution that is made during a particular interval of the conference when the first asset is presented. The collaboration system may link the second participant contribution to the first asset, may receive a request for the first asset after the conference has concluded, and may provide the first asset with the second participant contribution in response to the request.

Abstract: Disclosed is a collaboration system that synchronizes what is seen and heard by all participants to a conference such that participant input provided during the conference are seen and heard with respect to the same state of a presented asset. Additionally, the collaboration system may monitor the conference, may extract a first participant contribution prior to presentation of a first asset in the conference and a second participant contribution that is made during a particular interval of the conference when the first asset is presented. The collaboration system may link the second participant contribution to the first asset, may receive a request for the first asset after the conference has concluded, and may provide the first asset with the second participant contribution in response to the request.

Abstract: Disclosed is a collaboration system that synchronizes what is seen and heard by all participants to a conference such that participant input provided during the conference are seen and heard with respect to the same state of a presented asset. Additionally, the collaboration system may monitor the conference, may extract a first participant contribution prior to presentation of a first asset in the conference and a second participant contribution that is made during a particular interval of the conference when the first asset is presented. The collaboration system may link the second participant contribution to the first asset, may receive a request for the first asset after the conference has concluded, and may provide the first asset with the second participant contribution in response to the request.

Abstract: A metadata-driven file system prioritizes the distribution of files across different storage devices based on arbitrary file metadata matching to different file usage scenarios defined within one or more workflows or taxonomies. The file metadata may be tagged with different key-value pairs from the defined workflows or taxonomies. Upon receiving a file or file access request, the metadata-driven file system matches the file metadata to a key-value pair combination of the taxonomy, and stores the file to a storage device that is selected using a storage rule that is defined for the matching key-value pair combination. The taxonomy may be defined with other programmatic file operations that the metadata-driven file system may perform against files with matching metadata.

Abstract: A metadata-driven file system prioritizes the distribution of files across different storage devices based on arbitrary file metadata matching to different file usage scenarios defined within one or more workflows or taxonomies. The file metadata may be tagged with different key-value pairs from the defined workflows or taxonomies. Upon receiving a file or file access request, the metadata-driven file system matches the file metadata to a key-value pair combination of the taxonomy, and stores the file to a storage device that is selected using a storage rule that is defined for the matching key-value pair combination. The taxonomy may be defined with other programmatic file operations that the metadata-driven file system may perform against files with matching metadata.