WO2003075176A2 - Support for multiple content-management data models - Google Patents

Support for multiple content-management data models Download PDF

Info

Publication number
WO2003075176A2
WO2003075176A2 PCT/GB2003/000679 GB0300679W WO03075176A2 WO 2003075176 A2 WO2003075176 A2 WO 2003075176A2 GB 0300679 W GB0300679 W GB 0300679W WO 03075176 A2 WO03075176 A2 WO 03075176A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
relational database
item
multimedia
content
Prior art date
Application number
PCT/GB2003/000679
Other languages
French (fr)
Other versions
WO2003075176A3 (en
Inventor
Randal James Richardt
David Mun-Hien Choy
Tawei Hu
Lily Liang
Kenneth Carlin Nelson
Original Assignee
International Business Machines Corporation
Ibm United Kingdom Limited
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
Application filed by International Business Machines Corporation, Ibm United Kingdom Limited filed Critical International Business Machines Corporation
Priority to JP2003573563A priority Critical patent/JP4222947B2/en
Priority to AU2003215716A priority patent/AU2003215716A1/en
Priority to CA2477126A priority patent/CA2477126C/en
Priority to EP03743405A priority patent/EP1530762A2/en
Priority to KR1020047012103A priority patent/KR100745442B1/en
Priority to BRPI0308269-5A priority patent/BR0308269A/en
Publication of WO2003075176A2 publication Critical patent/WO2003075176A2/en
Publication of WO2003075176A3 publication Critical patent/WO2003075176A3/en

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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99943—Generating database or data structure, e.g. via user interface
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99944—Object-oriented database structure
    • Y10S707/99945—Object-oriented database structure processing

Definitions

  • the present invention relates to data structure models, including multimedia data structure models, and facilitates access, retrieval, and data conversion for content management applications.
  • the data structure model is used for organizing, inter-relating, and accessing data and files, including relational, network, hierarchical, and entity-relationship models, and graphics, text, and web page files, among others .
  • Multimedia data management and delivery is a complex, computer and memory intensive, task.
  • “multimedia” data refers to combinations of sound, graphics, animation, text, and video data, which may be linked in an associative system of storage and retrieval, which may be interactive, and which may be linked to other media.
  • a multimedia content management system needs to manage a large volume of disparate data, including unstructured data as well as structured data.
  • the structured data often include "metadata” that describe the unstructured data so that the latter can be ' organized, grouped and correlated in various ways, searched, retrieved, and administered.
  • RDBMS relational database management system
  • the type of the unstructured data that is, multimedia content, differs from application to application.
  • This description was normally expressed in the abstraction of a high-level data model supported by the content management system, usually through an application programming interface (API) or a graphical user interface (GUI) . While this high-level data model provided the flexibility to support more than one application, it also limited the coverage to only those applications that could be expressed in that particular high level model .
  • API application programming interface
  • GUI graphical user interface
  • the data model is an essential aspect of a content management system because it determines the potential capability of the system as well as its limitations. However, while a data model can sometimes be expanded somewhat, such an expansion is usually very limited and will not be able to capture a different paradigm, especially one with an incompatible or even conflicting concept.
  • the present invention provides a method of representing a multimedia content management object in a database.
  • a database is employed, comprising one or more high level content models and a low level physical model of the multimedia content data.
  • the low level physical model provides a mapping to a data engine.
  • the method includes the steps of entering multimedia data metadata and schema in the low level physical representation, and mapping the metadata and schema to the data engine.
  • the data engine is preferably a relational database management system, an object oriented database management system or an XML data repository.
  • the method preferably provides for the mapping to the data engine further comprising a method of representing the multimedia content management object as an item in a relational database adapted for representing multimedia content management data in one or more relational database tables .
  • Each of the relational database tables have at least one row with a plurality of columns.
  • the method comprises the steps of associating a root component of the object as an item to a row in a first relational database table; associating attributes of the root component to corresponding columns of the first relational database table; associating additional components of the object, if any, to rows in the additional relational database tables; and using the item as a building block to construct a plurality of high level content management data models .
  • the present invention further provides a computer program product comprising instructions which, when executed on a data processing system having a non-volatile memory storage device, causes the system to carry out the method described above.
  • the present invention further provides a system for managing and delivering multimedia data object items from a multimedia data object content repository through a multimedia data object content server to a client.
  • the multimedia data object comprises multimedia data object items, each comprising multimedia data object attributes and components.
  • the multimedia data object content server is controlled and configured to associate a root component of the object to a row in a first relational database table; associate attributes of the root component to corresponding columns of the first relational database table; and associate additional components of the object, if any, to corresponding rows in additional relational database tables.
  • the item is used as a building block to construct a plurality of high level data models.
  • FIGURE 1 illustrates a multimedia database system with multiple clients, a content management server, and multiple content servers.
  • FIGURE 2 illustrates the layered structure of the method, system, and program product of the invention, with a structure of the API's as high level data models, a generic, low level infrastructure as the physical data model, and the underlying Relational Database Management System.
  • FIGURE 3 illustrates a simplified overview of a Relational Database Management System of Figure 2 showing hierarchal RDBMS tables including an Item Table with a row for the root component and including component and attribute cells (columns) , component tables with sub-component and attribute cells (columns) , and grandchild tables for both sub-components and attributes, with suitable pointers.
  • FIGURE 4 depicts the relationships between the RDBMS tables of Figure 3, and illustrates a side-by-side mapping of an Item type, including the root table, child tables, and grand child tables, mapped to an Item, as an instance of the Item type, including the root components, child components, and grand child components. Each component is a row in the corresponding tables .
  • FIGURE 5 illustrates a row in a table of the RDBMS of Figure 2, relating source items, target items, and link items.
  • FIGURE 6 illustrates the application of resource references to target items .
  • FIGURE 7 illustrates a personal identification application having multimedia content stored at various servers for use at a terminal, for example in a security system.
  • a multimedia system is a complex client-server system with multiple clients, 11a, lib, a server, 13, and one or more content servers, 17a, 17b, each with one or more content stores, 19a, 19b, 19c, 19d.
  • the content stores may contain structured data, such as metadata for content, or unstructured data, such as textual data, image data, streaming audio, or streaming video. These data may be, and typically are, in a variety of disparate formats.
  • the content manager server is the repository of the content management RDBMS described herein. While the present invention is illustrated with respect to relational database management systems, alternative data repositories such as object oriented database management systems or XML data repositories may be used. To accommodate more than one content data model in a high-level data model, an extensible content management system which may be used to introduce appropriate metadata and schema and new APIs to support new high-level data models.
  • This extensibility is enabled by an architecture that is built around a low-level infrastructure supporting a physical data model and implemented through a hierarchical structure of RDBMS tables of content and content metadata, as items, components, sub-components, and attributes, with corresponding rows and columns (attributes) within the rows.
  • the architecture and an associated infrastructure and physical data model are used as building blocks to support high-level data models.
  • This physical data model is independent of application-specific semantics, maps directly and efficiently to a relational database designed to exploit RDBMS capabilities, and can be enriched over time to expand its functions and/or to exploit new RDBMS capabilities.
  • the design point for this physical data model is different from that of a high-level data model exposed to an application developer.
  • the high-level data model focuses heavily on its logical aspects (its usability and expressiveness with respect to a class of applications)
  • the physical data model focuses heavily on its physical aspects
  • This physical data model may or may not be exposed to user through a high-level data model.
  • the method, system, and program product of the present invention utilize a high level content model that is able to support a diverse and open set of content application requirements and a plurality of high level data models, and a low level physical model of the data content that is extensible to accommodate new technologies, new standards, and new requirements and provides efficient mapping to the data engine (a database management system, as a relational database management system or an object oriented database management system, by way of example and not limitation) .
  • each high level data model is in the form of an Application Program Interface (API) embodying a representation of data structure and constraints.
  • API Application Program Interface
  • the low level data model or infrastructure, 25, can support multiple high level models, 21, 22, 23.
  • the extensible and scalable content management system of the invention contains one or more APIs supporting disparate high level data models, 21, 22, 23, supported by a generic, low level infrastructure, 25, that is, a physical data model, which in turn is supported by the Relational Database Management System (RDBMS), 27.
  • RDBMS Relational Database Management System
  • FIGURES 3, 4, 5, and 6 illustrate the relationships between the physical model and its representation in a RDBMS environment.
  • a relational database data is represented as tables.
  • the building blocks of a relational database table are tables of rows and columns (attributes) .
  • a table consists of a row of column headings together with zero or more rows of data values.
  • the column heading specifies one or more columns, and (2) each data row contains exactly one value (or a null value) for each one of the columns specified in the column heading row.
  • FIGURE 3 shows an Item Database, 30, with a root component, 31, having Item Rows, 32a and 32b.
  • An item consists of a typed hierarchical structure of components, 35, and one or more levels of sub-components, 38a, 38b, with attributes 33a, 33b, 33c, 33d, 34a, 34b, 34c, and has a unique identifier "ItemID” .
  • Each component, 35 contains a reference, 36a, to the parent component.
  • the reference is through a foreign key.
  • the Sub-component tables, 38a and 38b may reference further sub-components or attributes.
  • the sub component table, 38b is illustrated as referencing pointers to content data repositories, 39a, and 39b.
  • FIGURE 4 represents a more general, higher level view of the model shown in FIGURE 3.
  • an "Item” that is, a multimedia content management object item
  • FIGURE 4 illustrates a mapping of hierarchal physical items and attributes thereof, 41b, on the right, to hierarchal RDBMS representation, that is, RDBMS Item Types, 41a, on the left.
  • An “ItemType,” is a user defined schema and a named hierarchical structure of RDBMS tables, each of which is called a "ComponentType, " 35, of the "ItemType”
  • Each "ComponentType” contains user-specified attribute (s) as well as certain system attributes.
  • a user- specified attribute can be of any data model supported by the RDBMS, or can be of a special data model supported by the content management system.
  • An “Item” logically consists of a row in the root table of the respective "ItemType,” and any number of rows in each child table of the "ItemType,” with a condition that the parent of a child row contained in an "Item” must also be contained in the "Item.”
  • An “Item” is a hierarchy of rows that are stored in a hierarchy of tables. Each of these rows is called a “Component” of the “Item” and has a “ComponentID” that uniquely identifies the "Component” within the respective "ComponentType. "
  • ComponentType to assure a minimum and/or a maximum number of rows of that type under each of their parent rows. The default minimum is zero and the default maximum is infinity.
  • An “ItemType” can also be ordered or unordered. For an “Item” of an ordered “ItemType,” the child rows under each parent row are ordered, and the ordering is maintained by the system.
  • An "ItemType” can be versioned. If so, multiple versions of an "Item” are maintained for every “Item” in the “ItemType.” They share the same "ItemID” but each has a different version number. The number of latest versions to be retained for an "Item” can be specified for each versioned "ItemType.” The default is infinity, i.e., no automatic purging of old versions will be performed by the system.
  • each "Component” in an "Item” contains at least the following system attributes: "ItemID”, “ComponentID”, and
  • ParentID and optionally may contain an "Item” VersionNumber, and ACL Code (Access Control List code) .
  • “ItemID” , “Item” VersionNumber, and ACL Code are only needed for the root “Component,” they may be included in every “Component” to facilitate access.
  • Other system attributes can also be included to facilitate access or maintenance, e.g., "ComponentType,” the number of immediate child Components underneath a "Component,” etc.
  • a separate RDBMS table is created for each "ComponentType” defined for an "ItemType,-” i.e., tables are not shared between two “ItemTypes” . This design simplifies the logic and also enhances database scalability.
  • a table can be shared among several "ItemTypes" to store Components (rows) of similarly defined ComponentTypes for these several "ItemTypes".
  • including "ItemType” as a system attribute in this shared table can facilitate access. Sharing a table in this manner allows a faster search when the search scope covers multiple "ItemTypes" that contain common attribute (s) being searched on.
  • Child Components and Attributes can relate to or be associated with each other, for example through a system table, using Links.
  • a Link is an "external" relationship that binds a source “Item,” 51, to a target “Item,” 53, along with a LinkType, 55, and an optional Link “Item,” 57. This relationship is “external” since it is not imbedded in either the source or the target "Item” .
  • the LinkType is a categorization label so that an application can selectively traverse, or search on, Links of a particular type.
  • a Link "Item” is a third "Item” that can be used to describe this relationship if needed. Links can be used to support one-to-many and many-to-many relationships, including aggregation and containment relationships.
  • each relationship is defined by a high-level data model.
  • Foldering in which case an "Item” representing a folder is Linked to the Items ⁇ representing documents or other folders) that are "contained” in this folder.
  • Source Item 51 acts as a container for Target Item, 53.
  • the binding of a Link to the source or the target "Item” can be either version-specific or version-independent .
  • the former binds a specific version of an Item, whereas the latter binds to any/all versions of an "Item” .
  • Links are maintained as rows in one or more dedicated RDBMS tables containing at least the following attributes: source “ItemID” , source “Item” VersionNumber, target “ItemID” , target “Item” VersionNumber, LinkType, Link “ItemID”, and Link “Item” VersionNumber.
  • items can also relate to each other using "Item Reference” attributes, which are maintained like other attributes contained in an "Item” .
  • An “Item Reference” attribute is a user-defined attribute created as a part of a "ComponentType,” 36, within an "ItemType,” 32. This attribute has a special data model maintained by the content management system. It contains a reference, 58, that points to a target "Item,” 32'. Similar to a Link, (FIGURE 5) the binding of the reference, 58, to the target "Item,” 32', can be either version-specific or version independent.
  • a Scope of Reference and a Delete Semantics are defined for the referenced Items.
  • the scope specifies which "ItemType” (s) the referenced Items can belong to, whereas the delete semantics are similar to the delete rules maintained by a RDBMS to assure referential integrity when a referenced "Item” is to be deleted.
  • An "Item Reference” attribute, 58 can also be unscoped, in which case a referenced “Item” can belong to any "ItemType.”
  • a homogeneously scoped "Item Reference” attribute i.e., when the scope is a single "ItemType" is supported by a RDBMS Foreign Key.
  • Heterogeneously scoped i.e., when the scope includes multiple "Item” Types
  • unscoped "Item Reference” attributes are maintained by the content management system using RDBMS triggers .
  • a Resource Reference attribute 59, also illustrated in FIGURE 6.
  • a Resource Reference, 59 contains a reference to a Resource, 61, managed by a Resource Manager of the content management system.
  • a Resource Manager is a special-purpose server that manages resources of a particular type. Examples are an Object Server, which manages a large volume of binary objects, and a Stream Server, which manages and delivers streaming objects (e.g., audio and video content) .
  • the extensible content management system is able to accommodate new Resource Managers, each of which is specially designed to manage a specific type of resources, with its specific representation and methods that are not necessarily modeled by the physical data model described here .
  • the unstructured data managed by the content management system are largely managed internally by one or more of these Resource Managers .
  • the integrity of a Resource Reference is maintained by the content management system.
  • the physical data model described herein is able to support a wide range of high-level data models to cover a diverse spectrum of application domains, as well as to support many industry standards (e.g., Dublin Core, XML) . Equally important, this physical data model also provides enough flexibility to allow database optimization so as to support high-level data models efficiently.
  • a high-level data model uses Items of one "ItemType" to represent standalone, sharable images, each of which has its own attributes, versions, and ACL. The actual images are stored as Resources. Items of another "ItemType" are then used to represent documents, and Links are used to bind each document to the images it contains.
  • ItemView(s) can be defined on an “ItemType.”
  • An “ItemView” is a named template to restrict access to an "ItemType” to certain "Component” tables and attributes. It is essentially a set of RDBMS views for the corresponding "Component” tables in the "ItemType.”
  • One application of the present invention is a multimedia distributed database management system with distributed card reader access, for example, as would be used in a magnetic card security system, a credit card or debit card or automatic teller machine card system, or an airline frequent traveler system.
  • a multimedia distributed database management system with distributed card reader access for example, as would be used in a magnetic card security system, a credit card or debit card or automatic teller machine card system, or an airline frequent traveler system.
  • FIGURE 7 One version of this system is shown in FIGURE 7.
  • the system, 70 is actuated by identification indicia, e.g., encrypted data, on a magnetic or optical card, 70b, read by a card reader 70a.
  • Exemplary biometric data includes fingerprints at finger print reader 70c, voice prints and samples, facial images, and eye images, at digital camera, 70d, among others.
  • the biographical, audio, and image data are typically accessed through and processed by separate servers 72a, 73a, 74a, and 75a, and stored in separate databases, 72b, 73b, 74b, and 75b, for example, fingerprint data, voice data, and facial and eye image data are stored as multimedia data objects on separate fingerprint data, voice data, and facial and eye image databases, with such attributes as data models (images, mathematical representations of image data, audio data, and mathematical representations of audio data) , as well as repository addresses (e.g., URL's or IP addresses), where the data is the item and the addresses and definitions of data models are the attributes, and the image presented to the screener, security guard, cashier, boarding agent, or enforcement professional is the resource.
  • repository addresses e.g., URL's or IP addresses
  • the method and system are physically implemented in a program product.
  • the program product may reside on one computer or on several computers or on a distribution server or a disk or disks or tapes.
  • the program itself may be encrypted and/or compressed, as would be the case of distribution media or a distribution server, for example, before installation or it may be installed on the one or more computers.
  • a further application of the invention is a method and program product in the nature of a wizard (that is, a structured series of dialogs that ask questions and use the answers or choices to produce a result) for populating the multimedia content management system with content schema and metadata, including high level content models and low level physical models. This is accomplished by presenting a query to a user as to a content item, and, based upon the end user's response, presenting one or more subsequent queries as to the content item, and based upon the responses, determining the sub-components and attributes of the item.
  • a wizard that is, a structured series of dialogs that ask questions and use the answers or choices to produce a result
  • This is accomplished by presenting a query to a user as to a content item, and, based upon the end user's response, presenting one or more subsequent queries as to the content item, and based upon the responses, determining the sub-components and attributes of the item.

Abstract

Methods, systems, and program products for managing multimedia content. These are built upon a combination of a high level content model for specific multimedia content types and a low level physical for mapping to a data engine. The method, system, and program product include representing multimedia content management objects and managing the objects in a relational database. The relational database is adapted for representing data in a plurality of relational database tables, where each of the relational database tables has at least one row with a plurality of columns. Content is managed by associating the object as an item to a row in a first relational database table; and associating additional components, if any, of the object to additional relational database tables.

Description

SUPPORT FOR MULTIP3.E CONTENT-MANAGEMENT DATA MODELS
Field of the Invention
The present invention relates to data structure models, including multimedia data structure models, and facilitates access, retrieval, and data conversion for content management applications. The data structure model is used for organizing, inter-relating, and accessing data and files, including relational, network, hierarchical, and entity-relationship models, and graphics, text, and web page files, among others .
Background of the Invention
Multimedia data management and delivery is a complex, computer and memory intensive, task. As used herein, "multimedia" data refers to combinations of sound, graphics, animation, text, and video data, which may be linked in an associative system of storage and retrieval, which may be interactive, and which may be linked to other media.
A multimedia content management system needs to manage a large volume of disparate data, including unstructured data as well as structured data. The structured data often include "metadata" that describe the unstructured data so that the latter can be' organized, grouped and correlated in various ways, searched, retrieved, and administered. Within a content management system, a relational database management system (RDBMS) is often used to manage these structured data so that off-the-shelf RDBMS data management technologies can be employed. However, the type of the unstructured data, that is, multimedia content, differs from application to application.
Because the type of data (including its schema, metadata, applicable extenders, and the like) differs between applications and content data models (as streaming, graphical, visual, video, audio, text, numeric) , a different database design is needed to support the metadata and schema database of each application and data model. Heretofore, it was not possible to support different content management applications using different content data models with a single, general-purpose content management system. Such a system could not have a pre-designed, i.e., "one size fits all," database management system. Rather, the content management system must have been provided with the capability of allowing an application developer to describe the required structured data so that a database with a suitable design could be created for that application. This description was normally expressed in the abstraction of a high-level data model supported by the content management system, usually through an application programming interface (API) or a graphical user interface (GUI) . While this high-level data model provided the flexibility to support more than one application, it also limited the coverage to only those applications that could be expressed in that particular high level model .
The data model is an essential aspect of a content management system because it determines the potential capability of the system as well as its limitations. However, while a data model can sometimes be expanded somewhat, such an expansion is usually very limited and will not be able to capture a different paradigm, especially one with an incompatible or even conflicting concept.
Thus, a clear need exists for an extensible and scalable data model that readily supports a wide range of disparate content data models, and which can be readily implemented in a system or program product.
A further need exists for a tool, tool kit, tool set, or wizard to create and populate a relational database of disparate content schema and metadata, for an extensible and scalable content management RDBMS.
Summary Of The Invention
Accordingly, the present invention provides a method of representing a multimedia content management object in a database. In accordance with the method of the present invention a database is employed, comprising one or more high level content models and a low level physical model of the multimedia content data. The low level physical model provides a mapping to a data engine. The method includes the steps of entering multimedia data metadata and schema in the low level physical representation, and mapping the metadata and schema to the data engine. The data engine is preferably a relational database management system, an object oriented database management system or an XML data repository.
The method preferably provides for the mapping to the data engine further comprising a method of representing the multimedia content management object as an item in a relational database adapted for representing multimedia content management data in one or more relational database tables . Each of the relational database tables have at least one row with a plurality of columns. The method comprises the steps of associating a root component of the object as an item to a row in a first relational database table; associating attributes of the root component to corresponding columns of the first relational database table; associating additional components of the object, if any, to rows in the additional relational database tables; and using the item as a building block to construct a plurality of high level content management data models .
Accordingly, the present invention further provides a computer program product comprising instructions which, when executed on a data processing system having a non-volatile memory storage device, causes the system to carry out the method described above.
Accordingly, the present invention further provides a system for managing and delivering multimedia data object items from a multimedia data object content repository through a multimedia data object content server to a client. The multimedia data object comprises multimedia data object items, each comprising multimedia data object attributes and components. The multimedia data object content server is controlled and configured to associate a root component of the object to a row in a first relational database table; associate attributes of the root component to corresponding columns of the first relational database table; and associate additional components of the object, if any, to corresponding rows in additional relational database tables. The item is used as a building block to construct a plurality of high level data models.
The Figures
A preferred embodiment of the invention will now be described in detail by way of example only with reference to the following drawings:
FIGURE 1 illustrates a multimedia database system with multiple clients, a content management server, and multiple content servers.
FIGURE 2 illustrates the layered structure of the method, system, and program product of the invention, with a structure of the API's as high level data models, a generic, low level infrastructure as the physical data model, and the underlying Relational Database Management System. FIGURE 3 illustrates a simplified overview of a Relational Database Management System of Figure 2 showing hierarchal RDBMS tables including an Item Table with a row for the root component and including component and attribute cells (columns) , component tables with sub-component and attribute cells (columns) , and grandchild tables for both sub-components and attributes, with suitable pointers.
FIGURE 4 depicts the relationships between the RDBMS tables of Figure 3, and illustrates a side-by-side mapping of an Item type, including the root table, child tables, and grand child tables, mapped to an Item, as an instance of the Item type, including the root components, child components, and grand child components. Each component is a row in the corresponding tables .
FIGURE 5 illustrates a row in a table of the RDBMS of Figure 2, relating source items, target items, and link items.
FIGURE 6 illustrates the application of resource references to target items .
FIGURE 7 illustrates a personal identification application having multimedia content stored at various servers for use at a terminal, for example in a security system.
Detailed Description of the Invention
As shown in FIGURE 1, a multimedia system is a complex client-server system with multiple clients, 11a, lib, a server, 13, and one or more content servers, 17a, 17b, each with one or more content stores, 19a, 19b, 19c, 19d. It should be noted that the content stores may contain structured data, such as metadata for content, or unstructured data, such as textual data, image data, streaming audio, or streaming video. These data may be, and typically are, in a variety of disparate formats.
The server, 13, which may include a web server, also includes the content manager server. The content manager server is the repository of the content management RDBMS described herein. While the present invention is illustrated with respect to relational database management systems, alternative data repositories such as object oriented database management systems or XML data repositories may be used. To accommodate more than one content data model in a high-level data model, an extensible content management system which may be used to introduce appropriate metadata and schema and new APIs to support new high-level data models. This extensibility is enabled by an architecture that is built around a low-level infrastructure supporting a physical data model and implemented through a hierarchical structure of RDBMS tables of content and content metadata, as items, components, sub-components, and attributes, with corresponding rows and columns (attributes) within the rows. The architecture and an associated infrastructure and physical data model are used as building blocks to support high-level data models. This physical data model is independent of application-specific semantics, maps directly and efficiently to a relational database designed to exploit RDBMS capabilities, and can be enriched over time to expand its functions and/or to exploit new RDBMS capabilities.
The design point for this physical data model is different from that of a high-level data model exposed to an application developer. The high-level data model focuses heavily on its logical aspects (its usability and expressiveness with respect to a class of applications) , whereas the physical data model focuses heavily on its physical aspects
(storage access efficiency and ability to exploit RDBMS capabilities) to provide generic, basic functions broadly useful to many content management applications. This physical data model, or any part of it, may or may not be exposed to user through a high-level data model.
Conceptually, as shown in FIGURE 2, the method, system, and program product of the present invention utilize a high level content model that is able to support a diverse and open set of content application requirements and a plurality of high level data models, and a low level physical model of the data content that is extensible to accommodate new technologies, new standards, and new requirements and provides efficient mapping to the data engine (a database management system, as a relational database management system or an object oriented database management system, by way of example and not limitation) . To be noted is that each high level data model is in the form of an Application Program Interface (API) embodying a representation of data structure and constraints. Also to be noted is that the low level data model or infrastructure, 25, can support multiple high level models, 21, 22, 23. The extensible and scalable content management system of the invention contains one or more APIs supporting disparate high level data models, 21, 22, 23, supported by a generic, low level infrastructure, 25, that is, a physical data model, which in turn is supported by the Relational Database Management System (RDBMS), 27.
FIGURES 3, 4, 5, and 6 illustrate the relationships between the physical model and its representation in a RDBMS environment. In a relational database data is represented as tables. The building blocks of a relational database table are tables of rows and columns (attributes) . Specifically, a table consists of a row of column headings together with zero or more rows of data values. For a given table (1) the column heading specifies one or more columns, and (2) each data row contains exactly one value (or a null value) for each one of the columns specified in the column heading row.
The primary, standalone unit of content managed by the physical layer of the content management system of the invention is an "Item." FIGURE 3 shows an Item Database, 30, with a root component, 31, having Item Rows, 32a and 32b. An item consists of a typed hierarchical structure of components, 35, and one or more levels of sub-components, 38a, 38b, with attributes 33a, 33b, 33c, 33d, 34a, 34b, 34c, and has a unique identifier "ItemID" .
Each component, 35, contains a reference, 36a, to the parent component. The reference is through a foreign key.
The Sub-component tables, 38a and 38b, may reference further sub-components or attributes. The sub component table, 38b, is illustrated as referencing pointers to content data repositories, 39a, and 39b.
FIGURE 4 represents a more general, higher level view of the model shown in FIGURE 3. Through the high-level data model, or within an application, an "Item", that is, a multimedia content management object item, can be used to represent a real object, as a document, a folder, a media asset, or other real-world content entity. FIGURE 4 illustrates a mapping of hierarchal physical items and attributes thereof, 41b, on the right, to hierarchal RDBMS representation, that is, RDBMS Item Types, 41a, on the left. An "ItemType," is a user defined schema and a named hierarchical structure of RDBMS tables, each of which is called a "ComponentType, " 35, of the "ItemType" Each "ComponentType" contains user-specified attribute (s) as well as certain system attributes.
A user- specified attribute can be of any data model supported by the RDBMS, or can be of a special data model supported by the content management system. An "Item" logically consists of a row in the root table of the respective "ItemType," and any number of rows in each child table of the "ItemType," with a condition that the parent of a child row contained in an "Item" must also be contained in the "Item." An "Item" is a hierarchy of rows that are stored in a hierarchy of tables. Each of these rows is called a "Component" of the "Item" and has a "ComponentID" that uniquely identifies the "Component" within the respective "ComponentType. "
Cardinality constraints can be defined for each child
"ComponentType" to assure a minimum and/or a maximum number of rows of that type under each of their parent rows. The default minimum is zero and the default maximum is infinity. An "ItemType" can also be ordered or unordered. For an "Item" of an ordered "ItemType," the child rows under each parent row are ordered, and the ordering is maintained by the system.
An "ItemType" can be versioned. If so, multiple versions of an "Item" are maintained for every "Item" in the "ItemType." They share the same "ItemID" but each has a different version number. The number of latest versions to be retained for an "Item" can be specified for each versioned "ItemType." The default is infinity, i.e., no automatic purging of old versions will be performed by the system.
In one preferred embodiment, the parent-child relationship between two "ComponentTypes" within an "ItemType" is maintained by a RDBMS Foreign Key created in the child "ComponentType" (or sub-component) referencing the parent "ComponentType." Thus, the referential integrity of each child "Component" (or sub-component) to its parent "Component" is assured by the RDBMS. In this embodiment, each "Component" in an "Item" contains at least the following system attributes: "ItemID", "ComponentID", and
ParentID, and optionally may contain an "Item" VersionNumber, and ACL Code (Access Control List code) . Although "ItemID" , "Item" VersionNumber, and ACL Code are only needed for the root "Component," they may be included in every "Component" to facilitate access. Other system attributes can also be included to facilitate access or maintenance, e.g., "ComponentType," the number of immediate child Components underneath a "Component," etc. Also a separate RDBMS table is created for each "ComponentType" defined for an "ItemType,-" i.e., tables are not shared between two "ItemTypes" . This design simplifies the logic and also enhances database scalability. In a different embodiment, a table can be shared among several "ItemTypes" to store Components (rows) of similarly defined ComponentTypes for these several "ItemTypes". In this case, including "ItemType" as a system attribute in this shared table can facilitate access. Sharing a table in this manner allows a faster search when the search scope covers multiple "ItemTypes" that contain common attribute (s) being searched on.
As illustrated in FIGURE 5, Items (including Child Components, Grand
Child Components and Attributes) can relate to or be associated with each other, for example through a system table, using Links. A Link is an "external" relationship that binds a source "Item," 51, to a target "Item," 53, along with a LinkType, 55, and an optional Link "Item," 57. This relationship is "external" since it is not imbedded in either the source or the target "Item" . The LinkType is a categorization label so that an application can selectively traverse, or search on, Links of a particular type. A Link "Item" is a third "Item" that can be used to describe this relationship if needed. Links can be used to support one-to-many and many-to-many relationships, including aggregation and containment relationships.
The semantics of each relationship are defined by a high-level data model. One example is "foldering", in which case an "Item" representing a folder is Linked to the Items {representing documents or other folders) that are "contained" in this folder. For example, Source Item 51, acts as a container for Target Item, 53. The binding of a Link to the source or the target "Item" can be either version-specific or version-independent . The former binds a specific version of an Item, whereas the latter binds to any/all versions of an "Item" . In one embodiment, Links are maintained as rows in one or more dedicated RDBMS tables containing at least the following attributes: source "ItemID" , source "Item" VersionNumber, target "ItemID" , target "Item" VersionNumber, LinkType, Link "ItemID", and Link "Item" VersionNumber.
As illustrated in FIGURE 6, items can also relate to each other using "Item Reference" attributes, which are maintained like other attributes contained in an "Item" . An "Item Reference" attribute is a user-defined attribute created as a part of a "ComponentType," 36, within an "ItemType," 32. This attribute has a special data model maintained by the content management system. It contains a reference, 58, that points to a target "Item," 32'. Similar to a Link, (FIGURE 5) the binding of the reference, 58, to the target "Item," 32', can be either version-specific or version independent. When an "Item Reference," 58, attribute is specified, a Scope of Reference and a Delete Semantics are defined for the referenced Items. The scope specifies which "ItemType" (s) the referenced Items can belong to, whereas the delete semantics are similar to the delete rules maintained by a RDBMS to assure referential integrity when a referenced "Item" is to be deleted. An "Item Reference" attribute, 58, can also be unscoped, in which case a referenced "Item" can belong to any "ItemType." In a preferred embodiment, a homogeneously scoped "Item Reference" attribute (i.e., when the scope is a single "ItemType") is supported by a RDBMS Foreign Key. Heterogeneously scoped (i.e., when the scope includes multiple "Item" Types) and unscoped "Item Reference" attributes are maintained by the content management system using RDBMS triggers .
Another special data model supported by this physical data model is that of a Resource Reference attribute, 59, also illustrated in FIGURE 6. As illustrated in FIGURE 6, a Resource Reference, 59, contains a reference to a Resource, 61, managed by a Resource Manager of the content management system. A Resource Manager is a special-purpose server that manages resources of a particular type. Examples are an Object Server, which manages a large volume of binary objects, and a Stream Server, which manages and delivers streaming objects (e.g., audio and video content) . The extensible content management system is able to accommodate new Resource Managers, each of which is specially designed to manage a specific type of resources, with its specific representation and methods that are not necessarily modeled by the physical data model described here . The unstructured data managed by the content management system are largely managed internally by one or more of these Resource Managers . The integrity of a Resource Reference is maintained by the content management system.
The physical data model described herein is able to support a wide range of high-level data models to cover a diverse spectrum of application domains, as well as to support many industry standards (e.g., Dublin Core, XML) . Equally important, this physical data model also provides enough flexibility to allow database optimization so as to support high-level data models efficiently. In one example, a high-level data model uses Items of one "ItemType" to represent standalone, sharable images, each of which has its own attributes, versions, and ACL. The actual images are stored as Resources. Items of another "ItemType" are then used to represent documents, and Links are used to bind each document to the images it contains. In another example, to support a high-performance production application, a single "Item" is used to represent a document together with the images contained in the document. (The actual images are also stored as Resources.) In this case, performance is critical but there is no sharing requirement for the images. "ItemView(s) " can be defined on an "ItemType." An "ItemView" is a named template to restrict access to an "ItemType" to certain "Component" tables and attributes. It is essentially a set of RDBMS views for the corresponding "Component" tables in the "ItemType."
One application of the present invention is a multimedia distributed database management system with distributed card reader access, for example, as would be used in a magnetic card security system, a credit card or debit card or automatic teller machine card system, or an airline frequent traveler system. One version of this system is shown in FIGURE 7. The system, 70, is actuated by identification indicia, e.g., encrypted data, on a magnetic or optical card, 70b, read by a card reader 70a.
After reading the card, 70b, biometric readings are taken.
Exemplary biometric data includes fingerprints at finger print reader 70c, voice prints and samples, facial images, and eye images, at digital camera, 70d, among others. The biographical, audio, and image data are typically accessed through and processed by separate servers 72a, 73a, 74a, and 75a, and stored in separate databases, 72b, 73b, 74b, and 75b, for example, fingerprint data, voice data, and facial and eye image data are stored as multimedia data objects on separate fingerprint data, voice data, and facial and eye image databases, with such attributes as data models (images, mathematical representations of image data, audio data, and mathematical representations of audio data) , as well as repository addresses (e.g., URL's or IP addresses), where the data is the item and the addresses and definitions of data models are the attributes, and the image presented to the screener, security guard, cashier, boarding agent, or enforcement professional is the resource.
The method and system are physically implemented in a program product. The program product may reside on one computer or on several computers or on a distribution server or a disk or disks or tapes. The program itself may be encrypted and/or compressed, as would be the case of distribution media or a distribution server, for example, before installation or it may be installed on the one or more computers.
A further application of the invention is a method and program product in the nature of a wizard (that is, a structured series of dialogs that ask questions and use the answers or choices to produce a result) for populating the multimedia content management system with content schema and metadata, including high level content models and low level physical models. This is accomplished by presenting a query to a user as to a content item, and, based upon the end user's response, presenting one or more subsequent queries as to the content item, and based upon the responses, determining the sub-components and attributes of the item.

Claims

1. A method of representing a multimedia content management object in a database comprising one or more high level content models and a low level physical model of the multimedia content data, said low level physical model providing a mapping to a data engine, said method comprising:
a. entering multimedia content data metadata and schema in the low level physical representation, and b. mapping the metadata and schema to the data engine.
2. The method of claim 1 wherein the one or more high level content models comprises an application program interface embodying a representation of data structure and constraints.
3. The method of claim 1 wherein the data engine is chosen from the group consisting of relational database management systems, object oriented database management systems, object-relational database management systems and XML data repositories.
4. A method of claim 1 wherein the mapping to a data engine comprises a method of representing the multimedia content management object as an item in a relational database adapted for representing multimedia content management data in one or more relational database tables, each of said relational database tables having at least one row with a plurality of columns, said method comprising:
a. associating a root component of the object as an item to a row in a first relational database table; b. associating attributes of the root component to corresponding columns of the first relational database table; c. associating additional components of the object, if any, to rows in additional relational database tables; and d. wherein the item is used as a building block to construct a plurality of high level content management data models.
5. The method of claim 4 further comprising a method of managing a multimedia content management system comprising the multimedia content management object and the relational database.
6. The method of claim 4 or claim 5 wherein each of the additional components comprises a child component of a root component or a child component of another component.
7. The method of claim 4 or claim 5 wherein an attribute comprises a pointer to a data resource stored in a separate repository.
8. The method of claim 4 or claim 5 wherein a row in a table comprises a link between a source item and a target item.
9. A computer program product comprising instructions which, when executed on a data processing system having a non-volatile memory storage device, causes said system to carry out a method as claimed in any one of claim 1 to claim 8.
10. A system for managing and delivering multimedia data object items from a multimedia data object content repository through a multimedia data object content server to a client, wherein the multimedia data object comprises multimedia data object items, each of the multimedia data object items comprising multimedia data object attributes and components, and wherein the multimedia data object content server is controlled and configured to:
a. associate a root component of the object to a row in a first relational database table; . associate attributes of the root component to corresponding columns of the first relational database table; and c. associate additional components of the object, if any, to corresponding rows in additional relational database tables;
wherein the item is used as a building block to construct a plurality of high level data models.
PCT/GB2003/000679 2002-03-05 2003-02-14 Support for multiple content-management data models WO2003075176A2 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2003573563A JP4222947B2 (en) 2002-03-05 2003-02-14 Method, program, and system for representing multimedia content management objects
AU2003215716A AU2003215716A1 (en) 2002-03-05 2003-02-14 Support for multiple content-management data models
CA2477126A CA2477126C (en) 2002-03-05 2003-02-14 Support for multiple content-management data models
EP03743405A EP1530762A2 (en) 2002-03-05 2003-02-14 Support for multiple content-management data models
KR1020047012103A KR100745442B1 (en) 2002-03-05 2003-02-14 Support for multiple content-management data models
BRPI0308269-5A BR0308269A (en) 2002-03-05 2003-02-14 support for multiple content management data models

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/091,919 2002-03-05
US10/091,919 US7043490B2 (en) 2002-03-05 2002-03-05 Method, system, and program product to support multiple content-management data models

Publications (2)

Publication Number Publication Date
WO2003075176A2 true WO2003075176A2 (en) 2003-09-12
WO2003075176A3 WO2003075176A3 (en) 2005-03-17

Family

ID=27787764

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2003/000679 WO2003075176A2 (en) 2002-03-05 2003-02-14 Support for multiple content-management data models

Country Status (9)

Country Link
US (1) US7043490B2 (en)
EP (1) EP1530762A2 (en)
JP (1) JP4222947B2 (en)
KR (1) KR100745442B1 (en)
CN (1) CN100470538C (en)
AU (1) AU2003215716A1 (en)
BR (1) BR0308269A (en)
CA (1) CA2477126C (en)
WO (1) WO2003075176A2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008506161A (en) * 2004-04-29 2008-02-28 インターナショナル・ビジネス・マシーンズ・コーポレーション Enterprise content management network connection system
JP2009501989A (en) * 2005-07-20 2009-01-22 レノボ・リミテッド Data storage method
EP3451190A1 (en) * 2017-09-04 2019-03-06 Sap Se Model-based analysis in a relational database

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040015514A1 (en) * 2002-04-03 2004-01-22 Austin Melton Method and system for managing data objects
US8195714B2 (en) 2002-12-11 2012-06-05 Leaper Technologies, Inc. Context instantiated application protocol
US7925246B2 (en) 2002-12-11 2011-04-12 Leader Technologies, Inc. Radio/telephony interoperability system
US7380217B2 (en) * 2003-06-06 2008-05-27 Intellecspace Coropration Method of graphical presentation of relationships between individuals, business entities, and organizations
US7287037B2 (en) * 2003-08-28 2007-10-23 International Business Machines Corporation Method and apparatus for generating service oriented state data mapping between extensible meta-data model and state data including logical abstraction
US7313572B2 (en) * 2003-09-30 2007-12-25 Oracle International Corporation Attribute partitioning for user extensibility
US7284235B2 (en) * 2003-10-15 2007-10-16 Microsoft Corp Creation of content versions using content layers
US7379945B1 (en) 2003-10-20 2008-05-27 International Business Machines Corporation Virtual foldering system for blending process and content in a collaborative environment
US20050091271A1 (en) * 2003-10-23 2005-04-28 Kasy Srinivas Systems and methods that schematize audio/video data
US8965936B2 (en) * 2004-02-26 2015-02-24 Comcast Cable Holdings, Llc Method and apparatus for allocating client resources to multiple applications
US7289997B1 (en) * 2004-04-23 2007-10-30 Sun Microsystems, Inc. System and method for an extensible metadata driven application framework
KR100622130B1 (en) * 2004-12-21 2006-09-19 한국전자통신연구원 Crash recovery system and method for a distributed file server using object based storage
US8356053B2 (en) * 2005-10-20 2013-01-15 Oracle International Corporation Managing relationships between resources stored within a repository
US20070143250A1 (en) * 2005-12-20 2007-06-21 Beckman Coulter, Inc. Adaptable database system
US8046677B2 (en) * 2006-01-30 2011-10-25 International Business Machines Corporation Displaying relationships between tabular data using spatial identifiers
KR100705600B1 (en) * 2006-03-13 2007-04-09 삼성전자주식회사 Database managing apparatus and method in element management system
DE102006034407A1 (en) * 2006-07-25 2008-01-31 Robert Bosch Gmbh Update procedure for databases, in particular navigation databases
US7730088B2 (en) * 2006-09-14 2010-06-01 International Business Machines Corporation Queriable hierarchical text data
US7552127B2 (en) * 2006-12-19 2009-06-23 International Business Machines Corporation System and method for providing platform-independent content services for users for content from content applications leveraging Atom, XLink, XML Query content management systems
US9262545B2 (en) 2007-01-22 2016-02-16 Syracuse University Distributed video content management and sharing system
US7702644B2 (en) 2007-01-25 2010-04-20 Ludi Labs, Inc. Data management system and method to host applications and manage storage, finding and retrieval of typed items with support for tagging, connections, and situated queries
US8355972B2 (en) * 2007-04-17 2013-01-15 Intellectspace Corporation Systems and methods for displaying information about financial markets
US20080270458A1 (en) * 2007-04-24 2008-10-30 Gvelesiani Aleksandr L Systems and methods for displaying information about business related entities
US7925645B2 (en) * 2007-07-19 2011-04-12 Microsoft Corporation Dynamic metadata filtering for classifier prediction
WO2010115204A2 (en) * 2009-04-03 2010-10-07 Wishlist Holdings Limited System and method for building and using member hierarchy structures
US20110216640A1 (en) * 2009-07-17 2011-09-08 James Curtis Universal multimedia distribution, storage, and playback systems, and methods
US9047288B2 (en) 2012-01-06 2015-06-02 Apple Inc. Intelligent data delivery and storage based on data characteristics
CN104035943B (en) * 2013-03-08 2018-07-06 联想(北京)有限公司 Store the method and respective server of data
CN105760372A (en) * 2014-12-15 2016-07-13 中兴通讯股份有限公司 Conversion method and conversion device for object-oriented model data
CN106484404A (en) * 2016-09-23 2017-03-08 北京赢点科技有限公司 Content Management System and the method for custom content model and attribute
CN112883249B (en) * 2021-03-26 2022-10-14 瀚高基础软件股份有限公司 Layout document processing method and device and application method of device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000045294A1 (en) 1999-01-27 2000-08-03 British Broadcasting Corporation Broadcast media metadata structure
WO2002001384A2 (en) 2000-06-28 2002-01-03 Twi Interactive, Inc. Database system, particularly for multimedia objects

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5560005A (en) * 1994-02-25 1996-09-24 Actamed Corp. Methods and systems for object-based relational distributed databases
US6466992B2 (en) * 1994-12-07 2002-10-15 Next Computer, Inc. Method for providing stand-in objects
US6078925A (en) 1995-05-01 2000-06-20 International Business Machines Corporation Computer program product for database relational extenders
US5913205A (en) * 1996-03-29 1999-06-15 Virage, Inc. Query optimization for visual information retrieval system
US5907846A (en) * 1996-06-07 1999-05-25 Electronic Data Systems Corporation Method and system for accessing relational databases using objects
US6078926A (en) * 1997-12-18 2000-06-20 Persistence Software, Inc. Method and apparatus for performing multi-class object fetch in a database management system
US6263342B1 (en) 1998-04-01 2001-07-17 International Business Machines Corp. Federated searching of heterogeneous datastores using a federated datastore object
US6272488B1 (en) 1998-04-01 2001-08-07 International Business Machines Corporation Managing results of federated searches across heterogeneous datastores with a federated collection object
US6233586B1 (en) 1998-04-01 2001-05-15 International Business Machines Corp. Federated searching of heterogeneous datastores using a federated query object
JP2000250791A (en) * 1999-03-03 2000-09-14 Nec Corp Method and device for displaying message in dml object reproduction mode and recording medium with this method programmed and recorded therein
US6732331B1 (en) * 2000-02-15 2004-05-04 Vlad Alexander System and process for managing content organized in a tag-delimited template using metadata
WO2001075679A1 (en) * 2000-04-04 2001-10-11 Metamatrix, Inc. A system and method for accessing data in disparate information sources
US6647396B2 (en) * 2000-12-28 2003-11-11 Trilogy Development Group, Inc. Classification based content management system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000045294A1 (en) 1999-01-27 2000-08-03 British Broadcasting Corporation Broadcast media metadata structure
WO2002001384A2 (en) 2000-06-28 2002-01-03 Twi Interactive, Inc. Database system, particularly for multimedia objects

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008506161A (en) * 2004-04-29 2008-02-28 インターナショナル・ビジネス・マシーンズ・コーポレーション Enterprise content management network connection system
JP2009501989A (en) * 2005-07-20 2009-01-22 レノボ・リミテッド Data storage method
EP3451190A1 (en) * 2017-09-04 2019-03-06 Sap Se Model-based analysis in a relational database
US11157780B2 (en) 2017-09-04 2021-10-26 Sap Se Model-based analysis in a relational database

Also Published As

Publication number Publication date
CN100470538C (en) 2009-03-18
JP4222947B2 (en) 2009-02-12
CA2477126A1 (en) 2003-09-12
AU2003215716A1 (en) 2003-09-16
US7043490B2 (en) 2006-05-09
US20030172049A1 (en) 2003-09-11
KR20040086346A (en) 2004-10-08
CA2477126C (en) 2011-07-26
EP1530762A2 (en) 2005-05-18
BR0308269A (en) 2007-01-09
JP2006507554A (en) 2006-03-02
CN1653449A (en) 2005-08-10
KR100745442B1 (en) 2007-08-03
WO2003075176A3 (en) 2005-03-17

Similar Documents

Publication Publication Date Title
CA2477126C (en) Support for multiple content-management data models
Böhm et al. Metadata for multimedia documents
US6662188B1 (en) Metadata model
US8356029B2 (en) Method and system for reconstruction of object model data in a relational database
US7533115B2 (en) Method for managing persistent federated folders within a federated content management system
US7873667B2 (en) System and method for electronic submission, procurement, and access to highly varied test data
US7668864B2 (en) Digital library system with customizable workflow
US5162992A (en) Vector relational characteristical object
US20040122849A1 (en) Assignment of documents to a user domain
US7469257B2 (en) Generating and monitoring a multimedia database
US7035842B2 (en) Method, system, and program for defining asset queries in a digital library
US20050080820A1 (en) Method and system for generating, associating and employing user-defined fields in a relational database within an information technology system
US20050160101A1 (en) Method and apparatus using dynamic SQL for item create, retrieve, update delete operations in a content management application
US20210141773A1 (en) Configurable Hyper-Referenced Associative Object Schema
US20030078938A1 (en) Database and method of storing and retrieving data
JPH0769920B2 (en) Document management processor
Mansingh et al. Towards an Ontology based Meta-Information Warehouse Architecture
Keith Equal Format Data using Semantic-Relational Encoding
Xiaxia et al. An object-oriented model of digital assets management systems in printing industries
Jain et al. EVOLUTION OF DATA HANDLING APPROACHES: A REVIEW
Jayaraman Object reational data base management systems and applications in document retrieval
White Data integration with data warehousing and data mining in database environments
Leung Data management for visual information systems
DuoLin A New Information Systems Model Based on Data Management
Petathirapat et al. CMS in e-Business Application.

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 1020047012103

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2337/DELNP/2004

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2477126

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2003215716

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2003573563

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 20038049805

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2003743405

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003743405

Country of ref document: EP

ENP Entry into the national phase

Ref document number: PI0308269

Country of ref document: BR