EP1147475A1 - Structure de m tadonn es associ es aux m dias lectroniques - Google Patents

Structure de m tadonn es associ es aux m dias lectroniques

Info

Publication number
EP1147475A1
EP1147475A1 EP99946306A EP99946306A EP1147475A1 EP 1147475 A1 EP1147475 A1 EP 1147475A1 EP 99946306 A EP99946306 A EP 99946306A EP 99946306 A EP99946306 A EP 99946306A EP 1147475 A1 EP1147475 A1 EP 1147475A1
Authority
EP
European Patent Office
Prior art keywords
metadata
storage
level
media
entities
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP99946306A
Other languages
German (de)
English (en)
Inventor
David Chan
Tracy-Anne Ormrod
Carol Janet Owens
Diane Marie Mcgregor
Wesley Jonathan Curtis
Smith John Jordan
Arthur Brian Haynes
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
British Broadcasting Corp
Original Assignee
British Broadcasting Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from GBGB9901807.9A external-priority patent/GB9901807D0/en
Application filed by British Broadcasting Corp filed Critical British Broadcasting Corp
Publication of EP1147475A1 publication Critical patent/EP1147475A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/48—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data

Definitions

  • This invention relates to methods and systems for storing and exchanging metadata, or data about data, between systems. It is particularly, but not exclusively, concerned with the storage and exchange of metadata associated with media materials, concepts and services within the context of media production and distribution, and its future evolution.
  • a video tape in a box with a label, is a physical object which is managed through well-understood logistical methods.
  • an Information Technology repository such as a server, it cannot be distinguished from any other data, whether media or business data .
  • a method for defining a metadata structure relating to media materials, concepts and services comprising the steps of: defining a plurality of storage entities at a plurality of levels for metadata relating to media materials, concepts and services, the storage entities having a plurality of storage elements and being related with a media metadata subject grouping, and arranged in hierarchical and non-hierarchical relationships allowing an appropriate combination of elements as required; storing metadata relating to a given storage entity in one of a plurality of storage elements of the entity at that level, each storage element representing an attribute or characteristic of the entity subject or media material; arranging media metadata entities and attributes relating directly to the media material, concepts and services in hierarchical and non-hierarchical entity level relationships allowing an appropriate combination of elements are required; and wherein for hierarchical entities, the storage elements of storage entities at a level apart from the lowest level, comprise the storage elements of the immediately lower storage level.
  • the invention further provides a data structure for defining broadcast media metadata comprising: a plurality of storage entities for metadata relating to media materials, concepts and services, the entities being arranged in storage levels and each entity comprising a plurality of storage elements each for storing metadata relating to a given entity, each storage element representing an attribute or characteristic of the entity subject or the media material; wherein the storage levels are hierarchical and non-hierarchical allowing the appropriate combination of elements as required, where the levels are hierarchical, the storage elements of storage entities, apart from the lowest level, comprise the stores of the immediately lower storage level.
  • the invention still further provides a data structure for defining media metadata comprising: a plurality of storage entities for metadata relating to media production and distribution, the entities being arranged at storage levels and each entity comprising a plurality of storage elements each holding metadata relating to a given entity level, each storage element representing an attribute or characteristic of the entity subject or the media material; a plurality of levels of business entities each comprising storage elements storing business metadata, the business entities being linked to the metadata stores at a storage level dependent on the business element metadata, one of the plurality of levels of business stores comprising a rights level and having one or more storage entities containing business metadata identifying legal rights attached to the media material, the business metadata including the legal jurisdiction of the right, the geographical territory of the right, the duration of the right and the owner of the right; wherein the metadata storage levels are hierarchical and non-hierarchical and, for hierarchical storage levels, the metadata stored in the storage elements of storage entities at a level, apart from the lowest level comprise the stores of the immediately lower storage level.
  • the invention also provides a data structure for defining media metadata comprising: a plurality of storage entities for metadata relating to media production and distribution, the entities being arranged at storage levels and each entity comprising a plurality of storage elements each holding metadata relating to a given entity level, each storage element representing an attribute or characteristic of the entity subject or the media material; a rights store linked to at least one of the metadata stores and comprising one or more storage entities containing business metadata identifying legal rights attached to the media material, the business metadata including the legal jurisdiction of the right, the geographical territory of the right, the duration of the right and the owner of the right; wherein the metadata storage levels are hierarchical and non- hierarchical and, for hierarchical storage levels, the metadata stored in the storage elements of storage entities at a level, apart from the lowest level, comprise the stores of the immediately lower storage level.
  • a method embodying the invention may define a metadata structure relating to media material, concepts and services, which in turn provides a method for defining storage and exchange requirements.
  • the method comprises of the steps of defining a plurality of storage entities for metadata related to media production and distribution, the entities being associated with a media metadata subject grouping, and arranged in hierarchical and non-hierarchical relationships. Metadata relating to a given storage entity is organised in one of a plurality of storage elements at that level, each element representing an attribute or characteristic of the entity subject or media material .
  • Media metadata entities and attributes relating directly to media material, concepts and services are arranged hierarchically and non-hierarchically allowing the appropriate combinations of metadata to be supported. Where storage levels are hierarchical, the storage elements in stores at the lower levels are linked in defined relationships with stores at the higher levels. The result is a structure for defining metadata, wherein all individual metadata values may be organised according to the entities and relationships defined.
  • a data structure embodying the invention may define the business data not directly related to media material but vital for its management and exploitation, by defining a plurality of business entities each comprising business elements storing business data, the business stores being related to the media metadata stores at a level dependent on the business element metadata.
  • One or more of a plurality of entities comprises a rights storage entity or entities containing business metadata identifying legal rights attached to the media material, wherein the relationships with the appropriate media metadata are recorded.
  • storage levels are hierarchical, the storage elements in stores at the lower levels are linked in defined relationships with stores at the higher levels.
  • the invention also provides a method of defining a standard media exchange framework comprising the steps of: storing media metadata by the method defined above; defining industry-specific processes involved in media production and distribution, and defining the flow of data between them.
  • the metadata defined by the metadata structure may be mapped on to this process flow, in order to define metadata exchange requirements between different process stages and business areas.
  • a method embodying the invention may define media metadata and related business metadata exchange requirements by using the process flow definitions on to which the storage entities may be mapped, so that the systems requirements at each interface may be identified against a standard structure, providing a framework for systems development and integration.
  • the method and data structure serves as a basis for defining standard media metadata exchange requirements between process and business interfaces at an appropriate level of granularity.
  • Embodiments of the invention have the advantage that metadata related to a media item can be stored in a manner which minimises storage space and minimises retrieval time.
  • a metadata item for a media item need only be stored once and is retrievable at any point in the broadcast media chain.
  • embodiments of the invention allow media exchange formats to be defined which embed certain metadata in the media object, for example into a video frame from where they can be accessed at any point in the broadcast chain.
  • media concept referred to herein refers to an idea for a media item such as a television programme or series of programmes independent of its realisation. It is common in the media industry to buy, sell and licence media concepts and as such they may be regarded as intellectual property.
  • Figure la), lb) and lc) show three views of an Entity Relationship Diagram embodying the invention
  • Figure 2 is an overall process flow diagram illustrating broadcast media production and distribution;
  • Figure 3 shows in more detail the CREATE TV/RADIO PROGRAMME process box of figure 2;
  • Figure 4 shows in more detail the GATHER NEWS process box of figure 2;
  • Figure 5 shows the RESEARCH EVENT process of figure 4 in more detail
  • Figure 6 shows ALLOCATE RESOURCES process of figure 4 in more detail
  • Figure 7 shows the CREATE NEWS PROGRAMMES process of figure 2 in more detail
  • Figure 8 shows the SELECT PROGRAMME CONTENT process of figure 7 in more detail
  • Figure 9 shows the RESEARCH AND CAPTURE process of figure 7 in more detail
  • Figure 10 shows the COMMISSION OUTPUT process in more detail
  • Figure 11 shows the EVALUATE and SELECT OFFERS process in figure 10 in more detail
  • Figure 12 shows the DEVISE OUTLINE SCHEDULE process of figure 10 in more detail
  • Figure 13 shows the ACQUIRE PROGRAMME/EVENT RIGHT process of figure 2 in more detail
  • Figure 14 shows the SCHEDULE & PROMOTE process of figure 2 in more detail
  • Figure 15 shows the CREATE TRANSMISSION SCHEDULE process of figure 14 in more detail
  • Figure 16 shows the PLAN & INITIATE ON-AIR PUBLICITY process of figure 14 in more detail
  • Figure 17 shows the PLAY-OUT AND TRANSMIT process of figure 2 in more detail
  • Figure 18 shows the PERFORM PLAY-OUT process of figure 17 in more detail
  • Figure 19 shows the MANAGE MATERIAL STORE and ARCHIVE process of figure 2 in more detail
  • Figure 20 shows the MANAGE INCOMING MATERIAL process of figure 19 in more detail
  • Figure 21 shows the RETRIEVE MATERIAL process of figure 19 in more detail
  • Figure 22 shows the MANAGE RIGHTS AGENCY process of figure 2 in more detail
  • Figure 23 shows the PLAN OUTPUT process of figure 2 in more detail
  • Figure 24 shows the UNDERSTAND AUDIENCE & COMPETITORS process of figure 2 in more detail
  • Figure 25 shows the MANAGE RESEARCH STATISTICS process of figure 24 in more detail
  • Figure 26 shows the HANDLE AUDIENCE FEEDBACK process of figure 24 in more detail
  • Figure 27 shows the DEAL WITH AUDIENCE FEEDBACK process of figure 24 in more detail
  • Figure 28 shows the PROVIDE RESOURCES TO PROGRAMMES process of figure 2 in more detail.
  • a media material item such as a television programme may be described as an interrelated series of entities .
  • the term media material includes any logical whole piece of media for distribution. It may, for example, be a news item, a section of video, a series of data or software or audio.
  • the central entity is the EDITORIAL OBJECT VERSION 10 together with its sub-types PROGRAMME VERSION 11 and ITEM VERSION 12 (it is assumed that these are included whenever the main entity 10 is referred to) .
  • An entity is a logical grouping of data to be stored, retrieved and used.
  • This data is all programme and item metadata as it describes a characteristic or attribute of the PROGRAMME or EDITORIAL OBJECT VERSION.
  • the entity contains a number of data items.
  • the EDITORIAL OBJECT VERSION entity 10 holds both key and non-key data.
  • the key data for the EDITORIAL OBJECT VERSION entity is the EOV count PK1 and EOC number PK2 which together make up a unique identifier.
  • the tags PK1 and PK2 show the two parts of the primary key. For data to be allocated a primary key it should be unique in its own right or unique when taken with another data item.
  • the primary key is the "way-in" to the information contained within the entity. It can be seen from figure la) that all the entities contain key data. Key data is essential to those entities. An entity might only hold key data.
  • the EDITORIAL OBJECT CONCEPT entity 20 is an example of an entity which holds key metadata which is unique in its own right. Thus, the primary key is simply EOC number PK1.
  • the non-key data relates to editorial information about the programme or item, such as the title, working title, synopsis, etc.
  • VERSION_INST 30 and MEDIA_OBJECT_INSTANCE 32 refers to a unique material embodiment of an editorial or media object, whether electronic or physical
  • THE EDITORIAL OBJECT VERSION entity 10 is linked to a number of other entities. As the programme or item is the end product of the creation process, it follows that the vast majority of the other entities will, either directly or indirectly, be linked to the EDITORIAL OBJECT VERSION 10.
  • the link between entities is a relationship, with the link line showing how the data is related.
  • the link line shows how the data is related.
  • At the end of the relationship line are two symbols indicating whether the connection is mandatory and whether only one or many connecting entities are to be supported.
  • a particular relationship with only a single symbol indicates an entity being a subtype of another entity.
  • the EDITORIAL OBJECT VERSION entity 10 is linked to a number of other entities such as the entity EDITORIAL OBJECT CONCEPT 20, the relationship being that the EDITORIAL OBJECT CONCEPT may give rise to a number of EDITORIAL OBJECT VERSIONS.
  • the EDITORIAL OBJECT VERSION PROGRAMME is linked to the entity SOUND, FORMAT, TYPE, 27, the relationship being "may describe”.
  • the EDITORIAL OBJECT VERSION entity 10 is linked to the EDITORIAL OBJECT VERSION INST entity 30 by the relationship "may be instantiated as".
  • a wide variety of terms may be used to describe relationships between entities and the terms vary from the very specific, such as "is made up of” to the more vague, such as "has associated”.
  • the EDITORIAL OBJECT CONCEPT entity 20 has the relationship "may be specified in” with the OFFER LINK EOC entity which in turn has the relationship "may specify” with the OFFER entity 28 which has the relationship "may specify as examples” with the OFFER_LINK_EOV_EXAMPLE entity 67. That latter entity has the relationship "may be specified as examples in” with the EDITORIAL OBJECT VERSION entity 10.
  • the entity relationship diagrams of figures la)-lc) provide a hierarchical and non-hierarchical breakdown of programme content and metadata through media object instances which point to individual media objects.
  • the structure also allows optimal storage of information by linking information to objects at the logical level.
  • rights, incorporating contributor rights and/or exploitation rights are linked to programmes and at lower levels, through a contract for a particular role, such as rights owner.
  • not all programme metadata need be stored at a very low level, such as on a video frame, as has previously been proposed.
  • the model sets out the entities required to hold metadata for say, a programme at the optimal level, not, for example, duplicating it across low level details such as video frames.
  • Figures la) to lc) set out the range of metadata hierarchical relationships necessary to support appropriate media metadata structures.
  • the EDITORIAL_OBJECT_VERSION entity 10 may be instantiated in terms of a number of media object instances which represent the physical make up of the item. These are represented by the MEDIA_OBJECT_INSTANCE entity 32.
  • the media object instance is connected to only one of a number of different elements such as shots, audio clip, text, graphics and stills which are determined through the relationship to the entity MEDIA_OBJECT_CONTENT entity 31 to MEDIA OBJECT entity 14 and its associated sub-types. Thus a given media object instance only comprises shots, or stills, etc. Each of these are represented by their own entity. Stored at each level is metadata relating to the media item at that level .
  • business information can be linked to the appropriate level entity. This again reduces the amount of storage required and avoids the need for business information to be embedded in the individual video or audio frames.
  • STORY entity 25 which is linked to the MEDIA OBJECT and EDITORIAL OBJECT entities 14, 10 via link entities. If the previously assumed constraints were followed, this data would have been embedded at the frame level.
  • the RIGHT entity 61 has RIG number and COM number as key data, and jurisdiction, start date, end date, and condition as non-key data.
  • the condition data item is included to provide a field for storage of additional information required to define the right over and above the jurisdiction, and other provided for.
  • the RIGHT entity 61 is linked to the TERRITORY entity 63 through the RIGHT LINK TERRITORY entity 72 along the relationship "is valid in”. This allows a series of predefined territories for rights management to be specified.
  • the data dictionary is therefore a compendium of data items with their definitions (complemented with local synonyms) and provides a basis to all the items a broadcaster needs to know about a media item throughout its life cycle with flexibility to cope with specialised terminology and future developments.
  • the structure of the data model described has hierarchical and non-hierarchical areas representing different levels of granularity through brand, programme group, programme, item and media objects.
  • the entities are linked by relationships that support the expected connections across sets of metadata necessary to support business functionality.
  • Each of the metadata items in figures la) to c) would appear in the data dictionary. Relationships linking data elements to the programme entity provide its CV or Resume.
  • the MEDIA OBJECT entity 14 is shown as having five different sub-types: SHOT entity 15, AUDIO CLIP entity 16, TEXT entity 17, GRAPHIC entity 17 and STILL entity 19.
  • SHOT entity 15 AUDIO CLIP entity 16
  • TEXT entity 17 TEXT entity 17
  • GRAPHIC entity 17 GRAPHIC entity 17
  • STILL entity 19 Each of these sub-type entities contain metadata relating to the subtype.
  • the AUDIO CLIP entity contains audio metadata, the GRAPHIC entity, graphic metadata etc.
  • Each of the entities may be realised as a storage entity having a series of storage elements .
  • Each of the entities may be realised as a storage entity having a series of storage elements.
  • An example of the metadata contained in the entity MEDIA OBJECT 14 is as follows:
  • the entity represents an editorial description of a section of continuous/discrete sound from a defined viewpoint.
  • the sound may be being planned to be captured, edited, or transmitted.
  • the name applied to a collection of assets which could include a series of programmes.
  • the assets could cover programmes, books, videos, characters, magazines, toys etc.
  • a brand can be defined at a high level as BBC Sport or as a sub-Brand as Grandstand.
  • GENRE A domain-specific conceptual grouping of programmes, e.g. comedy, drama etc. It is because genres are domain specific that a single programme concept may be described in terms of multiple genres.
  • PROGRAMME GROUP A grouping of programmes with shared identification and branding linked by common character, subject matter, style or story. could be a series, serial or themed grouping.
  • a fiction series (drama or comedy) will have common characters, themes and/or style between episodes, but individual stories.
  • a fictional series will have a common story running across all episodes, with part being told in each.
  • a factual series may have either individual or shared stories/arguments, such as a history series.
  • a series may be occasional or regular in its transmission pattern - a serial will always have a prescribed transmission pattern and order.
  • a themed group may draw together programme versions based around a campaign or anniversary.
  • Programme Type is the category of programme type taken from a standardised list for transmission to the consumer. Commonly used in RDS delivery, DAB delivery and MPEG-2 delivery. Programme types include News, Sport, Traffic Information, Pop, Classical, with further sub- categorisation. Also used for EPGs .
  • the entity provides the editorial description for a continuous section of moving images from a defined viewpoint, such as video or film.
  • the section may be planned, captured, created from other recorded images or transmitted.
  • the description may apply to a still image that is planned to be taken, captured, edited or transmitted.
  • This reference applies to the subject of the material (compared with, for example, the contributors or the action location) and is a "tag" by which a user may retrieve the material .
  • the entity provides an editorial description for a media object that contains alphanumeric content to be included in a presentation e.g. captions, website text, teletext.
  • a media object such as footage of wildlife.
  • information about this footage is stored such as the identifier, its name, creation date etc as shown in figure 1 (a) .
  • a simple object represents a continuous stream of action. Media objects may only exist conceptually, that is they may not have been captured.
  • the data held at the level of the MEDIA OBJECT entity is complemented by technical information about the digital representation of the action stored in the MEDIA OBJECT CONTENT and MEDIA OBJECT INSTANCE entities 31 and 32.
  • the combination of simple objects to become footage, or to become a compound media object is represented in the MOI SEGMENT USAGE entity 33, the complementary information about any processing applied being stored in the TRANSFORM and TRANSITION entity 38.
  • the audio clip used, for example in the signature tune for one of the programmes may have rights attached to it and may have been used for other programmes.
  • the data model gives a representation of the data required by media business processes.
  • the actual processes can be represented by ' process flow diagrams.
  • Process flow diagrams consist of process, data flows, data stores, and external entities and illustrate the process involved in the broadcast media production chain. In a process box, the action is linked with nouns to describe the process. The diagram does not show how many times the process is executed or any conditions that may prevent the process from being executed. However, the process must be triggered by a data flow.
  • a data flow carries data in a packet into and out of processes and must change the data in some way.
  • the data on the data flow is broken down into data structures and data items/elements. Data may flow to and from an external entity which is a source or recipient of data.
  • An external entity is a person, role organisation or body that is outside the area represented by the process flow diagram and not necessarily to the organisation as a whole.
  • a data store is a repository (possible temporary) of data. Everything in it should be retrieved and used by a process somewhere and data stored must be placed there by a process.
  • Figure 2 shows the content creation and distribution process flow diagram for a broadcasting organisation.
  • Figures 3 - 28 show process flow diagrams for each of the processes illustrated in figure 2.
  • CREATE TV/RADIO PROGRAMME 72 Central to this is CREATE TV/RADIO PROGRAMME 72 which has data flows from sources 74, 76 which represent an external archive and a contributor.
  • the data flow from the archive 74 represents information and footage.
  • Data flows both from and to the contributor, the flow into the contributor being contractual and the flow from the contributor being availability.
  • the process 72 has a data flow between the process PROVIDE RESOURCES to PROGRAMMES 78, the flow from the CREATE TV/RADIO PROGRAMME process 72 representing bookings and demand forecast and the flow to the process representing resources, equipment, studios and quotes.
  • the process CREATE TV/RADIO PROGRAMME 72 has data flow to the process COMMISSION OUTPUT 82 with data representing offers flowing from the CREATE TV/RADIO PROGRAMME 72 process to the commission output process and data representing commissioning brief, and offer response flowing to the CREATE TV/RADIO PROGRAMME process.
  • Data included in production contract will flow both ways.
  • the CREATE TV/RADIO PROGRAMME process 72 will exchange data with the PLAY-OUT and TRANSMIT process 84 with the flow of data to PLAY-OUT and TRANSMIT process 84 representing programme feed and the data flow to the CREATE TV/RADIO PROGRAMME 72 representing a confirmed transmission.
  • the data will flow from the CREATE TV/RADIO PROGRAMME process 72 to the process SCHEDULE and PROMOTE 86. That flow represents promotional material and presentation details.
  • the CREATE TV/RADIO PROGRAMME process 72 may be broken down into 6 sub-processes as follows: RESEARCH AND SUBMIT OFFER 196; PLAN PROGRAMME 198; PREPARE AND RESEARCH 200; CAPTURE MATERIAL 202; MANIPULATE MATERIAL 204; and DELIVER PROGRAMME .
  • FIG. 2 shows a STORE 100 which represents the programming schedule.
  • Data flows from the SCHEDULE STORE 100 to the SCHEDULE & PROMOTE PROCESS 86 representing MASTER SCHEDULE data.
  • MASTER SCHEDULE data also flows from the commission output process to the SCHEDULE STORE 100.
  • Data also flows to the SCHEDULE STORE 100 from the SCHEDULE & PROMOTE process 86 representing trail details and confirmed timings and from the play-out and transmit process 84 representing actual start and finish times.
  • the PROVIDE RESOURCES TO PROGRAMMES process is shown in more detail in figure 28.
  • the process is broken down into six sub-processes: PROVIDE QUOTES & TAKE BOOKINGS 212; SET UP, MONITOR AND MANAGE JOB 214; PROVIDE RESOURCES 216; MANAGE PROJECT FINANCES 218; ESTABLISH COST OF PRODUCTS AND SERVICES 220; and FORECAST DEMANDS OF PRODUCTS AND SERVICES 222.
  • the GATHER NEWS process receives data flow from 6 external data sources: NEWS EDITORS 96, REGIONAL NEWS 98, NEWSROOM 102, EXTERNAL NEWS PROVIDERS 104, THE PUBLIC/AGENCIES AND WIRES 106 AND EXTERNAL ARCHIVES 108.
  • NEWS EDITORS 96 represents guidance, from REGIONAL NEWS 98 and the NEWSROOM represents prospects and also from the NEWSROOM availability, from the EXTERNAL NEWS PROVIDERS 104 represents knowledge of competition, from PUBLIC/AGENCIES AND WIRE 106 represents prospects and diary events and from EXTERNAL ARCHIVE represents information and footage. Data flow is also received from the MANAGE MATERIAL STORE & ARCHIVE process 90 representing information and footage.
  • Data flows from the GATHER NEWS process 94 is to the NEWSROOM 102 representing an assignment, to the EXTERNAL ARCHIVE 108 representing an enquiry, to the MANAGE MATERIAL STORE & ARCHIVE 90 also representing an enquiry and to the CREATE NEWS PROGRAMMES process 88 representing a potential news item and an event, outline or story.
  • the GATHER NEWS process 94 is illustrated in more detail in figures 4-6 and comprises three sub-processes MAINTAIN DAILY PROSPECTS 110, ALLOCATE RESOURCES 112 and RESEARCH EVENT 114.
  • the RESEARCH EVENT and ALLOCATE RESOURCES processes are illustrated in detail in figures 5 & 6.
  • EXTERNAL ARCHIVE source 108 by way of enquiries to the archive and information and footage from the archive.
  • Data flow to the MANAGE MATERIAL STORE & ARCHIVE process 90 represents enquiries, rushes and documents, together with pre-recorded programme tape whereas data flow from the
  • MANAGE MATERIAL STORE & ARCHIVE process 90 represents information and footage. Data flow to the SCHEDULE AND
  • PROMOTE process 86 represents promotional material and presentation details and data flow to the PLAY-OUT and TRANSMIT process 84 represents programme feed.
  • the CREATE NEWS PROGRAMME process is illustrated in more detail in figures 7-9 and comprises 4 sub-processes: SELECT PROGRAMME CONTENT 116, RESEARCH & CAPTURE 118, COMPILE PROGRAMME 120 and EDIT 122.
  • the SELECT PROGRAMME content process is shown in more detail in figure 8 and the RESEARCH AND CAPTURE process is shown in more detail in figure 10.
  • the SELECT PROGRAMME CONTENT process is broken down into four sub-processes: FINALISE NEWS ITEMS 228, ALLOCATE ROUGH TIMINGS 230, ALLOCATE PRODUCTION TEAM 232 and CREATE DRAFT TREATMENT 234. These processes draw a data from a PROSPECTS store 234.
  • the ALLOCATE PRODUCTION TEAM process also draws on available production staff data from a PRODUCTION ROTA store 236.
  • the COMMISSION OUTPUT process 82 receives data from a STORE 124 which represents the controllers stock of untransmitted material. Data is also received from an external entity, representing offers from EXTERNAL PRODUCTION BODIES 126. Data flows from the COMMISSION OUTPUT process to the EXTERNAL PRODUCTION BODY 126 in the form of commissioning briefs, offer responses and production contracts.
  • a second external recipient of data is the CORPORATE CENTRE 128 which receives data relevant to actual versus planned quotas.
  • the COMMISSION OUTPUT process 82 also receives data flow from the SCHEDULE STORE 100 and from a process PLAN OUTPUT SERVICE 130.
  • the data from the STORE represents available slots and the data from the plan output service represents strategic output plan.
  • Data in the form of requirements is sent to the SCHEDULE STORE 100.
  • the COMMISSION OUTPUT process is shown in more detail in figures 10-12 and comprises four processes: DEVISE OUTLINE SCHEDULE 134, EVALUATE AND SELECT OFFICERS 136, NEGOTIATE AND AWARD COMMISSION 138 and CHECK WITH QUOTA TARGETS 140.
  • the ACQUIRE/PROGRAMME EVENT RIGHT 92 process involves data flow between an external source representing the EVENT RIGHT HOLDER 142 with the data representing negotiation and contract and also flow of data in from EXTERNAL EVENT ORGANISERS 144 representing possible events to cover. Data flows to an EXTERNAL SOURCE 146 representing other distributors. Data representing negotiation and contract flows both ways to and from that source and data to that source represents "ancillary rights which could be sold" and from the source represents "potential acquisitions and programme and paperwork information".
  • the ACQUIRE PROGRAMME/EVENT RIGHT process 92 is illustrated in more detail in figure 13.
  • the process 92 is broken down into five sub-processes: IDENTIFY ACQUISITIONS & EVENTS 238, NEGOTIATE & AGREE CONTRACT 240, SELL ANCILLARY RIGHTS 242, MAINTAIN ACQUIRED STOCK 244 AND ALLOCATE PROGRAMME TO SLOT 246.
  • the sub-processes make use of data in the CONTROLLERS STOCK STORE 124, the SCHEDULE STORE 100 and a RIGHTS STORE 248.
  • the SCHEDULE AND PROMOTE process 86 receives a flow of data from the UNDERSTAND AUDIENCE & COMPETITORS process representing upheld complaints regarding the content of a broadcast and sends data to the BROADCASTING DATA SERVICES SOURCE 77 representing weekly schedules and data to a recipient representing press and public relations 148 regarding off- air publicity and promotions.
  • Data also flows to the PLAY-OUT & TRANSMIT process representing on-air publicity and promotions and schedule and continuity script.
  • Data representing a tape list flows to the MANAGE MATERIAL STORE & ARCHIVE process 90.
  • the SCHEDULE AND PROMOTE process is illustrated in more detail in figures 14-16.
  • the SCHEDULE & PROMOTE process is broken down into three sub-processes: CREATE, TRANSMISSION SCHEDULE 250, PLAN & INITIATE ON-AIR PUBLICITY 252 AND PLAN & INITIATE OFF-AIR PUBLICITY 254. Each of these processes relies on data flow to and from the SCHEDULE STORE 100.
  • the CREATE TRANSMISSION SCHEDULE process is shown in more detail in figure 16 and the PLAN & INITIATE ON-AIR PUBLICITY process is shown in more detail in figure 16.
  • the PLAY-OUT AND TRANSMIT process 84 in addition to the data flows described already sends information requirements to the UNDERSTAND AUDIENCE & COMPETITORS process 132, transmitted programme data, transmission log and original documents to the MANAGE MATERIAL STORE & ARCHIVE process 90.
  • Pre-recorded tape information is received from the MANAGE MATERIAL STORE & ARCHIVE process and completed contract information flows to a MANAGE RIGHTS AGENCY process 150.
  • Distribution data flows to, and transmission service data flows from an External source/recipient labelled DISTRIBUTION SERVICE PROVIDER 152.
  • the PLAY-OUT AND TRANSMIT process is illustrated in more detail in figures 17 & 18.
  • the PLAY-OUT & TRANSMIT process comprises 4 sub-processes: PERFORM PLAY-OUT 256, CAPTURE ACTUAL TRANSMISSION DETAILS 258, INITIATE POST-TRANSMISSION RIGHTS PAYMENT 260 and PERFORM PROMOS ANALYSIS 262. These processes draw on data from the SCHEDULE 100 and from a store of research statistics 264.
  • the PERFORM PLAY-OUT sub- process is shown in more detail in figure 18.
  • the MANAGE MATERIAL STORE & ARCHIVE process 90 receives a data flow from the UNDERSTAND AUDIENCE & COMPETITORS process 132 in the form of request for tapes and sends data to that process in the form of pre-recorded programme tapes.
  • Data flow from two external sources, EXTERNAL ARCHIVE 154 and ARCHIVE STEERING GROUP 156 represent material and rights flowing from outside the Organisation and strategic direction respectively.
  • the MANAGE MATERIAL STORE & ARCHIVE process is illustrated in more detail in figures 19-21.
  • the MANAGE MATERIAL STORE & ARCHIVE process may be broken down into three sub- processes as shown in figure 19. These processes are CREATE ARCHIVING POLICY 266, MANAGE INCOMING MATERIAL 268 and RETRIEVE MATERIAL 270. The latter two sub-processes draw on data in a MATERIAL STORE & ARCHIVE 272.
  • the MANAGE INCOMING MATERIAL sub-process is shown in more detail in figure 20 and the RETRIEVE MATERIAL sub-process is shown in more detail in figure 21.
  • the MANAGE RIGHTS AGENCY process 150 will receive data flow representing Union & Framework Agreements from a source representing Union & Industry Bodies 156 and data will flow to a recipient representing Worldwide product Licences 158.
  • the MANAGE RIGHTS AGENCY process is illustrated in more detail in figure 22.
  • the PLAN OUTPUT service process 130 receives data flows from external sources representing the chief executive broadcast 160, the Government 162 and any relevant legislation represented here by the Broadcasting Act 1990, 164. Data also flows from the UNDERSTAND AUDIENCE & COMPETITORS process in the form of filtered statistics. Data is output to the SCHEDULE 100 in the form of news slots, to the COMMISSION OUTPUT process 82 in the form of strategic output plans and to the CREATE NEWS PROGRAMMES process 88 in the form of guaranteed news output.
  • the plan output service is illustrated in more detail in figure 23.
  • the UNDERSTAND AUDIENCE & COMPETITORS process gathers information from a variety of external sources such as the Government 162 in the form of broadcasting requirements, for example under a broadcasting charter, from broadcasting industry monitoring services in the form of viewer/listener statistics, quote requests and contracts and other research results, from viewers and listeners in the form of complaints and feedback. Information flows to external sources in the form of published statistics to an annual report, reports and statistics to a given channel controller, responses to viewers and listeners and requests to statistical gathering agencies.
  • the UNDERSTAND AUDIENCE & COMPETITORS process is illustrated in more detail in figures 24-27.
  • the UNDERSTAND AUDIENCE & COMPETITORS process can be broken down into two sub-processes: MANAGE RESEARCH STATISTICS 274 and HANDLE AUDIENCE FEEDBACK 276. These sub- processes are shown in more detail in figures 25 & 26 respectively.
  • Figure 26 shows that the HANDLE AUDIENCE FEEDBACK sub-process can be further sub-divided into two more sub-processes: DEAL WITH AUDIENCE FEEDBACK 278 and INVESTIGATE COMPLAINTS 280.
  • the DEAL WITH AUDIENCE FEEDBACK sub-process is further illustrated in figure 27.
  • a combination of the data model of figures la) to c) and the PROCESS flow diagram of figure 2 can be used to develop a standard media exchange framework. This sets out the metadata items which must be associated with media material, concepts or services at each level of the entity model and can be used to define the exchange at each process interface .
  • An example of a possible exchange framework interface is the data which is required to be created by or loaded into a capture device such as a camera. This requires standardisation amongst camera manufacturers. Some of that information might then be imported into the device from a data store before capture, to be embedded with a media material as it is created, then it and new data subsequently exported into an information system for media management purposes, or for access by an editing system for onward processing. Rather than capture the data at the end of a process, data is captured as it happens and is perpetuated.
  • the media exchange architecture described enables the linking of media materials together with their metadata in a way which enables extremely efficient development, re-use and re-purposing of media in an integrated but distributed device and database.
  • the data structure is typically implemented in software, for example the data dictionary may be held in a software repository.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

L'invention concerne une structure de métadonnées associées aux médias électroniques, laquelle structure est constituée d'un certain nombre d'entités de stockage de métadonnées associées aux matériels, aux concepts et aux services des médias, et définies par ladite structure. Ces entités, qui contiennent un certain nombre d'éléments de stockage mémorisant des métadonnées associées à un niveau de stockage donné, sont associées à des attributs ou à des caractéristiques de l'entité. Les niveaux de stockage sont organisés en un certain nombre de relations hiérarchiques ou non hiérarchiques mutuellement consistantes avec le niveau de stockage à chaque niveau situé au-dessus du niveau inférieur associé aux métadonnées du niveau immédiatement inférieur. Un certain nombre de niveaux d'entités commerciales comprennent chacune des éléments commerciaux associés aux métadonnées commerciales. Ces éléments commerciaux sont liés aux stocks de métadonnées de médias à un niveau de stockage approprié pour les métadonnées commerciales.
EP99946306A 1999-01-27 1999-09-10 Structure de m tadonn es associ es aux m dias lectroniques Withdrawn EP1147475A1 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US238761 1988-08-30
GBGB9901807.9A GB9901807D0 (en) 1999-01-27 1999-01-27 Broadcast media metadata structure
GB9901807 1999-01-27
US23876199A 1999-01-28 1999-01-28
PCT/GB1999/003010 WO2000045294A1 (fr) 1999-01-27 1999-09-10 Structure de métadonnées associées aux médias électroniques

Publications (1)

Publication Number Publication Date
EP1147475A1 true EP1147475A1 (fr) 2001-10-24

Family

ID=26315045

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99946306A Withdrawn EP1147475A1 (fr) 1999-01-27 1999-09-10 Structure de m tadonn es associ es aux m dias lectroniques

Country Status (5)

Country Link
EP (1) EP1147475A1 (fr)
AU (1) AU5872499A (fr)
CA (1) CA2359688A1 (fr)
HK (1) HK1042955A1 (fr)
WO (1) WO2000045294A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0118127D0 (en) * 2001-07-25 2001-09-19 Pressvault Ltd Data storage and retrieval systems
US7043490B2 (en) * 2002-03-05 2006-05-09 International Business Machines Corporation Method, system, and program product to support multiple content-management data models
GB2386978B (en) 2002-03-25 2007-03-28 Sony Uk Ltd Data communications network
EP1387295A1 (fr) * 2002-08-03 2004-02-04 Deutsche Thomson-Brandt Gmbh Structure de métadonnées constituée d'un format multi-couche
CN101073095A (zh) * 2004-08-30 2007-11-14 海时6有限公司 补偿广播源的设备、系统及方法
GB0423323D0 (en) 2004-10-20 2004-11-24 Nds Ltd Apparatus and method for grouping program meta-data
WO2006105604A1 (fr) * 2005-04-06 2006-10-12 Ruzz Tv Pty Ltd Programmes d'un systeme de gestion de radiodiffusion
EP1758398A1 (fr) 2005-08-23 2007-02-28 Syneola SA Moyens d'interface pour metadata et utilisateur basés sur une semiotique à plusieurs niveaux et une logique floue pour un système interactif multimédia ayant une capacité d'adaptation par acquisition de connaissances
US10372883B2 (en) 2016-06-24 2019-08-06 Scripps Networks Interactive, Inc. Satellite and central asset registry systems and methods and rights management systems
US10452714B2 (en) 2016-06-24 2019-10-22 Scripps Networks Interactive, Inc. Central asset registry system and method
US11868445B2 (en) 2016-06-24 2024-01-09 Discovery Communications, Llc Systems and methods for federated searches of assets in disparate dam repositories

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0045294A1 *

Also Published As

Publication number Publication date
AU5872499A (en) 2000-08-18
WO2000045294A1 (fr) 2000-08-03
CA2359688A1 (fr) 2000-08-03
HK1042955A1 (zh) 2002-08-30

Similar Documents

Publication Publication Date Title
Kallinikos et al. Video as digital object: Production and distribution of video content in the internet media ecosystem
CN100377155C (zh) 使用元数据索引的元数据搜索方法及设备
US9275084B2 (en) Digital asset management data model
CN107547912B (zh) 一种全媒资的资源处理方法、系统和存储介质
CN101681371B (zh) 多媒体内容搜索和记录安排系统
EP2092713B1 (fr) Accéder à un contenu
CN101321025B (zh) 信息提供系统、装置、方法和信息接收装置
CA2667670C (fr) Service d'inventaire mediatique
WO2002087244A1 (fr) Procede, systeme et produit de programme informatique permettant de produire et de distribuer des flux aval de mulimedia ameliores
KR20070042151A (ko) Ｖｏｄ 컨텐츠 전달 시스템 및 방법, 소비자가 생성한분류된 광고를 ｔｖ 상에 전달하는 방법
CN101075233B (zh) 多媒体内容收集部件、系统及其方法
JP2002184157A (ja) オーディオビジュアル情報を管理するための使用履歴記述スキーム、システム、及び方法
CN101472105A (zh) 一种基于互动电视平台的实现节目导视服务的系统和方法
CN101523429A (zh) 可占取的台站目录
WO2000045294A1 (fr) Structure de métadonnées associées aux médias électroniques
CN101515267A (zh) 网络媒体智能编目系统
EP2375344A1 (fr) Système de fourniture de contenu numérique
CN101116336A (zh) 用于使用包括传记信息和终端信息的使用环境描述提供自适应广播服务的设备和方法
Debevere et al. Enabling semantic search in a news production environment
Viana et al. A semantic management model to enable the integrated management of media and devices
Allen Digital Asset Management
Delgado et al. A multimedia content interchange framework for TV producers
Mannens et al. Production and multi-channel distribution of news
JP2024123690A (ja) 放送関連データ活用システム及びその方法
Delgado et al. Metadata and Rights Interoperability for Content Interchange between TV Programs Producers.

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20010820

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20040727

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20041207

REG Reference to a national code

Ref country code: HK

Ref legal event code: WD

Ref document number: 1042955

Country of ref document: HK