Systems and methods for managing and publishing managed content

• US 10,455,020 B2
• Filed: 02/27/2017
• Issued: 10/22/2019
• Est. Priority Date: 03/11/2013
• Status: Active Grant

• Current Assignee: Maven Coalition, Inc. (theMaven, Inc.)
• Original Assignee: Say Media, Inc. (theMaven, Inc.)
• Inventors: Lerman, David
• Primary Examiner(s): Higa, Brendan Y
• Application Number:
  US15/444,221
• Publication Number:
  US 20170171312A1
• Time in Patent Office: 967 Days
• CPC Class Codes: G06F 16/14 Details of searching files based on file metadata
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: H04L 51/06 Message adaptation to terminal or network requirements
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/303 Terminal profiles

Abstract

Systems and methods for content management server systems configured to manage and publish managed content in accordance with embodiments of the invention are disclosed. In one embodiment, a versioned content management server system, includes a processor, a versioned content management application, managed content, wherein managed content includes content and content version metadata, wherein the versioned content management application configures the processor to receive updated content, locate managed content based on the received updated content, determine version data based on a portion of the located managed content, the received updated content, update the content version metadata data, associate the updated version content data with the managed content, receive a request for content, identify a portion of the managed content that corresponds to the requested content, retrieve the identified portion of the managed content, and transmit the retrieved portion of the managed content.

Claims

1. A versioned content management server system, comprising:

a processor;

a content storage;

a memory connected to the processor and configured to store a versioned content management application, wherein the versioned content management application configures the processor to;

receive managed content comprising content and content version metadata;

store the managed content in the content storage;

receive a modified version of managed content;

locate the managed content stored in the content storage based on the received modified version of managed content;

determine version data based on a portion of the located managed content;

update the content version metadata based on the modified version of managed content and the version data;

update the managed content based on the differences between the modified version of managed content and the content within the located managed content;

obtain performance information from a system comprising of at least one of;

a client display device and a content delivery server system;

locate the managed content based on the performance information;

update the content version metadata based on the performance information;

receive a request for content, wherein the request comprises a requested content version; and

transmit a portion of the managed content based on the requested content version.

2. The versioned content management server system of claim 1, wherein the versioned content management application further configures the processor to update the managed content by updating the content and the content version metadata.

3. The versioned content management server system of claim 1, wherein the versioned content management application further configures the processor to update the managed content by storing a second managed content in the content storage based on the updated content and the managed content, wherein the second managed content comprises second content and second content version metadata.

4. The versioned content management server system of claim 3, wherein the managed content and the second managed content are arranged in a hierarchical relationship.

5. The versioned content management server system of claim 1, wherein the versioned content management application further configures the processor to update the managed content by:

storing a second content within the managed content based on the updated content and the content of the managed content; and

updating the content version metadata.

6. The versioned content management server system of claim 5, wherein the content and the second content are arranged in a hierarchical relationship.

7. The versioned content management server system of claim 1, wherein the versioned content management application further configures the processor to update the managed content by incorporating the updated content into the managed content to create merged content.

8. A method for managing versioned content, the method comprising:

receiving managed content comprising content and content version metadata;

storing the managed content in a content storage;

receiving a modified version of managed content;

locating the managed content stored in the content storage based on the received modified version of managed content;

determining version data based on a portion of the located managed content;

updating the content version metadata based on the modified version of managed content and the version data;

updating the managed content based on the differences between the modified version of managed content and the content within the located managed content;

obtaining performance information from a system comprising of at least one of;

a client display device and a content delivery server system;

locating the managed content based on the performance information;

updating the content version metadata based on the performance information;

receiving a request for content, wherein the request comprises a requested content version; and

transmit a portion of the managed content based on the requested content version.

9. The method of claim 8, wherein updating the managed content comprises updating the content and the content version metadata.

10. The method of claim 8, wherein updating the managed content comprises storing a second managed content in the content storage based on the updated content and the managed content, wherein the second managed content comprises second content and second content version metadata.

11. The method of claim 10, wherein the managed content and the second managed content are arranged in a hierarchical relationship.

12. The method of claim 8, wherein updating the managed content comprises:

storing a second content within the managed content based on the updated content and the content of the managed content; and

updating the content version metadata.

13. The method of claim 12, wherein the content and the second content are arranged in a hierarchical relationship.

14. The method of claim 8, wherein updating the managed content comprises incorporating the updated content into the managed content to create merged content.