Dynamic Metadata Request Forms in Cloud Collaboration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud-based collaboration environments limit the flexibility and functionality by not allowing users to specify metadata for requested content items, restricting the ability to customize metadata collection and assignment.

Innovation Solution

A method and system that enable users to define and request specific metadata for content items, allowing users to select and provide values for metadata tags, with the system generating a content request and form definition in JSON format, which is dynamically rendered on the submitter's device for metadata and content submission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If predefined metadata is used for content items, then system complexity is reduced and ease of operation is improved, but adaptability and versatility are limited

Engineering Contradiction:
Improvemetadata customizationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments metadata collection into two distinct parts: predefined system metadata and custom user-defined metadata. This allows the system to maintain simple predefined metadata structures while adding customizable metadata fields without increasing overall system complexity. Users can define their own metadata schemas independently of the core system metadata.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The metadata schema becomes dynamic and adaptable rather than static. The system allows metadata definitions to be modified, added, or customized by users based on specific content items or workflows. This dynamic approach enables the system to adapt to different collaboration needs without requiring complete system redesign.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If users can define custom metadata, then adaptability and versatility are improved, but ease of operation deteriorates due to increased complexity

Engineering Contradiction:
Improvemetadata specification capabilityVSAvoiduser operation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system performs preliminary action by providing pre-configured metadata templates and schemas that users can select from. This allows users to quickly set up metadata collection without having to design everything from scratch, reducing the operational burden while maintaining customization capability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Users are empowered to self-configure their own metadata schemas and definitions according to their specific needs. The system provides tools that allow users to independently define, modify, and manage their metadata requirements without requiring complex system administrator intervention or deep technical knowledge.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If flexible metadata requests are implemented, then adaptability is improved, but device complexity increases due to form generation and validation requirements

Engineering Contradiction:
Improvecontent request flexibilityVSAvoidform management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal form generation mechanism that handles multiple metadata schemas and content types through a single unified interface. This multi-functional approach allows the same form infrastructure to support diverse metadata requirements without requiring separate complex systems for each metadata type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system manages complexity by parameterizing metadata definitions rather than hardcoding specific metadata structures. By changing parameters such as metadata field names, types, and validation rules, the system can adapt to different content requirements while reusing the same underlying form generation and validation infrastructure.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11836196B2Methods and systems for making file requests in a collaboration environment
Publication Date: 2023.12.05 BOX INC
  • US11836196B2 patent drawing
  • US11836196B2 patent drawing
  • US11836196B2 patent drawing

AI summary

Embodiments of the disclosure provide systems and methods for obtaining content for a workspace of a collaboration environment. According to one embodiment, a method for requesting and obtaining a content item for a workspace of a collaboration environment can comprise generating, by a cloud-based collaboration environment system, a content request identifying the content item and metadata for the content item. The requested metadata for the content item can be defined by a requestor of the content item and the content item and the metadata for the content item can be requested from a submitter. The generated content request can be provided by the cloud-based collaboration environment system to a computing device associated with the submitter. In response to the provided request, the content item and the requested metadata for the content item can be obtained by the cloud-based collaboration environment system from the computing device associated with the submitter.