GB2377510A

GB2377510A - Content distribution system

Info

Publication number: GB2377510A
Application number: GB0102664A
Authority: GB
Inventors: Hishaam Mufti-Bey
Original assignee: ESUBSTANCE Ltd
Current assignee: ESUBSTANCE Ltd
Priority date: 2001-02-02
Filing date: 2001-02-02
Publication date: 2003-01-15
Also published as: GB0102664D0

Abstract

A content distribution system is disclosed that distributes content, such as stories, articles, books, images, etc., from a content provider to a content user. A method embodying the invention includes obtaining content from a provider and storing it in a content database, and obtaining syndication information from the content provider and storing it in a syndication database. A content user can conduct a search in the content database for content that has been indicated by the content provider as being available for use in circumstances specified by the content user. The content user can be granted a licence to use the content, the licence specifying conditions for use of the content that relate to information in the syndication database.

Description

CONTENT DISTRIBUTION SYSTEM This invention relates to a content distribution system. In particular, it relates to a system for controlled distribution of content to clients in accordance with authorisations possessed by the clients.

At present, there is a large and expanding market for content that can be used by on-line service providers to enhance their on-line services. However, the originators of such content are diverse so it is not easy for originators and clients to make contact with one another. It is also difficult to ensure that the originators are properly paid for their content.

An aim of this invention is to provide a system for distributing content developed by originators to clients for inclusion, for example, in on-line services.

Typically, a user of a system embodying the invention will acquire rights from book publishers, magazines, TV producers, talent agencies, photo agencies and so forth. The user then repackages and distributes, branded content in several selected market sectors, such as cookery, gardening, services, travel, sports, home improvement, health and beauty, etc. The user may license this branded content to (for example) e-commerce vendors, Internet consulting companies, Internet portals, Internet service providers (ISPs), major telecommunication companies, 3rd generation mobile phone service providers and broadband broadcasters using a sophisticated proprietary technology. In this way the user can become a centralised supplier of branded offline content to online companies.

Conventional computerised information management systems are known which enable a user to search through material for documents having certain subject matter content. However, using such a system for the present application, whilst technically feasible, would require a multi-step process in which content having suitable subject matter content is found in the conventional manner and then it must be established, normally

manually, whether the content is in fact available for a desired application. If not, the search must be repeated. This may lead to inefficient use of computer resources.

Accordingly, from a first aspect, this invention provides a method of making content available comprising obtaining content from a content provider and storing the content in a content database; obtaining syndication rights information for the content and storing the syndication rights information associated with the content; and making the content available to a client based on the associated syndication rights information.

By storing both content and syndication rights and making the content data available based on the syndication rights data, suitable content for a particular syndication can be found without requiring a multi-step or iterative process or the syndication rights associated with a particular selected content fragment may be directly retrieved without further searching. Computer resources may thus be saved by not conducting extensive but futile subject matter searches through material which later investigation may reveal not to be available for a particular application. Thus an overall improvement in processing efficiency may be realised as compared to prior art systems. As well as the technical benefit of reducing computer resources required to perform a particular task, the system additionally may provide savings of time for users and as a result may also enable a user to locate content more suitable for a specific syndication purpose in a given practical situation.

This method may give a content provider the opportunity to make their content available to a wide market while retaining control over the circumstances in which their content can be distributed. This may give a content provider access to a wider range of markets than might otherwise be possible. Moreover, it allows a content user to search for and obtain content that is suitable for their requirements without requiring the content user to contact the content provider directly nor to search multiple sources for content nor to perform repeated searches for content and then queries as to whether the content is available.

The syndication rights data typically includes data identifying a territory (or a plurality of territories) in which the data is available; this enables content for a particular geographical location to be rapidly found. The syndication rights data preferably

includes data identifying the owner of syndication rights; this facilitates contact with the owner and payment, to be discussed later below. The syndication rights data preferably identifies at least one available distribution format, for example web publishing, audio, video, multimedia, magazine article. The syndication rights data may include a specification of the use to which the content can be put.

The method will normally include managing the syndication rights data to update or modify syndication rights; this enables changes in permission to be implemented rapidly and without having to re-store the content.

The content is preferably stored in indexed or tagged format ; this may facilitate searching or identifying suitable portions. The method may further comprising receiving content and indexing or tagging items of content. The content may be stored in a mark-up language having tags defined or definable identifying portions of the content, preferably wherein the mark-up language is XML.

Items of content may represent items for publication, electronically or otherwise. The items may include articles, stories, books or images. The items may represent subdivisions of items for publication. The content may be encoded in a standardised format, such as XML. From the point of view of the content user, this ensures that the content will be made available in a format that is independent of the identity of the content provider.

In typical embodiments, items in the content database represent items for publication, electronic or otherwise. Such items may include articles, stories, books, images, amongst other things. Items in the content database may also represent subdivisions of items for publication. Such subdivisions might, for example, include chapters of a book for serialisation or, for example, individual recipes from a recipe book.

Often the stored content comprises portions of content stored as related fragments of an item of content, for example recipes or chapters or pictures from a book. This may facilitate widespread syndication in a number of formats or to a number of users who may not require the whole of the content. For example a single themed picture may be taken from a book. The method may further comprise receiving an item of content,

dividing the item into fragments of content and storing the fragments so as to be accessible separately or sequentially.

Preferably the method includes storing a brand associated with an item or fragment of content. This facilitates rapid searching for a particular brand among the content. A plurality of items or fragments of content may be associated with a single brand. These may have originally come from the same source, for example individual chapters from the same book, or multiple sources, for example separate books by the same author and a video clip.

Preferably, the content is fragmented into a series of independently syndicatable fragments, which may be termed"business objects"and which are stored in a database packaged together with the associated syndication rights.

To help a content user to find content that they require, a method embodying the invention may include receiving a search request from a client, and performing a search in the syndication database for content that is available to the particular client.

In preferred implementations, the method further comprises receiving desired content information and intended syndication information and performing a search for suitable content matching said desired content and available for the intended syndication based on the syndication rights data associated with the content. This enables the appropriate content to be found rapidly.

In response to such a search request, the method may perform a search in the syndication database for content that is relevant to a specified subject matter. Alternatively or additionally, the syndication database may be searched for content that is indicated as being available for use in a specified application. For example, the database may be searched for content that is available for use in a specific territory or in a specified context.

Most typically, searches performed in embodiments of the invention return references only to content that the syndication database indicates that the client is entitled to receive. The terms of a client's entitlement may be specified by the content provider and

stored in the syndication database. As an example, the syndication database may include a specification of the use to which the content can be put.

The method may include the step of filtering available content based on the intended syndication. This may be performed before, after, or with searching based on content, to reduce storage requirements or processing time or both for a search request.

Searching may comprise performing a database query using both said desired content information and said intended syndication information. Using database querying provides an efficient means of searching content. If certain information is omitted from the query, in conventional database query manner, records matching the specified terms will be found.

Often at least a portion of said intended syndication information comprises information entered by a user for a search; this enables the user to specify a particular use at the time of search. Alternatively or in addition at least a portion of said intended syndication information may be stored associated with a user profile for use in multiple searches for that user. For example, if a user is interested in syndication in the UK, that may be stored in the user profile and the user will be limited to suitable content without having to specify this for each search.

Desirably searching further comprises specifying a brand associated with the content.

This facilitates rapid location of particular branded content. In some cases a user may browse available brands and select one or more brands to search amongst. The "brand" may be a relatively broad category, as will become apparent herein.

Searching may include searching for content available in one or more specified territories based on the syndication rights data.

Searching may include presenting a list of available options for browsing by a user; this may facilitate searching by a user looking for some content but not initially critical as to what that content is.

The content and syndication rights data may be stored in a combined database.

Alternatively the content is stored in a content database and is linked to a syndication rights database.

Each item in the content database may be associated with a content provider. Each item in the content database may be associated with one or more rights variables in the syndication database. A rights variable may specify a condition under which the associated content may be used.

In a preferred implementation, the invention provides a method of making content available comprising: storing content from a content provider as a plurality of content fragments in a mark-up language having tags associated with portions of each content fragment; storing associated syndication rights information for each content fragment, the associated syndication rights information including at least one of a territory and distribution format for which the content is available; storing a brand associated with each content fragment ; and making the content available to a client for searching based on content, syndication rights and brand.

The method may include formulating a search query including information specifying desired content, intended syndication and chosen brand and searching for suitable content by matching information in the search query to stored information.

Multiple territories, brands or distribution formats may be specified in a search.

Searching may include one or more of receiving a search request from a client, and performing a search for content that is relevant to a specified subject matter; receiving a search request from a client, and performing a search for content that is indicated as being available for use in a specified application; and receiving a search request from a client, and performing a search for content that is available for use in a specific territory or in a specified context. Searches may return references only to content that the client is entitled to receive, based on stored information.

The method will preferably further comprise supplying selected information to a user, preferably direct from the database; this facilitates distribution of the content. Content may be transferred from the content database to a content user over the Internet.

The method preferably includes providing an interface to a network (such as the Internet) and making the content available to a user over the network; this facilitates searching or access to content by multiple users in multiple locations.

The method may include registering a user and storing syndication parameters for the user, wherein making information available comprises making available only content permitted to the user based on the syndication parameters.

The method may include providing an interface to a network over which a content provider can upload content information ; this facilitates entry of content from distributed content providers or agents.

An interface by means of which an authorised user can modify syndication rights information may be provided The method preferably includes storing usage information for content fragments. The method preferably includes storing fee or licensing parameters associated with the content fragments. These assist in arranging payment to content providers or rights owners. The method may further comprise generating billing information for users who obtain content based on stored fee or licensing parameters. The method may further comprise generating payment information for suppliers of content or content rights owners based on the stored fee or licensing parameters. Beneficiary details, optionally multiple beneficiaries, may be stored associated with particular syndication rights for each content fragment.

Such features facilitate distribution of content with automatic remuneration for owners of the content and are technically beneficial in reducing the computing resources required to implement a conventional billing system. Payment may be made to a content provider calculated upon the basis of the extent to which their content is downloaded. The method may include granting a licence to a content user for use of content selected from the content database. The licence may include terms that are related to the syndication information in the syndication database. This ensures that a content provider's intentions for use of the content are incorporated into a formal agreement with the content user.

In a further aspect, the invention provides a method of making content available for syndication comprising receiving content, identifying separately syndicatable fragments of the content; storing the content as a plurality of separately syndicatable fragments in

a mark-up language in which tags are associated with the content; and associating syndication rights with the fragments.

A further aspect of the invention provides a database for use in any method aspect storing content and syndication rights data associated with the content.

A further aspect of the invention provides a content fragment produced by any method aspect.

A further aspect provides a method of making content available comprising: receiving content; receiving syndication information identifying restrictions on use of the content; storing the content in a database associated with the syndication information ; subsequently making the content available subject to the restrictions on use.

The method preferably further comprises the step of analysing the content into a series of independently syndicatable fragments and storing each fragment associated with the syndication information for that fragment as a business object. The method may include storing a link from the fragments to the source of the fragments and/or storing a link from the source of the fragments to a brand owner, and advantageously includes monitoring usage of individual fragments and generating a report of usage for a brand owner.

Advantageously, if the syndication information indicates that an item of content is not available for an intended use, a warning is generated; this may enable the rights to be cleared so that the content can be syndicated subsequently. Preferably the item of content is not released for the intended use until the syndication information indicates that the content is available for the intended use.

In a further aspect, the invention provides a method of storing content comprising receiving content and initially storing the content in a mark-up language wherein tags identifying sections of content for a plurality of distribution formats are included in the initial storing step.

In a further general aspect, the invention provides a method of storing content comprising receiving content, analysing the content into a plurality of fragments ;

receiving rights information for the fragments and storing the fragments packaged with rights information as individually syndicatable business objects.

Aspects of the invention extend to apparatus, a computer program or computer program product containing instructions for performing the method of any method aspect.

A further aspect provides a computer system for making content available, the system comprising a database for storing content from a content provider and associated syndication rights information for the content. The computer system is preferably implemented on a networked server and having an interface for receiving and/or making content available over the network. The system may include a rights engine for managing syndication rights.

A further aspect of the invention provides a computer program or computer system comprising a database engine for managing a database storing content from a content provider and associated syndication rights information for the content and a rights engine for managing said syndication rights. This may further comprise a payment engine for assigning payment to a beneficiary identified in the database based on content usage by a user.

A further aspect of the invention provides a data packet transmitted over a network containing a request for content and containing information identifying intended syndication of the requested content.

A further aspect of the invention provides a content syndication server comprising a content repository, a syndication database, and a search engine, wherein the search engine refers to the syndication database to determine a user's rights to access content in the content repository, and returns in its search results only those documents that a client is entitled to access. This preferably includes networking hardware to enable the system to communicate with content providers and content users. A server according to this aspect of the invention typically executes a method according to the first aspect of the invention.

Although the content may be searched by the end user, preferably an interface (preferably graphical) is provided to enable an agent or operator to search through

content for each of a plurality of different end users. The interface may include provision of account information for each end user and may include means for providing a basket of provisionally selected items selected by the agent for the user to approve and means for storing a record of items used by the end user.

Preferred features of the method aspects may be applied to other aspects and vice versa.

An embodiment of the invention will now be described in detail, by way of example, and with reference to the accompanying drawings, in which: Figure 1 is a diagram of server software configuration in a system embodying the invention; Figure 2 is a diagram of server hardware configuration in a system embodying the invention; Figure 3 shows a login dialog of the system of Figure 1 or Figure 2; Figure 4 illustrates an external navigation bar for the system of Figure 1 or Figure 2; Figure 5 illustrates a client navigation bar for the system of Figure 1 or Figure 2; Figure 6 illustrates a providers navigation bar for the system of Figure 1 or Figure 2; Figure 7 illustrates a staff navigation bar for the system of Figure 1 or Figure 2; Figures 8A, 8B and 8C show a flowchart for the operation of a rights engine in the system of Figure 1 or Figure 2; Figure 9 shows a rights engine screen of the system of Figure 1 or Figure 2; Figure 10 shows a rights edit screen of the system of Figure 1 or Figure 2; Figure 11 shows a territory index screen of the system of Figure 1 or Figure 2; Figure 12 shows a territory edit screen of the system of Figure 1 or Figure 2; Figure 13 shows a copyright owner index screen of the system of Figure 1 or Figure 2;

Figure 14 shows a copyright owner edit screen of the system of Figure 1 or Figure 2; Figure 15 shows a rights holder index screen of the system of Figure 1 or Figure 2; Figure 16 shows a rights holder edit screen of the system of Figure 1 or Figure 2; Figure 17 shows a rights holder clone edit screen of the system of Figure 1 or Figure 2; Figure 18 shows a rights association index screen of the system of Figure 1 or Figure 2; Figure 19 shows a territory association index screen of the system of Figure 1 or Figure

2 ; Figure 20 shows a territory association select screen of the system of Figure 1 or Figure 2 ; Figure 21 shows a rights properties edit screen of the system of Figure 1 or Figure 2; Figure 22 shows an extraordinary payments dialog box of the system of Figure 1 or Figure 2; Figure 23 shows an approval dialog box of the system of Figure 1 or Figure 2; Figure 24 shows a condition dialog of the system of Figure 1 or Figure 2; Figure 25 shows a brand index screen of the system of Figure 1 or Figure 2; Figure 26 shows a brand edit screen of the system of Figure 1 or Figure 2; Figure 27 shows a book association dialog box of the system of Figure 1 or Figure 2; Figure 28 shows a content association index screen of the system of Figure 1 or Figure

2 ; Figures 29 and 30 are flowcharts describing the operation of the catalogue engine of the system of Figure 1 or Figure 2; Figure 31 shows a basket index screen of the system of Figure 1 or Figure 2; Figure 32 shows a basket edit screen of the system of Figure 1 or Figure 2;

Figure 33 shows a content search template of the system of Figure 1 or Figure 2; Figure 34 shows a search result screen of the system of Figure 1 or Figure 2; Figure 35 shows a book detail page of the system of Figure 1 or Figure 2; Figure 36 shows a content search tree form of the system of Figure 1 or Figure 2; Figure 37 shows a content item detail screen of the system of Figure 1 or Figure 2; Figure 38 shows a basket item edit screen of the embodiment of Figure 1 or Figure 2; Figure 39 shows a book index screen of the embodiment of Figure 1 or Figure 2; Figure 40 shows a book edit screen of the embodiment of Figure 1 or Figure 2; Figure 41 shows a verticals index screen of the embodiment of Figure 1 or Figure 2; Figure 42 shows an edit verticals screen of the embodiment of Figure 1 or Figure 2; Figure 43 shows a languages index screen of the embodiment of Figure 1 or Figure 2; Figure 44 shows a languages edit screen of the embodiment of Figure 1 or Figure 2; Figure 45 shows a navigation bar for an external site associated with an embodiment of the invention; Figure 46 shows a client report index dialog box of the system of Figure 1 or Figure 2 ; Figure 47 shows a client report index screen of the system of Figure 1 or Figure 2; Figure 48 shows a syndicated baskets report screen of the system of Figure 1 or Figure

2 ; Figure 49 shows a content purchased report screen of the system of Figure 1 or Figure 2 ; Figure 50 shows a scanned contents report screen of the system of Figure 1 or Figure 2;

Figure 51 shows a content purchased price report screen of the system of Figure 1 or Figure 2; Figure 52 shows a content sales contact information report screen of the system of Figure 1 or Figure 2; Figure 53 shows a client terms and conditions report screen of the system of Figure 1 or Figure 2; Figure 54 shows a provider report index screen of the system of Figure 1 or Figure 2; Figure 55 shows a further provider report index screen of the system of Figure 1 or Figure 2; Figure 56 shows an all content report index screen of the system of Figure 1 or Figure 2; Figure 56 shows a scanned contract report index screen of the system of Figure 1 or Figure 2; Figure 57 shows a subscribed content report screen of the embodiment of Figure 1 or Figure 2; and Fig. 58 shows the data model used in the embodiment.

In the following description of a preferred embodiment, numerous features are disclosed, the advantages of which, for example in providing a computationally efficient implementation, will be apparent to one skilled in the art and so will not be described in detail for conciseness, and such features may be provided independently of other features unless otherwise stated. In particular, advantageous features which may be provided independently or in combination with other features or as preferred features of the aspects disclosed above independently of other features of the embodiment include, but are not limited to :- the various rights variables, both individually and in the specific combinations disclosed, the features of data organisation, features of menu structures and overall menu and data structure, choice of tags and features of content fragmentation, server arrangement, choice of distribution formats, graphical presentation formats and arrangement of"verticals".

The following herms will be used in the following description: Administration: The part of the system used to manage internal control of the CMA functions. This system usually handles users, groups, and certain database records that control the operation of the CMA.

CDA: Content Display Application. The part of the system that is seen and used by visitors to the site.

CMA: Content Management Application. The part of the system used to create content and manage that content through workflow in order to make it available to the live site.

Content Item: Any logically related unit of content-book, image, paragraph, etc. (also known as a fragment) Association: A logical relationship between two or more entities physically stored in one or more database tables. Example, a book is associated to a brand-a right holder is associated to a book.

Rights Variable: A defined variable related to one or many rights. A right can have many variables associated to it. Example, the Digital Syndication right will have the variables Term, Option, Advance, etc. and their values associated to it. The Interactive Distribution right will have the same variables assigned to it, but the values may or may not be different.

Territory Group: A group of countries put together in order to associate a number of rights that are common across the members of the group.

Person: Either a copyright owner or a rights holder.

Business Object: A fragment of content packaged with rights information and available for syndication as an entity independently of other Business Objects derived from the same content source.

The functional interactions between users, templates, and the database, which together form the system will now be described in detail. Reference should be made to the data model shown in Fig. 58.

With reference to Figure 1, a development embodiment resides on two Sun E250 machines 110,112. The database (Oracle 8.1. 6) resides on a first of these. The StoryServer 5.0 CMA, a development CDA, and Netscape Enterprise Server 4.0 reside on the other. A live embodiment, as shown in Figure 2, may be distributed over a greater number (for example, four) servers 210... 216 for greater performance, connected to the Internet 218 through a firewall 220 and other networking equipment 222,224.

Users, including content providers, content users, and maintenance staff access the system over a web-based interface by means of a web browser. Those local to the system (typically, staff) may access the system over a local-area network, while remote users may access the system over the Internet.

Common CMA Functionality This standard template shown in Figure 2 provides secure access to the internal site. It will automatically be displayed when a user accesses any template path that requires a logon but has not previously logged in. There is no link to the staff logon from the external site. Instead staff will need to type an alternative URL, for example, http://www. server. com/intemal to access the logon prompt. Users of the system will be managed through StoryServer user manager.

The user is required to enter their usemame and password. If the user name or password is invalid, the user will be redirected to this page for another attempt.

All templates for the internal sites will include the NEEDS LOGIN command as the first line in the template.

Internal Site Diagram A navigation bar for the system will reside at the top of each page.

Dependant on each user's role, access will be restricted to functional areas of the internal site required to perform their job. There are four versions of the navigation bar; "external" (no logon required) shown in Figure 4,"client"shown in Figure 5, "provider"shown in Figure 6 and "staff'shown in Figure 7. Initially access is

restricted by simply not having the option to navigate to specific pages contained within the navigation bar's options. The correct navigation bar to display is determined by checking which group to which the logged on user (if logged on) belongs, and showing the appropriate navigation bar with options equivalent to their access rights.

The external navigation bar has the following menu structure: 1. Overview a. What is the Service; b. Benefits to Customers; c. Benefits to Content Owners; 2. Need Content; a. Content & e-Commerce; b. Subjects we cover; c. FAQ; 3. Own Content a. Why choose the service? b. FAQ 4. Corporate a. Management Team b. Partners c. Press Centre d. Careers e. Office location

5. Log in a. Client b. Provider The client navigation bar has the following menu structure: 1. Overview a. What is the service? b. Benefits to Customers c. Benefits to Content Owners 2. Need Content a. Content & e-Commerce b. Subjects we cover c. FAQ 3. Own Content a. Why choose eSubstance ? b. FAQ 4. Corporate a. Management Team b. Partners c. Press Centre d. Careers e. Office location

5. Syndication a. Offers b. Subscriptions c. History d. Transactions e. Syndication Agent download f. Syndication Agent Help g. Help 6. Reports 7. Log Out The providers navigation bar has the following menu structure : 1. Overview a. What is the service ? b. Benefits to Customers c. Benefits to Content Owners 2. Need Content a. Content & e-Commerce b. Subjects we cover c. FAQ 3. Own Content a. Why choose eSubstance ?

b. FAQ 4. Corporate a. Management Team b. Partners c. Press Centre d. Careers e. Office location 5. Reports 6. Log Out The staff navigation bar has the following menu structure: 1. Rights a. Copyright Owners b. Brands c. Right Holders d. Rights e. Territories 2. Catalogue a. Catalogue Manager b. Languages c. Verticals d. Books

Syndication a. Affiliate > i. Create Affiliate ii. List Affiliates by Name iii. List Affiliates by Group iv. Create Affiliate Group v. List Affiliate Groups b. Offers > i. Create Offer ii. List Offers by Name iii. List Offers by Affiliate iv. List Offers by Affiliate Group v. Create Default Bus Terms c. Subscriptions > i. Create Subscription ii. List Subscription by Offer iii. List Subscription by Affiliate iv. List Subscription by Client Affiliate Group d. Syndication Agent download e. Syndication Agent Help f. Help

4. Agents 5. Reports a. Affiliate reports b. Content owner reports 6. Intranet a. Staff directory b. Forms c. Press coverage d. Company guidelines e. Learning zone f. Web links g. Fun h. Affiliate CRM Look-up 7. Log Out Rights Engine The rights engine is a compilation of applications (CMAs) built to enable the rights management of content and the associations of this content. This tool enables quick and intuitive management of dynamic content related to acquisition rights. This includes associating brands, books, content items, the rights holders, and copyright holders.

Operation of the rights engine is illustrate in the flowchart of Figures 8A to 8C.

Rghts Management WorMlow Rights Manager Function: Enter, edit or delete a right.

1. User accesses the service internal site through a browser.

2. User is redirected to a login screen where they can log in if they haven't already done so.

3. User clicks on'Rights'link on navigation bar and is directed to the Rights Index.

4. User either selects a right listed in the index or selects the'ADD RIGHT'link.

Then is directed to the Right Edit Form page.

5. User enters or modifies a right and saves it to the database.

6. A delete can be processed from the Index screen.

Territory Manager: Enter, edit or delete a territory.

1. User accesses the service internal site through a browser.

3. User clicks on'Territories'link on navigation bar and is directed to the Territory Index.

4. User either selects a territory listed in the index or selects the'ADD TERRITORY'link. Then is directed to the Territory Edit Form page.

5. User enters or modifies a territory and saves it to the database.

6. A delete can be processed from the Index screen.

Copyright Owner: Enter, edit or delete a person.

1. User accesses the service internal site through a browser.

3. User clicks on'Copyright Owners'link on navigation bar and is directed to the Copyright Owner Index.

4. User either selects a person listed in the index or selects the'ADD COPYRIGHT OWNER'link. Then is directed to the Copyright Owner Edit Form Template.

5. User enters or modifies a copyright owner and saves it to the database.

6. A delete can be processed from the Index screen.

Brand Manager: Enter, edit or delete a brand.

1. User accesses the service internal site through a browser.

3. User clicks on'Brand Manager'link on the navigation bar and is directed to the Brand.

4. User either selects a brand listed in the index or selects the'ADD BRAND'link.

Then is directed to the Brand Edit Form.

5. User enters or modifies a brand and saves it to the database.

6. A delete can be processed from the Index screen.

Associate a book to a brand.

1. From Brand Edit Form user clicks ADD BOOK link and is directed to the Book Association Index page.

2. An index of all books in the database is displayed along with corresponding checkboxes. User will select one or more books by checking the checkbox and pressing the Associate button. This executes a transaction that associates the selected books to the brand. User is returned to the Brand Edit page.

Associate a rights holder to a book or content fragment.

1. User selects Brand Manager from Front Door.

2. User selects a brand from Brand Index.

3. User selects ADD BOOK from Brand Edit Form.

4. User selects multiple books from a list by checking a box next to each. Pressing the select button returns to the Brand Edit form.

5. User clicks on a book title from the Brand Edit screen. This takes the user to the Content Association screen, which displays a navigation tree, the currently selected content item, and a list of associated rights holder clones for the current content item.

6. User clicks the ADD CLONE link and is directed to the Rights Holder Index page. A right holder clone is chosen from a list by selecting the"associate"link next to the name. This returns the user to the Book Edit screen. If the desired clone does not exist in the list, clicking the ADD CLONE link will direct the user to the Rights Holder Clone Edit screen.

7. User enters information about the rights holder clone in the form. If no rights are associated with a clone, selecting ADD RIGHT will take the user to the Associate Right screen.

8. User selects a right to associate to an affiliate by clicking on the right, returning to the Rights Holder Clone Edit screen.

9. User selects a right and is taken to the Territory Association screen.

10. User selects a territory to edit. If there is no territory in the list, clicking ADD TERRITORY will take the user to the Territory Select screen. Select a territory to associate to the right by clicking on the territory, returning to the Territory Association screen.

11. User fills out the properties for the territory. Clicking on the'Back'button will return the user to the Rights Holder Edit screen.

12. From the Rights Holder Edit screen, an'Associate Clone'link will be displayed.

Clicking this link will associate the clone to the current content item. If at parent level, and no other associations exist in the book, the association will be applied to all content items in the book.

Template Definitions Rights engine front door: This static template is presented when accessing the rights engine, as shown in Figure 9. Access to specific CMA's contained within the rights engine are implemented via the rights menu with the navigation bar component.

Gateways into future rights engine CMAs should be added to this menu.

Table access: None Right Index : This template provides an index of acquisition rights selected from the database. From this page a right can be deleted or selected for editing.

Table Access: ESUBRIGHTS Links to Other Pages: Rights Edit Form, Rights Delete As shown in Figure 9, the rights engine presents an index of rights retrieved from the database, sorted by rights name (ESUBRIGHTS. ESUBRIGHTS. RIGHT-N The Add Right link directs the user to the Rights Edit Template passing an ID of 0. The right name link directs the user to the Rights Edit Template passing the unique Id of the selected right. The DELETE link deletes the corresponding right from the database.

Before deletion a confirmation dialog will be displayed.

Right Edit: This template is used for the addition or editing of a right selected from the Right Index. This is shown in Figure 10.

Table Access: ESUBRIGHTS Links to Other Pages: Rights Index, Rights Save, Rights Delete

Name (ESUBRIGHTS. RIGHTNAME) : free-form text. Required. Description (ESUB~RIGHTS. RIGHTDESC) : free-form text. Required. The Save button saves form fields to the database, the Cancel button returns the user to the Rights Index Template and the reset button resets the contents of the form to the state when page was originally generated.

Territory Index : This template, shown in Figure 11, provides an index of territories selected from the database sorted by groupings. From this page a territory or territory group can be added, deleted or selected for editing.

Table Access: ESUBTERRJTORIES Links to Other Pages: Territory Edit Form, Territory Delete Index of territories retrieved from the database, sorted by territory name (ESUBTERRITORIES. TERRITORYNAME).

The Add Territory link directs the user to the Territory Edit Template with an ID of 0.

The territory name link directs the user to the Territory Edit Template passing the unique Id of the selected territory.

The DELETE link deletes the corresponding territory from the database.

Territory Edit : This template shown in Figure 12 allows the addition or editing of a territory selected from the Territory Index.

Table Access : ESUB~TERRITORIES Links to Other Pages: Territory Index, Territory Save, and Territory Delete

Name (ESUBTERRITORIES. TERRITORYNAME) : free-form text. Required. Description (ESUB~TERRITORIES. TERRITORYDESC) : free-form text. Required.

Code (ESUBTERRITORIES. TERRITORYCODE) : free-form text. Required.

The Save button saves form fields to the database, the Cancel button returns the user to the territory index template and the Reset button resets the contents of the form to the state when page was originally generated.

Copyright Owner Index : This template provides an index of copyright owners selected from the database. From this page a copyright owner can be added, deleted or selected for editing.

Table Access: ESUB~COPYRIGHT~OWNERS Links to Other Pages: Copyright Owner Edit Form, Copyright Owner Delete Index of copyright owners retrieved from the database, sorted by surname (ESUBCOPYRIGHTOWNERS. CPYRTOWNRLNAME).

The Add Copyright Owner link directs the user to the Copyright Owner Edit Template with an ID of 0.

The name link directs the user to the Copyright Owner Edit Form Template passing the primary key of the selected brand.

The Delete link deletes the corresponding copyright owner from the database.

Copyright Owner Edit : As shown I Figure 14, this template displays a form for entering and editing a copyright owner. Basic information about the copyright owner such as name and address will be entered with this template.

Table Access: ESUBCOPYRIGHTOWNERS, ESUBPERSONTYPE Links to Other Pages: Copyright Owner Save, Copyright Owner Delete First Name (ESUB~COPYRIGHT~OWNERS. CPYRT~OWNR~FNAME) : free-form text. Required.

Surname Last name (ESUB~COPYRIGHT~OWNERS. CPYRT~OWNR~LNAME) : free-form text. Required.

Email (ESUB~COPYRIGHT~OWNERS. CPYRTOWNREMAIL) : free-form text.

Required.

Address (ESUBCOPYRIGHTOWNERS. CPYRTOWNRADDRESS) : free-form text. Required.

Phone Number (ESUB~COPYRIGHT~OWNERS. CPYRTOWNRPHONE) : freeform text. Required.

Fax (ESUB~COPYRIGHT~OWNERS. CPYRTOWNRFAX) : free-form text.

Required.

Person Type (ESUBPERSONTYPE. PERSONTYPENAME, ESUBPERSONTYPE. PERSONTYPEDESC) : drop-down. Required.

Primary Indicator (ESUB~COPYRIGHT~OWNERS. RT~HOLDR~TYPE) : drop-down.

Required.

The Save button saves form fields to the database and redirects the user back to the Copyright Owner Index Template, the Cancel button returns the user to Copyright Owner Index Template and the Reset button resets the contents of the form to the state when the page was originally generated.

Rights Holder Index : This template shown in Figure 15 provides an index of rights holders selected from the database. From this page a rights holder can be added, deleted or selected for editing.

Table Access: ESUBRIGHTHOLDERS Links to Other Pages: Rights Holder Edit Form, Rights Holder Delete Index of right holders retrieved from the database, sorted by surname (ESUBRIGHTHOLDERS. RTHOLDRLNAME).

The Add Right Holder link directs the user to the Right Holder Edit Template with an IDofO.

The Name link directs the user to the Right Holder Edit Template passing the passing the unique Id of the selected brand.

The DELETE link deletes the corresponding right holder from the database.

Right Holder Edit : As shown in Figure 16, this template displays a form for entering and editing a right holder.

Table Access: ESUBRIGHTSHOLDERS,ESUBPERSONTYPE Links to Other Pages: Right Holder Save, Right Holder Delete First Name (ESUB~RIGHTS~HOLDERS. RTHOLDRFNAME) : free-form text.

Required.

Surname (ESUB~RIGHTS~HOLDERS. RTHOLDRLNAME) : free-form text.

Required.

Email (ESUBRIGHTSHOLDERS. RTHOLDREMAIL) : free-form text. Required.

Address (ESUBRIGHTSHOLDERS. RTHOLDRADDRESS) : free-form text.

Required.

Phone Number (ESUB~RIGHTSHOLDERS. RT~HOLDR~PHONE) : free-form text.

Required.

Fax (ESUBRIGHTSHOLDERS. RTHOLDRFAX) : free-form text. Required.

The Save button saves form fields to the database and redirects the user back to the Rights Holder Index Template, the Cancel button returns the user to Rights Holder Index Template and the Reset button resets the contents of the form to the state when the page was originally generated.

The Clone Index displays a list of clones created for the current rights holder. The Add Clone button saves the rights holder information and directs the user to the Rights Holder Clone Edit Form Template to add a new clone for that rights holder. The clone name links the user to the Rights Holder Clone Edit Form Template to edit the selected

clone. The DELETE link deletes the selected clone from the database. The Associate link will only be displayed if the user has entered the Rights Holder Edit Form Template through the content association workflow path. This link will associate the clone to the selected content fragment.

Rights Holder Clone Edit : The template shown in Figure 17 displays a form for creating a clone; the clone name and description are required. An index of rights associated to the clone is displayed; associated rights can be added and deleted.

Table Access: ESUB RIGHTHOLDERCLONES, ESUBMAPRIGHTSRTHLDRCLONES Links to Other Pages: Rights Holder Clone Save, Right Holder Edit Form, Right Association Index, Right Association Delete, Territory Association Index First Name (ESUBRIGHTHOLDER. CLONE. RIGHTHOLDERNAME) : free-form text. Required.

Type: Drop down listing the type of Right Holder Choice buttons for type of right-Primary or Additional.

Description (ESUBRIGHTHOLDER. CLONE. RIGHTHOLDERDESC) : free-form text. Required.

The Save button saves form fields to the database and redirects the user back to the Rights Holder Clone Index Template, the Cancel button returns the user to Rights Holder Edit Form Template, and the Reset button resets the contents of the form to the state when the page was originally generated.

The Associated Rights Index displays a list of rights associated to the current clone. The Add Right button will save the clone information and direct the user to the Rights Association Index Template to associate a new right to the current clone. The clone name links the user to the Territory Association Index Template to edit the selected clone. The DELETE link deletes the association of the selected right to the clone from the database.

Rights Association Index : This template shown in Figure 18 displays a form for selecting a right. The user will select these fields and associate territories and rights properties to them.

Table Access : ESUBRIGHTS Links to Other Pages: Territory Association Index The page displays an index of all rights in the database as links. Clicking on a right name link will select it, this directs directing the user to the Territory Association Index Template where territories can be associated to the selected right. If a user attempts to associate variables to a right that has variables associated, a pop-up warning will be displayed. The user will have the option to continue or cancel the operation.

Territory Association Index : As shown in Figure 19, this template displays a list of territories and territory groups associated to a right. The user will select these territories and groups from the Territory Association Select Template and will then associate rights properties to them.

Table Access: ESUB~MAP~RIGHTS~TERRITORIES, ESUB~TERRITORIES Links to Other Pages: Territory Association Select, Territory Association Delete, Rights Properties Edit The ASSOCIATE TERRITORY/GROUP link directs the user to the Territory Association Select Template where territories and groups of territories can be selected.

The territory name links the user to the Rights Properties Edit Form Template where variables are associated to the current clone, right and territory. The DELETE link deletes the selected territory and right association. The FINISHED button returns the user to the Rights Holder Clone Edit Form Template.

Territory Association Select : This template generates a listing of territories and territory groups currently in the database. A user will associate a territory or group by clicking on the territory code.

Table Access : ESUBMAPRIGHTSTERRITORIES, ESUBTERRITORIES

Links to Other Pages: Territory Association Save, Territory Association Index The Territory Index displays territories and territory group codes. The Territory Index displays all territory names in the database. Parent child relationships up to four levels will be shown. The territory name link associates the selected territory or group to the current clone and right and is displayed in the Associated Right Index.

Rights Properties Edit : This template shown in Figure 21 contains a form where rights properties are entered and associated to a right, territory and a rights holder clone.

Table Access : ESUBMAPRIGHTSTERRITORIES, ESUBCURRENCIES, ESUBPRODUCTCPYRTHOLDER, ESUBEXTRAORDINARYPAYMENT, ESUBREQUIREDAPPROVALS, ESUBSALES~CONDITIONS Links to Other Pages: Rights Property Save, Rights Property Delete, Rights Holder Edit Form.

Territory: multi-Select. Required.

(ESUBMAPRIGHTSTERRITORIES. TERRITORYNAME), Exclusive term start date: date (ESUBMAPRIGHTSTERRITORIES. EXCLUSIVETERMSTART) Exclusive term end date: date (ESUBMAPRIGHTSTERRITORIES. EXCLUSIVETERMEND) Non-Exclusive term start date: date (ESUBMAPRIGHTSTERRITORIES. NONEXCLUSIVETERMSTART) Non-Exclusive term end date: date

(ESUBMAPRIGHTSTERRITORIES. NONEXCLUSIVETERMEND) Option : numeric (ESUBMAPRIGHTSTERRITORIES. OPTION) Advance: numeric (ESUBMAPRIGHTSTERRITORIES. ADVANCE) Currency: drop-down. Required (ESUBCURRENCIES. CURRENCYID)

Royalty rate: numeric. Required (ESUBMAPRIGHTSTERRITORIES. ROYALTYRATE) Royalty earn out amount 1: numeric. Required (ESUB~MAP~RIGHTS~TERRITORIES.RYLTY~EARN~OUT~AMT1) Royalty earn out amount 2: numeric (ESUB~MAP~RIGHTS~TERRITORIES.RYLTY~EARN~OUT~AMT2) Initial payment amount: numeric. Required (ESUBMAPRIGHTSTERRITORIES. INTLPAYMENTAMT) Initial payment date: date. Required (ESUBMAPRIGHTSTERRITORIES. INTLPAYMENTDATE) Delivery payment amount: numeric. Required (ESUBMAPRIGHTSTERRITORIES. DLVRYPAYMENTAMT) Subscriber revenue amount: numeric. Required (ESUBMAPRIGHTSTERRITORIES. SUBSCRREVENUEAMT) Regular payment amount: numeric. Required (ESUBMAPRIGHTSTERRITORIES. REGPAYMENTAMT) Regular payment date: date. Required (ESUBMAPRIGHTSTERRITORIES. REGPAYMENTDATE) Regular payment period: drop down, numeric. Required.

(ESUB~MAP~RIGHTS~TERRITORIES.REG~PAYMENT~PERIOD) Embargo date: date. Required.

(ESUBMAPRIGHTSTERRITORIES. EMBARGODATE) Marketing commitment amount: numeric. Required (ESUBMAPRIGHTSTERRITORIES. MKTGCOMMITMENTAMT)

E-commerce revenue percent: numeric. Required (ESUBMAPRIGHTSTERRITORIES. ECOMMERCEREVENUEPCT) Ad revenue percent: numeric. Required.

(ESUBMAPRIGHTSTERRITORIES. ADREVENUEPCT) Subscriber revenue percent: numeric. Required (ESUBMAPRIGHTSTERRITORIES. SUBSCRREVENUEPCT) Syndicate percent: numeric. Required.

(ESUBMAPRIGHTSTERRITORIES. SYNDICATEPCT) Assignment of contract: numeric. Required (ESUBMAPRIGHTSTERRITORIES. ASSGNMTOFCONTRACT)

Product copyright holder name : drop-down. Required Extraordinary payment amount (s): link to pop-up window. Required Required approver information : link to pop-up window. Required.

Sales Condition (s): link to pop-up window. Required.

The Save button applies the entered form information to the database, the Cancel button returns the user to the rights holder edit form, the Clear button resets the form fields to empty, the Copy button saves the contents of the form for pasting into a successive Rights Property Edit Form, and the Paste button produces a pop-up window where a list of previously copied form values is displayed. Clicking on the name of a copy will post it to the current form. The form must then be saved to make the paste permanent Extra Ordinary Payment Amount (Rights Properties Edit) : This section of the Rights Property Edit template allows the addition and deletion of extra ordinary payment amounts associated to a right or group of rights. The dialog box is shown in Figure 22.

Table Access: ESUBEXTRAORDINARYPAYMENT

Extraordinary payment amount: numeric. Required. If a payment amount exists the DELETE link deletes the amount from the database. Required Approver Edit (Rights Properties Edit) This section of the Rights Properties Edit template, shown in Figure 23, allows the addition and deletion of required approvers associated to a right or group of rights.

Table Access: ESUB~REQUIRED~APPROVALS Required approver name: free-form text. Required. Description: free-form text. The DELETE link deletes the approver from the database.

Sales Condition Edit (Rights Properties Edit) : This section of the template allows the addition and deletion of sales conditions associated to a right.

Table Access : ESUB~SALES~CONDITIONS Sales condition description: free-form text. Required. The DELETE link deletes the sales condition from the database.

Brand Index This template provides an index of brands selected from the database. This template is also the entry point to the Rights Management workflow process.

Table Access: ESUBBRANDS Links to Other Pages: Brand Edit Form, Brand Delete Index of brands retrieved from the database, sorted by brand name (ESUBBRANDS. BRANDNAME).

The Add Brand link directs the user to the Brand Edit Form Template with an Id of 0.

The name link directs the user to the Brand Edit Form Template passing the Id of the selected brand. The DELETE link deletes the corresponding brand from the database.

Brand Edit : This template shown in Figure 26 is composed of two sections: one section allows the user to add a brand or edit a brand selected from the Brand Index and

retrieved from the database. A copyright owner is associated to a brand from this template. This template also provides a link to the Book Association Index where the user can select books to associate to the selected brand.

Table Access: ESUB~BRANDS, ESUB~COPYRIGHT~OWNERS Links to Other Pages: Brand Index, Brand Save, Brand Delete, Book Index/Associate, Person Edit Form, Person Delete Name (ESUBBRANDS. BRANDNAME) : free-form text. Required.

Description (ESUBBRANDS. BRANDDESC) : free-form text. Required. Copyright Owner (ESUBBRANDS. COPYRIGHTOWNERID) : drop-down.

Required.

The ASSOCIATE BOOK button saves the brand information and directs the user to the Book Association Index Template passing the primary key of the saved brand.

The Save button saves form fields to the database, the Cancel button returns the user to the Brand Index Template, the Reset button resets the contents of the form to the state when page was originally generated, the Associated Books Index Template displays a list of books associated to the selected brand and the book name links the user to Content Association Index Template with the unique Id of the selected book.

The DELETE link purges the association of the book and the brand.

Book Association Index : This template displays a checkbox list of book names retrieved from the database that are associated to the selected brand or are not associated to a brand at all. One or more books can be associated to a brand at the same time.

Table Access: ESUBCONTENTITEMS Links to Other Pages: Brand Edit Form, Content Association Index, Front Door The current brand name is displayed as a link to the Brand Edit Form Template with the primary key of that brand as the ID. The Book Index Template displays a checkbox and

book titles for every book currently in the database. If the book is already associated to the brand it will be checked when the page is loaded. The Associate button creates an association between the selected brand and all books that are checked and returns the user to the Brand Edit Form Template.

Content Association Index : This template is composed of three components: an index/directory structure of the book selected from the Book Association Index template, a display area for selected content fragments within the book, and an index of right holders associated to selected content fragments and a link to associate additional right holders.

Table Access: ESUBCONTENTITEMS, ESUBMAPCNTNTITMSRIGHTHLDRS, ESUBRIGHTHOLDERS Links to Other Pages: Brand Edit Form, Content Association Index The left side of the page displays a directory structure of content fragments within a book selected on the Book Association Index Template. Fragments link to the upper right section of the page. When clicked the contents of the selected fragment will be displayed. The currently selected fragment will be displayed with a different colour font than non-selected fragments to indicate that it is being viewed.

The Cancel button returns the user to the Book Association Index Template.

The upper right section of the page displays the contents of the currently selected content fragment. On page loading the parent level content fragment (i. e. book) will be selected and details will be displayed-title, author, number of pages, publisher, back cover.

The associated Rights Holder (s) index on the bottom right section of the screen displays a list of right holders associated to the currently selected content fragment, sorted by name and type. The Remove button removes a fragment/right holder association. The Remove button will not be displayed if no right holders are associated to the fragment. The ASSOCIATE RIGHT HOLDER link opens a new browser with the Rights Holder

Index Template where the process of associating additional rights holders to content fragments is began.

Catalogue Engine Overview : The catalogue engine is a collection of applications that provide intuitive functionality for the sales team to browse the content catalogue and compile a selection of desired content forming an offer for a customer request.

Basket Index/Catalogue Manager : The Basket Index Template, as shown in Figure 31, is an index page and will contain a list of all the defined Baskets. This page also serves as the front door to the Catalogue Engine. The Sales Team will see a list of all baskets in the database. From this page, the Sales Team can add a new basket, edit an existing basket, or delete an existing basket.

The Basket Index Template has a list of available baskets. The list will has three columns. The list of available baskets has a column for the'Ready to Syndicate' checkboxes. This is a read-only flag to let the user know if a basket is ready to syndicate. This column is retrieved from the database. The list of available baskets has a column for the'Basket Name'. The name of the basket is a hyperlink. Clicking this link will open the Basket Edit Template. This column is retrieved from the database.

The list of available baskets has a column for a'delete'command. The'delete' command is a hyperlink to delete the basket. Clicking this link will call the Basket Delete Template.

The Basket Index Template has a'create basket'link. Clicking this link will open the Basket Edit Template.

Basket Delete : The Basket Delete Template is a transaction page. This page will delete the selected basket from the database. A confirmation message box will be displayed before any action takes place. There is no GUI for this template. When the basket has been deleted, the user is directed to the Basket Index Template.

Basket Edit : The Basket Edit Template is a content entry page and is shown in Figure 32. This page will be used to add new baskets to the database and to edit

existing baskets. Each basket will have a name, an affiliate, a right, a territory, a start date, an end date, a description, a ready to syndicate flag, license information, selected markets, licensed URLs, and a list of associated content. When in edit mode, data will be populated from the database. For every basket created, a license is also created.

The Basket Edit template has the following fields: A text field labelled'Basket Name'. The user will enter this field. This is a mandatory field. The Basket Edit template has a drop down list labelled 'Affiliate'. The user will select an affiliate from a drop down list of known affiliates. This is a mandatory field.

A drop down list labelled'Right'. The user will select a basket right from a drop down list of known rights. This template additionally has a drop down list labelled'Territory'. The user will select a basket territory from a drop down list of known territories.

* A text field labelled'Start date'. The user will enter the basket start date in this field.

* A text field labelled'End date'. The user will enter the basket end date in this field.

* A text area labelled'Basket Description'. The user will enter this field. This is an optional field.

* A drop down list labelled'Status'. The user will enter the basket's status (Work In Progress, Ready to Syndicate, or Syndicated). The default is WIPWork in Progress.

* A static text labelled'License Information'.

. A text field labelled'Payment Amount'. The user will enter the License Payment Amount in this field.

A text field labelled'Payment Date'. The user will enter the License Payment Date in this field.

A text field labelled'Payment Deal Type'. The user will enter the License Payment deal Type in this field.

A drop down list labelled'Currency'. The user will select a currency from a list of known currencies.

* A static text labelled'Selected markets'.

*A dynamic list for the'Territories'market.

An'add territory'button. Clicking this button will open a pop up window, which allows the user to select a territory from a drop down list of known territories. It also allows the user to set the territory as exclusive. The Territories list will display any territories already selected to the basket. Each territory will have an'exclusive'check box and a'delete'hyperlink. Clicking the delete hyperlink will remove the territory from the basket.

A dynamic list for the'Languages'market. The Languages list has an'add language'button. Clicking this button will open a pop up window, which allows the user to select a language from a drop down list of known languages. It also allows the user to set the language as exclusive. The Languages list will display any languages already selected to the basket. Each language will have an 'exclusive'check box and a'delete'hyperlink. Clicking the delete hyperlink will remove the language from the basket.

A dynamic list for the'Verticals'market.

An'add vertical'button. Clicking this button will open a pop up window, which allows the user to select a vertical from a drop down list of known verticals. It also allows the user to set the vertical as exclusive. The Vertical list displays any verticals already selected to the basket. Each vertical will have an

'exclusive'check box and a'delete'hyperlink. Clicking the delete hyperlink will remove the vertical from the basket.

* A text field labelled'Licensed URL'. The user will enter the URL the basket has content syndicated to.

* An'Add URL'button. Clicking this URL will save the entered URL as a licensed URL.

'A dynamic list of licensed URLs. Clicking on the URL will open the URL.

There will also be a'delete'hyperlink. Clicking on the delete hyperlink will delete the licensed URL from the basket.

* A'Save'button. Clicking on this button will save the basket information and keep the Basket Index Template open.

* A'Cancel'button. Clicking on this button will return the user to the Basket Index Template.

'An'Add Content'button. Clicking on this button will automatically save the basket information and then open the Search Index Template.

'A static text string labelled'Current selected content :' 'A dynamic list of the basket's selected content. The list will have four columns : 0 A column for the'Brand'. This column is retrieved from the database. 0 A column for the'Book Title'name. This column is retrieved from the database and ifs.

0 A column for the'Content'name. The content name will be a hyperlink.

Clicking the link will open the Basket Item Edit Template. This column is retrieved from the database and ifs.

o A column for a'remove'command. The'remove'command will be a hyperlink to delete the content item from the basket. Clicking this link will call the Basket Item Delete Template.

Basket Save : The Basket Save Template is a transaction page. This page will save the basket to the database. A name and an affiliate must be specified before the basket can be saved. There is no GUI for this template. When the basket has been saved, the user is directed back to the Basket Index Template.

Basket Item Delete : The Basket Item Delete Template is a transaction page. This page will delete the selected basket item from the basket. A confirmation message box will be displayed before any action takes place. There is no GUI for this template. When the basket item has been removed from the basket, the user is directed to the Basket Edit Template.

Search Index Template : The Search Index Template shown in Figure 33 will search for content based on market vertical, category, sub-category, and/or keywords. The Search Index Page will use the Autonomy search engine search and catalogue features. This page is used to add content to a basket.

The Content Search Template has the following fields: A read-only text field labelled'Basket'. This field contains the name of the basket the user is adding content to.

'A text field labelled'Search for'. The user will enter the keywords to search for in this field.

* A dynamic list of verticals. Only two levels of the vertical hierarchy will be displayed at one time. Clicking on one of the vertical names will open the Content Search Template with the next two levels of that vertical's hierarchy displayed.

* A'Search'button. Clicking on this button will enable the search engine and open the Search Results Template.

A'Cancel'button. Clicking on this button will return the user to the Basket Edit Template.

Search Results : The Search Results Template is an index or other page. This page will list the results of the search: the book title, author, and brand for each result. The user can view the book details by clicking on the book title.

The Search Results Template will has the following fields * A read-only text field labelled'Basket'. This field contains the name of the basket the user is adding content to.

* A static text field labelled'Results for Search Term'. This field displays the search criteria from the Search Template. The search text box will be a common component across the search and results templates.

* A'new search'link. Clicking this link will return the user back to the Search Index Template.

'A list of search results. The list has three columns.

0 A column for the'Score'. This column is derived.

0 A column for the'Book Title'. This column is retrieved from the database. The book title is a hyperlink. Clicking on this link will open the Book Detail Template.

0 A column for the'Book Author'. This column is retrieved from the database.

Book Detail : The Books Detail Template, shown in Figure 35, is an item page. This page displays the book title, author, brand, abstract, and a list of the content item search results (from the Search Results Template). Clicking on a content item will open the Content Search Tree Template.

The Book Detail Template has the following fields :

* A static text field labelled'Basket'. This field is retrieved from the database.

A static text field labelled'Title'. This field is retrieved from the database.

. A static text field labelled'Author'. This field is retrieved from the database.

'A text field labelled'Brand'. This field is retrieved from the database.

An image. This field is retrieved from the database.

. A static text area labelled'Book Abstract'. This field is retrieved from the database.

* A list of'Content Items'. The list of content items will have one column and will list the content items in this book that match the search results. The list of Content Items has a column for the score. This column is derived from the search results. The list of Content Items also has a column for the content item name. The content item name will be a hyperlink. Clicking this link will open the Content Item Detail Template. This column is retrieved from the database.

A'search results'link. Clicking this link will return the user to the Search Results Template.

Content Search Tree : The Content Search Tree Template is another page shown in Figure 36. The page displays the basket name, book title, book author, brand, book abstract, and book cover image as well as a tree like structure of the selected content item and it's children. An indication will be present if the content item or any child members have a rights violation.

The Content Search Tree Template has the following fields: w A static text field labelled'Basket'. This field is retrieved from the database.

* A static text field labelled'Title'. This field is retrieved from the database.

* A static text field labelled'Author'. This field is retrieved from the database.

. A static text field labelled'Brand'. This field is retrieved from the database.

* An image. This field is retrieved from the database.

* A static text area labelled'Content'. This field is retrieved from the database.

Content Item Detail : The Content Item Detail Template is an item page. This page displays the book title, author, brand, abstract, the rights of the content item, and the licenses sold. The user will be able to add the content item to the basket, define the license terms, and schedule the offer. The Content Item Detail Template has the following fields:

. A static text field labelled'Basket'. This field is retrieved from the database.

* A static text field labelled'Brand'. This field is retrieved from the database.

. An image. This field is retrieved from the database and ifs.

* A'view content'hyperlink. Clicking this hyperlink will open a new page that displays the content item as it would appear when syndicated.

'A static text field that lists the content item's rights violations in red. This field is derived from the database (depending on the rights of the content item). If there are no violations, no warning will be displayed.

A static text area that lists the content item's rights. This includes the following: 'Right', 'Rights Holder Alias','Territory','Exclusive Term Start Date', 'Exclusive Term End Date','Non-Exclusive Term Start Date','Non-Exclusive Term End Date', 'Option','Advance','Royalty Rate', 'Royalty Earn Out Amount 1', 'Royalty Earn Out Amount 2','Initial Payment Amount','Initial Payment Date', 'Delivery Payment Amount', 'Subscriber Revenue Amount', 'Regular Payment Amount', 'Regular Payment Date', 'Regular Payment Period', 'Embargo Date', 'Marketing Commitment Amount','E-Commerce

Revenue Percent', 'Ad Revenue Percent', 'Subscriber Revenue Percent', 'Syndicate Percent', 'Syndicate Unit', 'Assignment of Contract','Currency Code'.

'An'Override'button. Clicking this button will override the license warnings, add the content item to the current basket and return the user to the Basket Edit Template. Supervisors are the only users with access to this button.

An'Add to Basket'button. Clicking this button will add the content item to the current basket and return the user to the Basket Edit Template.

* A'Cancel'button. Clicking this button will return the user to the Content Search Tree Template.

Basket Item Add : The Basket Item Add Template is a transaction page. This page will add the selected content item to the basket. There is no GUI for this template. When the content item has been added to the basket, the user is directed back to the Basket Edit Template.

Basket Item Edit : The Basket Item Edit Template is a content entry page. This page will set the schedule information (for scheduling an offer for syndication) for the specified basket item. The terms include the right's holder approval, the start date, and the end date.

The Basket Item Edit Template has the following fields: * A static text field labelled'Basket'. This field is retrieved from the database.

'A static text field labelled'Title'. This field is retrieved from the database.

* An image. This field is retrieved from the database.

A static text area labelled'Content'. This field is retrieved from the database.

. A static text string labelled'Schedule Information'.

* A text field labelled'Start Date'. This is an optional field.

A text field labelled'End Date'. This is an optional field.

A checkbox labelled'Right's Holder Approval'. The user will enter this field.

The default is unchecked. This is an optional field.

* A'Content Detail'button. Clicking this button will open the Content Item Detail Template.

. A'Save'button. Clicking this button will save the license and schedule information and return the user to the Basket Edit Template.

* A'Cancel'button. Clicking this button will return the user to the Basket Edit Template.

Basket Item Save : The Basket Item Save Template is a transaction page. There is no GUI for this template. When the license terms and schedule information have been saved, the user is directed to the Basket Edit Template.

Book Index : The Book Index Template is an index page and will contain a list of all the defined books in the database. From this page, the users can edit an existing book or delete an existing book. The Book Index Template has the following fields: A list of available books. The list has three columns.

0 A column for the'Brand'. This column is retrieved from the database.

0 A column for the'Book Name'. The name of the book will be a hyperlink. Clicking this link will open the Book Edit Template. This column is retrieved from the database.

0 A column for the'Author'. This column is retrieved from the database.

Book Edit : The Book Edit Template is a content entry page. This page will be used to associate an image to an existing book. Book information will be displayed, but the user cannot edit this information. The book edit template has the following fields: 'A static text field labelled'Title'. This field is retrieved from the database and fs.

A static text field labelled'Author'. This field is retrieved from the database and ifs.

. A text field labelled'Brand'. This field is retrieved from the database.

* A text field labelled'Abstract'. This field is retrieved from the database and ifs.

A text field labelled'Copyright Text'. This is an optional field.

A static text area labelled'Abstract'. This field is retrieved from the database.

* A'Save'button. Clicking this button will save the information by calling the Book Save Template.

. A'Cancel'button. Clicking this button will return the user to the Book Index Template.

Book Save : The Book Save Template is a transaction page. There is no GUI for this template. When the book information has been saved, the user is directed to the Book Index Template.

Verticals Index : The Verticals Index Template will have a list of existing verticals. This ist has two columns: A column for the vertical name. Indentation will be used for each level of the vertical hierarchy.

'A column for a'delete'hyperlink. Clicking on this hyperlink will delete the vertical from the database.

The Verticals Index Template also has an'Add Vertical'hyperlink. Clicking on this link will open the Edit Vertical Template.

Edit Vertical : The Edit Vertical Template has the following fields: * A read-only text field labelled'ID'. This will show the user the database ID for the vertical. This field is retrieved from the database.

'A text field labelled'Name'. The user will enter the vertical name in this field.

This field is mandatory.

* A text field labelled'Description'. The user will enter the vertical description in this field. This field is mandatory.

* A drop-down list labelled'Parent Vertical'. The user will enter the parent vertical from a list of known verticals in this field. This field is mandatory.

* A'Save'button. Clicking this button will save the information and return the user to the Vertical Index Template.

. A'Reset'button. Clicking this button will reset the information on this screen.

* A'Cancel'button. Clicking this button will return the user to the Vertical Index Template.

Languages Index : The Languages Index Template has a list of existing languages. This list has two columns.

A column for the language name.

A column for a'delete'hyperlink. Clicking on this hyperlink will delete the language from the database.

The Languages Index Template also has an'Add Language'hyperlink. Clicking on this link will open the Edit Language Template.

Edit Language : The Edit Language Template has the following fields:

A read-only text field labelled'ID'. This will show the user the database ID for the language. This field is retrieved from the database.

A text field labelled'Name'. The user will enter the vertical name in this field.

This field is mandatory.

* A'Save'button. Clicking this button will save the information and return the user to the Language Index Template.

* A'Cancel'button. Clicking this button will return the user to the Language Index Template.

Syndication Engine Overview : Utilising out-of-the-box syndication server functionality, the Syndication Engine provides functionality for the sales team to create an offer ready for syndication for an affiliate for a pre-selected request.

The processes before syndication includes creation of a basket, search and add content to the basket, gain the copyright owners authorisation to syndicate the content and then set the basket to Ready To Syndicate. At this point manual intervention is needed to create the package template. The offer and subscription are then created within the syndication server application.

After the client then receives notification of the offer by email, they will then log onto the service provider's web site using the Client Logon drop down menu option and access the subscriptions available to them. This will then upload the package for the client's vsagent (or other ICE software) to unpackage.

Configuration/Customisation : Both the Subscription Manager and the Distribution Manager have been customised to include the Navigation Bar.

External Showroom Overview: The external showroom is the showcase for educating prospective clients as to what the system can provide. The site is not to be dynamically generated from content within the database, but rather from static HTML documents.

A navigation bar for the external site is shown in Figure 45. The External site Navigation Bar requires no logon.

The following menu items are available from the external site navigation bar.

Overview Need Content Own Content Corporate Log in What is the Content & e-Why choose Management Client system? Commerce the system? Team Benefits to Subjects we FAQ Partners Provider Customers cover Benefits to FAQ Press Centre Content Owners Careers Office location Reporting Client Reports Client Report Index : The Client Report Index displays a list of report links for the actual client or the selected client. When a staff member has logged in and tries to view the client reports, a selection screen is displayed. Once a client has been selected, the list of valid reports is displayed. Clients that log in will only see the list of valid reports.

The Client Report Index, as shown in Figure 46 has the following fields: A drop down list labelled'Client'. The list items will be valid clients. This information is retrieved from the database.

* A'Select Client'button. Clicking this button will display the reports for the selected client.

Client Report Index : The Client Report Index, as shown in Figure 47, has links to all Affiliate Reports, as listed below.

Syndicated Baskets Report. The Syndicated Baskets Report, as shown in Figure 48, displays previously syndicated basket information for the client. The Syndicated Baskets Report displays a list of syndicated baskets. The list has six columns, as follows.

'Client Name'column.

.'Basket ill'column.

.'Basket Name'column.

'Basket Description'column.

'Basket Start Date'column.

.'Basket End Date'column.

All information is retrieved from the database.

Content Purchased Report : The Content Purchased Report displays all content that has been purchased by this client, and is shown in Figure 49.

The Content Purchased Report has a list of content. Only the first 300 characters will be displayed.

Scanned Contracts Report : The Scanned Contracts Report will display a scanned image of the contract between the service provider and the client.

The Scanned Contract Report displays a list of contracts. The list has two columns: 'A'Client Name'column.

. A'Sales Contract'column. The sales contract will be a hyperlink. Clicking the link will display the actual contract.

Content Purchase Price Report : The Content Purchase Price Report will display the purchase price for the content the client bought.

The Content Purchase Price Report has a list of purchase prices. The list has three columns: # A Book Title' column.

# A Content' column.

. A'Purchase Price'column.

Sales Contact Information Report : The Sales Contact Information Report displays the client's contact information. The report screen has the following fields:

. A read-only text field labelled'Contact Name'.

* A read-only text field labelled'Contact Type'.

* A read-only text field labelled'Contact Phone'.

. A read-only text field labelled'Contact Email'.

Terms and Conditions Report : The Terms and Conditions Report will display the client's terms and conditions.

The Terms and Conditions Report has a list of terms and conditions. The list has four columns.

# A Client Name' column.

* A'License Information' column.

* A'Payment Information'column.

* A'Usage Information'column.

Provider Reports

Provider Report Index : The Provider Report Index displays a list of report links for the actual provider or the selected provider. When a staff member has logged in and tries to view the provider reports, a selection screen is displayed. Once a provider has been selected, the list of valid reports is displayed. Providers that log in will only see the list of valid reports.

The Provider Report Index has a drop down list labelled'Provider'. The list items are valid providers. This information is retrieved from the database. The Provider Report Index has a'Select Provider'button. Clicking this button will display the reports for the selected provider.

The Provider Report Index has links to all Content Owner Reports All Content Report : The All Content Report will display a content listing of all content the provider owns. The All Content Report has a'Content Listing'. The list has two columns : a'Book Title'column and a'Content'column.

Scanned Contract Report : The Scanned Contracts Report displays a scanned image of the contract between the service provider and the information provider. The Scanned Contract Report has a list of contracts. The list has one column : an'Acquisition Contract'column. The acquisition contract is a hyperlink. Clicking the link will display the actual contract.

Subscribed Content Report : The Subscribed Content Report displays a content listing of all content (that the provider owns) that has been subscribed. The Subscribed Content Report will has a list of subscribed content. The list has five columns: w A'Client'column.

* A'Book Title'column.

'A'Content'column.

* A'Start Date'column.

'A'End Date'column.

It will be understood that the present invention has been described above purely by way of example, and modifications of detail can be made within the scope of the invention.

The Applicant asserts design right and/or copyright in the accompanying drawings.

Each feature disclosed in the description, and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination.

Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.

Claims

1. A method of making content available comprising obtaining content from a content provider and storing the content in a content database; obtaining syndication rights information for the content and storing the syndication rights information associated with the content; and making the content available to a client based on the associated syndication rights information.

2. A method according to Claim 1 wherein the syndication rights data includes data identifying a territory in which the data is available.

3. A method according to any preceding claim wherein the syndication rights data includes data identifying the owner of syndication rights.

4. A method according to any preceding claim wherein the syndication rights data identifies at least one available distribution format.

5. A method according to any preceding claim, further comprising managing the syndication rights data to update or modify syndication rights.

6. A method according to any preceding claim wherein the content is stored in indexed or tagged format.

7. A method according to Claim 6 further comprising receiving content and indexing or tagging items of content.

8. A method according to Claim 6 or 7 wherein the content is stored in a mark-up language having tags defined or definable identifying portions of the content, preferably wherein the mark-up language is XML.

9. A method according to any preceding claim wherein the stored content comprises portions of content stored as related fragments of an item of content.

10. A method according to Claim 9, further comprising receiving an item of content, dividing the item into fragments of content and storing the fragments so as to be accessible separately or sequentially.

11. A method according to any preceding claim further comprising storing a brand associated with an item or fragment of content.

12. A method according to Claim 11, wherein a plurality of items or fragments of content are associated with a single brand.

13. A method according to any preceding claim further comprising receiving desired content information and intended syndication information and performing a search for suitable content matching said desired content and available for the intended syndication based on the syndication rights data associated with the content.

14. A method according to Claim 13 including the step of filtering available content based on the intended syndication.

15. A method according to Claim 13 wherein searching comprises performing a database query using both said desired content information and said intended syndication information.

16. A method according to any of Claims 13 to 15, wherein at least a portion of said intended syndication information comprises information entered by a user for a search.

17. A method according to any of Claims 13 to 16, wherein at least a portion of said intended syndication information is stored associated with a user profile for use in multiple searches for that user.

18. A method according to any of Claims 13 to 17 wherein searching further comprises specifying a brand associated with the content.

19. A method according to any of Claims 13 to 18 wherein searching includes searching for content available in one or more specified territories based on the syndication rights data.

20. A method according to any of Claims 13 to 19 wherein searching includes presenting a list of available options for browsing by a user.

21. A method according to any preceding claim wherein the content and syndication rights data are stored in a combined database.

22. A method according to any of Claims 1 to 20 wherein the content is stored in a content database and is linked to a syndication rights database.

23. A method of making content available comprising: storing content from a content provider as a plurality of content fragments in a mark-up language having tags associated with portions of each content fragment; storing associated syndication rights information for each content fragment, the associated syndication rights information including at least one of a territory and distribution format for which the content is available; storing a brand associated with each content fragment; and making the content available to a client for searching based on content, syndication rights and brand.

24. A method according to Claim 23, further comprising formulating a search query including information specifying desired content, intended syndication and chosen brand and searching for suitable content by matching information in the search query to stored information.

25. A method according to any of Claims 13 to 20 or 24 wherein multiple territories, brands or distribution formats are specified in a search.

26. A method according to any preceding claim, further comprising supplying selected information to a user.

27. A method according to any preceding claim further comprising providing an interface to a network and making the content available to a user over the network.

28. A method according to Claim 27 further comprising registering a user and storing syndication parameters for the user, wherein making information available comprises making available only content permitted to the user based on the syndication parameters.

29. A method according to any preceding claim further comprising providing an interface to a network over which a content provider can upload content information.

30. A method according to any preceding claim further comprising providing an interface by means of which an authorised user can modify syndication rights information.

31. A method according to any preceding claim further comprising storing usage information for content fragments.

32. A method according to any preceding claim further comprising storing fee or licensing parameters associated with the content fragments.

33. A method according to Claim 32 further comprising generating billing information for users who obtain content based on the stored fee or licensing parameters.

34. A method according to Claim 32 or 33 further comprising generating payment information for suppliers of content or content rights owners based on the stored fee or licensing parameters.

35. A method according to Claim 34 wherein beneficiary details, optionally multiple beneficiaries, are stored associated with particular syndication rights for each content fragment.

36. A method according to any preceding claim including receiving a search request from a client, and performing a search for content that is relevant to a specified subject matter.

37. A method according to any preceding claim including receiving a search request from a client, and performing a search for content that is indicated as being available for use in a specified application.

38. A method according to any preceding claim including receiving a search request from a client, and performing a search for content that is available for use in a specific territory or in a specified context.

39. A method according to any one of claims 36 to 38 in which searches return references only to content that the client is entitled to receive, based on stored information.

40. A method according to any preceding claim in which the syndication rights data includes a specification of the use to which the content can be put.

41. A method according to any preceding claim in which payment is made to a content provider calculated upon the basis of the extent to which their content is downloaded.

42. A method according to any preceding claim including granting a licence to a content user for use of content selected from the content database.

43. A method according to claim 42 in which the licence includes terms that are related to the syndication information in the syndication database.

44. A method according to any preceding claim in which items of content represent items for publication, electronically or otherwise.

45. A method according to claim 44 in which the items include articles, stories, books or images.

46. A method according claim 44 or claim 45 in which the items in the content database represent subdivisions of items for publication.

47. A method according to any preceding claim in which the content in the content database is encoded in a standardised format.

48. A method according to claim 47 in which the content is stored in the content database encoded in XML.

49. A method according to any preceding claim in which each item in the content database is associated with a content provider.

50. A method according to any preceding claim in which each item in the content database is associated with one or more rights variables in the syndication database.

51. A method according to claim 50 in which the or each rights variable specifies a condition under which the associated content may be used.

52. A method according to any preceding claim in which content is transferred from the content database to a content user over the Internet.

53. A method of making content available for syndication comprising receiving content, identifying separately syndicatable fragments of the content; storing the content as a plurality of separately syndicatable fragments in a mark-up language in which tags are associated with the content; and associating syndication rights with the fragments.

54. A database provided for use in the method of any preceding claim storing content and syndication rights data associated with the content.

55. A content fragment produced by the method of any of Claims 1 to 53.

56. A computer program or computer program product containing instructions for performing a method according to any of Claims 1 to 53.

57. A computer system for making content available, the system comprising a database for storing content from a content provider and associated syndication rights information for the content.

58. A computer system according to Claim 57 implemented on a networked server and having an interface for receiving and/or making content available over the network.

59. A computer system according to Claim 57 or 58 including a rights engine for managing syndication rights.

60. A computer program or computer system comprising a database engine for managing a database storing content from a content provider and associated syndication rights information for the content and a rights engine for managing said syndication rights.

61. A computer program or computer system according to Claim 60 further comprising a payment engine for assigning payment to a beneficiary identified in the database based on content usage by a user.

62. A data packet transmitted over a network containing a request for content and containing information identifying intended syndication of the requested content.

63. A method of distributing content substantially as herein described with reference to the accompanying drawings.

64. A content syndication server comprising a content repository, a syndication database, and a search engine, wherein the search engine refers to the syndication database to determine a user's rights to access content in the content repository, and returns in its search results only those documents that a client is entitled to access.

65. A content syndication server according to claim 64 executing a method according to any one of claims 1 to 52.

66. A content syndication server according to claim 64 or claim 65 including networking hardware to enable the system to communicate with content providers and content users.

67. A content syndication server substantially as herein described with reference to the accompanying drawings.

68. A method of making content available comprising: receiving content; receiving syndication information identifying restrictions on use of the content; storing the content in a database associated with the syndication information ; subsequently making the content available subject to the restrictions on use.

69. A method according to Claim 68, further comprising the step of analysing the content into a series of independently syndicatable fragments and storing each fragment associated with the syndication information for that fragment as a business object.

70. A method according to Claim 69 further comprising storing a link from the fragments to the source of the fragments.

71. A method according to Claim 70, further comprising storing a link from the source of the fragments to a brand owner.

72. A method according to Claim 71, further comprising monitoring usage of individual fragments and generating a report of usage for a brand owner.

73. A method according to any of Claims 68 to 72 wherein, if the syndication information indicates that an item of content is not available for an intended use, a warning is generated.

74. A method according to Claim 73, wherein the item of content is not released for the intended use until the syndication information indicates that the content is available for the intended use.

75. A method of storing content comprising receiving content and initially storing the content in a mark-up language wherein tags identifying sections of content for a plurality of distribution formats are included in the initial storing step.

76. A method of storing content comprising receiving content, analysing the content into a plurality of fragments ; receiving rights information for the fragments and storing the fragments packaged with rights information as individually syndicatable business objects.