Showing papers on "Meta Data Services published in 2013"

Metadata subsystem for a distributed object store in a network storage system

Abstract: A network storage server system includes a distributed object store and a metadata subsystem. The metadata subsystem stores metadata relating to the stored data objects and allows data objects to be located and retrieved easily via user-specified search queries. It manages and allows searches on at least three categories of metadata via the same user interface and technique. These categories include user-specified metadata, inferred metadata and system-defined metadata. Search queries for the metadata can include multi-predicate queries.

Content based traffic engineering in software defined information centric networks

Abstract: This paper describes a content centric network architecture which uses software defined networking principles to implement efficient metadata driven services by extracting content metadata at the network layer. The ability to access content metadata transparently enables a number of new services in the network. Specific examples discussed here include: a metadata driven traffic engineering scheme which uses prior knowledge of content length to optimize content delivery, a metadata driven content firewall which is more resilient than traditional firewalls and differentiated treatment of content based on the type of content being accessed. A detailed outline of an implementation of the proposed architecture is presented along with some basic evaluation.

Framework for facilitating implementation of multi-tenant SaaS architecture

Abstract: A framework for implementing multitenant architecture is provided. The framework comprises a framework services module which is configured to provide framework services that facilitate abstraction of Software-as-a-Service (SaaS) services and crosscutting services for a Greenfield application and a non SaaS based web application. Further the abstraction results in a SaaS based multitenant web application. The framework further comprises a runtime module configured to automatically integrate and consume the framework services and APIs to facilitate monitoring and controlling of features associated with the SaaS based multitenant web application. The framework further comprises a metadata services module configured to provide a plurality of metadata services to facilitate abstraction of storage structure of metadata associated with the framework and act as APIs for managing the metadata. The framework further comprises a role based administration module that facilitates management of the metadata through a tenant administrator and a product administrator.

Evaluation of header metadata extraction approaches and tools for scientific PDF documents

Abstract: This paper evaluates the performance of tools for the extraction of metadata from scientific articles. Accurate metadata extraction is an important task for automating the management of digital libraries. This comparative study is a guide for developers looking to integrate the most suitable and effective metadata extraction tool into their software. We shed light on the strengths and weaknesses of seven tools in common use. In our evaluation using papers from the arXiv collection, GROBID delivered the best results, followed by Mendeley Desktop. SciPlore Xtract, PDFMeat, and SVMHeaderParse also delivered good results depending on the metadata type to be extracted.

Data recovery using a cloud-based remote data recovery center

Abstract: A Remote Metadata Center provides Distaster Recovery (DR) testing and metadata backup services to multiple business organizations. Metadata associated with local data backups performed at business organizations is transmitted to the Remote Metadata Center. Corresponding backup data is stored in a data storage system that is either stored locally at the business organization or at a data storage facility that is at a different location than the Remote Metadata Center and the business organization. DR testing can be staged from the Remote Data Center using the metadata received and optionally with assistance from an operator at the business organization and/or the data storage facility.

Distributed data provenance for large-scale data-intensive computing

Abstract: It has become increasingly important to capture and understand the origins and derivation of data (its provenance). A key issue in evaluating the feasibility of data provenance is its performance, overheads, and scalability. In this paper, we explore the feasibility of a general metadata storage and management layer for parallel file systems, in which metadata includes both file operations and provenance metadata. We experimentally investigate the design optimality-whether provenance metadata should be loosely-coupled or tightly integrated with a file metadata storage systems. We consider two systems that have applied similar distributed concepts to metadata management, but focusing singularly on kind of metadata: (i) FusionFS, which implements a distributed file metadata management based on distributed hash tables, and (ii) SPADE, which uses a graph database to store audited provenance data and provides distributed module for querying provenance. Our results on a 32-node cluster show that FusionFS+SPADE is a promising prototype with negligible provenance overhead and has promise to scale to petascale and beyond. Furthermore, FusionFS with its own storage layer for provenance capture is able to scale up to 1 K nodes on BlueGene/P supercomputer.

Dealing with metadata quality: The legacy of digital library efforts

Abstract: In this work, we elaborate on the meaning of metadata quality by surveying efforts and experiences matured in the digital library domain. In particular, an overview of the frameworks developed to characterize such a multi-faceted concept is presented. Moreover, the most common quality-related problems affecting metadata both during the creation and the aggregation phase are discussed together with the approaches, technologies and tools developed to mitigate them. This survey on digital library developments is expected to contribute to the ongoing discussion on data and metadata quality occurring in the emerging yet more general framework of data infrastructures.

Implementation of Metadata Quality Metrics and Application on Public Government Data

Abstract: Public government data refers to documents and proceedings which are freely available and accessible. Repositories facilitate the collection, publishing and distribution of data in a centralized and possibly standardized way. Metadata is used to catalog and organize the provided data. The operationality and interoperability depends on the metadata quality. In order to measure the efficiency of a repository the metadata quality needs to be quantified. Quality assessment is considered to be most reliable when carried out by a human expert. This approach, however, is not always feasible. Hence, an automatic assessment of the quality of metadata should be pursued. Proposed metrics from the field of metadata quality assessment are taken, implemented and applied to three public government data repositories, namely GovData.de (Germany), data.gov.uk (United Kingdom) and publicdata.eu (Europe). Five quality metrics were applied: completeness, weighted completeness, accuracy, richness of information and accessibility. The metrics and their implementation will be discussed in detail and the results evaluated.

Metadata enabled third-party application access of content at a cloud-based platform via a native client to the cloud-based platform

Abstract: Techniques are disclosed for methods, architectures and security mechanisms for a third-party application to access content in a cloud-based platform. In one embodiment, a method includes, receiving, at the third-party application, metadata that identifies the file. The method further includes transmitting the metadata to a server which is associated with the third-party application. The metadata enables the server to request the file from the cloud-based environment.

Building information management system with building metadata

Abstract: A Building Information Management System, comprising: a Building Information System comprising: a database of operational information comprising lessons learned and idiosyncrasies regarding the particular building and the particular equipment in any particular building, of precautionary statements, of device operational configuration information, history and presets, and of emergency procedures; an Input region; a search function for locating all devices of a specific type throughout the building or buildings; a Report writing function.

Direct lookup and hash-based metadata placement for local file systems

Abstract: New challenges to file systems' metadata performance are imposed by the continuously growing number of files existing in file systems. The total amount of metadata can become too big to be cached, potentially leading to multiple storage device accesses for a single metadata lookup operation. This paper takes a look at the limitations of traditional file system designs and discusses an alternative metadata handling approach, using hash-based concepts already established for metadata and data placement in distributed storage systems. Furthermore, a POSIX compliant prototype implementation based on these concepts is introduced and benchmarked. A variety of file system metadata and data operations as well as the influence of different storage technologies are taken into account and performance is compared with traditional file systems.

Handbook Of Metadata, Semantics And Ontologies

Abstract: Foundations Metadata and Ontology Languages Metadata and Ontologies by Domain Technologies and Systems for Managing Metadata.

Status tool to expose metadata read and write queues

Abstract: A method to expose status information is provided. The status information is associated with metadata extracted from multimedia files and stored in a metadata database. The metadata information that is extracted from the multimedia files is stored in a read queue to allow a background thread to process the metadata and populate the metadata database. Additionally, the metadata database may be updated to include user-define metadata, which is written back to the multimedia files. The user-defined metadata is included in a write queue and is written to the multimedia files associated with the user-defined metadata. The status of the read and write queues are exposed to a user through a graphical user interface. The status may include the list of multimedia files included in the read and write queues, the priorities of each multimedia file, and the number of remaining multimedia files.

Metadata capital in a data repository

Abstract: This paper reports on a study exploring 'metadata capital' acquired via metadata reuse. Collaborative modeling and content analysis methods were used to study metadata capital in the Dryad data repository. A sample of 20 cases for two Dryad metadata workflows (Case A and Case B) consisting of 100 (60 metadata objects, 40 metadata activities) instantiations was analyzed. Results indicate that Dryad's overall workflow builds metadata capital, with the total metadata reuse at 50% or greater for 8 of 12 metadata properties, and 5 of these 8 properties showing reuse at 80% or higher. Metadata reuse is frequent for basic bibliographic properties (e.g., author, title, subject), although it is limited or absent for more complex scientific properties (e.g., taxonomic, spatial, and temporal information). This paper provides background context, reports the research approach and findings. Research implications and system design priorities that may contribute to metadata capital are also considered.

Generating metadata for cyberlearning resources through information retrieval and meta-search

Abstract: The goal of this study was to propose novel cyberlearning resource-based scientific referential metadata for an assortment of publications and scientific topics, in order to enhance the learning experiences of students and scholars in a cyberinfrastructure-enabled learning environment. By using information retrieval and meta-search approaches, different types of referential metadata, such as related Wikipedia pages, data sets, source code, video lectures, presentation slides, and (online) tutorials for scientific publications and scientific topics will be automatically retrieved, associated, and ranked. In order to test our method of automatic cyberlearning referential metadata generation, we designed a user experiment to validate the quality of the metadata for each scientific keyword and publication and resource-ranking algorithm. Evaluation results show that the cyberlearning referential metadata retrieved via meta-search and statistical relevance ranking can help students better understand the essence of scientific keywords and publications.

A system and method linking building information modeling and enterprise resource planning

Abstract: An electronic construction collaboration system for managing a construction project is provided. The electronic construction collaboration system includes an Enterprise Resource Planning (ERP) sub-system including a contract engine configured to generate at least one project contract including a contract data set and ERP metadata corresponding to Building Information Modeling (BIM) metadata included in a structural object of a construction project model in a BIM sub-system and an interconnection engine configured to associatively link the ERP metadata and the BIM metadata and send the contract data set to the BIM sub-system in response to associatively linking the ERP metadata and the BIM metadata.

Object oriented data and metadata based search

Abstract: An object oriented search mechanism extracts structural metadata and data based on type of document contents and data sources connected to the documents Relationships between textual and non-textual elements within documents as well as metadata associated with the elements and data sources are utilized to generate a unified object model with the addition of semantic information derived from metadata and taxonomy, which are used to enhance search indexing, ranking of search results, and dynamic adjustment of result rendering user interface with fine tuned relevancy Additional data from data sources connected to the documents may also be used to unlock hidden data such as data that has been filtered out in an original document

Computer implemented methods and apparatus for determining user access to custom metadata

Abstract: Disclosed are methods, apparatus, systems, and computer-readable storage media for determining user access to custom metadata. In some implementations, a server receives a request by or on behalf of a first user of a computing environment for a first custom metadata entity. A custom metadata entity may be a metadata component customized for use in the computing environment and having an entity type specifying a class or a category of the metadata component. The server may identify an association record indicating that the first user has permission to access the requested custom metadata entity. In some implementations, the association records are stored in an association database accessible by the server, wherein each association record identifies a user and a custom metadata entity. The server may also provide data including the requested custom metadata entity to a computing device.

A collaborative approach for metadata management for Internet of Things: Linking micro tasks with physical objects

Abstract: There has been considerable efforts in modelling the semantics of Internet of Things and their specific context. Acquiring and managing metadata related to the physical devices and their surrounding environment becomes challenging due to the dynamic nature of environment. This paper focuses on managing metadata for Internet of Things with the help of crowds. Specifically, the paper proposes a collaborative approach for collecting and maintaining metadata through micro tasks that can be performed using variety of platforms e.g. mobiles, laptops, kiosks, etc. The approach allows non-experts to contribute towards metadata management through micro tasks, therefore resulting in reduced cost and time. Applicability of the proposed approach is demonstrated through a use case implementation for managing sensor metadata for energy management in small buildings.

How portable are the metadata standards for scientific data? a proposal for a metadata infrastructure

Abstract: The one-covers-all approach in current metadata standards for scientific data has serious limitations in keeping up with the ever-growing data. This paper reports the findings from a survey to metadata standards in the scientific data domain and argues for the need for a metadata infrastructure. The survey collected 4400+ unique elements from 16 standards and categorized these elements into 9 categories. Findings from the data included that the highest counts of element occurred in the descriptive category and many of them overlapped with DC elements. This pattern also repeated in the elements co-occurred in different standards. A small number of semantically general elements appeared across the largest numbers of standards while the rest of the element co-occurrences formed a long tail with a wide range of specific semantics. The paper discussed implications of the findings in the context of metadata portability and infrastructure and pointed out that large, complex standards and widely varied naming practices are the major hurdles for building a metadata infrastructure.

AssocGEN: Engine for analyzing metadata based associations in digital evidence

Abstract: Traditionally, sources of digital evidence are analyzed by individually examining the various artifacts contained therein and using the artifact metadata to validate authenticity and sequence them. However, when artifacts from forensic images, folders, log files, and network packet dumps have to be analyzed, the examination of the artifacts and the metadata in isolation presents a significant challenge. Ideally, when a source is examined, it is a valuable task to determine correlations between the artifacts and group the related artifacts. Such a grouping can simplify the task of analysis by minimizing the need for human intervention. By virtue of the value that metadata bring to an investigation and its ubiquitous nature, metadata based associations is the first step in realizing such correlations automatically during analysis. In this paper, we present the AssocGEN analysis engine which uses the metadata to determine associations between artifacts that belong to files, logs and network packet dumps, and identifies metadata associations to group the related artifacts. A metadata association can represent any type of value match 1 or relationship that is deemed relevant in the context of an investigation. We have conducted preliminary evaluation of AssocGEN on the classical ownership problem to highlight the benefits of incorporating this

Metadata driven software architecture

Abstract: Embodiments of the present invention provide a metadata-driven software architecture that enables multi-tenant application development. Specifically, an application development architecture is provided including a data table that stores the application-accessible data that maps to all custom objects and their fields, as defined by metadata in objects and fields. Forms, reports, work flows, user access privileges, tenant-specific customizations and business logic, and definitions of underlying data tables and indexes exist as metadata. Application components are generated at runtime using the metadata.

Efficiently storing and retrieving data and metadata

Abstract: For efficiently storing and retrieving data and metadata in phases, in a first phase, metadata tokens, which are assigned to most active metadata-emitting entities, are used for storing the data and the metadata together in a single input/output operation while piggybacking the metadata of least active metadata-emitting entities onto one of the most active metadata-emitting entities having one of the metadata tokens. In a second phase, the metadata is re-written to a metadata delta journal for reclaiming the metadata tokens. In a third phase, the metadata journal is applied to a metadata structure containing the metadata of the storage system, the metadata delta journal is then cleared after successfully updating the main metadata structure with the metadata of the metadata journal. The metadata journal is swapped with an empty metadata journal for concurrently adding metadata while retaining the metadata journal until applying the metadata delta journal to the metadata structure.

Importing and Exporting Custom Metadata for a Media Asset

Abstract: In some implementations, metadata for a media asset can be imported to and/or exported from a media editing application. The metadata can include metadata fields that are predefined for the media editing application. The metadata can include metadata fields that are custom or user-defined or user-generated data fields. Graphical user interfaces of the media editing application can provide mechanisms to allow a user to define new metadata fields. Graphical user interfaces of the media editing application can provide mechanisms to allow a user to view imported metadata fields that were defined externally to the media editing application.

A Hierarchy of Metadata Elements for Business Intelligence Information Resource Retrieval

Abstract: Effectively managing information resources is an important activity contributing to the competitive advantage of modern organizations. Organizational knowledge workers must be able to search for pertinent information quickly and effectively. This research identifies the relative usefulness of the metadata elements associated with the Dublin Core metadata standard for the effective retrieval of three different information resources-structured business intelligence reports, structured spreadsheet reports, and unstructured reports in formats such as Word and PowerPoint. A survey of knowledge workers was conducted to determine the relative usefulness of the metadata elements for each of the three information resources and to develop a framework outlining where metadata tag requirements differ between such resources. Overall, the study and resulting framework emphasize the need for system developers and database management personnel to be cognizant of the type of information resources being used, and ensure that search metadata elements that are appropriate for these specific resources are in place.

Metadata manager for analytics system

Abstract: A metadata management system receives metadata changes and automatically updates a metadata architecture which maps the data. The metadata changes may be received through a simple user interface by a user or administrator. Once received, the system may automatically update schemas and data transformation code to process data according to the new data mapping preference. The system may handle metadata updates in a multi-tenant system having one or more applications per tenant, and may update data for a single tenant and 1 or more tenant applications in a multitenancy.

Metadata Analysis at the Command-Line

Abstract: This article discusses metadata analysis tools, processes, and methodologies aimed at helping to focus limited quality control resources on the areas of the collection where they might have the most benefit.