Abstract: A product management system receives one or modifications of a product, and separating the one or more modifications into two collections. The first collection includes one or more modifications that require approval. The second collection includes the one or more modifications. The product management system adds each modification from the first collection to a change management system, and stores each modification from the second collection that is not also in the first collection into production data. The product management system initiates a workflow for the change management system.

Abstract: A computing system provided according to an aspect of the present invention stores tags associated with relationships specified among objects. The tags can then potentially be used to search for objects of interest. In an embodiment, a search request is received indicating a first object, a second object and a search tag. A response is provided containing a sequence of objects and a sequence of relationships connecting the first object with the second object, with each relationship having an associated tag matching the search tag.

Abstract: Systems and methods for managing versions of product attribute information are described. A database management system that manages a database for storing attribute information of a product is described. The database management system in this implementation comprises a version control system and a querying system. The version control system is configured to enable a user to insert one or more versions of product information in the database. Each version has an effective date and is divided into a plurality of attribute groups, each attribute group containing a plurality of attributes. One or more attribute groups are modified with respect to a previous version. The version control system is further configured to record which attributes of a modified attribute group are changed. The querying system is configured to enable a user to search the database based on the effective dates of the versions.

Abstract: A change management model-based approach can be used for managing information, such as rows of data, presenting merged information from a pending and/or production datastore with rule-based redirection to an appropriate pending and/or production datastore. Such a model can support versioning, leveraging the pending data storage; can provide for direct or merged views of the appropriate datastore; and can provide a model logic for production data updates, version updates, and/or for change context updates. A unified presentation and update model for change management can merge pending data over the production information based on the context, and allow updates on top of production/date effective versioned information. Based on various rules, the data can be pushed to production or to a change order in the context of either datastore or to a fresh change order itself.

Abstract: A product management system receives one or modifications of a product, and separating the one or more modifications into two collections. The first collection includes one or more modifications that require approval. The second collection includes the one or more modifications. The product management system adds each modification from the first collection to a change management system, and stores each modification from the second collection that is not also in the first collection into production data. The product management system initiates a workflow for the change management system.

Abstract: A change management model-based approach can be used for managing information, such as rows of data, presenting merged information from a pending and/or production datastore with rule-based redirection to an appropriate pending and/or production datastore. Such a model can support versioning, leveraging the pending data storage; can provide for direct or merged views of the appropriate datastore; and can provide a model logic for production data updates, version updates, and/or for change context updates. A unified presentation and update model for change management can merge pending data over the production information based on the context, and allow updates on top of production/date effective versioned information. Based on various rules, the data can be pushed to production or to a change order in the context of either datastore or to a fresh change order itself.

Abstract: Systems and methods for managing versions of product attribute information are described with respect to a number of embodiments of the present disclosure. In one implementation, a database management system that manages a database for storing attribute information of a product is described. The database management system in this implementation comprises a version control system and a querying system. The version control system is configured to enable a user to insert one or more versions of product information in the database. Each version has an effective date and is divided into a plurality of attribute groups, each attribute group containing a plurality of attributes. One or more attribute groups are modified with respect to a previous version. The version control system is further configured to record which attributes of a modified attribute group are changed. The querying system is configured to enable a user to search the database based on the effective dates of the versions.

Abstract: A computing system provided according to an aspect of the present invention stores tags associated with relationships specified among objects. The tags can then potentially be used to search for objects of interest. In an embodiment, a search request is received indicating a first object, a second object and a search tag. A response is provided containing a sequence of objects and a sequence of relationships connecting the first object with the second object, with each relationship having an associated tag matching the search tag.