Redundant compounds

A further consideration when combining databases from multiple suppliers is how to identify and deal with redundant compounds. Here, some method of mapping multiple supplier information onto a single compound is needed for efficiency. Generally, all information can be mapped, although some consideration of cost and supplier reliability may allow a hierarchy of supplier information to be applied. 

Here, the identification of redundant compounds based on molecular diversity considerations is a key requirement, as any reduction in the number of compounds to be synthesized and tested, by reducing redundancy within a database yet not introducing voids, should impact on research efficiency and costs [14]. Even with new miniaturization technologies, smaller compound subsets are essential if more assays are to be handled in a given time frame. Designing subsets using an adequate method enables project teams to find the appropriate balance between the number of compounds for HTS and the project s lifetime. 

They produce redundancy and incompatibility. In addition to redundant and incompatible user interfaces, closed systems foster data redundancy, hardware and software incompatibility, duplication of programs and duplication of security schemes. In some cases, the user or programmer finds it easier to re-enter data that already reside in an existing database than to build a bridge to extract the information. Clearly, such duplication makes maintenance of consistency between data in various databases a major challenge. Each level of redundancy compounds the problem. Not only are direct costs increased unnecessarily, but the integrity, accuracy, and security of information are threatened. 

---