Abstract: Building, reusing and calibrating network of authored content, in one aspect, may comprise clustering a plurality of problem tickets into one or more clusters. The clusters may be associated to one or more FAQ nodes in a FAQ network. The associated one or more FAQ nodes may be checked to determine whether the nodes are part of a broken branch. If the one or more FAQ nodes leads to a broken branch, a user may be notified to update the branch, e.g., with an answer or resolution to the one or more FAQ nodes.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Methods and arrangements for handling user queries. Submitted queries are accessed, and there are identified queries as being insufficiently addressed. A priority is estimated for the identified queries, and the identified queries are ordered based on the estimated priority. A priority-ordered list of queries is provided as output.

Abstract: Building, reusing and calibrating network of authored content, in one aspect, may comprise clustering a plurality of problem tickets into one or more clusters. The clusters may be associated to one or more FAQ nodes in a FAQ network. The associated one or more FAQ nodes may be checked to determine whether the nodes are part of a broken branch. If the one or more FAQ nodes leads to a broken branch, a user may be notified to update the branch, e.g., with an answer or resolution to the one or more FAQ nodes.

Abstract: Diagnosing and detecting causes of an incident may comprise classifying the incident by keywords, searching for co-occurring and reoccurring group of incidents, summarizing commonalities in the group of incidents, correlating the group of incidents with causes, defining association rules between the commonalities, and predicting potential problems based on the correlated group of incidents with causes.

Abstract: An expert conversation builder contains a knowledge database that includes a plurality of dialogues having nodes and edges arranged as directed acyclic graphs. Users and authors of the system interface with the knowledge database through a graphical interface to author dialogues and to create expert conversations as threads traversing the node in the dialogues.

Abstract: Shared data management in software-as-a-service platform may provide a common object data schema for one or more data objects and one or more data attributes associated with said one or more data objects stored in a master database. A plurality of applications may be enabled to be deployed dynamically on a platform and interoperate by sharing said data values stored in the master database. Data trading is enabled in which applications request permissions to read from or write to, or both, the master database, and in which the requests are mediated by granting or denying permissions.

Abstract: Dynamic application adaptation in software-as-a-service platform, in one aspect, may receive an access permission associated with a published shared data management data object in the software-as-a-service platform having shared data management and a plurality of applications deployed, look up one or more rules associated with one or more features of an application deployed on the software-as-a-service platform, based on the received access permission, and activate or deactivate said one or more features associated with said plurality of applications based on said one or more rules.

Abstract: Federating multiple-level master data management systems may include a first set of master data management nodes having one or more common characteristics. A first group master data management node may be assigned to centrally manage the first set of master data management nodes, the first group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the first set of master data management nodes. Each master data management node in the first set has data access link with the first group master data management node based on implementation style of said each master data management node.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements automatically of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Coordinating data sharing among applications in mobile devices, in one aspect, may include a shared data manager application on a mobile device that manages data trade requirements of a plurality of mobile applications, and permission grants or denials to reads and writes of data managed by the shared data manager and used by the plurality of mobile applications.

Abstract: Building a runtime dialog may include receiving an initial answer to an initial question from a user; creating a state of a conversation thread based on the initial answer; selecting, automatically by a processor, a next question to ask based on the updated state of the conversation thread; presenting the next question to the user; receiving a next answer to the next question; updating the state of the conversation thread based on the next answer; and repeating the selecting, presenting, receiving, and updating until a criterion is satisfied.

Abstract: An expert conversation builder contains a knowledge database that includes a plurality of dialogues having nodes and edges arranged as directed acyclic graphs. Users and authors of the system interface with the knowledge database through a graphical interface to author dialogues and to create expert conversations as threads traversing the node in the dialogues.

Abstract: Managing data stewardship in multi-level MDM systems may include a steward data composer that creates data steward repository for a master data management system to define relationships between data stewards and data objects for which data stewards are responsible and steward data consolidator that creates an integrated data steward repository by combining multiple data steward repositories.

Abstract: Enforcing data sharing policy through shared data management, in one aspect, may include extracting data access rights from the one or more data policies based on a user role, data purpose, an object set and a constraint identification; extracting a data domain from the one or more data policies based on the data purpose and the object set; associating the data access rights and the data domain with data attributes of the shared data; automatically responding to application-based offers and requests for the shared data within a Software-as-a-Service platform based on the data access rights.

Abstract: Federating master data management systems may include a network-aware adapter configured with a host master data management node. The network-aware adapter may establish one or more links with other master data management systems to allow the system to work together and leverage each other's data.

Abstract: Federating multiple-level master data management systems may include a first set of master data management nodes having one or more common characteristics. A first group master data management node may be assigned to centrally manage the first set of master data management nodes, the first group master data management node maintaining master data management functionalities at a group level and providing a single logical view of master data to the first set of master data management nodes. Each master data management node in the first set has data access link with the first group master data management node based on implementation style of said each master data management node.

Abstract: Federating master data management systems may include a network-aware adapter configured with a host master data management node. The network-aware adapter may establish one or more links with other master data management systems to allow the system to work together and leverage each other's data.

Abstract: Managing data stewardship in multi-level MDM systems may include a steward data composer that creates data steward repository for a master data management system to define relationships between data stewards and data objects for which data stewards are responsible and steward data consolidator that creates an integrated data steward repository by combining multiple data steward repositories.

Abstract: Shared data management in software-as-a-service platform may provide a common object data schema for one or more data objects and one or more data attributes associated with said one or more data objects stored in a master database. A plurality of applications may be enabled to be deployed dynamically on a platform and interoperate by sharing said data values stored in the master database. Data trading is enabled in which applications request permissions to read from or write to, or both, the master database, and in which the requests are mediated by granting or denying permissions.