Content authoring and deployment technology

• US 9,183,537 B2
• Filed: 02/01/2012
• Issued: 11/10/2015
• Est. Priority Date: 02/19/2011
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Yambal, Sachin, Jain, Jitendra J., Kapoor, Madhur, Gupta, Sunjeet
• Primary Examiner(s): Padmanabhan, Kavita
• Assistant Examiner(s): MARRERO, ZAIDA
• Application Number:
  US13/363,417
• Publication Number:
  US 20120216108A1
• Time in Patent Office: 1,378 Days
• Field of Search: 715/234
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Content authoring and deployment, in which mobile authoring templates that enable a user to make updates to a subset of a web page using a mobile device are generated and provided to a mobile device application. Configuration data that defines operations needed to publish content updates received through the mobile authoring templates is stored. When input defining a content update entered into a particular mobile authoring template is received, the configuration data associated with the particular mobile authoring template is accessed and content management services needed to publish the received content update to a web page are invoked. Content is published to the web page to reflect the received content update made on the mobile device using the particular mobile authoring template.

Claims

1. A method comprising:

generating a mobile authoring template that includes pre-defined interface controls that are configured to enable a user to make updates to a subset of a web page using a mobile device;

associating a unique identifier with the generated mobile authoring template;

providing the generated mobile authoring template to a mobile device application operating on a mobile device;

storing configuration data in association with the unique identifier, the configuration data defining operations needed to publish content updates received through the generated mobile authoring template to the web page, by;

receiving user input describing operations needed to publish content updates received through the generated mobile authoring template to the web page,

based on the received user input, generating a configuration file that defines all of the operations needed to publish content updates received through the generated mobile authoring template to the web page, and

storing, in electronic storage, the configuration file in association with the unique identifier;

receiving, from the mobile device application, input defining a content update entered into the generated mobile authoring template using the mobile device, the input including the unique identifier associated with the generated mobile authoring template;

in response to receiving the input defining the content update, accessing the configuration data based on the unique identifier by;

searching configuration files for the configuration file associated with the unique identifier;

identifying the configuration file associated with the unique identifier based on the searching; and

retrieving, from the electronic storage, the configuration file associated with the unique identifier;

based on the configuration data, invoking content management services needed to publish the received content update to the web page by;

invoking content management services defined within the retrieved configuration file; and

publishing content to the web page to reflect the received content update made on the mobile device using the generated mobile authoring template.

2. At least one non-transitory computer-readable storage medium encoded with executable instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising:

generating multiple, different mobile authoring templates that each includes pre-defined interface controls that are configured to enable a user to make updates to a subset of a web page using a mobile device, the multiple, different mobile authoring templates being generated for multiple, different types of content management systems and enable updates to multiple, different web pages;

associating a unique identifier with each of the multiple, different mobile authoring templates;

providing some of the multiple, different mobile authoring templates to a mobile device application operating on a mobile device of a user;

storing, for each of the multiple, different mobile authoring templates, configuration data in association with the respective unique identifier, the configuration data defining operations needed to publish content updates received through the mobile authoring template to the web page;

receiving, from the mobile device application, input defining a content update made using one of the multiple, different mobile authoring templates selected by the user in accordance with which of the subsets of the multiple, different web pages the user desires to update, the input including the respective unique identifier associated with the one of the multiple, different mobile authoring templates;

in response to receiving the input defining the content update, accessing the configuration data for the respective unique identifier associated with the one of the multiple, different mobile authoring templates selected by the user;

based on the configuration data for the respective unique identifier, invoking content management services needed to publish the received content update to the subset of the web page the user desires to update; and

publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates.

3. A system comprising:

at least one processor; and

at least one memory coupled to the at least one processor having stored thereon instructions which, when executed by the at least one processor, causes the at least one processor to perform operations comprising;

generating multiple, different mobile authoring templates that each includes pre-defined interface controls that are configured to enable a user to make updates to a subset of a web page using a mobile device, the multiple, different mobile authoring templates being generated for multiple, different types of content management systems and enable updates to multiple, different web pages;

associating a unique identifier with each of the multiple, different mobile authoring templates;

providing some of the multiple, different mobile authoring templates to a mobile device application operating on a mobile device of a user;

storing, for each of the multiple, different mobile authoring templates, configuration data in association with the respective unique identifier, the configuration data defining operations needed to publish content updates received through the mobile authoring template to the web page;

receiving, from the mobile device application, input defining a content update made using one of the multiple, different mobile authoring templates selected by the user in accordance with which of the subsets of the multiple, different web pages the user desires to update, the input including the respective unique identifier associated with the one of the multiple, different mobile authoring templates;

in response to receiving the input defining the content update, accessing the configuration data for the respective unique identifier associated with the one of the multiple, different mobile authoring templates selected by the user;

based on the configuration data for the respective unique identifier, invoking content management services needed to publish the received content update to the subset of the web page the user desires to update; and

publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates.

4. The computer-readable storage medium of claim 3 wherein:

storing configuration data in association with the unique identifier, the configuration data defining operations needed to publish content updates received through the generated mobile authoring template to the web page, comprises;

receiving user input describing operations needed to publish content updates received through the generated mobile authoring template to the web page,

based on the received user input, generating a configuration file that defines all of the operations needed to publish content updates received through the generated mobile authoring template to the web page, and

storing, in electronic storage, the configuration file in association with the unique identifier;

in response to receiving the input defining the content update, accessing the configuration data based on the unique identifier comprises;

searching configuration files for the configuration file associated with the unique identifier;

identifying the configuration file associated with the unique identifier based on the searching; and

retrieving, from the electronic storage, the configuration file associated with the unique identifier; and

based on the configuration data, invoking content management services needed to publish the received content update to the web page comprises invoking content management services defined within the retrieved configuration file.

5. The system of claim 3, wherein associating a unique identifier with each of the multiple, different mobile authoring templates comprises embedding, for each of the multiple, different mobile authoring templates, the respective unique identifier in the corresponding mobile authoring template to enable identification of the corresponding mobile authoring template when content updates are received through the corresponding mobile authoring template.

6. The system of claim 5:

wherein receiving, from the mobile device application, input defining a content update made using one of the multiple, different mobile authoring templates selected by the user in accordance with which of the subsets of the multiple, different web pages the user desires to update comprises receiving, from the mobile device application, a version of the one of the multiple, different mobile authoring templates that includes a content update entered using the mobile device and that has the unique identifier embedded therein; and

wherein accessing the configuration data for the respective unique identifier comprises;

extracting the respective unique identifier embedded in the received version of the one of the multiple, different mobile authoring templates that includes the content update,

identifying configuration data for the extracted identifier, and

retrieving the identified configuration data.

7. The system of claim 3:

wherein the system includes multiple, different connectors that enable the system to connect with multiple, different types of content management systems;

wherein publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates comprises;

selecting, from among the multiple, different connectors, a connector for a content management system that manages content included on the web page, and

using the selected connector to transfer the received content update to the content management system that manages content included on the web page.

8. The system of claim 3, wherein the system is configured to add a new connector to support a new content delivery channel and publish content to the new content delivery channel using the new connector.

9. The system of claim 3, wherein publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates comprises enabling an update to the web page managed by a content management system from a user that is in a location in which a broadband internet connection is unavailable.

10. The system of claim 3, wherein the operations further comprise:

processing each of multiple inputs defining respective content updates by;

in response to receiving the input defining the content update, determining an identity of the user attempting to make the content update;

determining whether the user attempting to make the content update is authorized to make the content update;

in response to a determination that the user attempting to make the content update is authorized to make the content update for at least some of the multiple inputs, accessing the configuration data for the respective unique identifier associated with the one of the multiple, different mobile authoring templates selected by the user; and

in response to a determination that the user attempting to make the content update is not authorized to make the content update for at least some of the multiple inputs, generating an error condition and preventing the content update.

11. The system of claim 3, wherein invoking content management services needed to publish the received content update to the subset of the web page the user desires to update comprises converting the content update into a proper format and structure for integration into the subset of the web page the user desires to update.

12. The system of claim 3:

wherein invoking content management services needed to publish the received content update to the subset of the web page the user desires to update comprises determining, for each of multiple content updates, whether a content management system supporting the web page requires synchronous or asynchronous transactions; and

wherein publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates comprises;

in response to a determination that the content management system supporting the web page requires synchronous transactions, publishing, for a first subset of the multiple content updates, content using a synchronous transaction; and

in response to a determination that the content management system supporting the web page requires asynchronous transactions, publishing, for a second, different subset of the multiple content updates, content using an asynchronous transaction.

13. The system of claim 3:

wherein invoking content management services needed to publish the received content update to the subset of the web page the user desires to update comprises;

validating that the content update includes appropriate information for the content update, and

transforming the content update into a form appropriate for incorporation into the web page; and

wherein publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates comprises;

determining publishing activities needed to publish the transformed content update into the web page, and

publishing the transformed content update into the web page using the determined publishing activities.

14. The system of claim 13:

wherein determining publishing activities needed to publish the transformed content update into the web page comprises determining, from among multiple, possible destination devices, a destination device for publishing the transformed content update into the web page, the multiple, possible destination devices including at least a database and a file server; and

wherein publishing the transformed content update into the web page using the determined publishing activities comprises publishing the transformed content update to the determined destination device.

15. The system of claim 3, wherein invoking content management services needed to publish the received content update to the subset of the web page the user desires to update comprises invoking an authorization service to confirm authorization to publish the content update.

16. The system of claim 3, wherein invoking content management services needed to publish the received content update to the subset of the web page the user desires to update comprises invoking a syndication service.

17. The system of claim 3, wherein invoking content management services needed to publish the received content update to the subset of the web page the user desires to update comprises invoking authorization, validation, syndication, and conversion services.

18. The system of claim 3, wherein the operations further comprise, in response to receiving the input defining the content update, placing the content update in a queue until content management services are available to process the content update.

19. The system of claim 3, wherein publishing content to the web page for the subset of the webpage the user desires to update to reflect the received content update made on the mobile device using the one of the multiple, different mobile authoring templates comprises integrating the received content update made on the mobile device using the one of the multiple, different mobile authoring templates into other enterprise content included in the web page.

20. The system of claim 3 wherein:

storing configuration data in association with the unique identifier, the configuration data defining operations needed to publish content updates received through the generated mobile authoring template to the web page, comprises;

receiving user input describing operations needed to publish content updates received through the generated mobile authoring template to the web page,

based on the received user input, generating a configuration file that defines all of the operations needed to publish content updates received through the generated mobile authoring template to the web page, and

storing, in electronic storage, the configuration file in association with the unique identifier;

in response to receiving the input defining the content update, accessing the configuration data based on the unique identifier comprises;

searching configuration files for the configuration file associated with the unique identifier;

identifying the configuration file associated with the unique identifier based on the searching; and

retrieving, from the electronic storage, the configuration file associated with the unique identifier; and

based on the configuration data, invoking content management services needed to publish the received content update to the web page comprises invoking content management services defined within the retrieved configuration file.