199 results about "Metadata repository" patented technology

A metadata repository for use in an integrated development environment is provided. The metadata repository is layered to define levels of common behaviour useful to different types of application development tools. The most general use tools have access to metadata at the level of simple constructed types; more specialised tools have access to components that contain properties of a target language; highly specialised tools have access to composed partitionable part metadata that can be used for constructing distributed applications.

The present invention provides a system, method and software for linking persistent and unique business identifiers, associated with business entities, for associating corresponding business records without a loss of historical records, regardless of subsequent changes, updates, and mergers. In the various embodiments, a first business record, of the plurality of business records, is associated with a first business identifier; and a second business record, which does not match the first record, is associated with a second business identifier. Subsequently, when the first business identifier and the second business identifier are determined to correspond to a singular business entity, the first business identifier and the second business identifier are linked, and respective associations of the first business record and the second business record with the linked first business identifier and second business identifier are maintained, with corresponding source references, and collectively utilized in subsequent search and match determinations.

A harvester is disclosed for harvesting metadata of managed objects (files and directories) across file systems which are generally not interoperable in an enterprise environment. Harvested metadata may include 1) file system attributes such as size, owner, recency; 2) content-specific attributes such as the presence or absence of various keywords (or combinations of keywords) within documents as well as concepts comprised of natural language entities; 3) synthetic attributes such as mathematical checksums or hashes of file contents; and 4) high-level semantic attributes that serve to classify and categorize files and documents. The classification itself can trigger an action in compliance with a policy rule. Harvested metadata are stored in a metadata repository to facilitate the automated or semi-automated application of policies.

Disclosed is a method, system, and program for searching a data repository managed by a content provider to gather indexable metadata on content at addresses locations at the data repository. Settings capable of being customized by the content provider are accessed. The customized settings provide instructions on how to search the content provider's data repository. The content of content pages at the content provider's data repository is accessed in accordance with instructions included in the accessed customized settings. Metadata from accessed content pages is generated and added to an index of metadata for accessed addressable locations at the data repository.

A method and apparatus for obtaining metadata from multiple information sources in real time are described. According to one aspect, the method includes receiving a user request pertaining to one or more of source metadata objects residing in multiple source metadata repositories. Each source metadata repository is maintained by a specific data management application. The method further includes responding to the user request in real time by identifying a data management application that corresponds to the source metadata objects associated with the user request and retrieving the source metadata objects using an application program interface (API) with the corresponding data management application.

The present invention discloses systems and methods for automating the EII, using a smart integration engine based on metadata. On-line execution (i.e. data access, retrieval, or update) is automated by integrating heterogeneous data sources via a centralized smart engine based on metadata of all data sources managed in a metadata repository. The data-source assets are mapped to business metadata (terminology) giving programmers the ability to use business terms, and overcome technical terms. IT departments can use the business-level terms for easy and fast programming of all services “at the business level”. The integration is performed by the engine (via pre-configuration) automatically, dynamically, and on-line, regardless of topology or technology changes, without user or administrator intervention. MDOA is a high-level concept in which the metadata maps the technical low-level terms to business high-level terms. MDOA is used for seamless integration of a fully-distributed organization with many data sources and technologies.

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.

A computer program product is provided as a business rating system to rank business that are relevant to a given Internet search topic. Business ratings are stored in a ranking repository that can be optionally searched by the user along with a user-defined search engine query. The business ratings are compiled from on-line questionnaires attached to the search engine results and / or on-line surveys obtained through other web based rating services. The business ratings assess the quality of the businesses in terms of “interactive” criteria such as customer satisfaction, professionalism, and cost and ease of use of the businesses' products or services. The business rating system is comprised of an on-line indexing engine, a query transformer, a search results transformer, a ranking based result sorter, an on-line ranking system, a metadata repository, and an on-line ranking repository. The business rating system integrates the ratings with the search results, and ranks the search results based on such business ratings. In this manner, the user of a search engine receives feedback from other users about businesses of interest. Eventually, businesses with higher ratings will be ranked at the top of the search list, while business with lower ratings will be ranked lower.

An Internet-scale file sharing system includes a client-side file sharing application that allows file-sharing users to identify files to share and transmit metadata corresponding to those files to a metadata repository. A server-side application operating on the metadata repository tracks metadata received from associated file-sharing users, as well as metadata from other affiliated metadata repositories. Each metadata repository acts as a search engine for any querying users and can provide search results based on locally stored metadata alone. Each metadata repository may additionally choose to locally-store popular files from an associated file-sharing user so as to alleviate transmission burdens on that file-sharing user. Associated metadata repositories each periodically synchronize their stored metadata so that all metadata repositories may generate similar search results. In such manner, file-sharing queries need only be performed by the metadata repository receiving the query, and not by all associated metadata repositories.

A method for turning variable-length file path names into fixed-length object identifiers in a data repository, the method comprising, assigning a fixed-value identifier to a file system in the data repository, computing a first deterministic pseudo-random function that combines a first component of a plurality of file system pathname components associated with a file with the fixed-value identifier, computing a second determininstic pseudo-random function that combines a second component of the plurality of file system pathname components with the result of the first function, and using at least one of the computed deterministic pseudo-random functions to produce a fixed-length object identifier for the file.

The present invention is generally directed to a system, method and article of manufacture for accessing data represented abstractly through an abstraction model. In one embodiment, a data repository abstraction layer provides a logical view of an underlying data repository that is independent of the particular manner of data representation. A query abstraction layer is also provided and is based on the data repository abstraction layer. A runtime component performs conversion of an abstract query (i.e., a request for results or a request to modify data) into a form that can be used against a particular physical data representation. Abstract and / or physical queries are transformed according to model entities which define a relationship between logical fields of the data repository abstraction layer.

A method, system and article of manufacture for architecting a relationship between different representations of data. One embodiment provides a method of architecting a relationship between a first physical representation of data and a second physical representation of the data. The method comprises mapping the first physical representation to a logical model abstractly describing the second physical representation.

A system, apparatus, and method are provided for entitlement security and control. According to one embodiment, an entitlement request is received from a user seeking entitlement permission, the entitlement request is matched against entitlement rules and roles that are retrieved from a metadata repository, and the entitlement permission is granted if the entitlement request satisfies the entitlement rules and roles.

A method, apparatus, and a computer program product for storing and accessing multi-tenancy data. The method includes the steps of: creating a plurality of table sets in one or more databases, wherein each table set is used to store data of a group of tenants selected from a plurality of tenants; accessing data of a tenant in a table set in response to receiving a data access request from the tenant; and recording relationships between the tenants and the table sets in a multi-tenancy metadata repository, wherein the step of accessing the data of the tenant comprises the steps of finding the table set by querying the metadata repository and accessing the data of the tenant in the table set based on the result received from the query of the metadata repository.

Methods, systems, and computer program products for ensuring data quality and integrity of a data set derived from a data source are described. The data source may be one or more data repositories or data warehouses, or one or more transaction systems. Data from the data source may be stored in a staging area. A data repository is built using the data. The data repository comprises a data structure that forms a model of the data from the data source. The building step involves applying business rules from a rules database to the data. The business rules are dependent upon meta data. The building step further involves detecting any errors in the data and storing data satisfying the business rules in the data repository. A log of any detected errors may be maintained in the data repository.

Systems and methods are disclosed for reporting customer feedback. The disclosed systems and methods may include extracting data in response to content selections by the customer, wherein the extracted data indicates customer preference data based on a content selection. Furthermore, the disclosed systems and methods may include storing the extracted data into a data repository and categorizing the extracted data for use by the content operator. Moreover, the disclosed systems and methods may include receiving a query requesting categorized data from the data repository and reporting the categorized data to the content operator.

A metadata management system for importing, integrating and federating metadata, including a configurable metamodel, a metadata repository for storing metadata whose structure reflects the metamodel, at least one external metadata source, which is able to persist metadata in accordance with the structure of a meta-schema, a mapping module for mapping the meta-schema to the metamodel, and a transformation module, operatively coupled to the metadata mapping module, for translating specific metadata from the at least one external metadata source to the metadata repository, for use in import, export or synchronization of metadata between the external metadata source and the metadata repository. A method and a computer-readable storage medium are also described.

Systems, methods and computer program products for distributed content storage and management are provided. The distributed content storage and management system includes an indexed archive system; information source agents, information source clients; and a network to couple the information source clients to the indexed archive system. In an alternate embodiment, a legacy back-up system is also used. The index archive system includes an information entryway for gathering file information, a triage engine, an indexing engine, a metadata engine, and a content engine. These engines generate content indexes, metadata and metadata indexes from received files and store them along with the file content into a set of repositories, including an indexing repository, a metadata repository and a content repository. Methods are provided for the efficient retrieval and indexing of files, and for the storage of files, file content, content indexes, metadata and metadata indexes.

A method by which more than one client program connected to a network stores the same data item at the same location or locations in a data repository connected to the network, the method comprising having a first client program deposit a first data item in a data repository, the depositing including determining a digital fingerprint from the data item using a reproducible pseudorandom process that produces digital fingerprints having a pseudorandom distribution, storing the data item in the data repository at a location or locations associated with the digital fingerprint, and associating a deletion permission token with the data item, and storing this association in the data repository, having a second client program initiate a process for depositing a second data item in the data repository, wherein the second data item is identical to the data item stored by the first client program, the process including determining a digital fingerprint from the second data item using the reproducible pseudorandom process, determining from the digital fingerprint that a data item identical to the second data item is already stored in the data repository, relying on the data item already stored in the data repository for storage of the second data item rather than storing a separate copy of the second data item, and associating a second deletion permission token with the data item already stored, and storing this association in the data repository, having a client program initiate a process for deleting the data item already stored in the repository, wherein a deletion permission token associated with the data item is deleted from the repository, but the data item itself is not deleted.

An Internet-scale file sharing system includes a client-side file sharing application that allows file-sharing users to identify files to share and transmit metadata corresponding to those files to a metadata repository. A server-side application operating on the metadata repository tracks metadata received from associated file-sharing users, as well as metadata from other affiliated metadata repositories. Each metadata repository acts as a search engine for any querying users and can provide search results based on locally stored metadata alone. Each metadata repository may additionally choose to locally-store popular files from an associated file-sharing user so as to alleviate transmission burdens on that file-sharing user. Associated metadata repositories each periodically synchronize their stored metadata so that all metadata repositories may generate similar search results. In such manner, file-sharing queries need only be performed by the metadata repository receiving the query, and not by all associated metadata repositories.

A computer-implemented method for processing information includes collecting data objects from one or more data repositories, the data objects having respective properties, which identify the data objects. The properties of the collected data objects are analyzed in order to derive respective identifiers corresponding to the data objects. A text string that matches one of the identifiers of a data object is identified within a context in a document. Responsively to the context, an indication that the identified text string is a valid instance of the data object is generated, and the document is processed responsively to the indication.

Embodiments of the invention are generally related to semantic search and service metadata repositories, particularly with regards to methods and systems for performing a semantic asset search in a service metadata repository. One embodiment includes identifying service metadata assets with similar metadata, relationships, and categorizations to the service metadata assets with the most relevant keywords and identifying service metadata assets have been used in conjunction with the one or more selected service metadata assets.

A harvester is disclosed for harvesting metadata of managed objects (files and directories) across file systems which are generally not interoperable in an enterprise environment. Harvested metadata may include 1) file system attributes such as size, owner, recency; 2) content-specific attributes such as the presence or absence of various keywords (or combinations of keywords) within documents as well as concepts comprised of natural language entities; 3) synthetic attributes such as mathematical checksums or hashes of file contents; and 4) high-level semantic attributes that serve to classify and categorize files and documents. The classification itself can trigger an action in compliance with a policy rule. Harvested metadata are stored in a metadata repository to facilitate the automated or semi-automated application of policies.

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.

Heterogeneous data at a plurality of remote nodes is accessed automatically in parallel at high speed from a user site using a simple script request containing a data source object name wherein the heterogeneous data is treated as a single data source object, the script further containing code representing a user-defined program to be executed on the data source object. The user-defined program may be represented by an embedded script, a user-defined script or an executable program designation. A user site agent breaks the user-generated script into new scripts appropriate for execution at the remote nodes. A messenger process transmits the new scripts to the appropriate remote nodes where respective agent processes respond to automatically access the appropriate data and to automatically execute the specified program. If the program is a user-defined script or executable, the respective agent processes access a metadata repository to obtain the specified program.