Showing papers on "Meta Data Services published in 2009"

Associating and linking compact disc metadata

Abstract: Improved techniques for enhancing, associating, and linking various sources of metadata for music files, to allow integration of commercially generated metadata with user-entered metadata, and to ensure that metadata provided to the user is of the highest quality and accuracy available, even when the metadata comes from disparate sources having different levels of credibility. The invention further provides improved techniques for identifying approximate matches when querying metadata databases, and also provides improved techniques for accepting user submissions of metadata, for categorizing user submissions according to relative credibility, and for integrating user submissions with existing metadata.

Metadata Quality in Digital Repositories: A Survey of the Current State of the Art

Abstract: This study presents the current state of research and practice on metadata quality through focus on the functional perspective on metadata quality, measurement, and evaluation criteria coupled with mechanisms for improving metadata quality. Quality metadata reflect the degree to which the metadata in question perform the core bibliographic functions of discovery, use, provenance, currency, authentication, and administration. The functional perspective is closely tied to the criteria and measurements used for assessing metadata quality. Accuracy, completeness, and consistency are the most common criteria used in measuring metadata quality in the literature. Guidelines embedded within a Web form or template perform a valuable function in improving the quality of the metadata. Results of the study indicate a pressing need for the building of a common data model that is interoperable across digital repositories.

Spyglass: fast, scalable metadata search for large-scale storage systems

Abstract: The scale of today's storage systems has made it increasingly difficult to find and manage files. To address this, we have developed Spyglass, a file metadata search system that is specially designed for large-scale storage systems. Using an optimized design, guided by an analysis of real-world metadata traces and a user study, Spyglass allows fast, complex searches over file metadata to help users and administrators better understand and manage their files. Spyglass achieves fast, scalable performance through the use of several novel metadata search techniques that exploit metadata search properties. Flexible index control is provided by an index partitioning mechanism that leverages namespace locality. Signature files are used to significantly reduce a query's search space, improving performance and scalability. Snapshot-based metadata collection allows incremental crawling of only modified files. A novel index versioning mechanism provides both fast index updates and "back-in-time" search of metadata. An evaluation of our Spyglass prototype using our real-world, large-scale metadata traces shows search performance that is 1-4 orders of magnitude faster than existing solutions. The Spyglass index can quickly be updated and typically requires less than 0.1%of disk space. Additionally, metadata collection is up to 10× faster than existing approaches.

Editing metadata in a social network

Abstract: A system and method for server-side method for editing metadata in a file, the method including steps of: receiving from a user a request for editing the metadata in the file; presenting a window to the user for display on a user's screen wherein the window displays properties of the metadata; receiving from the user an edit to the metadata properties; and updating the metadata properties with the edit received from the user, for producing an updated metadata.

System, method and apparatus for enterprise policy management

Abstract: Disclosed are systems, methods and apparatuses for managing objects (files and directories) in network file systems according to policies. Each policy may have one or more rules, each of which ties a condition to an action. Each condition can be expressed in terms of metadata harvested across file systems and stored in a metadata repository. The actions are user-programmable. Users can apply and/or enforce a policy by manipulating the metadata stored in the metadata repository. For example, suppose a policy prohibits storing MP3 files in corporate storage, a user can specify a rule that ties the condition “no MP3 files in volumes A-Z” to an action “delete MP3 files from volumes A-Z.” A file management application may apply a filter to the metadata repository to produce metadata records having values that meet the specified condition and take the corresponding action on managed objects associated with those metadata records.

Automatic evaluation of metadata quality in digital repositories

Abstract: Owing to the recent developments in automatic metadata generation and interoperability between digital repositories, the production of metadata is now vastly surpassing manual quality control capabilities. Abandoning quality control altogether is problematic, because low-quality metadata compromise the effectiveness of services that repositories provide to their users. To address this problem, we present a set of scalable quality metrics for metadata based on the Bruce & Hillman framework for metadata quality control. We perform three experiments to evaluate our metrics: (1) the degree of correlation between the metrics and manual quality reviews, (2) the discriminatory power between metadata sets and (3) the usefulness of the metrics as low-quality filters. Through statistical analysis, we found that several metrics, especially Text Information Content, correlate well with human evaluation and that the average of all the metrics are roughly as effective as people to flag low-quality instances. The implications of this finding are discussed. Finally, we propose possible applications of the metrics to improve tools for the administration of digital repositories.

Method and system of generating reference variations for directory assistance data

Abstract: Methods and systems of performing user input recognition are disclosed. A digital directory comprising listings is accessed. Metadata information is associated with individual listings describing the individual listings. The metadata information is modified to generate transformed metadata information. Therefore, the transformed metadata information is generated as a function of context information relating to a typical user interaction with the listings. Information is generated for aiding in an automated user input recognition process based on the transformed metadata information.

A Metadata Best Practice for a Scientific Data Repository

Abstract: Digital data repositories ought to support immediate operational needs and long-term project goals. This paper presents the Dryad repository's metadata best practice balancing of these two needs. The paper reviews background work exploring the meaning of science, characterizing data, and highlighting data curation metadata challenges. The Dryad repository is introduced, and the initiative's metadata best practice and underlying rationales are described. Dryad's metadata approach includes two prongs: one addressing the long-term goal to align with the Semantic Web via a metadata application profile; and another addressing the immediate need to make content available in DSpace via an extensible markup language (XML) schema. The conclusion summarizes limitations and advantages of the two prongs underlying Dryad's metadata effort.

System and method for building virtual appliances using a repository metadata server and a dependency resolution service

Abstract: A system and method for building virtual appliances using a repository metadata server and a dependency resolution service is provided. In particular, a hosted web service may provide a collaborative environment for managing origin repositories and software dependencies, whereby remote clients may follow a simple and repeatable process for creating virtual appliances. For example, the repository metadata server may cache and parse metadata associated with an origin repository, download software from the origin repository, and generate resolution data that can be used by the dependency resolution service. The dependency resolution service may then use the resolution data to resolve dependencies for a package selected for an appliance, wherein the dependencies may include packages that are required, recommended, suggested, banned, or otherwise a dependency for the selected package.

Opinion search engine

Abstract: A computer-readable storage medium having stored thereon computer-executable instructions which, when executed by a computer, cause the computer to implement an opinion search engine. The instructions to implement an opinion search engine cause the computer to collect opinion data about one or more objects from the Internet, extract metadata about the opinion data from the opinion data, remove duplicate metadata from the metadata to generate a resulting metadata, categorize the resulting metadata for similar objects according to one or more taxonomies from one or more websites on the Internet and rank the similar objects based on the categorized metadata.

Metadata server and metadata management method

Abstract: Provided are a metadata server cluster and a metadata management method thereof, which distribute metadata for a file to a cluster including a plurality of metadata servers to replicate the metadata. The metadata server includes a directory hierarchy storage unit, a metadata storage unit, and a search unit. The directory hierarchy storage unit stores all directory hierarchies which are stored in the metadata server cluster. The metadata storage unit stores metadata for a data file. The search unit searches the directory hierarchies and the metadata.

Systems and methods for using metadata to enhance data management operations

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.

Repository Metadata: Approaches and Challenges

Abstract: Many institutional repositories have pursued a mixed metadata environment, relying on description by multiple workflows. Strategies may include metadata converted from other systems, metadata elicited from the document creator or manager, and metadata created by library or repository staff. Additional editing or proofing may or may not occur. The mixed environment brings challenges of creation, management, and access. In this article, repository efforts at three major universities are discussed. All three repositories run on the DSpace software package, and the opportunities and limitations of that system will be examined. The authors discuss local strategies in light of current thinking on metadata creation, user behavior, and the aggregation of heterogeneous metadata. The contrasts between the mission of each repository effort will show the importance of local customization, while the experience of all three institutions forms the basis for recommendations on strategies of benefit to a wide range of librarians and repository planners.

An Overview of e-Government Metadata Standards and Initiatives based on Dublin Core

Abstract: the broad definition of metadata is 'data about data' or 'data that describe data or information'. In more specific terms, 'metadata is data about other data or objects, used to describe digitized and non-digitized resources located in a distributed system in a network environment' (Haynes, D, p 8). In e-Government applications it may be used, amongst other for the discovery and retrieval of government information, as well as to assist in the management of government electronic resources. In other words, metadata is the key to interoperability. This paper aims to highlight the use of metadata in e-Government projects with a review of the most widely metadata standard used in e-Government application (DC). Also, it will compare the work which has been carried out in the UK, Australia, New Zealand, Canada and Ireland with DC, as all these metadata projects are based on simple Dublin Core metadata. Finally, roadmap for metadata development will be proposed.

Metadata and Digital Information

Abstract: The range of metadata activity over this last decade is both extensive and astonishing, and substantiates metadata as an integral part of our digital information infrastructure. This entry begins with a brief history of metadata relating to digital information, followed by an overview of different metadata types, functions, and domain-specific definitions. Next, the family of standards comprising a metadata architecture are defined, followed by an overview of metadata generation processes, applications, and people: this latter section gives particular attention to automatic metadata generation approaches. The following section explores four key metadata models. The conclusion summarizes the entry, highlights a number of significant metadata challenges, and notes efforts underway to address metadata challenges in the new millennium

Client-server systems and methods for accessing metadata information across a network using proxies

Abstract: Embodiments of the present invention include a computer-implemented systems and methods for accessing metadata across a network. A metadata server receives requests to access a data source from one or more clients. The metadata server is coupled between one or more backend servers and the clients. The backend servers may be coupled to the data sources of interest. The metadata server provides a metadata service proxy for establishing communications with the backend servers and for signaling the backend servers to establish connections to data sources. Data sources may be stateful or stateless. For stateless data sources, the metadata server may dynamically create reusable metadata service provider proxies that receive metadata from metadata service providers on the backend servers. For stateful data sources, unique metadata service provider proxies may be dynamically created and used to service client requests.

Multimedia distribution and playback systems and methods using enhanced metadata structures

Abstract: A metadata systems and methods are provided that enhance the playback features of multimedia files. A metadata structure is used that includes metadata tags and objects to allow access to various data typically not available to most playback devices.

System and method for harvesting metadata into a service metadata repository

Abstract: Business Process Execution Language (BPEL) engines and Enterprise Service Buses (ESBs) often connect to adapters to integrate backend packaged applications with a process flow by invoking web services using Java Connector Architecture (JCA) and Simple Object Access Protocol (SOAP) bindings. The Web Service Description Language (WSDL) files for the web services that interact with the adapters can be introspected to harvest adapter integration and transformation information into a service metadata repository. This permits dependency and impact analysis to extend from services to adapters and transformations.

An evaluation framework of user interaction with metadata surrogates

Abstract: This paper proposes a framework for the evaluation of user interaction with textual metadata surrogates in the search result interfaces of various types of Information Retrieval (IR) systems. Metadata surrogates are representations of the full-text documents displayed to the user as a list of retrieved results after a search has been performed in an IR system. By examining the metadata surrogates, users can make judgments about the relevance of the full-text document without having to access and evaluate the document itself, thus saving a considerable amount of time and effort. The literature review, however, reveals a lack of frameworks for the evaluation of users' interaction with metadata surrogates. The implications of such a framework would be to inform designers and researchers of IR systems about the main components of users' interaction with metadata surrogates and to facilitate the process of evaluating metadata surrogates in terms of content and presentation.

Metaphysically addressed cache metadata

Abstract: Storing metadata that is disjoint from corresponding data by storing the metadata to the same address as the corresponding data but in a different address space. A metadata store instruction includes a storage address for the metadata. The storage address is the same address as that for data corresponding to the metadata, but the storage address when used for the metadata is implemented in a metadata address space while the storage address, when used for the corresponding data is implemented in a different data address space. As a result of executing the metadata store instruction, the metadata is stored at the storage address. A metadata load instruction includes the storage address for the metadata. As a result of executing the metadata load instruction, the metadata stored at the address is received. Some embodiments may further implement a metadata clear instruction which clears any entries in the metadata address space.

SDI and Metadata Entry and Updating Tools

Abstract: Deposited with permission of the authors. © 2009 Abbas Rajabifard, Mohsen Kalantari & Andrew Binns

A pattern language for metadata-based frameworks

Abstract: Metadata-based frameworks are those that process their logic based on the metadata of the classes whose instances they are working with. Many recent frameworks use this to get a higher reuse level and to be more suitably adapted to the application needs. However, there is not yet a complete best practices documentation or reference architecture for the development of frameworks by using the metadata approach. As a result, this paper presents a pattern language that addresses preliminarily the internal structure of metadata-based frameworks, helping in the understanding and development of such kind of framework.

Metadata requirements analysis for the emerging Sensor Web This was orally presented at the European Geosciences Union General Assembly 2008, Vienna, Austria, 13-18 April 2008.

Abstract: The Sensor Web has emerged from Earth Science research with the development of Web technology, to achieve process automation, sensor interoperation, and service synergy. These promises require the discovery of the right sensor at the right time and the right location with the right quality. Metadata, for sensor, platform, and data, are crucial for achieving such goals. However, analysis and practical use of these metadata reveals that the metadata and their associations are not applicable or suitable for the Sensor Web. The shortfalls are (1) the non-standard metadata expression language; (2) the missing link between sensor and domain knowledge; (3) the insufficiency in the information for geographic locating and sensor tasking; and (4) the enhanced requirements on the quality, security, and ownership of both sensors and their sensed data. This paper reviews the current standards that have metadata components for the sensor and its platform, especially those from ISO TC211, Open Geospatial Consor...

Method and apparatus for accessing content based on user geolocation

Abstract: An approach is provided for mapping content, such as audio files, to associated metadata about the content The approach includes initiating a search for local metadata associated with particular content It is determined whether the local metadata is insufficient A request for metadata associated with the particular content is generated, if the local metadata is insufficient The request is sent to a metadata service to obtain result data including metadata for the particular content A search of the result data from the metadata service is initiated based on a description of the particular content to obtain most relevant metadata of the result data

Metadata plug-in application programming interface

Abstract: Computer-based methods and systems for editing a time-based media program involve receiving an instruction to associate metadata with a selected portion of the program, determining a type of the metadata, wherein the type of the metadata is one of a predetermined set of metadata types, identifying a software component available to the editing system that is configured to process metadata of the determined type, and associating the metadata with the selected portion of the program by executing the identified software component to process the metadata. Metadata is represented using a scheme that is shared among the various computational components that manipulate the metadata; the scheme may also be shared with a host media processing system, as well as with other systems that are used in a time-based media editing and production workflow.

Correlation of media metadata gathered from diverse sources

Abstract: A DVR, server, or other agent correlates media metadata from diverse sources, like an EPG data provider and multiple video-on-demand (VOD) service providers. Metadata sets from different sources are compared in order to attempt to identify identical programs to which the metadata sets pertain. From at least one metadata set, information about the program that the other metadata set lacks is selected. A “canonical” data structure instance for the program is created. The information that is lacking from at least one of the metadata sources is inserted into that instance. For each source from which a program is available, the DVR stores the identity of that source on the DVR's persistent storage device in association with the canonical data structure instance for that program. The DVR receives search criteria from a user and then searches the stored canonical data structure instance for programs that satisfy the criteria.

Foundations of a metadata repository for databases of registers and trials.

Abstract: The planning of case report forms (CRFs) in clinical trials or databases in registers is mostly an informal process starting from scratch involving domain experts, biometricians, and documentation specialists. The Telematikplattform fur Medizinische Forschungsnetze, an um brella organization for medical research in Germany, ai ms at supporting and improving this process with a metadata repository, covering the variables and value lists used in databases of registers and trials. The use cases for the metadata repository range from a specification of case report forms to the harmonization of variable collections, variables, and value lists through a form al review. The warehouse used for the storage of the metadata should at least fulfill the definition of part 3 "Registry metamodel and basic attributes" of ISO/IEC 11179 Information technology - Metadata registries. An implementation of the metadata repository should offer an import and export of metadata in the Operational Data Model standard of the Clinical Data Interchange Standards Consortium. It will facilitate the creation of CRFs and data models, improve the quality of CRFs and data models, support the harmonization of variables and value lists, and support the mapping of metadata and data.

User editable metadata for interactive television programs

Abstract: Television programming may be annotated with metadata and the metadata may be shared among subscribers. A set-top box may receive, from a server, metadata relating to a television program, the metadata having been created by users of other set-top boxes and at least some elements of the metadata including information describing portions of the television program to which the metadata is relevant. The set-top box may present the metadata during portions of the television program at which the metadata is relevant.