# US 2020/0287946 A1 · Configurable metadata-based automation and content classification architecture for cloud-based collaboration platforms

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0287946 A1
- Document ID: US20200287946A1
- Status: Published application
- Kind: A1
- Application number: 16/883,645
- Filed: 2020-05-26
- Published: 2020-09-10
- Earliest claimed: 2014-08-29
- Assignees: Box, Inc.
- Applicants: Box, Inc.
- Inventors: Annie Pearl; James Huamonte; Brian Tran; Tiffany Low; Pierre-Alexandre Masse; Ted Blosser
- Web page: https://patentgrep.com/patent/US20200287946A1

## CPC

- H04L 65/403: Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15)
- G06F 16/11: File system administration, e.g. details of archiving or snapshots (error detection or correction of the data by redundancy in operations G06F11/14)
- G06F 16/14: Details of searching files based on file metadata
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04W 4/02: Services making use of location information
- H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Scalable architectures, systems, and services are provided herein for generating jobs by applying user-specified metadata rules to metadata events. More specifically, the scalable architecture described herein uses metadata to drive automations and/or polices in a cloud-based environment. In one embodiment, the architecture integrates a metadata service with an event-based automation engine to automatically trigger polices and/or automations based on metadata and/or changes in metadata changes. The metadata service can include customizable and/or pre-build metadata templates which can be used to automatically apply a metadata framework (e.g., particular fields) to files based on, for example, the upload or placement of a particular file in a particular folder. The architecture also provides for advanced metadata searching and data classification.

## Claims

### Claim at position 1

1-25. (canceled)

### Claim 26

A method for processing a metadata event in a collaborative cloud-based environment, the method comprising:
monitoring, by a server of the collaborative cloud-based environment, metadata associated with each of a plurality of work items in a work space of the collaborative cloud-based environment;
detecting, by the server of the collaborative cloud-based environment, a change in the metadata associated with a particular work item in the collaborative cloud-based environment based on the monitoring of metadata associated with each of the plurality of work items, the change in the metadata resulting from an action performed on the particular work item by a collaborator of the collaborative cloud-based environment;
generating, by the server of the collaborative cloud-based environment, a job including a set of parameters describing work to be executed in the collaborative cloud-based environment with respect to the particular work item based on the detected change in the metadata associated with the particular work item; and
distributing, by the server of the collaborative cloud-based environment, the generated job into a particular job queue to be processed by one or more worker machines in a distributed computing cluster associated with the collaborative cloud-based environment, the particular job queue comprising one of a plurality of job queues.

### Claim 27 (depends on 26)

The method of claim 26, further comprising selecting, by the server of the collaborative cloud-based environment, the particular job queue based on a type of the generated job.

### Claim 28 (depends on 27)

The method of claim 27, wherein the particular job queue is designated for jobs of a particular job type, and wherein the particular job queue is serviced by one or more worker machines configured to process the particular job type.

### Claim 29 (depends on 26)

The method of claim 26, wherein the generated job is performed by the one or more worker machines processing the job.

### Claim 30 (depends on 26)

The method of claim 26, further comprising injecting, by the server of the collaborative cloud-based environment, callback information into the generated job prior to distributing the job into the particular job queue, the callback information configured to cause a worker machine to transmit notifications to the job manager system while processing the job.

### Claim 31 (depends on 26)

The method of claim 26, further comprising injecting, by the server of the collaborative cloud-based environment, a token into the job before distributing the job to the particular job queue, wherein the token is used by the one or more worker machines when processing the job and follows any additional job requests initiated by the one or more worker machines, and wherein additional job requests received by the job manager system are not generated into jobs or distributed to job queues if the token has been received by the job manager more than a threshold number of times.

### Claim 32 (depends on 26)

The method of claim 26, wherein the generated job comprises a workflow.

### Claim 33

A system comprising:
a processor; and
a memory coupled with and readable by the processor and storing therein a set of instructions which, when executed by the processor, causes the processor to process a metadata event in a collaborative cloud-based environment by:
monitoring metadata associated with each of a plurality of work items in a work space of the collaborative cloud-based environment;
detecting a change in the metadata associated with a particular work item in the collaborative cloud-based environment based on the monitoring of metadata associated with each of the plurality of work items, the change in the metadata resulting from an action performed on the particular work item by a collaborator of the collaborative cloud-based environment;
generating a job including a set of parameters describing work to be executed in the collaborative cloud-based environment with respect to the particular work item based on the detected change in the metadata associated with the particular work item; and
distributing the generated job into a particular job queue to be processed by one or more worker machines in a distributed computing cluster associated with the collaborative cloud-based environment, the particular job queue comprising one of a plurality of job queues.

### Claim 34 (depends on 33)

The system of claim 33, wherein the instructions further cause the processor to select the particular job queue based on a type of the generated job.

### Claim 35 (depends on 34)

The system of claim 34, wherein the particular job queue is designated for jobs of a particular job type, and wherein the particular job queue is serviced by one or more worker machines configured to process the particular job type.

### Claim 36 (depends on 33)

The system of claim 33, wherein the one or more worker machines perform processing of the job.

### Claim 37 (depends on 33)

The system of claim 33, the instructions further cause the processor to inject callback information into the generated job prior to distributing the job into the particular job queue, the callback information configured to cause a worker machine to transmit notifications to the job manager system while processing the job.

### Claim 38 (depends on 33)

The system of claim 33, the instructions further cause the processor to inject a token into the job before distributing the job to the particular job queue, wherein the token is used by the one or more worker machines when processing the job and follows any additional job requests initiated by the one or more worker machines, and wherein additional job requests received by the job manager system are not generated into jobs or distributed to job queues if the token has been received by the job manager more than a threshold number of times.

### Claim 39 (depends on 33)

The system of claim 33, wherein the generated job comprises a workflow.

### Claim 40

A non-transitory, computer-readable medium comprising a set of instructions stored therein which, when executed by a processor, causes the processor to process a metadata event in a collaborative cloud-based environment by:
monitoring metadata associated with each of a plurality of work items in a work space of the collaborative cloud-based environment;
detecting a change in the metadata associated with a particular work item in the collaborative cloud-based environment based on the monitoring of metadata associated with each of the plurality of work items, the change in the metadata resulting from an action performed on the particular work item by a collaborator of the collaborative cloud-based environment;
generating a job including a set of parameters describing work to be executed in the collaborative cloud-based environment with respect to the particular work item based on the detected change in the metadata associated with the particular work item; and
distributing the generated job into a particular job queue to be processed by one or more worker machines in a distributed computing cluster associated with the collaborative cloud-based environment, the particular job queue comprising one of a plurality of job queues.

### Claim 41 (depends on 40)

The non-transitory, computer-readable medium of claim 40, wherein the instructions further cause the processor to select the particular job queue based on a type of the generated job.

### Claim 42 (depends on 41)

The non-transitory, computer-readable medium of claim 41, wherein the particular job queue is designated for jobs of a particular job type, and wherein the particular job queue is serviced by one or more worker machines configured to process the particular job type.

### Claim 43 (depends on 40)

The non-transitory, computer-readable medium of claim 40, wherein the one or more worker machines perform processing of the job.

### Claim 44 (depends on 40)

The non-transitory, computer-readable medium of claim 40, the instructions further cause the processor to inject callback information into the generated job prior to distributing the job into the particular job queue, the callback information configured to cause a worker machine to transmit notifications to the job manager system while processing the job.

### Claim 45 (depends on 40)

The non-transitory, computer-readable medium of claim 40, the instructions further cause the processor to inject a token into the job before distributing the job to the particular job queue, wherein the token is used by the one or more worker machines when processing the job and follows any additional job requests initiated by the one or more worker machines, and wherein additional job requests received by the job manager system are not generated into jobs or distributed to job queues if the token has been received by the job manager more than a threshold number of times.
