<P> Because attributes are defined by metadata, CMDBs also contain metadata, and thus the concept overlaps with that of a metadata repository, which is also used to more effectively run IT organizations . Configuration management addresses how the data is to be kept up to date, which has historically been a weakness of metadata repositories . </P> <P> At a minimum relationships are often composed of a Source CI that is related to a Target CI . In the case of more advanced relationships, such as semantic relationships, it is desirable to have a descriptor between the Source CI and Target CI that helps provide context . For example, "Database X" is related as a "Component" of "Application Y". The descriptor is also known as a Predicate . </P> <P> A configuration item type (or CI type) is the data type of the element or configuration item an enterprise wishes to store within the CMDB . At a minimum, all software, hardware, network, and storage CI types are stored and tracked in a CMDB . As enterprises mature, they start to track business CI types in their CMDB, such as people, markets, products, and 3rd party entities such as vendors and partners . This allows the relationships between CI's to become more meaningful and the CMDB to become a stronger source for knowledge management . </P> <P> CI types are: </P>

Extracting ci from repository for browsing editing or printing is