Browse Prior Art Database

Controlling Progression Of Reference Data Set Versions

IP.com Disclosure Number: IPCOM000239375D
Publication Date: 2014-Nov-03
Document File: 4 page(s) / 66K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system is disclosed for controlling progression of versions of one or more reference data sets throughout a life cycle of the reference data set. The progression of versions is based on relationships and dependencies between the versions of the one or more reference data sets.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 4

Controlling Progression Of Reference Data Set Versions

Reference data is a special class of metadata that is used to categorize other data present in an enterprise and that is referenced across multiple systems. A reference data set is a collection of reference data. If two reference data sets that need to be changed at the same time are related, then coordination of the changes is required. Similarly, dependencies are introduced in related reference data sets that make it difficult to know when it is appropriate to approve changes in one reference data set. For instance, it may not be appropriate to approve and publish a reference data set that is dependent on another reference data set until the other reference data set is approved.

Disclosed is a method and system for controlled progression of versions of one or more reference data sets throughout a life cycle of each reference data set. The progression of versions is based on relationships and dependencies between the versions of the one or more reference data sets.

A reference data set may be present in one or more versions, which may include reference data values. The one or more versions of the reference data set differ from each other through one or more of, but not limited to, a difference operation, an addition operation and an update operation.

In an embodiment of the present invention, two reference data set versions may be related to each other through an attribute value relationship in which a version being referenced is controlled by current version logic. For example, a relationship between a reference data set City and a reference data set Country may be defined over a current version of the reference data set Country. Thus, when a user tries to pick a value for a Country attribute of the reference data set City, the user may be presented with values only from the current version of the reference data set Country. The current version may be computed by monitoring one or more of an effective timestamp, an expiry timestamp and a last modified timestamp across one or more versions of a reference data set.

The disclosed method and system utilizes two or more levels within a state machine to coordinate separate state machine instances that are related through dependent managed data. State machines are used to manage the life-cycle changes to the one or more reference data sets. Fig. 1 illustrates life cycle changes associated with the reference data set.

1


Page 02 of 4

Figure 1

As illustrated in Fig. 1, one or more reference data set versions may be governed using one or more life cycle state transition models and proceed through different state transitions as per one or more lifecycle state transition models. Here, the different states may be draft, pending approval, approved, rejected and retired. This represents a time-span in life cycle of a version of the reference data set.

State machine levels may include, but need not be limited to, level 0, level 1, level 2,...