Content management system
AssigneeAmazon Technologies, Inc.
InventorsKenny Xie, Maan Shamoon, Amanda Josephine Sambawa, Joseph David Wolf
Life of this patent
Estimating the term…
Abstract
A content management system is provided. The content management system (CMS) uses a unique content modeling architecture using nested, reusable data entities, as well as a method for constructing a system around those entities to enable features and automation within the CMS. The solution's novelty lies in (1) a mechanism for efficiently and robustly governing, triggering, and enabling complex processes (e.g., translation workflows, publication workflows) for content within a CMS by dynamically associating system models with the content, and (2) enabling schema consistency and the creation of flexibly typed content via “model set” entities that aggregate one or more reusable content schemas.
Claims16
A content management system comprising:
- memory that stores computer-executable instructions;
- and
- one or more processors configured to access the memory and execute the computer-executable instructions to:
- generate, by the content management system and based on a first input to a user interface of the content management system, a first field entity including at least one of:
- an identifier, a data type, or a validation;
- store the first field entity in the content management system;
- generate, by the content management system and based on a second input to a user interface of the content management system, a first model entity and a second model entity that reference the first field entity, wherein the first model entity and the second model entity include at least one of:
- a system model, a metadata model, and a content model, wherein the system model includes fields associated with automated workflows performed by the content management system, wherein the metadata model includes fields defining properties and attributes associated with content, and the content model includes fields that are readable within first content;
- store the first model entity and the second model entity in the content management system, wherein the first model entity and the second model entity are stored as reusable entities that are referenceable across different model sets;
- generate, by the content management system and based on a third input to a user interface of the content management system, a first model set referencing the first model entity and the second model entity;
- receive, by the content management system and via the user interface, a first request to publish first content, the first request indicating that the first model set is to be used with the first content;
- receive, by the content management system and via the user interface, a second request to publish second content, the second request including a selection of at least one of:
- the first model set, the first model entity, or the first field entity via the user interface;
- publish the first content via the content management system, wherein the first content is presented via the user interface of the content management system;
- and
- publish the second content via the content management system leveraging the at least one of the:
- first model set, the first model entity, or the first field entity stored in the content management system by reference rather than re-generating the at least one of the:
- first model set, the first model entity, or the first field entity for the second content, wherein the second content is presented via the user interface of the content management system.
A content management system comprising:
- memory that stores computer-executable instructions;
- and
- one or more processors configured to access the memory and execute the computer-executable instructions to:
- generate, by the content management system and based on a first input to a user interface of the content management system, a first field entity including at least one of:
- an identifier, a data type, or a validation;
- store the first field entity in the content management system;
- generate, by the content management system and based on a second input to the user interface of the content management system, a first model entity and a second model entity that reference the first field entity;
- generate, by the content management system and based on a third input to the user interface of the content management system, a first model set including the first model entity and the second model entity;
- store the first model entity and the second model entity in the content management system, wherein the first model entity and the second model entity are stored as reusable entities that are referenceable across different model sets;
- receive, by the content management system and via the user interface, a first request to publish first content, the first request indicating that the first model set is to be used with the first content;
- receive, by the content management system and via the user interface, a second request to publish second content, the second request including a selection of at least one of:
- the first model set, the first model entity, or the first field entity via the user interface;
- publish the first content via the content management system, wherein the first content is presented via the user interface of the content management system;
- and
- publish the second content via the content management system leveraging the at least one of the:
- first model set, the first model entity, or the first field entity stored in the content management system rather than re-generating the at least one of the:
- first model set, the first model entity, or the first field entity for the second content, wherein the second content is presented via the user interface of the content management system.
A method comprising:
- generating, by a content management system and based on a first input to a user interface of the content management system, a first field entity including at least one of:
- an identifier, a data type, or a validation;
- storing the first field entity in the content management system;
- generating, by the content management system and based on a second input to a user interface of the content management system, a first model entity and a second model entity that reference the first field entity;
- storing the first model entity and the second model entity in the content management system, wherein the first model entity and the second model entity are stored as reusable entities that are referenceable across different model sets;
- generating, by the content management system and based on a third input to a user interface of the content management system, a first model set referencing the first model entity and the second model entity;
- receiving, via a user interface of the content management system, a first request to publish first content, the first request indicating that the first model set is to be used with the first content;
- receiving, by the content management system and via the user interface, a second request to publish second content, the second request including a selection of at least one of:
- the first model set, the first model entity, or the first field entity via the user interface;
- publishing, by the content management system, the first content, wherein the first content is presented via the user interface of the content management system;
- and
- publishing the second content via the content management system leveraging the at least one of the:
- first model set, the first model entity, or the first field entity stored in the content management system rather than re-generating the at least one of the:
- first model set, the first model entity, or the first field entity for the second content, wherein the second content is presented via the user interface of the content management system.
Dependencies are inferred from the claim text.