Abstract: System and method for performing Unicode matching for comparing and merging similar data objects having Unicode strings that are equivalent yet not exact matches. Unicode characters are characterized by number of strokes, stroke order, radicals, geometry, phonemes in association with input method editor and keyboard characteristics such as location of a character on an IME or keyboard (or number of GUI interface interactions used in entering the character, e.g., via tapping where “a” on a mobile device keyboard takes 1 tap of a key, “b” takes 2 taps). These characteristics associated with code points and IME's/keyboards are utilized to create subdomains for matching and determining “distance” to other Unicode code points (e.g., number of keyboard keys away). Allows for determining whether close, yet incorrect data entry may have taken place. Enables merging of duplicate data objects into master data object where minor differences or spelling errors introduce actually represent duplicate data.

Abstract: A system and method for automation of consistent lock management, wherein a shared resource is accessed through an accessor object. An accessor object class includes at least one const read access function and one write access function. A const accessor object is received for read-only access of a shared resource. The compiler is enlisted to enforce lock selection.

Abstract: A system and method for on-demand indexing in a data management system is described. An index is generated when it is requested, such as when a database operation requires access to the index. If the index is loaded in memory, the index is retrieved from memory. Otherwise, the index is generated on-demand. A priority configuration identifies at least one priority index which is generated and loaded in memory. The priority configuration can identify priority indexes either directly or indirectly, such as by a threshold parameter.

Abstract: A system and method for automation of consistent lock management, wherein a shared resource is accessed through an accessor object. An accessor object class includes at least one const read access function and one write access function. A const accessor object is received for read-only access of a shared resource. The compiler is enlisted to enforce lock selection.

Abstract: One or more embodiments of the invention enable a user to search for at least one value in layers of audience specific data comprising language, regional, regulatory and/or cultural specific values per layer. The word “audience” for the purposes of this specification means a group of document consumers such as people or computers that are associated with a language, country, region, regulation or culture. A search utilizing at least one embodiment of the invention occurs with respect to data that makes use of rule-based inheritance. For a three level inheritance embodiment, there are 8 permutations involving a NULL value in at least one of the layers, instead of making the user calculate the proper mask, the Current Audience Layer mask can be logical ORed with the Primary Audience Layer Mask or the Secondary Audience Layer Mask in order to create the desired search combination.

Abstract: A system and method for on-demand indexing in a data management system is described. An index is generated when it is requested, such as when a database operation requires access to the index. If the index is loaded in memory, the index is retrieved from memory. Otherwise, the index is generated on-demand. A priority configuration identifies at least one priority index which is generated and loaded in memory. The priority configuration can identify priority indexes either directly or indirectly, such as by a threshold parameter.

Abstract: A method for performing expression-based validation with records in a computer system database, eliminating the need to write programs or scripts. A validation expression can define complex intra-record tests and inter-record tests and may be performed manually against one or more records and have a success or failure indicated for each record in an interface. A validation expression may be placed into one or more groups and performed as a group with the success or failure indicated for each record. A validation expression may be initiated from workflows to implement a business process with system-enforced data integrity. A validation expression may be manually executed or automatically executed when attempting record update to prevent the entry of invalid data and ensure data integrity. A validation expression may also be used to search using the Boolean result of validation expressions.

Abstract: Expression-based data may comprise data that is processed by a validation expression for example. After a validation expression is created it may then be performed with respect to one or more data values or data records. A validation expression returns a Boolean result that signifies a success or failure result. A validation expression can define complex intra-record tests and inter-record tests with unlimited complexity. In order to improve processing of validations, the system uses virtual data known as calculation fields. Calculation fields are stored in memory at runtime and not in a database thereby eliminating the necessity of selecting and updating records in the database. A dirty bit identifying fields and attributes that need to be calculated based on a dependent data may be used to defer calculation to a later time when the calculation field is displayed or a sort operation occurs for example.

Abstract: One or more embodiments of the invention enable a user to create multiple non-redundant views using metadata targeted at a specific audience that comprises language, regional, regulatory and/or cultural specific values. The word “audience” for the purposes of this specification means a group of document consumers such as people or computers that are associated with a language, country, region, regulation or culture. Audience specific data therefore is data targeted at a specific audience and audience specific metadata is related to the descriptive information related to the data, such as a table name or a field name for example. At least one embodiment of the invention makes use of rule-based inheritance in providing metadata values via layers that comprise audience specific data.

Abstract: Enables locating and merging potential data record matches. Enables locating duplicates through the definition of matching strategies. Each strategy may include transformations, matching rules and scoring thresholds to implement fuzzy matches that match closely related data records that are not exact matches. Performing a search allows for narrowing down the records to a desired set on which to apply a given matching strategy. Merging is performed on the potential duplicates thus located to consolidate data and remove duplicates. By narrowing down the records to a closely related set via a search, merging is simplified to work on a small number of closely related records, thus simplifying the process. The total matching score obtained via execution of match strategies may be utilized to determine which potential record(s) to merge for example. May utilize past user input to provide intelligent inputs for rules, tokens, weights, fields, parameters or any other past user input.

Abstract: Audience specific document targeted at a particular media type are generated by accessing data from an audience hierarchy. When obtaining a data value for a particular audience, if that value does not exist for that audience then the audience hierarchy may be utilized to find the data value for an inherited audience. By adding regional, cultural or regulatory subdivisions within the audience hierarchy and inheriting large portions of existing audience specific data entries, a large number of audience specific documents may be generated with a minimal amount of data entry required. Audiences may be specified in a given order for traversal within the hierarchy and displayed in a data entry and editing application utilizing visual characteristics to inform a user if the value for a particular piece of data is inherited from another layer or utilized from the particular layer in use. Audience specific documents may be masked and accessed by payment.

Abstract: One or more embodiments of invention are directed to a multi-layered data model for generating audience-specific documents will now be described. The invention is used in the context of generating a document such as a catalog or web page for publication across regions and cultures comprising multiple languages. It allows users to rapidly generate multi-language, multi-culture and multi-region documents since fields flagged as multi-lingual may utilize existing buckets that comprise pre-filled multi-language, multi-culture and multi-region values without requiring the user to specify every multi-value when creating a record.

Abstract: System and method for performing Unicode matching for comparing and merging similar data objects having Unicode strings that are equivalent yet not exact matches. Unicode characters are characterized by number of strokes, stroke order, radicals, geometry, phonemes in association with input method editor and keyboard characteristics such as location of a character on an IME or keyboard (or number of GUI interface interactions used in entering the character, e.g., via tapping where “a” on a mobile device keyboard takes 1 tap of a key, “b” takes 2 taps). These characteristics associated with code points and IME's/keyboards are utilized to create subdomains for matching and determining “distance” to other Unicode code points (e.g., number of keyboard keys away). Allows for determining whether close, yet incorrect data entry may have taken place. Enables merging of duplicate data objects into master data object where minor differences or spelling errors introduce actually represent duplicate data.

Abstract: An interface for indicating the presence of inherited values in a document. The interface enables a user to rapidly determine if an audience specific document conforms to the expectations or requirements of an intended audience. The interface distinguishes between current, primary and secondary audience layer values through the use of color or any other mechanism that allows a user to quickly identify data that is missing and needs to be populated, changed or remain unchanged if the inherited data is suitable for the given audience. Using the interface, users can determine at a glance what information is inherited and what level of inheritance that information is from. Before generating an audience specific document targeted at a particular media type, an audience hierarchy may be created and utilized for entry and edit of data for a desired audience.