Code sheet

Container - Provide the corresponding code for the type of container in which the reportable substance is stored. If you have a container other than the ones listed on the Code Sheet, you should use Code 34, "other". If a hazardous substance is present in different contacts, provide an individual report for each type of storage container, giving the corresponding codes. For example, if a solvent is stored in th 55-gallon steel drums and glass bottles, two separate reports should be made for that solvent. 

In the Project Explorer window you will see a hierarchy "tree" with a node for each open workbook. In the example illustrated in Figure 13-3, a new workbook. Workbooks, has been opened. The node for Workbooks has a node (a folder icon) labeled Microsoft Excel Objects click on the folder icon to display the nodes it contains — an icon for each sheet in the workbook and an additional one labeled ThisWorkbook. If you double-click on any one of these nodes you will display the code sheet for it, but these code sheets are for a special type of procedure called an automatic procedure (see Chapter 18). 

Group (i) By applying all possible arrangements of U and D symbols on the net,[24] coded sheet structures are generated. To reduce the number of sheets, equal numbers of U... 

We design a reaction coding sheet to contain most of the information needed by both reaction retriever and synthesizer programs (Figure 4) Data on reactants, products, intermediates, reagents, conditions, yields work-up procedures mechanism, and... 

In phase lip we asked Merck chemists to code reactions in their area of expertise We received 44 coded sheets from 31 chemistst a gratifying response. However while these were eminently suitable for current awareness circulation and for a reaction retrieval service they were generally unsuitable for a synthesizer. Thus as summarized in Table I over 50% of the... 

Material data are complied using specific data coding sheets, and the data inputs to the computer data processing system SMAT are still continued. 

This compendium of microbial feature descriptors is designed to employ computer technology in the storage, retrieval and analysis of data descriptive of individual strains. A set of filled out code sheets of the type now used is appended as an example it has been encoded for descriptors of the genus Salmonella and should be consulted as a model for the understanding of the following coding directions. 

TABLE 3. Xtem numbers and code sheet column positions for selected strain information in RKC1 and RKC2 formats (The full text of the items is given in the follouing document. 

When entering information onto the code sheets, please use pencil, marking heavily, for those sections requiring coded answers. PRINT CLEARLY. Correct any errors by erasing, not by crossing out and/or writing over the error. 

For accurate data entry and proof reading the code sheets should be neatly prepared. 

In addition, when a field is to be duplicated, use a Z as shown in the example set of code sheets. 

In Section 2. Strain Information, use the special code sheets as follows. Answer Questions 002001 through 002004 and 001997 on CSSC-05. If more than 20 strains are being coded, use additional sheets. Serially number each code sheet used in the space provided (PAGE NUMBER) in the upper left corner. Answer each question in the columns on the code sheets as denoted in parentheses after each question in the text. 

The same procedure is used for CSSC-07 and CSSC-10. This structured approach is advocated (but not intrinsically required by the computer) to facilitate record keeping on data flow as part of data processing quality control. If data are not being submitted as called for on a given CODE SHEET (e.g., no COMMENTS, CSSC-06), those code sheets should be omitted from the data set. However, the data manager should be informed in writing to avoid confusion as to whether the sheets were intentionally omitted. 

The upper right corner of all CODE SHEETS (except for Section 1) is for identifying information which is filled out under the same rules as for Section 1. In the spaces provided, the following information MUST be entered on each code sheet 1) The respondent s surname 2) The genus or other microbial group and 3) The date. Items 1,2, and 3 should be the same as the corresponding answers in Section 1. The spaces for Form Number (i.e., data set number) should be left blank. 

Figure 2. An example of coding features for binary data on CODE SHEET 08/09. Only the upper left hand corner is shown.

Place the strain designation or identifier (as many as 10 characters, any letters, numbers, punctuation, i.e.,., , -, /, etc.) in columns 1 through 10 on CODE SHEET-08/09, one strain to each row. Use of blanks or zeros is optional in this case. The information for as many as 20 strains may be entered for as many as 60 features on each code sheet. Thus, answers to 190 features regarding 105 strains would require 24 sheets. 

Record the Question Number on CODE SHEET-08/09 as usual. 

In addition to filling out the CODING SHEETS as described above, it would be extremely useful for each respondent to provide a list of the methods used to obtain the answers to the various questions. This list is maintained as an ancillary text file in the computer. 

HAVE ANY STRAINS OF SPECIES OF THIS GENUS BEEN REPORTED AS PATHOGENIC IF ANY STRAINS FOR WHICH YOU ARE SUBMITTING DATA ARE PATHOGENIC, PLEASE SUPPLY THE FOLLOWING INFORMATION ON A SEPARATE SHEET OF PAPER (A) STRAINS BY SPECIFIC EPITHETS, (B) HOSTS (BOTH COMMON AND SCIENTIFIC NAMES), AND (C) DISEASE. IDENTIFY EACH SHEET OF PAPER WITH THE WORLD DIRECTORY OF CULTURE COLLECTIONS NUMBER IF APPLICABLE, AND ALSO THE SAME INFORMATION AS REQUIRED IN THE TOP RIGHT CORNER OF CODE SHEET-1. 

WHAT IS THE TOTAL NUMBER OF CODE SHEETS YOU ARE SUBMITTING FOR STRAINS OF THIS GENUS (OR SUBGENUS) OR ARBITRARY GROUP (NOTE ALL CODE SHEETS MUST BE SECURELY FASTENED... 

Respondents requiring general information about the system, directions for coding, coding sheets or forms, or who wish to offer suggestions for improvements, please contact ... 

---