Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Design databases

Briefly, in relational databases, diverse types of information are stored in different data tables that are connected and often embedded in an ORACLE database architecture [Pg.40]

Clearly, much of the progress of collaborative R D significantly depends on the availability of advanced and flexible database structures for data handling, sharing, and management. The design and implementation of such databases continue to be major tasks for chemoinformatics. This has also been realized by a number of software companies that provide commercial compound database and management systems and offer customization services. [Pg.42]


Nuclear Magnetic Resonance Spectroscopy. Bmker s database, designed for use with its spectrophotometers, contains 20,000 C-nmr and H-nmr, as weU as a combined nmr-ms database (66). Sadder Laboratories markets a PC-based system that can search its coUection of 30,000 C-nmr spectra by substmcture as weU as by peak assignments and by fiiU spectmm (64). Other databases include one by Varian and a CD-ROM system containing polymer spectra produced by Tsukuba University, Japan. CSEARCH, a system developed at the University of Vieima by Robien, searches a database of almost 16,000 C-nmr. Molecular Design Limited (MDL) has adapted the Robien database to be searched in the MACCS and ISIS graphical display and search environment (63). Projects are under way to link the MDL system with the Sadder Hbrary and its unique search capabiHties. [Pg.121]

NERAC, bibhography. Database Design, pub. no. PB92-861665, ToUand, Conn., 1992. [Pg.134]

Jollis JG, Ancukiewicz M, DeLong ER, et al. Discordance of databases designed for claims payment versus clinical information systems. Implications for outcomes research. Ann Intern Med 1993 119 844-50. [Pg.589]

Cmcial documentation needed in the development phase includes end-user manuals, a unit test summary report, a user acceptance test plan, results of the database design, results and methods employed in the source code evaluations, and a trace-ability analysis. A source code traceability analysis verifies that all code is linked to established specifications and established test procedures. [Pg.1057]

Halpin, T. 1995. Conceptual Schema and Relational Database Design. 2nd edition. Prentice Hall, 547p. [Pg.392]

If you ve done any database design, you ll be familiar with the idea that every entity must have a unique key, which it is up to you to assign. The key is an explicit combination of the entity s attributes, and any two entities with the same attribute values are actually the same one. But in object-oriented design, we always assume an imphcit unique key. If you implement in an OO language or on an OO database, it provides the key for you otherwise, you make it explicit when you get to coding. [Pg.79]

Data are still generally typed into a database rather than electronically loaded from other systems. The first step of any data entry process should involve a check for duplicate cases. The need for decision making at the data entry stage will depend upon the type of database design. In all cases, there should be clear rules on how data should be entered into each field to ensure consistency and aid subsequent searching and outputting. This is particularly important when there are multiple users distributed over a number of international sites. Use of electronically available field specific lists of value and well-defined coding conventions will help with this. [Pg.850]

DIPPR 801 Database. Design Institute for Physical Properties, November 2006 (dippr.byu.edu). [Pg.276]

A lot of technology is required to achieve effective federation of disparate information sources. The Cabinet design is such that the computer does a tremendous amount of data processing to deliver a simple and powerful interface to the user. This is contrary to traditional database design that focuses on processing efficiency at the cost of flexibility and simplicity. Fortunately, current computers are more than adequate to do this job well. By the standards of the last few years, current desktop computers are supercomputers (and they are stiU getting faster and more capable each year). [Pg.267]

The requirements for hardware validation are identical to those of any other equipment in use, comprising the OQ/IQ/PQ cycle, except that in the PQ, it is the test of software used. The software validation comprises functional testing, in which defined inputs produce outputs that meet expectations or specifications a thorough examination of source codes, database designs, programming standards, control methods, and support documentation or a quality-assurance program that includes alternate plans, contingency practices, record retrieval, and security practices... [Pg.46]

Database design and development Data entry, editing, verification CRF tracking... [Pg.357]

Physicochemical properties of amino acids are very useful descriptors for understanding the structures and properties of proteins. These properties are expressed numerically in indexes that can be retrieved from the AAindex database. Design an index database of physicochemical properties of amino acids with Microsoft Access that may facilitate the data retrieval according to their chemical similarities ... [Pg.101]

Chemical data collection, analysis, and management Data representation and communication Database design and organization... [Pg.2]

VERIFY is a computerized database designed for the storage, management, and search of chemical and analytical reference data (44). Properties and contents of the NMR part of VERIFY are ... [Pg.346]

Analytical database design and implementation are important to the analytical chemist for several reasons ... [Pg.29]

A database can be described as a collection of inter-related data organized into records and connected by known (set) relationships. Typically, a database is organized around a function such as personnel, manufacturing, etc. A LIMS database is organized around the analytical and research laboratory. Good database design involves several well established principles (1)... [Pg.30]

VAX LIMS DMDB. The key to good database design is the definition of records and the set relationships between them. The VAX DMDB schema (Bachman diagram) is shown in Figure 4. The diagram shows the major records (boxes) in the database and the relationship (arrows) between the records (sets). The records and their fields are determined by the nature of the data encountered in an analytical laboratory... [Pg.34]

Case report form design Database design Data entry Data evaluation... [Pg.449]

Hybrid audit trails electronically logging last changed by with date and link to related paper-based change records are acceptable for critical records so long as previous versions of the record are maintained. It may be possible in some cases to fulfill the audit trail requirements with a transaction database log. Some database designs require the user to execute a commit record step, while others commit the data as soon as the next field is tabbed to. In cases where a conscious decision to commit the record is required, data entered should not be defined as an electronic record until this action is taken, thus potentially simplifying the audit trail. In cases where there is no commit step, the audit trail should start as soon as each data item is entered. [Pg.361]

A more sophisticated database design is relational. This design makes use of defined relationships between data to vastly increase the efficiency of data retrieval. Its popularity is largely attributed to its relatively simple data model ... [Pg.751]

Relational database design is certainly unlike other forms of programming, but there are tools available to help with the task. Since the relationship between data elements is a key consideration, the Entity Relationship Diagram (ERD) is an important one of these tools. There are many conventions for documenting ERDs the one depicted below is one of the simpler examples to understand. [Pg.754]

In view of 21 CFR Part 11, audit trails have become a standard part of many database designs. When specifying any database that will include GxP data, it is important to recognize that specifications for Part 11 compliance must go beyond a statement that the application must be Part 11 compliant. Not all designers or suppliers of commercially available solutions will have intimate... [Pg.755]


See other pages where Design databases is mentioned: [Pg.234]    [Pg.8]    [Pg.245]    [Pg.790]    [Pg.72]    [Pg.121]    [Pg.2]    [Pg.568]    [Pg.40]    [Pg.41]    [Pg.41]    [Pg.117]    [Pg.224]    [Pg.10]    [Pg.500]    [Pg.517]    [Pg.753]    [Pg.756]    [Pg.757]    [Pg.758]    [Pg.928]    [Pg.924]    [Pg.390]    [Pg.519]    [Pg.554]   
See also in sourсe #XX -- [ Pg.23 , Pg.24 ]




SEARCH



Base case design detailed database

Computer Database Design Selection Procedure

Database Resources for Chemical Design

Databases Molecular Design Limited

Databases catalyst design

Designing Databases

Designing with databases

Engineering design database

Molecular Design Limited Reactions Databases

Representing Chemical Structures in Databases for Drug Design

© 2024 chempedia.info