MINUTES OF THE FORTY-THIRD MEETING, 1 JUNE 1966

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP80B01139A000400070009-4
• Release Decision: RIPPUB
• Original Classification: C
• Document Page Count: 3
• Document Creation Date: December 16, 2016
• Document Release Date: April 7, 2005
• Sequence Number: 9
• Publication Date: June 8, 1966
• Content Type: MIN

Approved For ReILge 2005/04/13: CIA-RDP80B01139AO 00070009-4
T/I/M-43
8 June 1966
Minutes of the Fory-third Meeting I June 1966
Members or Their Representatives Present
CIA -
DIA -
STATE -
Css -
Others Present
1. Minutes of the forty-second meeting were approved.
2. Mr. Toler reported that application test data had been
received from CIA, DIA, NSA, and State. Suggested changes to the code
were being consolidated and would be distributed to members in the
near future.
3. Follow-on actions as called for in the Terms of Reference
were discussed. The overall usefulness of the code was considered.
The need for additional application rules, instructions, and manuals
were -d ified as necessary adjuncts to achieving an operating system.
pointed out the need for a formal request for review and
comments y the various agencies. He felt that the results of the
informal application and dissemination testing should be cranked into
the code as soon as possible and that a report be submitted to CODIB
requesting formal agency reactions before the team attempted to
complete the system and its supporting procedures, tools, etc.
Group 1
t'-O-N-F-I-D-E-N-T? .I-A-L Excluded from automatic
downgrading and
declassification.
Approved For Release 2005/04/13 : CIA-RDP80B01139A000400070009-4
 Approved For Rel a 2005/04/13 : CIA-RDP80B01139AOQ 000070009-4
4. then referred to the need to identify and describe
overall benefits which might accrue to agencies as a result of placing
content control notations on intelligence documents.
distributed a paper on possible uses of the proposed code in NSA.
then discussed the results of emphasis on secondary dissemi-
nation that had characterized the past approach. He discussed the
potentialities of the scheme in terms of a first step in attaining a
cooperative effort by the various agencies looking toward its
effective use for a variety of purposes. These might include, in
addition to support to dissemination, information storage & retrieval,
selection activities, consumers filing needs, management data
accumulation, and the possibility of automation and data exchange.
noted that the shallow content control code is unique in
a. it was designed to provide a uniform method of describing the
substantive content of the bulk of all intelligence documents regard-
less of source, method of acquisition, or parochial indexing require-
ments of any one group. Thus, it should be an effective vehicle for
establishing an initial compatibility among existing source- and
use-oriented systems which are processing the contents of these
documents.
25X1
5. The Team discussed potential uses of content control in
connection with storage and retrieval of documents for retrospective
research, in associating the same or similar information acquired by
various sources and methods, as well as in providing varied support
to existing dissemination systems, requested that team 25X1
members continue to be alert for additional, content control applications.
6. Mrs., Veilleux distributed a series of papers on the content
control applications test in the Department of State. She summarized
the findings for the team. In the course of discussion, she raised
questions concerning the degree of exhaustivity, i.e., should every
subject, area, and identifier which appears in the document be coded,
or should there be selection criteria? Along this line, she questioned
the advisability of aggregating into more general groupings either
areas or subjects which are actually specified in the documents. She
noted that this practice would result in substantial loss of definition
and degrade system performance.
7. Mrs., Veilleux discussed some of her suggestions for content
control system development including working aids, suggested additions
to the code, and sample indexing rules. In this connection,
Mr. Handwerger distributed a suggested outline for a content control
training manual which would cover definition and purpose of content
control, a general description of the codes, and guidance and
instructions for its use.
Approved For Release 2005/04/13 : CIA-RDP80B01139A000400070009-4
 Approved For Rel a 2005/04/13: CIA-RDP80B01139AOQW00070009-4
reported that dissemination testing
in their agencies was being analyzed and results verified.
9, eported that application
testing had been completed and reports sent to the secretary. Dis-
cussion followed concerning exchange of content control coded documents
between members. noted that he did not anticipate merging
the results of the ssem ion tests being conducted in the various
agencies, since testing was purposely oriented to local conditions.
10. The team discussed the possibility of linking identifiers
with pertinenet subject(s) and/or area(s). Some members felt that
these relationships should be preserved in all cases where it was
possible to do so. Others felt that such a requirement would result
in increased complexity in code application and much coding redundancy.
No consensus was reached on this matter.
11. reiterated his request for members to identify
additional applications for content control. The next meeting will
be held Wednesday, 13 July at 0900 hours at CIA Headquarters.
Secretary
Approved For Release 2005/04/13 : CIA-RDP80B01139A000400070009-4