Showing papers on "Metadata repository published in 2006"

Intelligent electronic appliance system and method

Abstract: An intelligent electronic appliance preferably includes a user interface, data input and/or output port, and an intelligent processor. A preferred embodiment comprises a set top box for interacting with broadband media streams, with an adaptive user interface, content-based media processing and/or media metadata processing, and telecommunications integration. An adaptive user interface models the user, by observation, feedback, and/or explicit input, and presents a user interface and/or executes functions based on the user model. A content-based media processing system analyzes media content, for example audio and video, to understand the content, for example to generate content-descriptive metadata. A media metadata processing system operates on locally or remotely generated metadata to process the media in accordance with the metadata, which may be, for example, an electronic program guide, MPEG 7 data, and/or automatically generated format. A set top box preferably includes digital trick play effects, and incorporated digital rights management features.

Systems and methods for classifying and transferring information in a storage network

Abstract: Systems and methods for data classification to facilitate and improve data management within an enterprise are described. The disclosed systems and methods evaluate and define data management operations based on data characteristics rather than data location, among other things. Also provided are methods for generating a data structure of metadata that describes system data and storage operations. This data structure may be consulted to determine changes in system data rather than scanning the data files themselves.

Media object metadata association and ranking

Abstract: Metadata may be associated with media objects by providing media objects for display, and accepting input concerning the media objects, where the input may include at least two different types of metadata. For example, metadata may be in the form of tags, comments, annotations or favorites. The media objects may be searched according to metadata, and ranked in a variety of ways.

Method and apparatus to control operation of a playback device

Abstract: Media metadata is accessible for a plurality of media items (See FIG. 12). The media metadata includes a number of strings to identify information regarding the media items (See FIG. 12). Phonetic metadata is associated the number of strings of the media metadata (See FIG. 12). Each portion of the phonetic metadata is stored in an original language of the string (See FIG. 12).

Highly meaningful multimedia metadata creation and associations

Abstract: Systems and methods for generating temporal metadata for a media source as a function of detected content. An analysis engine detects content within a media stream of a media source. A metadata creation engine generates temporal metadata as a function of the detected content. The generated temporal metadata may be used to create a media log for the media source, generate metadata subsequent detected content and to compare to media sources.

Method and apparatus for processing metadata

Abstract: Methods and apparatuses for processing metadata are described herein. In one embodiment, when a file (e.g., a text, audio, and/or image files) having metadata is received, the metadata and optionally at least a portion of the content of the file are extracted from the file to generate a first set of metadata. An analysis is performed on the extracted metadata and the content to generate a second set of metadata, which may include metadata in addition to the first set of metadata. The second set of metadata may be stored in a database suitable to be searched to identify or locate the file. Other methods and apparatuses are also described.

Metadata Interoperability and Standardization - A Study of Methodology Part I Achieving Interoperability at the Schema Level

Abstract: The rapid growth of Internet resources and digital collections has been accompanied by a proliferation of metadata schemas, each of which has been designed based on the requirements of particular user communities, intended users, types of materials, subject domains, project needs, etc. Problems arise when building large digital libraries or repositories with metadata records that were prepared according to diverse schemas. This article (published in two parts) contains an analysis of the methods that have been used to achieve or improve interoperability among metadata schemas and applications, for the purposes of facilitating conversion and exchange of metadata and enabling cross-domain metadata harvesting and federated searches. From a methodological point of view, implementing interoperability may be considered at different levels of operation: schema level, record level, and repository level. Part I of the article intends to explain possible situations in which metadata schemas may be created or implemented, whether in individual projects or in integrated repositories. It also discusses approaches used at the schema level. Part II of the article will discuss metadata interoperability efforts at the record and repository

Metabase for facilitating data classification

Abstract: Systems and methods for managing electronic data are disclosed. Various data management operations can be performed based on a metabase formed from metadata. Such metadata can be identified from an index of data interactions generated by a journaling module, and obtained from their associated data objects stored in one or more storage devices. In various embodiments, such processing of the index and storing of the metadata can facilitate, for example, enhanced data management operations, enhanced data identification operations, enhanced storage operations, data classification for organizing and storing the metadata, cataloging of metadata for the stored metadata, and/or user interfaces for managing data. In various embodiments, the metabase can be configured in different ways. For example, the metabase can be stored separately from the data objects so as to allow obtaining of information about the data objects without accessing the data objects or a data structure used by a file system.

System and method for translating between relational database queries and multidimensional database queries

Abstract: A method for mapping a data source of an unknown configuration to that of a known configuration, comprising the steps of submitting a request for metadata to the data source of the unknown configuration; generating a relational schema from the known configuration based on the metadata received from the data source of the unknown configuration; and returning the metadata of the generated relational schema which maps the data source of the unknown configuration to the known configuration. In a preferred embodiment data source of the unknown configuration is a multidimensional database and the known configuration is a star or snowflake relational schema.

Distributed maintenance of snapshot copies by a primary processor managing metadata and a secondary processor providing read-write access to a production dataset

Abstract: A primary processor manages metadata of a production dataset and a snapshot copy, while a secondary processor provides concurrent read-write access to the primary dataset. The secondary processor determines when a first write is being made to a data block of the production dataset, and in this case sends a metadata change request to the primary data processor. The primary data processor commits the metadata change to the production dataset and maintains the snapshot copy while the secondary data processor continues to service other read-write requests. The secondary processor logs metadata changes so that the secondary processor may return a “write completed” message before the primary processor commits the metadata change. The primary data processor pre-allocates data storage blocks in such a way that the “write anywhere” method does not result in a gradual degradation in I/O performance.

Methods, systems, and computer program products for extensible, profile-and context-based information correlation, routing and distribution

Abstract: Methods, systems, and computer program products for extensible, profile- and context-based information correlation, routing, and distribution are disclosed. According to one system, source plug-ins receive output from a plurality of different sensors. A content manager merges data from individual sensors together with metadata that is representative of a context and aggregates the sensor data and the context metadata into knowledge items. A scenario engine achieves sensor fusion by comparing the sensor data and its context metadata against a defined set of policies and/or rules and provides for performance of an action when a rule or policy is satisfied.

Rules driven pan id metadata routing system and network

Abstract: A method and system for provides routing of metadata related to media content, using content identifiers to locate the metadata content and rules to determine a subset of the metadata to deliver. This method registers globally unique identifiers for content objects. These globally unique identifiers each comprise a content identifier provided with the content object and a bounding identifier identifying a set of content identifiers of which the content identifier is a member. For each of the globally unique identifiers, information is maintained about a metadata source. The method receives a first content identifier for the content object, and uses a bounding identifier associated with the set of the first content identifier to determine the globally unique identifier for the first content identifier. The user is routed to the metadata source associated with globally unique identifier.

Video search and services

Abstract: Arrangements and methods are described that provide organization of motion image data. In one exemplary implementation, a metadata file is stored in a memory of a computing device. The metadata file includes metadata derived from motion image data. The metadata may include at least a genre associated with the motion image data and a semantic attribute related to the motion image data. The metadata is capable of facilitating text-based searching operations to locate one or more motion image data associated with the metadata.

Digital asset management system, including customizable metadata model for asset cataloging and permissioning of digital assets, such as for use with digital images and songs

Abstract: A method, system, and metadata model is provided that allows for the organization of electronic assets, such as songs, videos, documents, images, etc. Virtual libraries are created based on virtual copies of assets created based on metadata, thereby avoiding copying of the actual assets. The metadata model also facilitates searching for assets from the virtual libraries and the implementation of permissioning schemes.

Ontology‐Based Metadata

Abstract: Metadata are an extant mechanism for conveying ontological information about semantic data. Metadata have the advantage of being institutionally and structurally ensconced in GIS. At present, however, they lack fields to express information beyond the technical and geometric domain. This paper describes a framework for the creation of extended metadata for non-spatial attributes, with the goal of incorporating ontological context. We use an informatics interpretation of ontology which refers to the total universe of discourse associated with a given attribute (database field). In other words, an ontology is the possible range of meaning offered by an encoded field. Current ontology research in GIScience has focused on data structuring and modelling. Implementation of these schemes demands restructuring of existing relational database models. An alternative is to extend current metadata schemes (e.g. ISO 19115) to include context-based and tacit information about semantic attributes. Such ontology-based extended metadata permits data selection and interoperability decisions that are ultimately more defensible. We have developed eight preliminary fields to add to existing metadata frameworks that will enable ontological context to travel with the data. This paper illustrates a preliminary implementation based on the integration of non-commensurate cadastral data. The results illustrate the value of ontology-based metadata in highlighting descriptive and substantive differences between similar classification systems. Recognition of semantic heterogeneity is the basis for creating defensible data linkages between multiple datasets. The development of ontology-based metadata is profoundly

System and method for analyzing data sources to generate metadata

Abstract: A system and method are provided for generating metadata relating to an enterprise management system including at least one data source having one or more of tables and columns. Constraints existing on at least one of the tables and columns in the data source are inferred based on data in the tables and columns. Metadata that includes information on the inferred constraints is generated.

Methods and structure for dynamic appended metadata in a dynamically mapped mass storage device

Abstract: Methods and structures for appending metadata with recorded data in a dynamic mapped storage device. In a dynamically mapped storage device in which all user supplied logical blocks are dynamically mapped by the storage device controller to physical disk blocks, features and aspects hereof allow presently unused physical space to be used for storing additional metadata associated with recorded data. As the current capacity ratio of the storage device increases, appending of metadata may cease and previously recorded data including metadata may be re-recorded (migrated) to eliminate the appended metadata. The appended metadata may be used for enhanced diagnosis and analysis of characteristics of the operating storage device and may be used to restore the content of the storage device to an earlier state. The metadata may include, for example, track following position of the read/write head, temperature, head flying height, and time of day.

Techniques for transmitting personal data and metadata among computing devices

Abstract: Personal data services, such as a set of Web services, are enabled that allow a user to enter personal metadata information, e.g., about likely people and/or events to be targets of a camera capture event. Then, when a user's computing device acquires such metadata, e.g., via embedded Web services software, an intelligent user interface allows the user to enter whether any of such personal metadata information pertains to any personal data, such as a video, an audio file or an image, which is captured by the user's computing device. The personal data including the metadata information can be automatically uploaded via one or more wired and/or wireless networks to a device that hosts a personal data service, which stores the personal data and associated metadata, providing for effective means to access and manage a user's personal data store. The services of the invention also enable a system for identifying unknown or new metadata where existing metadata is not sufficient to describe a video, audio or image capture event. In addition, a gateway is provided that enables transfer of content from the Web services to other media service providers, such as a cable or television over Internet Protocol (“TVoIP”) video or other video on demand (“VOD”) service.

System and method for classifying electronically posted documents

Abstract: A method for classifying electronically posted documents includes receiving two posted documents and generating corresponding metadata summaries for each, wherein each of the metadata summaries includes at least one sub-tree structure. The structures of the two summary sub-trees within the respective metadata summaries are subsequently compared. If the two summary sub-trees are different, the two documents are deemed distinct. If the two summary sub-trees are the same, attribute values and text content of the metadata summaries are compared over a portion of the metadata summaries. If the compared attribute values and text content are determined to be the same, the documents are deemed duplicative.

Functionalities for automatic metadata generation applications: a survey of metadata experts' opinions

Abstract: This paper reports on the automatic metadata generation applications (AMeGA) project's metadata expert survey. Automatic metadata generation research is reviewed and the study's methods, key findings and conclusions are presented. Participants anticipate greater accuracy with automatic techniques for technical metadata (e.g., ID, language, and format metadata) compared to metadata requiring intellectual discretion (e.g., subject and description metadata). Support for implementing automatic techniques paralleled anticipated accuracy results. Metadata experts are in favour of using automatic techniques, although they are generally not in favour of eliminating human evaluation or production for the more intellectually demanding metadata. Results are incorporated into Version 1.0 of the Recommended Functionalities for automatic metadata generation applications (Appendix A).

Information access with usage-driven metadata feedback

Abstract: In a method for displaying and capturing metadata of documents within result presentations in information access or search systems, a metadata server is used for storing a metadata associated with any searchable document and the end users are given the opportunity to view and edit metadata associated with documents returned from the metadata server which is capable of automatically creating metadata objects associated with any combination of document query and document position in a result set for a given query A search engine capable of implementing the method comprises a metadata server as part of or connected with its core search engine.

System and method for optimizing federated and ETL'd databases having multidimensionally constrained data

Abstract: Method, system, and program product for configuring and using a federated database management system. The design of the metadata and queries includes the steps of first determining schema and metadata configurations of the data source servers. The next step is enumerating available resources, and enumerating security and confidentiality requirements. These are used for calculating an optimal federated database management system design based on the schema and metadata, the enumerated available resources, and the enumerated security and confidentiality requirements; and designing an optimal federated database management system.

Hierarchal data management

Abstract: A hierarchal data management system (302) for a storage device includes an entity relationship discover to generate meta data fi-om a business object, a file manager to create a partition based (310) on the metadata, a data mover to generate a logical partitioning (312) key and to store the logical partitioning (310) key in the metadata for the partition. The file manager includes a data management policy to define a data class and a storage policy to map the dataxlass to the storage device to form a partition table (304).

The evolution of metadata from standards to semantics in E-learning applications

Abstract: Metadata attempts to describe the content, format, purpose and structure of data. Over the past few years, the IEEE-LOM standard has dominated the metadata world in e-learning applications. However, with the advent of the Semantic Web, e-learning applications are beginning to evolve their metadata representation from these standards by adding semantic structure or by converting entirely to semantic representations of structure. This shift enables the implementation of a range of new tools which can reason over the metadata, providing added value from the stored data. This review paper summarizes this evolution of metadata used in e-learning applications from standards to semantic representation.

Ontology based document annotation: trends and open research problems

Abstract: Metadata is used to describe documents and applications, improving information seeking and retrieval and its understanding and use. Metadata can be expressed in a wide variety of vocabularies and languages, and can be created and maintained with a variety of tools. Ontology based annotation refers to the process of creating metadata using ontologies as their vocabularies. We present similarities and differences with respect to other approaches for metadata creation, and describe languages and tools that can be used to implement these annotations.

Data flow system and method for heterogeneous data integration environments

Abstract: A computer implemented method, apparatus, and computer usable program code for generating an execution plan graph from a data flow. A metadata representation of the data flow is generated in response to receiving the data flow. A set of code units is generated from the metadata representation. Each code unit in the set of code units is executable on multiple different types of runtime engines. The set of code units is processed to produce the execution plan graph.

Health-care related database middleware

Abstract: An exemplary embodiment providing for one or more improvements includes a database translation architecture that has an object model for defining a variety of health-related classes and a plurality of data bridge / data set pairs wherein each data bridge is coupled to the object model. A plurality of external components are coupled to all but one of the data bridge / data set pairs of the plurality of data bridge / data set pairs wherein the plurality of external components are operative to send and receive data in formats unique to each external component such that each format is translated to and from the object model by each corresponding data bridge / data set pair. Also included is a database coupled to a remaining data bridge / data set pair not coupled to an external component wherein the database is responsive to data queries from the object model as translated by the remaining data bridge / data pair and the database and operative to deliver requested data back to the object model through the remaining data bridge / data set pair which is in turn sent to an external component that originally initiated the data query.

Packaged warehouse solution system

Abstract: A data warehouse solution system comprises a metadata model, a user interface and an engine. The metadata model has an information needs model including metadata regarding information needs for building reports by users, and a data information model including metadata describing data that is available for building reports. The user interface has a customer user interface for presenting the information needs model to the users for report generation, and a modeling user interface for presenting the data information model to the users for manipulating data warehouse objects. The engine has a report management service unit for providing report management service using the information needs model, and a data management service unit for providing data management service including generation of a data warehouse using the data information model.

Push framework for delivery of dynamic mobile content

Abstract: A push proxy and push client for use in a generic dynamic content delivery system the push proxy having: a content provider registration service provider interface, said service provider interface adapted to register said push proxy with content providers and to further receive channel metadata for the content providers; a channel metadata repository adapted to store said channel metadata received from the content providers; a content metadata extractor and cache module adapted to extract metadata for said push proxy from a content and metadata envelope received from the content providers, said content metadata extracting cache further adapted to cache said metadata on said push proxy; a content fragmentation module adapted to break a content and metadata envelope into segments; a deferred retrieval message store module adapted to store a content envelope or one or more segments from said content fragmentation module; a content expiry and replacement module adapted to expire content stored in the deferred retrieval message store or to replace content stored in the deferred retrieval message store; a content dependencies module adapted to provide selection of push clients to advertise a service to; a push scheduler, said push scheduler adapted to schedule the pushing of a content envelope stored in the deferred retrieval message store; and a subscription and rules module adapted to maintain a subscription between an application and the content provider and maintain a list of rules for the subscription.

Metadata driven user interface

Abstract: Metadata is used to create customized user interface (UI) portions for an application. The metadata may be XML-based and can be interpreted and then rendered to implement a customized UI that also supports data binding between data and the UI controls. Once created, the metadata is processed by a rendering engine to display the UI controls. An interpreter may be used to interpret the metadata file before it sent to the rendering engine. Neither the rendering engine nor the interpreter needs knowledge of the host application and provides support for arbitrary metadata driven UI. The metadata schema may include mechanisms to create custom controls for the UI; programmatically modify the UI controls by providing access to a code-behind assembly as well as support event handling for the UI controls.