Abstract: According to some embodiments, a method and apparatus are provided to receive an indication of data corrections to a database and receive an indication that the data corrections to the database were verified. A first amount of points to award to a first user associated with the data corrections and a second amount of points to award to a second user associated with the verification of the data corrections is determined. The first amount of points is awarded to the first user and the second amount of points is awarded to the second user.

Abstract: A method for refining data discrepancies in data loads from multiple data stores includes receiving a data set containing data records from one or more data sources, comparing the received data set with a prior data set to identify delta records among corresponding records of the received and the prior data sets, recalculating a best record for data located in each of the corresponding delta records, and if a discrepancy exists in a data value for corresponding delta records, executing a refinement action rule. The refinement action rule includes at least one replace statement and search criteria. The method also includes capturing a user's interaction with a user interface presenting the data set, and storing the interaction in a data store as a refinement action rule. A system for implementing the method and a computer readable medium are also described.

Abstract: A method for refining data discrepancies in data loads from multiple data stores includes receiving a data set containing data records from one or more data sources, comparing the received data set with a prior data set to identify delta records among corresponding records of the received and the prior data sets, recalculating a best record for data located in each of the corresponding delta records, and if a discrepancy exists in a data value for corresponding delta records, executing a refinement action rule. The refinement action rule includes at least one replace statement and search criteria. The method also includes capturing a user's interaction with a user interface presenting the data set, and storing the interaction in a data store as a refinement action rule. A system for implementing the method and a computer readable medium are also described.

Abstract: A latch device is provided with a driver and a shadow latch. The driver has an input to accept a binary driver input signal, an input to accept a clock signal, and an input to accept a shadow-Q signal. The driver has an output to supply a binary Q signal equal to the inverse of the driver input signal, in response to the driver input signal, the shadow-Q signal, and the clock signal. The shadow latch has an input to accept the driver input signal, and an input to accept the clock signal. The shadow latch has an output to supply the shadow-Q signal equal to the inverted Q signal, in response to the driver input signal and clock signal.

Abstract: A latch device is provided with a relay and a shadow latch. The relay has an input to accept a binary relay input signal, an input to accept a clock signal, an input to accept a shadow-Q signal, and an output to supply a binary Q signal value equal to the relay input signal value. The relay output is supplied in response to the relay input signal, the shadow-Q signal, and the clock signal. The shadow latch has an input to accept the relay input signal, an input to accept the clock signal, and an output to supply the shadow-Q signal with a value equal to an inverted Q signal value. The shadow latch output is supplied in response to the relay input signal and clock signal.

Abstract: A system and method for providing collaborative master data process management. A master data store comprises data for at least one data domain. A master data management module is configured to provide access to the data to one or more applications. A master data management service module provides at least one service providing access to the data based on a service-oriented architecture. A business process management module is configured to generate, execute and manage at least one business process related to the data domain. The at least one business process uses at least one of the at least one service provided by the master data management service module. A master data process module is configured to generate at least one data process comprising a business process involving an operation on the data.

Abstract: According to some embodiments, a central hub may establish a preference profile associated with a user, and the preference profile may include, for example at least some information not provided by the user. Catalogue data may then be exchanged between the central hub and a first and second retailer that store product information in association with a enterprise data management systems. The central hub may receive user information associated with the user (including location information) from a remote user device. Based on (i) the user information, (ii) the catalogue data from the first and second retailers, and (iii) a set of business rules established at the central hub, an offer may be selected and information about the selected offer may be transmitted to the remote user device.

Abstract: According to some embodiments, a plurality of input records may be received from a plurality of sources, and each input record may include a plurality of fields. It may then be detected that a set of input records from different sources are related to each other (e.g., are duplicates). One of the set of input records may be automatically selected as a master record in accordance with a record level rule. At least one field in the master record may, according to some embodiments, be automatically modified based on a corresponding field in another input record in accordance with a field level rule. The modified master record could then be stored for subsequent use by other applications.

Abstract: A system and method for providing semantic access of data in a master data management system. Data stored in a dynamic repository schema is exposed in a semantically accurate format. The schema is determined from information received from the master data management system describing the schema. A set of database views is generated based on said schema. A query from an external application in a standard query language is received and the query is performed using at least one database view. The database views are updated when a schema change is detected.

Abstract: According to some embodiments, a plurality of input records may be received from a plurality of sources, and each input record may include a plurality of fields. It may then be detected that a set of input records from different sources are related to each other (e.g., are duplicates). One of the set of input records may be automatically selected as a master record in accordance with a record level rule. At least one field in the master record may, according to some embodiments, be automatically modified based on a corresponding field in another input record in accordance with a field level rule. The modified master record could then be stored for subsequent use by other applications.

Abstract: A system and method for providing collaborative master data process management. A master data store comprises data for at least one data domain. A master data management module is configured to provide access to the data to one or more applications. A master data management service module provides at least one service providing access to the data based on a service-oriented architecture. A business process management module is configured to generate, execute and manage at least one business process related to the data domain. The at least one business process uses at least one of the at least one service provided by the master data management service module. A master data process module is configured to generate at least one data process comprising a business process involving an operation on the data.

Abstract: A schema modeler for generating an efficient database schema. Provides intelligent choices for schema structure, generates efficient schemas while minimizing the amount of experience required by a database designer. Architectural elements of a schema design are proposed based on field inputs such as field type or relationship. Schema information is manually entered or imported. Configured for structural compatibility and semantic compatibility checking on fields and relationships for data integrity due to nested structure denormalization, inspection of lookup tables that can hold an unlimited number of records, inspection of taxonomy defined on a non-main table, and inspection of the schema for the existence of a main table. Provide suggested field types or schema structures that allow for a more efficient schema to be generated. Field types may include qualifier, multi-lingual, calculation and may include family or attribute table suggestions as well.

Abstract: Enables a database generator interface configured to map complex constructs and semantics so internal complexities are hidden while providing efficient internal storage and speed. Extracts and analyzes complex relationships in database and exposes schema as XSD to allow for external interfacing. Presents a list of tables and fields that exist in database and accepts user input to determine which tables and fields to create an interface for. Lookup fields are listed which allow for user input for specifying which fields to create XSD enumeration lists for. The generated XSD file may be saved and utilized by other mapping tools to allow for interfacing with other databases. Mapping the schema of a extended SQL database allows for users with limited understanding of the internals of the extended SQL database to connect the database to other systems using commonly available tools. May be coupled with web services to provide universal access.

Abstract: A data generator for database schema verification, system sizing and functional test of data dependent applications. Allows for generation of data from random values or from working databases which may be profiled to generate patterns for occurrences of values and sizes of values. The data may be filled with a fill rate that dictates the percentage of fields assigned nulls. Cardinality allows for a fixed number of values to occur across the records for a field. May utilize reference data associated with an existing database to fill fields. Qualifiers and multi-value fields may be filled to mimic real data. Maximum, nominal and average number of occurrences of sizes of data and qualifiers and multi-value data may be specified. May also utilize dictionaries to fill. Hierarchical levels and number of child nodes may also be specified and used in filling taxonomy tables and hierarchy tables for example.

Abstract: A system and method for providing semantic access of data in a master data management system. Data stored in a dynamic repository schema is exposed in a semantically accurate format. The schema is determined from information received from the master data management system describing the schema. A set of database views is generated based on said schema. A query from an external application in a standard query language is received and the query is performed using at least one database view. The database views are updated when a schema change is detected.

Abstract: A user interface for parsing unstructured data using pattern recognition. The patterns used in parsing data are formed from regular expressions. The parsed data may be displayed in a first format and unmatched strings in the unstructured text may be displayed in a second format. A format may comprise a desired color, font or any other user interface parameter. In addition, the data that parses according to a pattern may be placed in a column associated with the pattern in a tabular user interface, for example a spreadsheet like Excel™. Associating a pattern with a position to display successful matches in allows for breaking unstructured text into pieces associated with a particular field or column. Modification of the patterns allows for more and more of the unstructured text to match the patterns and when the data has been parsed to the desired level, the data may be imported into a database.

Abstract: A data generator for database schema verification, system sizing and functional test of data dependent applications. Allows for generation of data from random values or from working databases which may be profiled to generate patterns for occurrences of values and sizes of values. The data may be filled with a fill rate that dictates the percentage of fields assigned nulls. Cardinality allows for a fixed number of values to occur across the records for a field. May utilize reference data associated with an existing database to fill fields. Qualifiers and multi-value fields may be filled to mimic real data. Maximum, nominal and average number of occurrences of sizes of data and qualifiers and multi-value data may be specified. May also utilize dictionaries to fill. Hierarchical levels and number of child nodes may also be specified and used in filling taxonomy tables and hierarchy tables for example.

Abstract: A method for metadata verification of a data repository of a computer system is described comprising accessing a data repository through a data profiler program, querying the data repository for metadata information about the data repository, presenting statistics regarding the metadata information using the profiler, analyzing the metadata information to identify suspect metadata information from the data repository and presenting the suspect metadata information for inspection using the profiler.

Abstract: Embodiments of the invention provide an accelerated system and methods for gathering business information, augmenting that information to conform to requirements for sharing the information and for synchronizing, managing and publishing the information across the supply chain. Through use of a control module business information is gathered from a variety of enterprise wide systems and stored via an acceleration engine. After augmenting and/or altering the information to conform to the requirements of a desired repository of information known as a data pool, the information is published to the data pool and registered by the data pool with a registry for looking up the published information. One or more embodiments of the invention allow for the rapid publication and modification of publication related data using advanced querying mechanisms of the acceleration engine.

Abstract: A data generator for database schema verification, system sizing and functional test of data dependent applications. Allows for generation of data from random values or from working databases which may be profiled to generate patterns for occurrences of values and sizes of values. The data may be filled with a fill rate that dictates the percentage of fields assigned nulls. Cardinality allows for a fixed number of values to occur across the records for a field. May utilize reference data associated with an existing database to fill fields. Qualifiers and multi-value fields may be filled to mimic real data. Maximum, nominal and average number of occurrences of sizes of data and qualifiers and multi-value data may be specified. May also utilize dictionaries to fill. Hierarchical levels and number of child nodes may also be specified and used in filling taxonomy tables and hierarchy tables for example.