WO2007104100A1

WO2007104100A1 - Content management

Info

Publication number: WO2007104100A1
Application number: PCT/AU2007/000310
Authority: WO
Inventors: Laurent Behan; Tamer Abdel-Wahed
Original assignee: Càvea Systems Australia Pty Ltd
Priority date: 2006-03-14
Filing date: 2007-03-14
Publication date: 2007-09-20

Abstract

The present invention relates to systems and methods for content management, generation and/or delivery. The system (100) 1 includes a central content management system (CMS) (102), and the remote content management system (104). The remote CMS (104) is able to be communicatively coupled to the central CMS (102) via a communications network (106). The remote system (104) preferably includes, a synchronization subsystem (108); a remote content repository (110); a content generation subsystem (112); a content delivery subsystem (114); and a data gathering and/or feedback subsystem (116).

Description

Content Management Field of the invention

The present invention relates to systems and methods for content management, generation and/or delivery. In a particularly advantageous embodiment the present invention is adapted for use in circumstances where content is primarily generated and controlled centrally but delivered remotely, and where the systems used for remote delivery or generation of content are only connected to a central content management system from time to time.

Background of the invention

In companies with large numbers of sales people the effective management of branded collateral is of primary concern.

Historically branded collateral has been in print form and has taken the form of brochures, price lists, and other marketing documents that sales people may need in their interactions with current or prospective customers. However, print collateral is difficult to manage as it has high production costs, long production lead times and requires careful inventory planning. Moreover, it is highly vulnerable to being outdated. Collateral in digital or electronic form is more flexible and may appear to be lower in cost than printed documents. However, it has its own drawbacks that can make its use problematic and increase its cost.

One of the primary issues with digital collateral is that, once it is in the hands of the sales team, the marketing and communications team who are given the task of creating the content lose control of the content, and therefore lose control of the company's corporate image and marketing messages. To minimize this risk it will typically be company policy that only approved content can be used or incorporated into marketing and communications documents. However such a policy is difficult to police, especially in companies with large numbers of people who use marketing materials in different capacities; or whom engage agents and distributors to market and sell on their behalf.

This problem is exacerbated if many of these individuals deliver their content remotely. In this type of remote use scenario a user will not have access to the latest marketing documents and may inadvertently use out of date materials. Moreover some users may take advantage of this remote operation to go against the company policy and customize or modify branded collateral in a way that is against the company's policies.

One area that is particularly susceptible to such problems is the building of presentations for delivery to customers. As can be appreciated each presentation will have a slightly different audience and therefore it is likely that the presenter wilt want to personalise his or her presentation to his or her audience.

The most common way of generating presentation in this scenario is to use software such as Microsoft PowerPoint, Adobe Acrobat, or an HTML editor to build presentations based on approved content stored in a content management system (CMS). However the tatter method only altows presentations to be built while the user is in communication with the CMS, thus largely precluding its use by presenters who are offline.

The traditional approach for addressing this problem is to have Marketing centrally create presentations and distribute them manually to remote users, e.g. by email or other means. Presentations created by this method are either static and once distributed to end users, offer no means for updating or personalising the presentation, or alternatively, are distributed in a medium in which subsequent updates can be made by end users, but which deprives or severely reduces Marketing's ability to exercise any physical control over the types of changes that end users may make to the presentation or distributed material. This latter scenario leaves open the risk of abuse of brand and content compliance guidelines. Summary of the invention

In a first aspect the present invention provides a digital content management system including: at least one content management server including a database structure configured to store digital content; at least one remote content management component having an associated remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote content management component, a synchronization system configured to update the digital content stored in the remote digital content repository to reflect changes made to the digital content stored on the digital content server and send feedback data to the server system relating to the digital content stored on the remote content management component.

In a second aspect of the present invention there is provided a remote content management system configured to be synchronized with a centralized content management server including a digital content server, the remote content management system including a remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote content management system, and a synchronization system configured to update the digital content stored in the remote digital content repository to reflect changes made to the digital content stored on the digital content server and send feedback data to the centralised content management system relating to the digital content stored on the remote content management system.

In a further aspect the present Invention provides a content management server system configured to cooperate with a remote content management system, the content management server system including

^" a database structure configured to store digital content and a synchronization interface configured to cooperate with a synchronization system of the remote content management system to update digital content stored in a remote digital content repository of the remote content management system to reflect changes made to the digital content stored in the database structure and to receive feedback data relating to the digital content stored on the remote content management system. The synchronization system can be configured to selectively update content objects from the content management server in accordance with a user access permission level assigned to a user of the remote content management component.

Content objects to be updated on the remote content management component can be assigned a priority level. The synchronisation system can be configured to perform updates of the remote content management component in accordance with the assigned priority levels, In one embodiment, the synchronization system implements mandatory updating of content objects assigned a first priority level. The synchronization system may allow updating of content objects assigned at least one second priority level in accordance with a user-made selection. The synchronization system can include a communications interface configured to allow the synchronization system to communicate with a CMS application running on the content management server. Preferably the communications interface can be configured to interface with a CMS application using a standardised data exchange protocol.

Preferably the feedback data sent to the server system includes one or more of the following types of data: modified digital content stored on the remote client system; digital content created on the remote content management component; data relating to use of at least part of the digital content stored on the remote content management component : feedback relating to any one or more of the quality, style, effectiveness of digital content stored on the remote content management component; data obtained from a form stored on the remote content management component.

Preferably the digital content includes a plurality of content objects. In this case the synchronization system can be configured to update the digital content stored In the remote digital content repository to reflect changes made to selected digital content objects stored on the digital content server. More preferably only content objects stored in the server system that have been changed or added to the server system are updated in the remote digital content repository.

Preferably the digital content includes composite content objects which include a plurality of component content objects. In this case the synchronization system is configured to update composite content objects stored in the remote digital content repository in a manner such (hat only those component content objects forming a complex content object that have been changed or added to the server system are updated.

In an aspect of the present invention lhere is provided a remote content management system configured to enable use of authorized digital content by a system user, said remote content management system including: a remote digital content repository configured to store digital content derived from a central content management system (CMS); content delivery means configured to deliver content from the digital content repository; a content authentication system configured to verify that one or more digital content objects to be delivered by the content delivery means have been authorized for use by the central content management system.

Preferably each digital content object stored in the remote digital content repository has associated verification data. The associated verification data can be generated on the basis of at least part of content object data. Preferably the content of each digital content object stored in the remote digital content repository has associated verification data supplied by the central CMS. Alternatively it can be generated by the remote CMS system.

In one embodiment the remote CMS system is configured to calculate a digital signature for the each content object upon the receipt of the content object. Preferably the digital signature is stored as metadata associated with the content object. The digital signature for the each content object can be updated to reflect updates to the content object.

Preferably the digital signature relating to each content object can be used by the content authentication system to determine whether one of the following has occurredj; a content object has been approved for use by the remote CMS a content object has been modified from a form approved by the remote CMS; and a content object has been approved for use delivery by the content delivery system, Preferably the digital signature is generated using a hash function.

The remote content management system can further include a content generation subsystem configured to generate a composite content object, including a plurality of content objects stored in the remote digital content repository. For example a composite content object could be a presentation including a plurality of content objects.

In one embodiment of the system, the content authentication system can be configured to, alternatively or additionally, verify digital content objects used in the generation of composite content objects that are authorized by the central content management system. In an aspect of the present invention there is provided a remote content management system configured to enable use of digital content by a system user, said remote content management system including: a remote digital content repository configured to store digital content objects derived from a central content management system (CMS); a content generation subsystem configured to generate composite content objects, including a plurality of content objects stored in the remote digital content repository; and content delivery means configured to deliver content objects stored in the digital content repository andfor composite content objects generated by the content generation subsystem. The content generation subsystem preferably includes content selection means enabling the selection of content objects stored in the remote digital content repository for inclusion in a composite content object.

The content generation subsystem can be configured to enable modification of content objects or composite content objects.

In the event that a content object or composite content object is modified_! the content generation subsystem can be configured to store both the modified and unmodified version of the content object or composite content object in the remote digital content repository.

Preferably the content generation subsystem includes one or more of the following interfaces: a localization selection Interface enabling the customization of a composite content object in a predetermined manner for one of a plurality of locales; a theme selection interface enabling the application of theme to composite content object; a metadata insertion interface, configured to enable metadata to be associated with at least a portion of a content object used in a composite content object; an introduction selection interface configured to enable the selection of a content object or composite content object which, in use, will provide an introduction to a composite content object; a conclusion selection interface configured to enable the selection of a content object or composite content object which, in use, will provide a conclusion to the composite content object; a content rearrangement interface configured to enable a default order of delivery of content objects forming the composite content to be established.

In a particularly preferred embodiment the selection and/or rearrangement interfaces include a display portion in which content objects are presented in a hierarchical structure. Preferably the hierarchical structure indicates which of a plurality of content objects have been selected for inclusion in the composite content object. In some embodiments the hierarchical structure indicates a default order of delivery of content objects forming the composite content. In one embodiment a plurality of hierarchies can be provided to enable navigation through a plurality of content objects, In this case a navigation hierarchy selection object can be provided, that in use, enables a user to select which default delivery hierarchy to will apply. Preferably the hierarchy selection object can be accessed by the user during delivery to allow a change in the default delivery hierarchy to be made.

In a preferred form the hierarchical structure is a tree structure including a plurality of content nodes, each of which optionally has sub-nodes depending there from. Nodes can be content objects or composite content objects. In the event that a node Is a composite content object, its sub-nodes can include either content objects or composite content objects. This pattern can continue until the lowest level "leaves" of the tree structure are content objects.

The content rearrangement and selection interfaces can be combined into a single interface enabling both selection and rearrangement of content objects. In a preferred embodiment the content generation means is configured to generate a visual presentation including a plurality of content objects. The presentation may also include the presentation of associated audio content objects. in an aspect of the present invention there is provided a remote content management system configured to manage digital content derived from a central content management system (CMS), said remote content management system including; a remote digital content repository configured to store the digital content objects derived from the central CMS; one or more, complex content objects including a plurality of digital content objects stored on remote digital content repository, wherein in at least two of the plurality of digital content objects forming a complex content object have been assigned at least one default order of delivery to a content receiver; and a content delivery subsystem configured to deliver content to one or more content receivers, which is further adapted to enable delivery of least two of the plurality of digital content objects forming a complex content object in an order different to the assigned default order. The content delivery subsystem can be configured to selectively deliver content to one or more content receivers in user determined order. The content delivery subsystem can be provided with a user interface to enable hierarchical or sequential delivery of a plurality of content objects. The content delivery subsystem can also be provided for means for traπsitioπing to a termination point in the delivery of a plurality of content objects from at least one Intermediate point in tha delivery of a plurality of content. At least a portion of the complex content object can be assigned a plurality of default delivery orders. In. this case the complex content object can be provided with selection means configured to enable a selection between the plurality of default delivery orders during delivery. The content delivery subsystem can be provided with selection means configured to enable a selection between the plurality of default delivery orders during delivery. In an aspect of the present invention there is provided a remote content management system configured to manage digital content derived from a central content management system (CMS), said remote content management system including: a remote digital content repository configured to store the digital content objects derived from the central CMS; at least one second subsystem configured to use digital content objects stored in the remote digital content repository; and a data collection subsystem configured to gather data relating to use of one or more content objects stored in the remote digital content repository.

Preferably the data collection subsystem is connected to a data storage system having a database structure configured to store the gathered data. ^■ The at least one second subsystem can include any one of the following types of subsystem: a content modification subsystem; a content creation subsystem; a content output subsystem; a synchronization subsystem; a content formatting subsystem.

The data collection subsystem can be configured to gather data relating to any one or more of the following types of use of a content object, by any one or more of the subsystems belonging to the system: Notification, receipt, transmission, storage, creation, modification, updating, deletion, recording, viewing, playing, broadcasting and output.

In a particularly advantageous form, the data collection subsystem can be configured to gather data related to one or more of the following: which content objects or groups thereof are used; an order of use of content objects or groups thereof; and a duration of use of one or more content objects.

The data collection subsystem can be further configured to gather feedback data input by a system user. In this case the data collection subsystem include a feedback interface to receive feedback from a user.

In exemplary embodiments the feedback data can include one or more of the following types of data: response data indicative of an answer to a question, order data, data derived from forms, uploaded files and/or content objects.

In embodiments having a content modification subsystem configured to enable modification of content objects or composite content objects, in the event that a content object or composite content object is modified the content generation subsystem can be configured to store both the modified and unmodified version of the content object or composite content object in the remote digital content repository.

In a preferred embodiment the system includes a synchronization subsystem configured to update the digital content stored in the remote digital content repository and to transmit said data gathered by the data collection subsystem to the central CMS. Preferably the data transmitted to the central CMS is formatted in a predetermined manner. The synchronization subsystem can be configured to transmit newly created versions of content stored in the remote digital content repository to the central CMS as part of the synchronization process.

In another aspect the present invention provides a method of operating a content management system (CMS) including at least one central CMS server including a database structure configured to store digital content, and a remote client system including an associated remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote client system, the method including: updating at least some the subset of the digital content stored on the remote client system to reflect changes made to the digital content stored on the central CMS server; and updating the centra! CMS server with feedback data relating to the digital content stored on the remote client system.

In another aspect the present invention provides a method, in a remote client system associated with a content management system (CMS), said CMS including at least one central CMS server including a database structure configured to store digital content, the remote client system including an associated remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote client system, the method including:

Receiving and updating at least some the subset of the digital content stored on the remote client system to reflect changes made to the digital content stored on the central CMS server; and transmitting feedback data relating to the digital content stored on the remote client system to the central CMS server.

The method can include an initial step of establishing network communications wilh the central CMS server. This can include verifying at least one of a user identification and access permissions to digital content stored in the central CMS server.

In a further aspect of the present invention there is provided a method in a remote content management system, the method including: storing a digital content object derived from a cental CMS; storing a digital signature corresponding to the digital content object, signifying that the digital content object is authorized for use on the remote content management system; and prior to using the digital content object on the remote client system checking at least that the digital content object is correctly associated with its digital signature.

In the event the digital content object stored on the remote client system and its digital signature are not correctly associated preventing use of the digital content object on the remote client system.

The step of checking that the digital content object is correctly associated with its digital signature can include generating a new digital signature on the basis of at least part of the digital content object and comparing it to the stored associated digital signature.

A method of generating a content object including a plurality of other content objects for use in a remote content management system, the method including: selecting a plurality of content objects for inclusion in the content object; establishing a default delivery order for the content objects by arranging them in at least one hierarchical structure; generating a content object for delivery from the plurality of content objects. The hierarchical structure is preferably a tree structure. In preferred embodiments the method can include establishing a plurality of default delivery orders for a same plurality of content

The generated content object preferably includes a navigation means, which can be used in during delivery to deliver the content objects in an order other than the default order. The navigation means is preferably a menu structure. The navigation means can also provide means to select one of a plurality of default delivery orders to be used. Preferably the default delivery order in use can be changed during delivery.

The method can further include one or more of the following steps: configuring the generated content object for use in one or more selected locale; configuring the generated content object for to comply with a chosen theme; storing metadata relating to at least a portion of a content object used in the generated content object; applying an introduction object to the generated content object; and applying a conclusion object to the generated content object.

In a further aspect the present invention provides a method in the remote content management system configured to use digital content derived from a central content management system (CMS), said method including: providing at least one subsystem configured^" to use one or more digital content objects stored in a remote digital content repository; and collecting data relating to use of one or more content objects stored in the remote digital content repository.

The method can include gathering data relating to any one or more of the following types of use of a content object: notification, receipt, transmission, storage, creation, modification, updating, deletion, recording, viewing, playing, broadcasting and output; of a content object or group of objects.

In a particularly advantageous form, the method includes ore or more of the following: gathering data reflecting which content objects or groups thereof are used; gathering data reflecting an order of use of a plurality of content objects; and gathering data reflecting a duration of use of one or more content objects. The method can further include, gathering human feedback data entered by a system user data

Preferably the method includes uploading at least part of the gathered data to a central content management system. The step of uploading preferably is performed intermittently. In a further aspect the present invention provides a method of delivering a content object to a recipient, the method including: delivering content to a recipient; and gathering feedback data related to the delivery of said content object.

The method includes transmitting the feedback data to a central management system. Preferably the method is performed in a mode in which no data communication is made with the central management system. The step of transmitting the feedback data to a central management system can include an initial sub step of establishing communications with the central management system.

In a further aspect the present invention provides a delivering a content object to a recipient, which includes the step of generating a content object using an aspect of the present invention. In further aspects the present invention provides a software application including an instruction set and/or data configured to enable a remote system, or central CMS to implement a method of any one of the methods herein described, and a memory means for storing such a software application.

Brief description of the drawings

Illustrative embodiments of the present invention will now be described, by way of a non-limiting example, with reference to the accompanying drawings, in which:

Figure 1 is a schematic diagram showing an overview of an exemplary content management system according to an embodiment of the present invention;

Figure 2 is a figure depicting schematically an introductory interface presented to a user of a remote content management system of an embodiment of the present invention: Figure 3 is a schematic representation of the phases in a synchronization process used in an embodiment of the present invention;

Figure 4 depicts an exemplary interface for enabling. a user to select which content objects should be updated in a synchronization process of an embodiment of the present invention;

Figure 4A illustrates an alternative interface for enabling a user to select content objects Io be updated Figure 5 is a schematic representation of the phases in a content formatting process used in an embodiment of the present invention;

Figure 6 depicts an exemplary user interface enabling the creation of a new presentation using an embodiment of the present invention;

Figure 7 depicts an exemplary user interface enabling the localization of a presentation using an embodiment of the present invention;

Figure 8 depicts an exemplary user interface enabling the application of a theme to a presentation being created or modified in embodiment of the present invention;

Figure 9 depicts an exemplary user interface enabling the addition of metadata to a digital content object used in a new presentation created using an embodiment of the present invention; Figure 10 depicts an exemplary user Interface enabling the selection of an introduction object for use in a presentation in an embodiment of the present invention;

Figure 11 depicts an exemplary user interface enabling the selection of a conclusion object for use in a presentation in an embodiment of the present invention; Figure 12 depicts an exemplary user interface enabling the selection and ordering of content objects for inclusion in a presentation in an embodiment of the present invention;

Figure 13 depicts an exemplary user interface enabling the arrangement of content objects for use in a presentation in an embodiment of the present invention;

Figures 13 A and B show alternative hierarchical arrangements for the same content that can be established using the interface of figure 13;

Figure 14 is a schematic representation of the operation of a content delivery or presentation process used in an embodiment of the present invention;

Figures 15A to 15D depict a series of layout templates used in an embodiment of the present invention for delivery of content objects in a linear fashion; Figures 16A to 16F depict a series of layout templates used in an embodiment of the present invention for delivery of content objects in a non-linear, hierarchical fashion

Figures 16A to G depict a main interface screen configured to enable a user to select which presentation order to use during delivery of a presentation;

Figure 17 depicts an exemplary electronic form used to gather feedback in an embodiment of the present invention;

Figure 18 shows an exemplary interface for listing metrics data in respect of content objects to a user; and

Figure 19 shows an exemplary interface showing detailed metrics data in respect of a content object. Detailed description of the embodiments Figure 1 depicts an exemplary content management system in accordance with an embodiment of the present invention. It will be convenient to describe this example in connection with the management, generation and use of marketing materials however the present invention should not be considered to be limited to this field of application.

The system 100 of Figure 1 includes two main parts, namely the server side, or central content management system (CMS) 102, and the remote, or client side content management system 104 (hereinafter termed the remote system 104). The remote system 104 will typically be implemented as a laptop or other mobile computing platform or a desktop computer that is located remotely from the CMS 102. In the exemplary embodiment the remote system 104 is able to be communicatively coupled to the central CMS 102 via a communications network 106, such as the internet, an intranet or LAN. Network connections used may communication through any suitable protocol and use either wired or wireless transmission means or a combination of both. In some embodiments the network connection between the remote system 104 and the central CMS may not be permanent, rather the remote system 104 may only connect to the central CMS 102 from time to time. For example the remote system may be a laptop computer that connects to the central CMS via an internet connection through the remote system user's internet service provider. In this case the network connection will only be formed at time when the remote system is actually connected to the CMS, not when the remote system is off-line. Similarly, if the remote system is a laptop that Is configured to connects to the central CMS via a LAN the communication link 106 between the two will only exist when the laptop is connected to the LAN, and not when the laptop is being used offsite. Notwithstanding this, in some embodiments the connection may be permanent. In either case the remote system is configured to operate and perform one or more of the functions described below in a largely stand alone fashion, i.e. with out requiring constant communication with the central CMS.

The central CMS 102

The central CMS 102 wilt typically be a conventional content management system running on a server system. In this regard it will include a 'central repository of digital content objects and management software configured to enable this content to be uploaded, deleted changed or otherwise controlled by a user of the central CMS. The central CMS may also have an interface component, e.g. a web server, or other network accessible component configured to make content from the CMS available to external systems via one or more communications ports.

As will be discussed below, the synchronization component of the remote system 104 is configured to communicate with the central CMS 102 via this interface component to exchange data with the central CMS 102. The central CMS 102 may also include a user validation service component configured to allow or disallow access to the central CMS on the basis of credentials input by the user of either the remote system 104 or the central CMS 102. The validation service component may also provide means for determining permission levels assigned to each user to determine which portions or types of content stored in the central CMS 102 they are allowed to access and what they are allowed to do with the accessible content, e.g. view content, add content, modify content etc.

As will be appreciated, content stored in the central CMS may include, but is not limited to content objects, such as brochures, fact sheet, rate and price schedules, templates or forms, image files, videos, sound files, reports, policy documents etc. Because of the nature of these documents and their potential criticality to a business their authorship, modification and approval for use is likely to be closely monitored and/or controlled. Accordingly the database structure of the central content repository can be configured to store metadata associated with a content object. The metadata can include an importance level for each content object. Depending on the assigned importance level synchronization of a content object will be handled differently if it is changed, or deleted on the central CMS Each content object stored in the central content repository may also have an associated digital signature (e.g. created applying a hash function (MD5, CRC or the like) to all or part of the contents data) which designates that the content has been approved/authorised for use by an approved content author, e.g. marketing or sales management. The central CMS may perform this signing function or the signature associated with each approved content object may be created and associated with the content object by the software used to create the object. The digital signature may be created and stored permanently with the content object, or may be created only on synchronisation of the content object with the remote system (as discussed below).

Remote system 104 The remote system 104 include the following main functional components or sub-systems: a synchronization subsystem 108; a remote content repository 110; a content generation subsystem 112; a content delivery subsystem 114; and a data gathering and/or feedback subsystem 116.

These modules will typically be implemented by one or more software applications (or modules) running on the remote system 104. Accordingly the remote system will require associated hardware, e.g. memory means, processing devices, input/output devices and data storage systems, networking hardware to run such applications. Determining the details of the hardware requirements of such as system will be within the skill of one skilled in the art and will not be described further.

Turning firstly to the remote content repository 110 - this component of the remote system 104 will typically include a database structure that is configured to store content objects, and associated data that have been derived from the central CMS 102 or created by the content generation subsystem 112. The remote content repository 110 can also be configured to store feedback data generated or gathered by the data gathering subsystem 116 for later uploading to the central CMS 102.

The content objects stored in the remote content repository 110 can include the same type of objects mentioned above in connection with the central CMS 102.

Turning now to the synchronization subsystem 108, which effectively provides a bi-directional data transfer gateway between the remote system 104 and the central CMS 102. The synchronization subsystem 108 provides a means for keeping remote system 104, and the central CMS 'in sync' such that both have a consistent view of the available poo! of content objects. In some embodiment the entire content base from the central CMS can be synchronized with the remote content repository 110.

Preferably the synchronization subsystem supports selective synchronization, and smart synchronization as described below. Smart synchronization allows the user of the client system to determine what content needs to be updated from the total pool of data available in the central CMS 102, and only update that data. This potentially speeds up synchronization times. Forced synchronisation can also be supported. In forced synchronization, certain updates made by the content managers that are deemed to be critical {e.g. policy changes, price changes, or corrections for example), are automatically downloaded and installed by the synchronization subsystem. The criticality of these updates is determined by the use of CMS metadata associated with the objects. In selective synchronization the user is presented with a list of all content that has changed since they last synchronised, and optionally which existing presentations (or other composite content objects) stored in their remote content repository 110 in the use that data. The user can then select what content objects they wish to update, potentially speeding synchronization, and allowing presenters to give a consistent message when re-visiting customers.

The synchronization subsystem 108 also performs content pushback to the central CMS 102. This involves the uploading of customized content generated or modified on the remote system 104 since its last synchronization being pushed back to the central CMS 102 for storage there.

The synchronisation subsystem 108 also performs uploading of captured data to the central CMS 102. Form data, usage analysis data or other feedback data which is captured by the data capture subsystem during use is pushed back to the central CMS, and made available for analysis within the CMS.

Depending on the type (e.g. vendor and version) of the CMS software being run on the central CMS 104 the requirements for the interoperability of the synchronization subsystem 108 and the central CMS 102 will differ from implementation to implementation. In order to make the synchronization subsystem 108 capable of interfacing with a wide range of CMS types the authentication system preferably uses a web service architecture or plug-in structure. In this regard, it can be provided with an authentication web service that queries the user for their authentication credentials (username password, etc), and provides storage for those detail within the security framework of the central system 102.

In a preferred form a transfer web service Is used to generate requests for the available content within the system, and performs download and storage of the data in the remote content repository 110. It also provides the services of file/data transfer in the uplink direction (i.e. to the CMS). This web service is configured to match the data transfer protocols and formats required by the particular CMS application being run on the central CMS 102.

A formatter mechanism is also used to change the data provided by the CMS from its chosen format into one of a number of formats required by remote system's 104 content generation subsystem 112 or content delivery subsystem 114. This mechanism may perform transcoding of navigation structures, and rich text, and may also support re-formatting images, audio, and video to meet appropriate requirements.

The synchroniser 108 is configured to generate a digital signature for each content object when it is received from the central CMS 102. This can be updated if necessary when the object is updated during synchronisation. In this case the remote system 104 is operating on the basis that any document that is received from the central CMS 102 has been approved for use and therefore can be signed safely upon receipt. This signature can be used to determine in use whether the object has been modified compared to its initial received state (at all, or from an approved form) prior to use by the remote system 104.

Turning to the content generation subsystem 112 - this subsystem provides the user of the remote system with the ability to customize, in a limited way, content stored in the remote content repository 110, and Io generate presentations or other types of content output object for delivery by the delivery subsystem 114.

In a preferred embodiment the content generation subsystem 112 allows the user to create customised presentations targeted at a specific user. It manages the customisation of metadata, themes and localization, and provides the ability to select content for inclusion in a presentation and ordering of the content, as described below. The content generation subsystem 112 also supports previewing presentations.

The ability to customize metadata provided by the content generation subsystem 112 allows the user to enter a range of values against different metadata fields associated with part or all of a content object. These fields are then used in specific areas of the presentation. The content generation subsystem 112 allows an introduction for a presentation to be created or added to a presentation using, preferably a wizard style interface. For example the introduction could be built from approved content objects by allowing the user to pick appropriate super images, and audio, and review the super text.

The selection of content and presentation flow functionality provided by the content generation subsystem 112 allows a user to select which objects to include in a presentation, e.g. slides or slide packs in a visual presentation, sounds, tracks etc. in audio presentation and to place them in a desired order of presentation. Depending on the metadata properties attached to each object the ability to select/deselect or reorder certain content objects may be limited. The content generation subsystem 112 also allows the user to select a presentation navigation style. These can be either linear or hierarchical (as described below).

The content generation subsystem 112 can allow a user to localize and apply a theme to content for delivery. Selection of a locale for a presentation selects the language/s that the presentation will be given in and may affect the default navigation style (top to bottom, right to left, left to right etc) in hierarchical mode and the character set displayed. On the other hand theme selection supports the selected language and the theme controls navigation look and feel by applying features such as default backgrounds, font styling and table look and feel.

The user is also able to select or create a conclusion with the content generation subsystem 112 in a similar manner to the introduction functionality. However the conclusion stage may also include the generation or presentation of selected forms (order forms, feedback forms, requests for additional information or documents etc.) or to generate "leave behinda" for the audience, e.g. copies of the presentation slides, notes pages, summary documents, pricelists etc. Such "leave behinds" can be created or presented in hard copy or digital form. When a presentation or other content delivery item is created the content generation subsystem 112 enables creation of the presentation/item using a tree navigation structure. This navigation structure is preserved and forms the basis of the Hierarchical navigation in the final presentation used in content delivery. As described below, branches of the tree that are not selected in the content selection phase are pruned when generating the navigation structures.

A preview function can also be supported in preferred embodiments of the content-generation subsystem 112 which allow the user to quickly preview the flow of a presentation's content, without having to launch a presentation application.

In a preferred form the content generation subsystem outputs a content object, or file that can be executed to deliver the content to a user. The output object may include an executable file that can be run in a standalone manner i.e. without needing another application program, such as a Flash executable file, or as a file type that requires a player or delivery application, e.g. an MPEG movie or the like, The output of the generation phase may be in an archive structure and include all of the component objects necessary for the delivery subsystem 114 to generate the final delivery form of the content "on the fly". The data capture subsystem 116 provides two key functions. The first of these is the collection of data from a data capture mechanism provided in the presentation, and is intended to provide a structured method for a presenter to record information pertaining to the presentation, for example sales order information or CRM information. The other is to capture presentation or content usage metrics. All data captured is fed back into the central CMS 102 during synchronization for central post processing. In order to implement these functions the data capture subsystem 116 can generate predefined forms for use as predefined components within a presentation. As with all content objects, new forms can be created and sent to remote system 104 during the synchronization process.

Such forms can be used to capture client details such as name, company name, phone number, address, etc. or to deliver and capture data using a questionnaire pertaining to the presentation or presentation content. Fee comment data may also be captured. Forms may also support ratings or check boxes to record answers to simple yes/no multiple choice style questions.

Presentation metric data collected can include data such as which presentations and content objects were used. Also presentation timing can also be used to record how much time was spent on each slide, and the total time taken to present. The presentation path can also be recorded as metric data by the data capture component 116.

The presentation subsystem 114 preferably includes a stand alone content delivery application system designed to allow users of the remote system 104 to deliver content both locally and remotely. The delivery application is preferably configurable in terms of, the content it displays, themes- and styling of a presentation, its navigation structure and support for dynamic introductions and conclusions. In a preferred embodiment it is based in XML and/or XHTML.

The presentation subsystem 114 may include more than one delivery application for delivering different types of presentation. For example a visual presentation may be rendered in a Flash, whereas an audio- only presentation may be more conveniently presented in a different format. In such cases a format specific delivery applications can be used.

In a preferred system the delivery application delivers visual presentations and supports navigational structures as described above. In particular the delivery application has the ability to deliver an optional introduction to the presentation, consisting of animated supers (text), images and audio. It can also deliver the main content (body) of the presentation, containing multiple content objects assembled into slides which can be navigated by either linear flow or hierarchal flow. The delivery application can also deliver a conclusion ending the presentation, this may be a simple closing or finish slide.

In a particularly preferred embodiment the delivery application can also deliver an interactive data capture form to receive feedback, CRM information, take orders etc.

Figures 2 through 16 will now be used to more clearly illustrate the operation of an exemplary system such as that depicted in Figure 1 : To more clearly illustrate the process of synchronization, customization and delivery of digital content by its end users e.g. sales people {as opposed to marketing, communications staff who are responsible for the development of content) the description will be made primarily from the point of view of the user of the remote system 104.

It will be appreciated by those skilled in the art that many interface options can be used in embodiments of the present invention, and the present embodiment should be considered to be illustrative rather than limiting on the scope of the present invention.

Figure 2 shows the options that are available to a user 202 when using the remote system 104 upon launching the content management system software residing on the remote device. Initially, the user 202 Is presented with a main interface screen 204 displaying the following selectable options: synchronise 206, format 208, review 210, configure 212, and play 213 each of which will be described in detail below. In alternative embodiments one or more of these buttons may be omitted, or combined, or interfaces may be arranged to be accessed sequentially. Each option may be presented to the user as a "button' allowing the user 202 to easily select the desired option by moving a mouse cursor over the button corresponding to the desired button and clicking the mouse. To assist in usability, the interface screen may be configured so that movement of the mouse cursor over a button causes a textual description of the function of the button to be - displayed. The interface screen may also be configured to provide keyboard shortcuts for each of the option buttons. In some embodiments all four options may not be made available to the content presenter 202 at all times. For example, if the system has not been synchronised recently (as discussed below), the format option 208 may not be available for the user 202, In this case the text displayed when the user places the mouse cursor over the disabled button will inform the user 202 why the option is not available. The availability of options will be discussed in the discussion of each of the options below. Synchronise

If the user 202 selects the synchronise option 206, the user synchronization process 300 as shown in figure 3 begins. The synchronization process Is the process used by the remote content management system to ensure that the user has the latest approved content made available to him or her to use. In the downlink direction, i.e. from the central CMS to the remote CMS, the synchronization process involves the transfer of digital content objects that have been updated in the central CMS since the last synchronization of the two CMS systems, or the transfer of newly created digital content objects that are not already stored on the remote CMS. tn the uplink direction, i.e. transmission from the remote CMS to the central CMS, the synchronization process involves the upload of feedback data gathered by the remote CMS. This feedback data can include, but is not limited to: customer or user feedback on content that has been distributed or used since the last synchronization (or earlier); data relating to actions arising from use of the digital content, e.g. order data resulting from a sales presentation; content usage data that is gathered by the remote CMS, e.g. usage statistics for the digital content objects stored on the remote CMS; and digital content objects created or modified on the remote CMS since the last synchronization, e.g. a customized presentation used by a sales person.

The first stage of the synchronization process is the user authorization stage 302. If the system has not correctly been configured to synchronise (see discussion below regarding the configure option 212), the synchronise option 206 will not be available and the user 202 will be directed to configure the system by using the configure option 212. [see client comment re slightly different operation in production system]

Authorise User In the authorise user stage 302 the user 202 is required to provide credentials to a credential validation service, which may be part of the central CMS or provided by a third party application or service. The provision of user credentials to the validation service may be achieved either by manually keying in and submitting the credentials or by automatically submitting previously cached credentials.

If no credentials have been previously cached the system may allow for any credentials entered to be cached for subsequent uses of the system.

If the submitted credentials are valid, the system informs the user 202 and transitions to the query data stage 306.

If the credentials are not valid, the system informs the user and prompts the user to re-enter credential information. In this case any cached credentials are discarded. Further, for security purposes a limit may be placed on the number of times a user is provided with the option of re-entering credentials. Alternatively, if the system is unable to connect to the credential validation service the system will inform the user of this and may provide additional troubleshooting device with regard to the correct configuration of the system and/or network requirements.

Although included within the synchronise process in the preferred embodiment, authorisation of the user 202 may of course take place at alternate and/or additional times throughout use of the system.

Query Data

In the query data stage 306 the system queries the central CMS to determine what digital content objects have been added or updated since the last synchronization and therefore what files need to be downloaded by the remote CMS. In the preferred embodiment updates can be classified by importance level. During the Query data phase the synchronizer determines whether there are any mandatory updates and/or optional updates. In one preferred form there can be 5 importance categories applied to content object updates, ranging from "Mandatory" as the highest to "Low" as the lowest.

During the query data stage 306 a progress dialog may be displayed to the user indicating, for example, the action currently being undertaken by the system and the approximate progress of the query data stage 306.

If an error occurs during the query data stage 306, for example due to a system failure, a network failure, corrupted data or similar, the system may present the user 202 with an option to retry or cancel the query data stage 306. If the user selects to retry, any data that may have been obtained from the initial attempt is discarded and the query data stage 306 begins anew. If the user selects to cancel the user is returned to main interface screen 204 described above.

Once the query data stage 306 is complete the system transitions to the select updates stage 308. Select updates

In the select updates stage 308 the user 202 is presented with options regarding content to be updated. Figure 4 depicts an example interface 400 that the user may interact with to make his or her selections. Updates are divided into classes e.g. content updates 402 and critical updates 404. Within each of these update options the user 202 is provided with a tree structure comprising root nodes 406 and sub-nodes 408. As with known implementations of such tree structures, each root node may be collapsed or expanded by operation of the +/- button associated with that node. A user 202 selects or deselects nodes according to the content they wish to update by clicking on the associated box. Further, If one of the root nodes 406 is selected/deselected all sub-nodes 408 on that root node are also selected/deselected. A button allowing for the selection or de-selection of all nodes may also be provided (not shown).

The select update screen 400 is also provided with two navigation buttons next 410 and back 412. When the next button 410 is selected the system records the update nodes selected by the user 202 and transitions to the retrieve updates stage 310. If the back button 412 is selected the system transitions to main interface screen 204. With regard to updates classed as "critical" 404, the system default is for all nodes in the critical updates tree to be selected for update. If the user 202 deselects any of the critical update nodes and selects the next button 410, trie system will display a warning to the user that critical updates are unselected and presents the user with an option to continue or return to the select updates stage 308. If the user 202 continues the system transitions to the retrieve updates stage 310, however if the user 202 selects to return they are returned to screen 400 where they are again able to select/deselect content nodes and critical update nodes.

In this embodiment a "wizard" interface can be presented to a user to guide him or her through the synchronisation process. When the synchronisation is begun the synchroniser communicates with the central CMS and checks for updates.

Figure 4A illustrates an interface 420 that illustrates each of the available updates for the remote CMS. The updates interface 420 provides the following data each content object available for update: the action to be taken In respect of the content object 422; the content object's name 424; a description of the content object 426; and and the priority level assigned to the content object 428.

Using this interface the user can click select the files they wish to update to their remote CMS. then select the "Next" button 430 to move to the updating phase.

Alternatively, the user can filter the available selections using a drop-down "Filter" menu 432. This menu lists the available priority classifications that may be assigned to objects. By selecting a given priority classification level the synchroniser will select those content objects of that priority level for updating.

The drop down menu "Select" allows a user to specify how their selections are to be treated, e,g. that selected items are updated, or selected items are ignored (not updated), or that all content objects should be selected or deselected. Once "Next" is selected the updating begins. As will be known to those skilled in the art of interface design a progress dialogue box can be provided to illustrate to the user the progress of the updating. Upon completion of the updating of an object, its icon in the column 422 can be updated to illustrate that an item has been successfully updated.

If no updates are available the system displays an information dialog box informing the user 202 of this fact and provides a link for the user to return to the main interface screen 204.

In an alternative embodiment the updating of content objects classed as "critical" may be mandatory. In which case users will not be given the option to deselect these items in the selection interface 400.

As mentioned above, each user can be assigned certain access rights to content stored on the central CMS, in the case the content objects that may be selected in the selection screen only include content objects or which they are have sufficient access rights. For example, take a motor vehicle salesperson, the company for which he or she works may have several product groupings e.g. small cars, family cars, commercial vehicles, prestige vehicles and off-road vehicles, and within each of these groupings there may be several products, e.g. different model vehicles. Moreover each product may have several pages of content that may be included in a presentation, e.g. several slides describing each model vehicle. If a sales person is in the companies "car^* division he or she may not be given access to content relating to commercial vehicles and off-road vehicles. Moreover if the salesperson in question is in personal sales to individuals, as opposed sales to fleets, certain fleet- related data such as fleet pricing, maintenance packages and financing related content will not be made available to him or her by the CMS. Accordingly this excluded data will be omitted from the synchronization process for this salesperson.

Retrieve Updates

In the retrieve updates stage 310 the content selected by the user (by selectioπ/de-selection of content nodes and critical update nodes) in the select updates stage 308 is retrieved from the content management system via the network connection linking the central and remote CMS systems. During the retrieve updates stage 310 a progress dialog may be displayed to the user 202 indicating, for example, the action currently being undertaken by the system and the approximate progress of the retrieve update stage 310.

The system may also provide the user 202 with a button allowing the user 202 to cancel the retrieve updates stage. If the user 202 elects to cancel the retrieval the, system requests confirmation of the instruction and, if confirmed the synchronizer, returns the user 202 to the main interface screen 204. If the cancellation is not confirmed the retrieve updates stage 310 continues.

If the remote CMS is unable (or is disconnected mid-retrieval) to connect to the content management the user 202 is prompted, to retry the connection or to cancel, if the user 202 selects to retry the retrieve updates stage 310 begins anew and if the user 202 selects to cancel they are returned to the main Interface screen 204.

Format

Once the retrieve updates stage 310 has completed and all required data has been retrieved, the system transitions to the format stage 314 and formats the data obtained in the retrieve updates stage 310.

During the format stage 314 a progress dialog may be displayed to the user 202 indicating, for example, the action currently being undertaken by the system and the approximate progress of the format stage 314.

The system may also provide the user 202 with a button allowing the user 202 to cancel the format stage. If the user 202 elects to cancel the system requests confirmation and, if confirmed, returns the user 202 to the main interface screen 204. If the cancellation is not confirmed the formatting stage 312 continues. If the system is unable to complete the format stage 314 an error message is displayed and the user 202 is prompted to retry or to cancel. If the user 202 selects to retry the format stage 314 begins anew and if the user 202 selects to cancel they are returned to the main interface screen 204.

Upon completion of the format stage 314 the system transitions to the send data stage. Send Data

The send data stage 320 is the stage in which data to be uploaded to the central CMS is uploaded. In order to ensure the integrity of data reflecting content use auditing or content modification auditing, the process for sending data back to the central CMS is largely automatic, e.g. the user is not able to select which files are uploaded. Format [note clients comment that format and configure now referred to as manage]

The format process can be used by a user of the remote CMS to perform limited customization of approved digital content objects prior to their delivery to their ultimate audience. The formatting process may include tailoring the look-and-feel of a presentation to the audience to which it will be delivered or the removal of content objects such as one or more sections from a presentation that is not deemed to be relevant to the audience.

In order to ensure the integrity and currency of local data, when the application program is started the format option is not made available to the user until synchronization has occurred. If a user attempts to select the format option 208 prior to synchronization the user 202 will be directed to synchronise the system by using the synchronise option 206. The format option is accessed by the user 202 by selecting the "format option" button 208 on the main interface screen 204. Figure 5 provides a representation of the format process 500 and figures 6 to 11 depict example screens presented to the user 202 to work through the format process 500.

Initially, the format process provides the user 202 with two options: to create a new presentation or to modify an existing presentation. Create new presentation stage

If the user selects to create a new presentation, the create new presentation stage 502 begins. As shown in figure 6 a name screen 600 is provided prompting the user 202 to enter a unique name for the presentation into a name text entry box 602 and a description for the presentation into a description text box 604, Once. a name and description have been entered into the appropriate text boxes the user 202 may select the next button 606 to save the information entered and optionally transition to the localisation stage 506 of the format process 500.

If the user 202 selects the back button 608 the user is returned to the main interface screen 204. Select existing presentation stage

If instead of electing to create a new presentation the user 202 chooses the "select existing presentation" stage 504, the system provides the user 202 with a list of existing presentations which the user 202 can browse through. The user 202 then selects which existing presentation they wish to base their new presentation on and the system transitions to the enter metadata stage 510 (discussed below). Alternatively, the user may select to exit the select existing presentation stage 504 in which case the user is returned to the main interface screen 204.

As is seen, by selecting an existing presentation user 202 bypasses the select localisation stage 506 and select theme stage 508 which would typically only required if a new presentation it to be created.

Select localisation stage

After selecting the create new presentation stage 502 and entering a presentation name and description, the system transitions to the select localisation stage 506. As can be seen in figure 7, depicting an example localisation screen 700 of the select localisation stage 506, the user is provided with a drop down list of available localities 702. Once a locality has been selected from the list 702 (the locality may either be a single place, such as "Japan" or "all" localities), the system displays a metric of how much data and how many themes are available for that locality in the preview box 704.

If the user 202 wishes to continue with the selected locality, the next button 706 is pressed which saves the selected locality and transitions the user 202 to the select theme stage 508. If the locality selected by the user 202 from the list 702 does not have any associated themes the user 202 is provided with a warning informing of this and is given the option to proceed, in which case the system transitions to the select theme stage 508, or to cancel in which case the user is ab!e to reselect a locality from the list 702.

If the user selects the back button 708, any locality selected from the list 702 is saved and the user is returned to the "create new presentation' stage 502. Select theme stage

As shown in figure 8, once the system has transitioned to the select theme stage 508 the user 202 is presented with a theme screen 800. The drop down theme list S02 provides the user 202 with a list of themes corresponding to the locality selected by the user 202 in the select localisation stage 506. If "all^* localities were selected all available themes will be displayed in the list 802. Once the user 202 selects a theme from the list 802, a preview of the selected theme is displayed in the theme preview area 804 for the users review. If the user 202 wishes to select that theme and proceed, the next button 806. is selected which saves the theme selection and the system transitions to the enter metadata stage 510.

If the user selects the back button 808, any theme selected from the list 802 is saved and the user is returned to the select localisation stage 506. Enter metadata stage

Figure 9 depicts an example metadata screen 900 which is displayed to the user 202 in the enter metadata stage 510 of the format process 500. This stage can be entered sequentially from the select theme stage or immediately when the "select existing presentation" button is selected. The text box 902 displays a list of all metadata fields (not shown) associated with the theme selected from the select theme stage 508, or used in the existing presentation. For each selected content object, the metadata fields may either be optional or mandatory and are clearly marked, for example via an icon or specific colour, so the user 202 can see which fields must be completed and which are optional. By selecting each object in the

"presentation tree" in the pane 550 the user can work through the process of adding metadata for each content object.

For example metadata associated with a content object can include hash code related to the object, its date of creation, an associated theme. As discussed above some metadata may be applied by the central CMS, whereas other metadata fields will be filled by the remote CMS. Metadata managed by the remote CMS can include configurable information about a client to whom a presentation is being delivered, their location etc, as well as the information to certain "call to action slides". In sales presentations the "call to action slides" are slides are those slides (typically delivered towards the end of a presentation) intended to achieve goals and outcomes planned for the presentation, e.g. to make a sale or be Invited to start a product trial etc. and therefore can be very client and presentation specific. Accordingly the addition to metadata to such slides makes can increase their level of remote custom isability by the presentation creator, whilst maintaining centralised control over the layout and style of the slide.

A dear all button (not shown) is also provided. If selected, the system shows a confirmation dialog box asking the user to confirm they wish to clear all data from the metadata fields and, if the user 202 does confirm, all data from the metadata fields is cleared.

Once the user 202 has completed data entry into the metadata fields they can select the next button 904 to save the data and proceed to the select introduction stage 512. If the user 202 selects the next button 904 prior to entering data into all mandatory metadata fields the system informs the user of this and returns the user 202 to the metadata screen 900 to complete the required data entry.

If the user selects the back button 906, all data is saved and the user is returned to the select theme stage 508. Select introduction stage

Figure 10 depicts an example introduction screen 1000 which is displayed to the user 202 in the select introduction stage 512 of the format process 500. The drop down select introduction list 1002 displays a list of introductions available. In embodiments that support localisation of content the available list will be limited to those that are appropriate for the locality specified by the user 202 in the "select localisation" stage 506. When an introduction is selected from list 1002, a visual indication of the look and feel of the introduction is provided in box 1004, and text box 1006 displays information about what elements the introduction requires and allows the user 202 to choose resources for the Introduction. If the introduction selected from the list 1002 does not require any elements to be configured (or the user selects "no introduction" from the list 1002), the user 202 selects the next button 1008 to save the selected introduction and transition to the select conclusion stage 514.

If the introduction selected from the list 1002 does require elements to be selected, the user 202 selects the desired elements such as audio, visual and animation elements and then selects the next button 1008 to save the selected introduction and transition to the select conclusion stage 514. If the introduction requires elements and the user 202 selects the next button 1008 without selecting the required elements, the system will notify the user that elements must be selected and return the user to the introduction screen 1000. If the user selects the back button 1010, all data is saved and the user is returned to the enter metadata stage 510.

Select conclusion stage

Figure 11 depicts an example introduction screen 1100 which is displayed to the user 202 in the select conclusion stage 514 of the format process 500. The drop down select conclusion list 1102 displays a list of conclusions. In embodiments that support localisation of content the list may be limited to those conclusions available for the locality specified by the user 202 in the 'select localisation" stage 506. When an conclusion is selected from list 1102, a visual Indication of the look and feel of the conclusion is provided in box 1104, and text box 1106 displays information about what elements the conclusion requires and allows the user 202 to choose resources for the conclusion. If the conclusion selected from the list 1102 does not require any elements to be configured (or the user •selects "no conclusion" from the list 1102), the user 202 selects the next button 1108 to save the selected conclusion and transition to the select content stage 516.

If the conclusion selected from the list 1102 does require elements to be selected, the user 202 selects the desired elements such as audio, visual and animation elements and then selects the next button 1108 to save the selected conclusion elements and transition to the select content stage 516. If the conclusion requires elements and the user 202 selects the next button 1108 without selecting the required elements, the system will notify the user that elements must be selected and return the user to the conclusion screen 1100.

If the user selects the back button 1110, all data is saved and the user is returned to the select introduction stage 512.

Select content stage

Figure 12 depicts an example content screen 1200 which is displayed to the user 202 in the select content stage 516 of the format process 500. The select content screen 1200 includes a selection area 1202 and a preview area 1204. In the selection area 1202 the system displays all content available to the user 202. If the tree tab button 1206 is selected the content available is displayed in a hierarchical navigation view, and if the linear tab button 1208 is selected the content available is displayed as a list. In the illustrated example the content displayed in the selection area 1202 is displayed in the hierarchical, or 'tree', view. It will be noted that when content is displayed in the tree view the selection area 1202 appears and functions in a similar fashion to the select updates screen 400 discussed above in connection with the synchronization process 300. When the user 202 selects to view the available content in the 'tree view' (by selecting the tree tab button 1206), the system displays a tree structure comprising root nodes 1210 and sub-nodes 1212. As with known implementations of such tree structures, each root node may be collapsed or expanded by operation of the +/- button associated with that node. A user 202 selects or deselects nodes according to the content they wish to select by clicking on the associated box. Further, if one of the root nodes 1210 is selected/deselected all sub-nodes 1212 on that root node are also selected/deselected. A button allowing for the selection or de-selection of all nodes may also be provided (not shown).

In an example of the creation of a sales presentation the salesperson e.g. a car salesperson, may have several product groupings to sell e.g. small cars, family cars, commercial vehicles, prestige vehicles and off-road vehicles, and within each of these groupings there may be several products, e.g. different model vehicles. Moreover each product may have several pages of content that may be included in a presentation, e.g. several slides describing each model vehicle.

In this vehicle sales example content relating to each model vehicle may be included in several presentation pages (each of which is comprised of one or more content objects) that have been created or approved for use by the marketing department. In an interface such as that presented in figure 12 an individual slide(s) relating to features of a particular model car (e.g. resale value statistics for the model over the last 5 years, or current model specifications) could be selected by choosing the appropriate sub- node(s) on the lowest hierarchy level. If all data relating to a particular model is desired the sub-node on the next lowest hierarchy level corresponding to that model can be selected. If all slides relating to a particular class of vehicles are desired the top level node corresponding to the class, say prestige cars, is selected.

When the name of a content object is selected by the user the preview area 1204 shows a preview of the selected content (possibly along with a summary of the content details), content object content object

Once the user 202 has selected all the content required for the presentation the next button 1214 is selected which saves the selections and transitions the user 202 to the arrange content stage 518. Alternatively, the back button 1216 may be selected by the user 202 to save all selections and transition the user to the select conclusion stage 514.

To increase the usability of the system filter and search options may be provided allowing the user 202 to search the available content for specific terms or keywords, or to filter the content to. display a subset of that content relevant to the user 202. Arrange content stage Figure 13 depicts an example screen 1300 which is displayed to the user 202 in the arrange content stage 518 of the format process 500. The order screen 1300 includes an order area 1302, a top button 1304, an up button 1306, a down button 1308 and a bottom button 1310.

In the order screen 1300 the system displays the a tree structure similar to that described in connection with the select content screen 1200 of figure 12. However in the arrange content screen 1300 the tree structure only includes content that has been selected by the user 202 in the select content stage 516. the interface allows the user to use the hierarchical navigation view of the layout and to click-drag content nodes to place the content in a desired order for presentation. As the user click-drags a particular node, the system may show a preview of the item being moved. If the user 202 selects a sub-node and drags that sub-node to another placement within the root the sub- node node originally existed in the system displays a 'drop' pointer indicating to the user 202 that the sub- node can be dropped at the position under the mouse. If the user 202 'drops' the sub-node (i.e. releases the mouse button) while this 'drop' pointer is being displayed, the sub-node will be repositioned to the location under the mouse, thereby changing the order of the presentation objects. Using the motor vehicle sales example given above the user may wish to display content relating to resale values before content relating to optional extras for a car. Such a rearrangement can be made using the process described above.

If the user selects a sub-node and drags that sub-node outside the root from which that sub-node came, the system may display an 'invalid drop location' pointer, indicating to the user 202 that the sub-node may not be placed in that location - i.e. that the user 202 is attempting to order the presentation in an invalid way. In the motor vehicle sales example such an invalid rearrangement may include a rearrangement that would put a presentation object relating to the performance statistics of one model car into the middle of a presentation sequence relating to another car. If the user 202 'drops' the sub-node while the 'invalid drop location' pointer is displayed, the sub-node will remain in its original position and not be moved - i.e. the order of the presentation will not be changed.

In a particularly preferred embodiment the hierarchical arrangement can include a plurality of alternative default navigation paths through a common group of content objects. This can be represented by an alternative hierarchical structure being established by a user in the content selection and arrangement stages of the process. For example take figure 13 A and B [what happened to 13B?] which show two hierarchical tree structures for displaying the same data arranged in content objects A through J. Using the motor vehicle example nodes A relates to warranty packages relating to new cars and node F relates to roadside assistance programs. Nodes B and G respectively relate to reliability statics for various model cars with a focus on how this impacts on claims or callouts on each of the services respectively. Whereas nodes C to E and H to J relate to the car models themselves. In the first example If a sales person is trying to sell an extended warranty and roadside assistance package he or she might use a presentation flow hierarchy as shown in figure 13A to focus on the services of interest, if this draws our specific questions about car models the presenter can drill down through the presentation heirerchy to get to the model of interest.

On the other hand if the focus is the cars themselves then the hierarchy of figure 13B may be more appropriate, in which car models are the initial focus and the user can drill down to the warranty or roadside assistance slides to demonstrate added value or services that are available.

These two hierarchies can be displayed In separate panes of the arrangement interface 13 or may be arranged each to depend from a different primary node In the same structure.

In some embodiments the user may prefer to view the presentation in a linear format in this case a view can be selected by the user 202. In the linear format the content objects are displayed in a list in their default presentation order. In this linear view , the order of the content objects may be changed by use of the top 1304, up 1306, down 1308 and bottom 1310 buttons. In the linear view content is arranged by the user 202 by selecting a content object in the list (which, as with the tree view, may cause a preview of ^•

^• that content object to be displayed in a preview pane {not shown) of the interface 1300) and then selects one of the four buttons 1304 to 1310. If, after selecting a content item, the user 202 selects the top button 1304 that content object is moved to the top of the list. Similarly, selection of the bottom button 1310 will move the content object to the bottom of the list. Selection of the Up button 1306 and the down button 1308 will move the content object above (i.e. to an earlier place in the presentation) or below (i.e. to a later place in the presentation) the content object immediately above or below the selected content object respectively. If the selected content object is at the top of the list the up button 1306 and top button 1304 are disabled. Similarly if the selected content object is at the bottom of the list the down button 1308 and bottom button 1310 are disabled.

If the user 202 selects multiple adjacent content items from the list (or a group of items that would be grouped under a node in the hierarchical view) and then selects to move those items by use of the buttons, the order of the selected items remains the same and all items are moved according to the function of the button selected as discussed above. For example, if a user 202 selects 4 content items and then selects the up button 1306, all four selected items will be moved above the content object immediately above the uppermost selected item. The order of the 4 selected items will remain the same,

Once the user 202 has finished arranging the content for the presentation the next button 1312 is selected which saves the order of the content and transitions the user 202 to the navigation screen 204. Alternatively, selection of the next button 1312 may be configured to transition the user directly to the review process, discussed below.

Alternatively, the back button 1314 may be selected by the user 202 at any time to save the order of the content items and transition the user to the select content stage 516. It should be noted that the format interfaces allows for forwards and backwards navigation through the process stages. If₁ for example, the user selects a locality in the select localisation stage 506 and elects to proceed to the select theme stage 508, they are still able to return to the select localisation stage 506 by operation of a 'back' button (or similar) and select a different locality before proceeding onwards again.

To further assist navigation through the format process 500 the interfaces (as shown in figures 6 to 11 ) are provided with a formatting process navigation tree 550. The navigation tree 550 provides a tree- structure similar to that used in the selection stage of synchronization listing the stages of the formatting process, to enable quick selection and navigation to a new stage.

Review

After a content object, such as a presentation has been delivered, the content object can be reviewed as part of a wrap-up process. The review process includes the ability to: Review the structure of the presentation using the presentation delivery tool, or other software application. It also enables the user of the remote system to review tracking information gathered by the data gathering subsystem. For example for each presentation the review process can provide data as to what content was used, in which order it was viewed and for how long it was viewed.

The review process also allows a user to review a previously created, modified or downloaded content object prior to modification to create a new presentation.

If no data presentations have been made (as discussed below), the review option 208 is not available to the user 202.

Configure

If the user 202 selects the configure option 210 a configuration interface is provided to the user {not shown). This interface allows a user to access their personal preferences and settings. For example it can be used to access security-related and application-related settings and information, e.g. username and password, the type of Central CMS being accessed, application versiortiπg information etc. All application and configuration details are preferably accessible through a tabbed interface and are stored in the local users' application data repository which is stored in the storage means of the remote CMS. Use of the content delivery subsystem

Once a presentation (or content object of a different type) has been prepared (either by working through the format process 500 or by obtaining a pre-prepared presentation through the synchronization process 300) the user is able to launch the content object from the remote content repository. In the preferred embodiment the content object is a presentation created using the methods and systems described above.

Using the interface 204 depicted in figure 2, if the user selects the "play" button 213 process for displaying a presentation will be initiated.

Figure 14 depicts the process for delivering a presentation created by these systems and processes in an embodiment of the present invention. The presentation process 1400 depicted in figure 14 incorporates an introduction stage 1402 from which the presentation process 1400 may branch into a hierarchical presentation stage 1404 or a linear presentation stage 1406. The presentation process 1400 concludes with the conclusion stage 1408. Each stage of the presentation process 1400 will be discussed in detail below. In certain presentations it is possible for the user to skip between presentation styles.

Introduction stage When the user 202 begins the presentation the introduction is displayed. The introduction may be an animation, video, image or image with text, and may be displayed along with a next button and an exit button.

If the user 202 selects the next button, which depending on the requirements of the presentation may be inoperable or not displayed until completion of the introduction, the presentation transitions to the body of the presentation. in the body of the presentation the presentation process 1400 will either transition to the hierarchical presentation stage 1404 or the linear presentation stage 1406 depending on the nature of the presentation or default settings.

The introduction stage 1402 may be configured to loop the introduction, in the case that the introduction is an animation or video, or hold the last "screen" of the introduction if it is a static image, until the next button is selected by the user 202, or may be configured to automatically proceed to the body of the presentation once a certain period of time has elapsed.

If the user 202 selects the exit button the presentation process will exit. In a preferred embodiment when the exit button is selected to presentation transitions immediately to the conclusion stage of the process or a the display of a predetermined "end screen^* in order to provide a "graceful" but quick, exit from the presentation.

Hierarchical presentation

If the presentation being presented by the user supports hierarchical navigation, on completion of the introduction stage 1402 the presentation process 1400 will transition to the display of the body of the presentation in a hierarchical mode 1404. The hierarchical presentation stage 1404 will be described with reference to figures 16A to 16F which depict a series of layout templates used for hierarchical delivery of content objects. Hierarchal navigation allows quick and user selected access to multiple areas of the presentation.

The layout templates depicted in figures 16 and 15 represent the body of a presentation. The body of a presentation provides the bulk of the information to the audience and is broken up into a plurality of presentation slides, each of which comply with a approved template style. The body templates allow display of content objects and navigation tools and are intended to allow navigation and presentation if information in content objects in a clear, quick and stylistically consistent manner during delivery to a user. The templates depicted in these figured display layout-controlled copy, images, tables, charts, graphs bullets, headlines, footnotes, and pages and other types of content object. They may also include presentation headers which contain logos, metadata, or section/slide headers, and are designed to contain relatively static presentation elements, and simple navigation elements (next section, exit presentation etc.)- Footer sections can be included and are designed to contain static presentation content, such as company names, and simple navigation elements (next section, exit presentation etc.) In the hierarchical presentation mode 1404 the presentation screen 1600 arranges content objects into sections 1602, menu items 1604 and sub menu items 1606. As can be seen from the different figures 16A to 16 F, there are a number of ways the various sections and items can be arranged for ease of navigation by the user 202.

The sections 1602 provide high level headings regarding the menu items 1604 and sub menu items 1606 falling within that section. The menu items correspond to the root nodes in the select content stage 516 of the format process 500. Each menu item 1606 contains one or more sub-menu items 1608, corresponding to the sub-nodes in the select content stage 516 of the format process 500. The sub menu items 1606 are the individual content objects of the presentation such as slides. During the creation of the presentation the content layout chosen in the arrangement stage 516 is mapped to the navigation menu layout used in the presentation.

Depending on the style of navigation used in the presentation screen 1600, one option for navigating through the various menu levels by implementing a fly-out style menu system. In such a system the user places the mouse cursor over a menu item which causes the menu items below that item to be displayed (for example the menu items below section 3 in figures 16A and 16B). When the user 202 removes the mouse cursor from the menu item the sub menu items will be hidden.

Alternatively, the navigation system may require that the menu items are actually selected (clicked on) in order to display the sub menu items (for example the menu items below section 3 in figure 16D). In this case the sub menu items remain visible until the top menu item is selected again, at which point the menu 'collapses', hiding the sub menu items. In addition to the menu items, the presentation screen may also provide a next button 1607 and a previous button 1608. If the next button 1607 is selected by the user and the current content object (e.g. a multi-slide package) has more pages to be displayed, the application will navigate to the next page in the slide. If the next button 1607 is selected and the page on display is the last in the slide package, and there are more siide packages in the presentation, the application will navigate to the first slide in the next slide package. If there are no further slides or slide packages the next button 1607 can be disabled or configured to take the user to the conclusion stage, described below.

If the previous button 1608 is selected by the user 202 and the first page of the current slide package is not being displayed, the application navigates to the previous slide in the package. If the previous button 1608 is selected and the current slide is the first in the package, and there are earlier slides in presentation, the application navigates to the last slide of the previous package. If the current page is the first page in the presentation the previous button 1608 is disabled and cannot be selected. The presentation screen 1600 also provides a home button 1610 and an exit button 1612 If the user 202 selects the home button 1610, the Presentation returns to the first screen of the presentation. If the exit button 1612 is selected the application exits. If desired, the system may place conditions on the use of the home and exit buttons, for example not allowing application exit until all content objects have been viewed.

In the event that more than one possible hierarchical structure has been established in the generation stage a presentation having the same content may also be displayed in a number or different ways. Whilst the content and look and feel of the presentations will be similar the menu structure and default navigation paths will differ. In order to select which of the various structures to use a presenter may be presented with an initial "home" screen after the introduction. Figure 16G is a schematic example of a screen that might be used in a presentation in connection with the motor vehicle sales example of figure 13A and B. In this example the interface 1650 includes three presentation options to the user, entitled, "Us" 1652, "The cars" 1654 and The service" 1656. If a user selects "The cars" 1654 he will be provided with a presentation ordered as established by the order of figure 13B. If The service" 1656 is selected the hierarchy of figure 13A is used for the presentation. If "Us" 1652 is chosen a third hierarchy is used for the presentation flow (not shown). At any stage the user can jump back to this home screen to change their chosen flow if this is convenient. Alternatively a "fly-out" bar e.g. bar 1620 on figure 16A can be provided on one border of the presentation interface that can be used to make the three options appear for the user. Upon completion of the presentation the application navigates to the conclusion stage 1408 of the presentation process 1400. This transition may be automatic, upon reaching the last slide or performed in response to pressing the next or exit button.

Linear presentation stage

If the presentation being presented by the user supports linear navigation, on completion of the Introduction stage 1402 the presentation process 1400 will transition to the linear presentation stage 1406. This linear presentation mode is effectively used for progressing through the presentation in a sequential manner.

The linear presentation stage 1406 will be described with reference to figures 15A to 15D which depict a series of layout templates used for linear delivery of content objects. In the linear presentation stage 1406 the presentation screen 1500 displays a list of presentation sections 1502 providing the user 202 with a reference for where in the presentation they are currently at. A next button 1504 and previous button 1506 are also provided.

If the next button 1504 is selected by the user and the current content object (e.g. slide pack) has more pages to be displayed, the application will navigate to the next page in the slide pack. If the next button 1504 is selected and the page on display is the last in the slide pack, and there are more slide pack in trie presentation, the application will navigate to the first page in the next slide pack . If there are no further slides or pages the next button 1504 is disabled and cannot be selected. Alternatively, in this case selection of the next button takes the user to the conclusion stage.

If the previous button 1506 is selected by the user 202 and the first page of the current slide pack is not being displayed, the application navigates to the previous page in the slide pack. If the previous button 1506 is selected and the cuσent slide is the first in the slide pack, and there is an earlier slide pack in the presentation, the application navigates to the last slide of the previous slide pack. If the current page is the first page in the presentation the previous button 1506 is disabled and cannot be selected.

The presentation screen 1500 also provides a home button 1508 and an exit button 1510, which operate as described in relation to the hierarchical mode above. Upon completion of the presentation of all content objects the application navigates to the conclusion stage 1408 of the presentation process 1400.

Conclusion stage

When the user 202 has completed presentation of the content objects the conclusion is displayed. The conclusion may be an animation, video, image or image with text, and may be displayed along with an exit button and a capture data button.

The conclusion stage 1402 may be configured to loop, in the case that it is an animation or video, until the exit button is selected by the user 202, or may be configured to automatically exit the presentation once a certain period of time has elapsed.

If the user 202 selects the exit button the presentation process will exit. Feedback collection

Figure 17 depicts a feedback capture form usable in an embodiment of the present invention. This form can be used by a presentation user to record audience feedback, sales orders or CRM data etc. Such a screen can be used as a final screen of a presentation conclusion object or as an object in its own right. The capture data screen 1700 is provided with a number of text entry fields 1702 for recording the desired data, a submit button 1704, a reset button 1706, a home button 1708 and an exit button 1710.

If the submit button 1704 is selected the data entered into the text entry fields 1702 is saved and is stored locally in a data storage, e.g. hard drive, of the presenters client system for submission to the central CMS in the next synchronization. If the reset button is selected any data entered into the text entry fields 1702 is cleared. Selecting the home button will transition the presentation system to the associated presentation's first body screen and selection of the exit button 1710 will exit the presentation application.

In an alternative embodiment the form of figure 17 could be an order form for capturing orders from one or more audience members. In this case the customers' orders are stored in a database structure on the presenter's system and uploaded with the next synchronization.

Figure 18 and 19 illustrate two exemplary interfaces that can be user by a user of the system to view metrics data gathered in respect of content objects in the remote CMS. Figure 18 shows an interface 1800 that allows a user to select a content object for wich metric data is to be viewed, the interface 1800 lists a plurality of content objects in a 1802. In this case, the list is ordered by date and time or last use of the object, but other sorting orders may be used. By selecting an object of interest e.g. object 1804, and selecting "View^* 1806 the user if presented with the interface shown in figure 19.

Figure 19 shows an exemplary interface 1900 showing the detailed metrics data that has been gathered in respect of a content object 1804 selected from the list 1802 in Figure 18. In this case the content object is a presentation that is made up of component content objects e.g. slides, buttons menus. The metrics displayed include the data 1902 regarding the session to which the which metrics data relates, including its date, and time of occurrence.

Each event that is undertaken in respect of the content object is listed in the activity log 1904. From the data in this list it is possible to effectively reconstruct the manner in which the content object was used, e.g. the order of presentation, how log the user dwelled on each slide, what data was printed etc.

Data regarding the identity and creation of the content object is also displayed at time 1906. This allows the content object to be identified.

As described above, this metric data, and other captured feedback data, will typically be pushed back to the central CMS server during synchronisation. This data can then be used for post event analysis of presentations or content objects using other software tools that will be known to those skilled in the art.

As mentioned above, the illustrative embodiments of the present invention have been described, by way of example only, in connection with the management, generation and use of marketing materials. However, the present invention should not be considered to be limited to this field of application. Embodiments of the present invention could be implemented in circumstances, including but not limited to:

The delivery of reference information such as maintenance manuals used by technical staff. In this case feedback could include completed maintenance checklists and equipment condition reports.

The delivery of student information such as lecture notes, reading materials etc. In this case feedback may include, questions to a lecturer about content, and records showing which pages a student has viewed.

Distribution of music selections, advertisements, and station promotions etc. to a radio or television station from a central controller, Feedback may include playlists enabling calculation of royalty payments and recordings of station generated programming.

As can be seen from the foregoing, exemplary implementations of the present invention can advantageously be used for the presentation or delivery of information In situations where control (e.g. authorised development, publishing. release and constant update) of content and its format is required, but where the Information may be delivered or read in a standalone, or offline manner. Embodiments can also be advantageously implemented where it is desirable to collect information associated with information¹ delivery, e.g. from users or people to which information delivery is targeted, in the form of feedback (e.g. form entered information) and/or information use patterns, which can be automatically fed back to a central system when communication is next made to a monitoring system. tt will be understood that the invention disclosed and defined in this specification extends to all alternative combinations of two or more of the individual features mentioned or evident from the text or drawings. All of these different combinations constitute various alternative aspects of the invention.

It will also be understood that the term "comprises" (or its grammatical variants) as used in this specification is equivalent to the term "includes" and should not be taken as excluding the presence of other elements or features.

Claims

1. A digital content management system including: at least one content management server including a database structure configured to store digital content; at least one remote content management component having an associated remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote content management component, a synchronization system configured to update the digital content stored in the remote digital content repository to reflect changes made to the digital content stored on the digital content server and send feedback data to the server system relating to the digital content stored on the remote content management component.

2. A system according to claim 1 , wherein the digital content includes a plurality of content objects.

3. A system according to claim 2, wherein the synchronization system can be configured to selectively update content objects from the at least one content management server in accordance with a user access permission level assigned to a user of the remote content management component.

4. A system according to either claim 2 or claim 3, wherein content objects to be updated on the remote content management component are assigned priority levels and the synchronisation system is configured to perform updates of the remote content management component in accordance with the assigned priority levels.

5. A system according to claim 4, wherein the synchronization system implements mandatory updating of content objects assigned a first priority level.

6. A system according to any either one of claim 4 or claim 5, wherein the synchronization system updates content objects assigned at least one second priority level in accordance with a user-made selection.

7. A system according to any one of claims 1 to 6, wherein the remote content management component further includes a communications interface configured to allow the synchronization system to communicate with a content management system application running on the content management server.

8. A system according to claim 7, wherein the communications interface is configured to interface with the content management system application using a standardised data exchange protocol.

9. A system according to any one of the preceding claims, wherein the feedback data includes one or more of the following types of data: modified digital content stored on the remote content management component; digital content created on the remote content management component; data relating to use of at least part of the digital content stored on the remote content management component: feedback relating to any one or more of the quality, style, effectiveness of digital content stored on the remote content management component; data obtained from a form stored on the remote content management component.

10. A system according to any one of claims 2 to 9, wherein the synchronization system is configured to update the digital content stored in the remote digital content repository to reflect changes made to selected digital content objects stored on the digital content server.

11. A system according to any one of claims 2 to 10, wherein only content objects stored in the server system that have been changed or added to the server system are updated in the remote digital content repository.

12. A system according to any one of the preceding claims, wherein the digital content includes composite content objects which include a plurality of component content objects.

13. A system according to claim 12, wherein the synchronization system is configured to update composite content objects stored in the remote digital content repository in a manner such that only those component content objects forming a complex content object that have been changed or added to the server system are updated.

14. A remote content management system configured to be synchronized with a centralized content management server including a digital content server, the remote content management system including: a remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote content management system; and a synchronization system configured to update the digital content stored in the remote digital content repository to reflect changes made to the digital content stored on the digital content server and send feedback data to the centralised content management system relating to the digital content stored on the remote content management system.

15. A system according to claim 14, wherein the digital content includes a plurality of content objects.

16. A system according to claim 15, wherein the synchronization system can be configured to selectively update content objects from the centralised content management server in accordance with a user access permission level assigned to a user of the remote content management system.

17. A system according to either claim 15 or claim 16, wherein content objects to be updated on the remote content management system are assigned priority levels and the synchronisation system is configured to perform updates of the remote content management system in accordance with the assigned priority levels.

18. A system according to claim 17, wherein the synchronization system implements mandatory updating of content objects assigned a first priority level.

19. A system according to any either one of claim 17 or claim 18, wherein the synchronization system updates content objects assigned at least one second priority level in accordance with a user-made selection.

20. A system according to any one of claims 15 to 19, wherein the remote content management system further includes a communications interface configured to allow the synchronization system to communicate with a content management system application running on the centralised content management server,

21. A system according to claim 20, wherein the communications interface is configured to interface with the content management system application using a standardised data exchange protocol.

22. A system according to any one of claims 14 to 21, wherein the feedback data includes one or more of the following types of data: modified digital content stored on the remote content management system; digital content created on the remote content management system; data relating to use of at least part of the digital content stored on the remote content management system : feedback relating to any one or more of the quality, style, effectiveness of digital content stored on the remote content management system; data obtained from a form stored on the remote content management system.

23. A system according to any one of claims 15 to 22, wherein the synchronization system is configured to update the digital content stored in the remote digital content repository to reflect changes made to selected digital content objects stored on the centralised digital content server.

24. A system according to any one of claims 15 to 23, wherein only content objects stored in the centralised digital content server that have been changed or added to centralised digital content server are updated in the remote digital content repository.

25. A system according to any one of claims 14 to 24, wherein the digital content includes composite content objects which include a plurality of component content objects.

26. A system according to claim 25, wherein the synchronization system is configured to update composite content objects stored in the remote digital content repository in a manner such that only those component content objects forming a complex content object that have been changed or added to the server system are updated.

27. A content management server system configured to cooperate with a remote content management system, the content management server system including: a database structure configured to store digital content; and a synchronization interface configured to cooperate with a synchronization system of the remote content management system to update digital content stored in a remote digital content repository of the remote content management system to reflect changes made to the digital content stored in the database structure and to receive feedback data relating to the digital content stored on the remote content management system.

28. A system according to claim 27, wherein the digital content includes a plurality of content objects.

29. A system according to claim 28, wherein the synchronization system can be configured to selectively update content objects from the content management server system in accordance with a user access permission level assigned to a user of the remote content management system.

30. A system according to either claim 28 or claim 29, wherein content objects to be updated on the remote content management system are assigned priority levels and the synchronisation system is configured to perform updates of the remote content management system in accordance with the assigned priority levels.

31. A system according to claim 30, wherein the synchronization system implements mandatory updating of content objects assigned a first priority level.

32. A system according to any either one of claim 30 or claim 31 , wherein the synchronization system updates content objects assigned at least one second priority level in accordance with a user-made selection.

33. A system according to any one of claims 28 to 32, wherein the remote content management system further includes a communications interface configured to allow the synchronization system to communicate with a content management system application running on the content management server system.

34. A system according to claim 33, wherein the communications interface is configured to interface with the content management system application using a standardised data exchange protocol.

35. A system according to any one of claims 28 to 34, wherein the feedback data includes one or more of the following types of data: modified digital content stored on the remote content management system; digital content created on the remote content management system; data relating to use of at least part of the digital content stored on the remote content management system: feedback relating to any one or more of the quality, style, effectiveness of digital content stored on the remote content management system; data obtained from a form stored on the remote content management system.

36. A system according to any one of claims 28 to 35, wherein the synchronization system is configured to update the digital content stored in the remote digital content repository to reflect changes made to selected digital content objects stored on the centralised digital content server.

37. A system according to any one of claims 28 to 36, wherein only content objects stored in the centralised digital content server that have been changed or added to centralised digital content server are updated in the remote digital content repository.

38. A system according to any one of claims 27 to 37, wherein the digital content includes composite content objects which include a plurality of component content objects.

39. A system according to claim 38, wherein the synchronization system is configured to update composite content objects stored in the remote digital content repository in a manner such that only those component content objects forming a complex content object that have been changed or added to the server system are updated.

40 A remote content management system configured to enable use of authorized digital content by a system user, said remote content management system including: a remote digital content repository configured to store digital content derived from a central content management system; content delivery means configured to deliver content from the digital content repository; a content authentication system configured to verify that one or more digital content objects to be delivered by the content delivery means have been authorized for use by the central content management system.

41. A system according to claim 40, wherein the digital content includes a plurality of content objects.

42. A system according to claim 41, wherein each content object stored in the remote digital content repository has associated verification data.

43. A system according to claim 42, wherein the associated verification data is generated on the basis of at least part of content object data.

44. A system according to either claim 42 or claim 43, wherein each digital content object stored in the remote digital content repository has associated verification data supplied by the central content management system.

45. A system according to claim 42 or 43, wherein the verification data is generated by the remote content management system.

46. A system according to any one of claims 41 to 45, wherein the remote content management system is configured to calculate a digital signature for the each content object upon the receipt of the content object.

47. A system according to claim 46, wherein the digital signature is stored as metadata associated with the content object.

48. A system according to claim 46 or 47, wherein the digital signature for the each content object is updated to reflect updates to the content object.

49. A system according to any one of claims 46 to 48, wherein the digital signature relating to each content object can be used by the content authentication system to determine whether one of the following has occurred;. a content object has been approved for use by the remote content management system; a content object has been modified from a form approved by the remote content management system; and a content object has been approved for use delivery by the content delivery system.

50. A system according to any one of claims 46 to 49, wherein the digital signature is generated using a hash function.

51 A system according to any one of claims 41 to 50, wherein the remote content management system can further include a content generation subsystem configured to generate a composite content object, including a plurality of content objects stored in the remote digital content repository.

52. A system according to claim 51, wherein the content authentication system is configured to verify digital content objects used in the generation of composite content objects that are authorized by the central content management system.

53. A remote content management system configured to enable use of digital content by a system user, said remote content management system including: a remote digital content repository configured to store digital content objects derived from a central content management system; a content generation subsystem configured to generate composite content objects, including a plurality of content objects stored in the remote digital content repository; and content delivery means configured to deliver content objects stored in the digital content repository and/or composite content objects generated by the content generation subsystem.

54. A system according to claim 53, wherein the content generation subsystem Includes content selection means enabling the selection of content objects stored in the remote digital content repository for inclusion in a composite content object.

55. A system according to claim 54, wherein the content generation subsystem is configured to enable modification of content objects or composite content objects.

56. A system according to claim 55, wherein in the event that a content object or composite content object is modifiedi the content generation subsystem is configured to store both the modified and unmodified version of the content object or composite content object in the remote digital content repository.

57. A system according to any one of claims 53 to 56, wherein the content generation subsystem includes one or more of the following interfaces: a localization selection interface enabling the customization of a composite content object in a predetermined manner for one of a plurality of locales; a theme selection interface enabling the application of theme to composite content object; a metadata insertion interface, configured to enable metadata to be associated with at least a portion of a content object used in a composite content object; an introduction selection interface configured to enable the selection of a content object or composite content object which, in use, will provide an introduction to a composite content object; a conclusion selection interface configured to enable the selection of a content object or composite content object which, in use, will provide a conclusion to the composite content object; a content rearrangement interface configured to enable a default order of delivery of content objects forming the composite content to be established.

58. A system according to claim 57, wherein the selection and/or rearrangement interfaces include a display portion in which content objects are presented in a hierarchical structure.

59. A system according to claim 58, wherein the hierarchical structure indicates which of a plurality of content objects have been selected for inclusion in the composite content object.

60. A system according to claim 59, wherein the hierarchical structure indicates a default order of delivery of content objects forming the composite content.

61. A system according to any one of claims 68 to 60, wherein a plurality of hierarchies is provided to enable navigation through a plurality of content objects.

62. A system according to claim 61 , wherein a navigation hierarchy selection object is provided, that in use, enables a user to select which default delivery hierarchy to will apply.

63. A system according to claim 63, wherein the hierarchy selection object can be accessed by the user during delivery to allow a change in the default delivery hierarchy to be made.

64. A system according to any one of claims 58 to 63, wherein the hierarchical structure is a tree structure including a plurality of content nodes, each of which optionally has sub-nodes depending there from.

65. A system according to claim 64, wherein nodes are content objects.

66. A system according to claim 64, wherein nodes are composite content objects.

67. A system according to claim 66, wherein it's the sub-nodes can include either content objects or composite content objects.

68. A system according to any one of claims 57 to 67, wherein the content rearrangement and selection interfaces are combined into a single interface enabling both selection and rearrangement of content objects.

69. A system according to any one of claims 53 to 68, wherein the content generation subsystem is configured to generate a visual presentation including a plurality of content objects.

70. A system according to claim 69, wherein the presentation also includes the presentation of associated audio content objects.

71. A remote content management system configured to manage digital content derived from a central content management system , said remote content management system including: a remote digital content repository configured to store the digital content objects derived from the central content management system; one or more complex content objects including a plurality of digital content objects stored on remote digital content repository, wherein in at least two of the plurality of digital content objects forming a complex content object have been assigned at least one default order of delivery to a content receiver; and a content delivery subsystem configured to deliver content to one or more content receivers, which is further adapted to enable delivery of least two of the plurality of digital content objects forming a complex content object in an order different to the assigned default order.

72. A system according to claim 71, wherein the content delivery subsystem is configured to deliver content to one or more content receivers in user determined order.

73. A system according to either one of claim 71 or claim 72, wherein the content delivery subsystem is provided with a user interface to enable hierarchical or sequential delivery of a plurality of content objects.

74. A system according to any one of claims 71 to 73, wherein the content delivery subsystem is provided with means for transitioning Io a termination point in the delivery of a plurality of content objects from at least one intermediate point in the delivery of a plurality of content.

75. A system according to any one of claims 71 to 74, wherein at least a portion of a complex content object is assigned a plurality of default delivery orders.

76. A system according to claim 75, wherein the complex content object is provided with selection means configured to enable a selection between the plurality of default delivery orders during delivery.

77. A system according to claim either one of claims 75 or 76, wherein the content delivery subsystem is provided with selection means configured to enable a selection between the plurality of default delivery orders during delivery.

78. A remote content management system configured to manage digital content derived from a central content management system, said remote content management system including: a remote digital content repository configured to store the digital content objects derived from the central content management system; at least one second subsystem configured to use digital content objects stored in the remote digital content repository; and a data collection subsystem configured to gather data relating to use of one or more content objects stored in the remote digital content repository.

79. A system according to claim 78, wherein the data collection subsystem is connected to a data storage system having a database structure configured to store the gathered data.

80. A system according to either one of claim 78 or claim 79, wherein at least one second subsystem includes any one of the following types of subsystem: a content modification subsystem; a content creation subsystem; a content output subsystem; a synchronization subsystem; or a content formatting subsystem.

81. A system according to any one of claims 78 to 80, wherein the data collection subsystem is configured to gather data relating to any one or more of the following types of use of a content object, by any one or more of the subsystems belonging to the system: ' notification, receipt, transmission, storage, creation, modification, updating, deletion, recording, viewing, playing, broadcasting and output.

82. A system according to any one of claims 78 to 81 , wherein the data collection subsystem is configured to gather data related to one or more of the following: which content objects or groups thereof are used; an order of use of content objects or groups thereof; and a duration of use of one or more content objects.

83. A system according to any one of claims 78 to 82, wherein the data collection subsystem is further configured to gather feedback data input by a system user.

84. A system according to claim 83, wherein the data collection subsystem includes a feedback interface to receive feedback from a user.

85. A system according to claim 84, wherein the feedback data includes one or more of the following types of data: response data indicative of an answer to a question; order data; data derived from forms; uploaded files; and/or content objects.

86. A system according to any one of claims 78 to 85, wherein the content modification subsystem is configured to enable modification of content objects or composite content objects.

87. A system according to claim 86, wherein, in the event that a content object or composite content object is modified the content generation subsystem is configured to store both the modified and unmodified version of the content object or composite content object in the remote digital content repository.

8θ. A system according to any one of claims 78 to 87, wherein the system further includes a synchronization subsystem configured to update the digital content stored in the remote digital content repository and to transmit said data gathered by the data collection subsystem to the central content management system.

89. A system according to claim 88, wherein the data transmitted to the central content management system is formatted in a predetermined manner.

90. A system according to either one of claim 88 or claim 89, wherein the synchronization subsystem is configured to transmit newly created versions of content stored in the remote digital content repository to the central CMS as part of the synchronization process.

91. A method of operating a content management system including at least one central content management system server including a database structure configured to store digital content, and a remote client system including an associated remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote client system, the method including: updating at least some the subset of the digital content stored on the remote client system to reflect changes made to the digital content stored on the central CMS server; and updating the central CMS server with feedback data relating to the digital content stored on the remote client system.,

92. A method, in a remote client system associated with a content management system , said content management system including at least one central content management system server including a database structure configured to store digital content, the remote client system including an associated remote digital content repository configured to store at least a subset of the digital content stored on the digital content server for use by the remote client system, the method including: Receiving and updating at least some the subset of the digital content stored on the remote client system to reflect changes made to the digital content stored on the central content management system server; and transmitting feedback data relating to the digital content stored on the remote client system to the central content management system server.

93. A method according to either of claims 91 or 92, wherein the method further includes an initial step of establishing network communications with the central content management system server.

94. A method according to claim 93,. wherein the step of establishing network communications includes verifying at least one of a user identification and access permissions to digital content stored in the central content management system server.

95. A method in a remote content management system, the method including: storing a digital content object derived from a cental content management system; storing a digital signature corresponding to the digital content object, signifying that the digital content object is authorized for use on the remote content management system; and prior to using the digital content object on the remote client system checking at least that the digital content object is correctly associated with its digital signature.

96. A method according to claim 95, wherein in the event the digital content object stored on the remote client system and its digital signature are not correctly associated the method includes the step of preventing use of the digital content object on the remote client system.

97. A method according to either one of claim 95 or claim 96, wherein the step of checking that the digital content object is correctly associated with its digital signature includes generating a new digital signature on the basis of at least part of the digital content object and comparing it to the stored associated digital signature.

98. A method of generating a content object including a plurality of other content objects for use in a remote content management system, the method including: selecting a plurality of content objects for inclusion in the content object; establishing a default delivery order for the content objects by arranging them in at least one hierarchical structure; and generating a content object for delivery from the plurality of content objects.

99. A method according to claim 98, wherein the hierarchical structure is a tree structure.

100. A method according to either one of claim 98 or claim 99, wherein the method further includes establishing a plurality of default delivery orders for a same plurality of content.

101. A method according to any one of claims 98 to 100, wherein the generated content object includes a navigation means which can be used during delivery to deliver the content objects in an order other than the default order.

102. A method according to claim 101 , wherein the navigation means is a menu structure.

103. A method according to either one of claim 101 or claim 102, wherein the navigation means also provides means to select one of a plurality of default delivery orders to be used.

104. A method according to claim 103, wherein the default delivery order in use can be changed during delivery.

105. A method according to any one of claims 98 to 104, wherein the method further includes one or more of the following steps: configuring the generated content object for use in one or more selected locale; configuring the generated content object for to comply with a chosen theme; storing metadata relating to at least a portion of a content object used in the generated content object; applying an introduction object to the generated content object; and applying a conclusion object to the generated content object.

106. A method in the remote content management system configured to use digital content derived from a central content management system), said method including: providing at least one subsystem configured to use one or more digital content objects stored in a remote digital content repository; and collecting data relating to use of one or more content objects stored in the remote digital content repository.

107. A method according to claim 106, wherein the method further includes gathering data relating to any one or more of the following types of use of a content object: notification, receipt, transmission, storage, creation, modification, updating, deletion, recording, viewing, playing, broadcasting and output; of a content object or group of objects.

108. A method according to either one of claim 106 or claim 107, wherein, the method further includes one or more of the following: gathering data reflecting which content objects or groups thereof are used; gathering data reflecting an order of use of a plurality of content objects; and gathering data reflecting a duration of use of one or more content objects.

109. A method according to any one of claims 106 to 108, wherein the method further includes gathering human feedback data entered by a system user data.

110. A method according to claim 109, wherein the feedback data includes one or more of the following types of data: response data indicative of an answer to a question, order data, data derived from forms, uploaded files and/or content objects.

111. A method according to any one of claims 108 to 110, wherein the method further includes uploading at least part of the gathered data to a central content management system. The

112. A method according to claim 111, wherein the step of uploading is performed intermittently.

113. A method of delivering a content object to a recipient, the method including: delivering content to a recipient; and gathering feedback data related to the delivery of said content object.

114. A method according to claim 113, wherein the method includes transmitting the feedback data to a central management system.

115. A method according to either one of claim 113 or claim 114, wherein the method is performed in a mode In which no data communication is made with the central management system.

116. A method according to either one of claim 114 or claim 115, wherein the step of transmitting the feedback data to a central management system includes an initial step of establishing communications with the central management system.

117. A software application including an instruction set and/or data configured to enable a system according to any one of claims 1 to 90.

118. A software application including an instruction set and/or data configured to implement a method according to any one of claims 91 to 116.

119. A memory means for storing a software application according to either one of claim 117 or claim 118.