INTERNATIONAL INFORMATION SYSTEM ON CULTURAL DEVELOPMENT

MODEL DATABASE FOR CULTURAL DEVELOPMENT ON CDS/ISIS

Manual and Accompanying Diskette

prepared by Alan Hopkinson

First Experimental Draft

January 1993

Acknowledgement

This manual is based on another manual which was developed on behalf of Unesco by the compiler with the assistance of Andrew Buxton 

CONTENTS

1.  Introduction                                                    1

2.  Installation                                                    5

3.  Creating records - general                                      8

4.  Creating records for documents                                 12

5.  Creating records for persons                                   55

6.  Creating records for institutions                              69

7.  Creating records for projects                                  93

8.  Creating records for events                                      

9.  Creating records for training opportunities                      

10. How to enter personal names                                      

11. How to enter corporate names                                     

12. Codes for languages                                              

13. Codes for countries                                              

14. Codes for currencies                                             

15. The sample database                                              

16. References                                                       

- iii -
1. INTRODUCTION

This manual and the database it accompanies has been produced to facilitate the exchange of data between institutions participating in the International Information System on Cultural Development.

It is based on and fully compatible with the data elements which have been devised for the Common Communication Format for Information on Cultural Development which is in turn based on the Common Communication Format (CCF/B and CCF/F)

This introduction is intended for readers already familiar with bibliographic formats and in particular the Common Communication Format.  It places this manual in the context of international exchange formats, and the information here is intended to justify this manual and accompanying database, not to explain its operation.  Readers without this background who wish only to make use of this manual in order to operate the accompanying database should begin at Chapter 2.

1.1 The integrated database

This database is an integrated database which means, in this context, one which can include records not only of certain types of factual information but also of bibliographic references;  therefore, it is possible to construct a database on cultural development, which would contain records of events such as exhibitions as well as of documents such as exhibition catalogues and journal articles produced as reviews of the exhibitions and the profiles of the organizations and persons involved in the organization of the event.  The scope of this database is detailed more precisely below.

This implementation includes worksheets for Institutions and Persons, Events,  Projects and Fellowships and training opportunities.  Also there are worksheets for bibliographic data: monographs, articles in serials and articles in monographs. Note that projects as used in the cultural field includes not only research projects but artistic projects.  Events are usually shorter in time than projects and are covered by a distinct type of record.

Any one user may not wish to include all these different kinds of data in one database, but the facility is there if required.  Thus, it is possible to include, in one database, everything about a chosen field, whether it is institutions involved, training courses, events, etc.  It is also possible to include records relating to documents about and resulting from these events in the same database and make links to them.  In fact, links can be made between any of the different categories of record. However, it has been decided to make them only between projects and projects, between projects and bibliographic data and between institutions and bibliographic data (so that bibliographic records can be reproduced in records relating to factual entities).

Certain kinds of material have not been included.  Patents, standards and serials as complete entities (as opposed to articles in serials) have been omitted, but it will be easy for the user to follow the existing methodology and add the required fields if desired.

2.INSTALLATION

This section assumes familiarity with MS/DOS and CDS/ISIS and that CDS/ISIS has been installed using various sub-directories as recommended in the Manual. In particular, parameter 5 of SYSPAR.PAR should point to \ISIS\DATA\.  The files may be installed into either the data subdirectory, or into a sub-directory of DATA called CULTURE.  Follow 2.1 or 2.2 but not both.

2.1 Installing into DATA sub-directory

Copy the contents of the diskette into the subdirectory as follows, after placing the diskette in drive A.

CD\ISIS\DATA
COPY A:*.*

2.2 Installing into CULTURE subdirectory

Place the diskette in drive A.
CD\ISIS\DATA
MD CULTURE
CD CULTURE
COPY A:*.*
CD..

Then create the following file in \ISIS\DATA using EDLIN or any other editor. Call this file CULTURE.PAR.

1=C:\ISIS\DATA\CULTURE\
2=C:\ISIS\DATA\CULTURE\
3=C:\ISIS\DATA\CULTURE\
4=C:\ISIS\DATA\CULTURE\
5=C:\ISIS\DATA\CULTURE\
6=C:\ISIS\DATA\CULTURE\
7=C:\ISIS\DATA\CULTURE\
8=C:\ISIS\DATA\CULTURE\
9=C:\ISIS\DATA\CULTURE\
10=C:\ISIS\DATA\CULTURE\

2.3 Installing DATE.PAS

The PASCAL program DATE.PAS with its compiled version DATE.PCD copies the system date from the computer on to function key F9.  The program depends, of course, on the system date's having been correctly set in the microcomputer. See the DOS manual which accompanies the computer for instructions on how to set the date (usually achieved by entering at the C> prompt the command DATE).  The DATE.PAS and DATE.PCD files will have been copied as per the instructions followed in 2.1 or 2.2.  They may be deleted from the DATA or DATA\CULTURE subdirectories.  They should be added to the PROG subdirectory and then it is advisable to  recompile the program as follows:

CD\ISIS\PROG
COPY A:DATE.PAS
CD..
ISIS
A (select from main menu)
C DATE <Carriage return> R <Carriage return> Q

Each time ISIS is run, select A from the main menu and type (without spaces):
R DATE <Carriage return> Q 

Alternatively add the following line to the SYSPAR.PAR file (using EDLIN)
9=ardate^Mq

2.4 Files in the implementation

The following is a list of files generated for the database. 

Data Entry Worksheets

CLT   Default worksheet. Use for editing, contains all fields, but
      no help text.
CLTAM Worksheet for articles in monographs
CLTAS Worksheet for articles in serials
CLTMO Worksheet for monographs
CLTPR Worksheet for projects
CLTIN Worksheet for institutions
CLTPE Worksheet for persons

Display formats

CLT     Default format shows all fields: has been automatically
        generated from FDT
CLTISB  Format for the display of bibliographic records
CLTPRO  Format for the display of records of projects
CLTPER  Format for the display of records of persons
CLTINS  Format for the display of records of institutions

Field select Tables (FSTs)

CLT     Default FST for generating index for inverted file
CLT3ID  FST for export to IDIN Manual format
CLT3EX  FST for export to CCF ISO 2709 exchange format
CLT3IM  FST for import from CCF ISO 2709 exchange
        format

The last three files are reformatting FSTs. CLT3ID works only for document records.

As can be seen from the above, there is one worksheet for each different type of material and, in the case of bibliographic data, for each combination of bibliographic level.  There is a worksheet for editing (the default worksheet, CLT) which contains all fields but does not contain help messages as they do not easily apply to all materials.  There is only one display format for all bibliographic material.  Unfortunately, since there is a limit on the size of display formats in CDS/ISIS, it has not proved possible to develop a format which can reproduce on the screen records for all material in a user-friendly way, so different formats have been produced for each kind of factual information.  The default format CLT.PFT can be used at any time.

Each file begins with CLT or, in the case of worksheets, ACLT, BCLT, CCLT, etc where the first character is a CDS/ISIS device to denote the sequence of the pages of a worksheet.  This is to facilitate copying the database to other computers.  Users may change the names of the worksheets and display formats as they wish (except for the defaults which must be called CLT).  This is best done in ISISDEF (option K) by copying files to a new name and deleting the original.  However, if this is done, the display formats will need slight modification as they refer to other formats by names commencing with 'CLT'.

3.  CREATING RECORDS - GENERAL

3.1  Fields and subfields

The information about each document, person, institution, project, training opportunity or event forms a record.  In the integrated database, any or all of the four types of records may be present.  The information within each record is divided into fields.  For example, the PERSON records contain fields for name, address, subject expertise, nationality, etc.  Each field is denoted by a three-figure tag (or, in the case of host items containing a document, a four-figure tag).  Thus the field for the person's name is 300 and the field for address is 430.

Within a field, the information may be further divided into subfields.  For example, the address field is divided into building, street address, town, state or region, country, etc.  Subfields are identified by a lower-case letter (or occasionally a figure).  Thus the address field is divided into subfield a for building, subfield b for street address, subfield c for town, etc.  Every field has at least subfield a, except for certain fixed-length non-repeatable coded fields where the subfield identifier has been omitted to facilitate data entry (see 015).

When data are being entered into the computer, each field is prompted for by its name.  The data should then be typed in using a circumflex in front of each subfield identifier.  For example, in the address field:
     ^aCentury House^b100 Maynard Road^cLondon

Do not leave spaces between the subfield identifiers and text; spaces should only occur where they will be required when the text is displayed. Do not include punctuation at the end of a subfield as it will be provided automatically on display.

3.2  Repeated data

It may be that you need to enter more than one value of a data element.  For instance, in the field for Subject Descriptor you may want to enter several descriptors.

In the following sections (4 to 9) each field is described as "Repeatable" or "Not repeatable".  If the field is repeatable you can enter each value in a separate occurrence of the field.  Repeats are entered separated by a percent sign in CDS/ISIS.  So, to use several descriptors, you would enter:
     ^aTelecommunications%^aIntegrated Services Digital
     Network%^aCommunications protocols
Note that the subfield marker needs to be used in each repeat of the field.

If the field is described as "Not repeatable", only one value of the data element should be recorded there.

As explained in Section 1.2.5, CDS/ISIS cannot cope with repeated subfields within a field.  So, for example, if you want to record more than one place of publication in the Place of Publication and Publisher field, you should separate the place names by means of semicolons (the punctuation prescribed by AACR and ISBD), not by repeating the ^a identifier:
     ^aLondon; Oxford; Melbourne; Delhi^bOxford University Press

3.3  Mandatory and optional fields

In the following sections, each field is described as "Mandatory" or "Optional".  "Mandatory" means that you should enter data in this field whenever they are applicable to the item being described and are known to you.  There will be cases where the data element is not applicable even though marked "Mandatory".  For example, Name of Meeting (field 320) is mandatory for documents, but should be left blank if the document does not emanate from a meeting or an event.

Within a mandatory field, not all subfields may be mandatory.  For subfields which are mandatory, the "Rules for Entry" are written in the imperative, e.g. "Enter the ISBN of the document in subfield a."  For subfields which are optional, i.e. not mandatory, the word "may" is used, e.g. "The acronym may be entered in subfield x".

The general principle in selecting data as mandatory is that these are the minimum elements necessary to identify the item being described.  For documents, the selection of mandatory fields is based on that in the CCF, though it does not correspond exactly.  It is somewhat less than the "First level of description" of AACR2, in that it omits the Extent of item and Note(s).

3.4  Standards for Cataloguing 

In sections 4 to 9, sets of fields and subfields are given for creating records for documents, persons, institutions, projects, events and training opportunities.  These structures constitute formats for each type of record.  In addition, rules are given for entering data in these fields and subfields.

The standard on which the format and rules for documents are based is the Anglo-American Cataloguing Rules, Second edition (Library Association, 1978), referred to as AACR2.  The descriptive part of AACR2 conforms with ISBD(M) : International Standard Bibliographic Description for Monographic Publications, First standard edition (IFLA Committee on Cataloguing, 1974) and is closely related to ISBD(G) : General International Standard Bibliographic Description: Annotated text (IFLA International Office for UBC, 1977).  A principle source for the choice and construction of headings is Statement of Principles Adopted at the International Conference on Cataloguing Principles, Paris, October 1961 (IFLA Committee on Cataloguing, 1971).  Some aspects of AACR2 have not been retained, for example the distinction between main entry and added entry, which is irrelevant in the database on CDS/ISIS.  The DOCUMENTS format (CLTISB.PFT) provides fields for all data elements included in the "First level of description" in AACR2, and the implementation can produce correctly-formatted records according to ISBD for this level.  It can also accommodate the data elements for higher levels of description, but there may occasionally be problems with the output format when data elements are repeated (e.g. subsequent statements of responsibility).

One consequence of following AACR2 is that the preferred language for entering data is English.  Thus, when an organization's name appears in more than one official language and one of these is English, the English form should be entered.  For example, "World Health Organization" is preferred over "Organisation Mondiale de Santé" or "Organización Mundial de la Salud".  Place names are also preferred in their English form when available, e.g. "Copenhagen" rather than "Kφbenhavn".  It is recognized that agencies whose working language is not English, or who are following adapted language versions of AACR, may prefer to use forms in their own language where available, and this is offered as an option in the following sections, introduced by the word alternatively.

As regards persons, institutions, projects, events and training opportunities,  no comparable "cataloguing rules" are available.  However, in an integrated database it is necessary that those elements intended to be searched are entered in the same way in all types of records.  Therefore, the rules for entering personal names in documents are also applied to such names in PERSONS, INSTITUTIONS, PROJECTS, EVENTS and TRAINING OPPORTUNITIES records, where they represent directors, investigators, contact persons, etc.  They are given in Section 10.  Similarly the same rules are applied to corporate names in all types of records: they are given in Section 11.

The set of data elements for institutions and projects follows closely that in the Reference Manual for machine-readable descriptions of research projects and institutions (Unesco, 1982) and in the CCF/F: Common Communication Format for Factual Information. Those for persons follow the CCF/F.  Some simplifications have been made, e.g. the keywords, discipline and geographical area fields have been combined as "Subject Descriptor".  Account has been taken of the format used in the Survey of Malawi Scientific and Technological Potential (STP) of the National Research Council of Malawi, from which the lists of terms for Type of institution and Type of project (field 064) have been taken.   The formats are also broadly compatible with those of FIIR : Formato de Intercambio de Información Referencial (Unesco, 1989) and Documentation - Directories of libraries, archives, information and documentation centres, and their data bases (ISO 2146: 1988).  The set of data elements for training opportunities and events follows closely those for projects and institutions in the CCF/F and for meetings in CCF/B - CCF/B deals with the cataloguing of conference proceedings; assumptions have been made where necessary.

3.5  Character set

CCF/B : The Common Communication Format (Unesco, 1992) and Implementation notes for users of the Common Communication Format (CCF) (Unesco, 1990) have detailed treatments of character sets.  At the inputting stage, the character set will depend on the hardware and operating system being used.  As well as characters present on the keyboard, additional characters can be entered on PC-compatible computers by holding down the Alt key and typing a numerical value on the numeric keypad (usually to the right of the main keyboard).  The following is a selection of the commonly-required characters that may be obtained in this way.

Numeric value       Character

123                 {  (US and UK keyboard)
124                 |  (US and UK keyboard)
125                 }  (US and UK keyboard)
126                 ~  (US and UK keyboard)
128                 Ç
129                 ü
130                 é
131                 â
132                 ä
133                 à
134                 å
135                 ç
136                 ê
137                 ë
138                 è
139                 ï
140                 î
141                 ì
142                 Ä
143                 Å
144                 É
145                 æ
146                 Æ
147                 ô
148                 ö
149                 ò
150                 û
151                 ù
152                 ÿ
153                 Ö
154                 Ü
155                 ¢
156                 £
157                 ¥
158                 ₧
159                 ƒ
160                 á
161                 í
162                 ó
163                 ú
164                 ñ
165                 Ñ

4.  CREATING RECORDS FOR DOCUMENTS
4.1 Monographs

To create records for monographs (i.e. books, reports, conference proceedings as a whole, etc.) select the worksheet CLTMO. Please note that serials as a whole as opposed to serial analytics, and patents are not yet included in this implementation.

4.2 Analytics

An 'analytic' is an item which is not published alone but is part of a larger work.  Typical examples would be an article within a serial, a paper in a conference proceedings, or a chapter within a book where each chapter has its own author and title.  The larger work is known as the 'host' item.

In such cases, the record will contain data for two different bibliographic levels.  Details of the analytic (the author, article title, page numbers, subject information, etc.) constitute one level and should be entered in the fields 015 to 620.  Details of the host item containing the analytic (such as the serial title, editor, publisher, etc.) constitute the second level, and should be entered in the fields 1015 to 1440.  These fields constitute the 'secondary segment' of the record.

To create records for analytics within monographs, select the worksheet CLTAM.  To create records for analytics within serials, select the worksheet CLTAS.

____________________________________________________________

4  DOCUMENTS
____________________________________________________________

015  BIBLIOGRAPHIC LEVEL

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

NB  The subfield identifier is not used in this fixed length subfield in this implementation. The field corresponds to character position 7 of the record label which is not accessible to users of CDS/ISIS.

	Bibliographic level

RULES FOR ENTRY

1.  Enter here one of the following codes to denote the bibliographic level of the main part of the record.  The term 'analytic' is explained above.

If the correct worksheet is used (CLTMO, CLTAS, CLTAM), the appropriate code is the default and pressing carriage return will cause the correct code to be entered in the field.

	m  Monograph  
	a  Component part ("analytic")

2.  The level of the host item, if any, is recorded in field 1015.  

EXAMPLES

1.	m

2.	a

____________________________________________________________

4  DOCUMENTS
____________________________________________________________

022  DATE ENTERED ON FILE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD
	^a  Date

RULES FOR ENTRY

1.  Enter here the date when the record was added to the file.

2.  If the program DATE.PAS has been installed, the date can be entered by pressing function key 9.

3.  The date should be constructed in accordance with ISO 8601, i.e. the year in full, two figures for the month, and two figures for the day.  Do not use any punctuation or spaces within the date.

4.  If your organization distributes records to other organization, it may choose to substitute the date of distribution in this field.

5.  If your organization takes records from other organizations, this field should contain the date that the record was originally created, if that is available.  Otherwise it may contain the date that the record was entered into your system.

EXAMPLES

1.	^a19870917				[17th September, 1987]

2.	^a19901130				[30th November, 1990]

NOTE FOR SYSTEMS ANALYSTS

If necessary, add an extra subfield to allow for greater detail, e.g. when records are taken from other organizations.

__________________________________________________________

4  DOCUMENTS
____________________________________________________________

040  LANGUAGE OF ITEM

This field is:

-  Optional
-  Repeatable

SUBFIELD
	^a  Language of the item

RULES FOR ENTRY

1.  The language or languages in which the document is written may be entered here.

2.  Use the language codes from Section 12.

3.  If the document is in more than one language, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aspa                                 [document is in Spanish]

2.  ^adut%^aeng%^ager                     [document is in Dutch,
                                          English and German]

____________________________________________________________

4  DOCUMENTS
____________________________________________________________

050  PHYSICAL MEDIUM

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Physical medium code

RULES FOR ENTRY

1.  The physical medium of the item may be recorded here using a code from the list below.

	010		Paper
	020		Film
	030		Braille
	040		Magnetic
	050		Laser/optical
	900		Other

2.  If the item consists of more than one physical medium, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.    ^a010         [record describes a book: code 010 for
                    print on paper]

2.    ^a010%^a020   [record describes a book (code 010)
                    which contains a microfiche in a pocket:
                    code 020 for film]

____________________________________________________________

4  DOCUMENTS
____________________________________________________________

060  TYPE OF MATERIAL

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

NB  The subfield identifier is not used in this fixed length field in this implementation.

    Type of material code

RULES FOR ENTRY

1.  Enter here a code from the list below to represent the form of presentation of the intellectual content of the document.

	100		Textual (general code)
	105		Report/technical report
	110		Thesis, dissertation
	115		Meeting document
	120		Periodical
	125		Newspaper
	130		Annual
	150		Monographic series (when record relates to series)
	199		Other textual materials

2.  The codes are not mutually exclusive.  If more than one applies, use the first one in the list (excluding 100).

EXAMPLES

1.  115         [The proceedings of the conference of a
                learned society published as a serial.]

2.  110         [Thesis]

____________________________________________________________

4  DOCUMENTS
____________________________________________________________

100  INTERNATIONAL STANDARD BOOK NUMBER (ISBN)

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

	^a  ISBN

RULES FOR ENTRY

1. Enter the ISBN of the document in subfield a.

2.  The ISBN is a number identifying the document and allocated in accordance with ISO 2108 and the ISBN Users' Manual.  It consists of four parts of variable length, separated by hyphens.

3.  Hyphens should be used to separate the parts of the ISBN, even if the document uses spaces, full stops, other punctuation, or no separator.

4.  Only one ISBN should be entered.  If the document bears more than one number, enter the one for the binding, publisher, etc., of the item in hand.

EXAMPLES

1.	^a0-7214-0191-0

2.	^a0-903043-10-6

3.	^a2-06013-213-4

NOTE FOR SYSTEMS ANALYSTS

CDS/ISIS does not check the ISBN for validity, so the number printed on the document may be entered whether or not it is correctly constructed and assigned.
____________________________________________________________

4  DOCUMENTS
____________________________________________________________

120  DOCUMENT NUMBER

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Document identification number
	^b  Type of number

RULES FOR ENTRY

1.  The document number is a number appearing on the item intended for unique identification and usually allocated by the publisher.

2.   ISBNs should not be entered here, but in field 100.  Numbers of items within series should be entered in field 480.

3.  The document number may be entered in subfield a.

4.  The type of document number may be entered in subfield b.

5.  If there is more than one document number, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^a4206

2.	^a1756-88^bStandard Technical Report Number

3.	^aPGI-90/WS/3

____________________________________________________________

4  DOCUMENTS
____________________________________________________________

200  TITLE AND STATEMENT OF RESPONSIBILITY

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Title
	^b  Statement of responsibility associated with title

RULES FOR ENTRY

1.  Enter the title of the document in subfield a.  Follow the document as regards wording, order and spelling, but not necessarily as to punctuation and capitalization.  Use a capital letter for the first word and then follow the conventions of the language of the title.

2.  Separate the subtitle, if any, by means of a space, colon and space.

3.  The statement of responsibility may be entered in subfield b.  This consists of any name(s) or phrase(s) relating to persons responsible for the intellectual or artistic content of the document, or to corporate bodies from which the content emanates.  Follow the form and sequence of the original, but not necessarily the punctuation or capitalization.  The statement of responsibility may be omitted in records for analytics.

4.  If the item contains more than one work and lacks a common title, enter the titles of each work in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aCultural rights and cultural democracy

2.  ^aI'm OK - you're OK^bThomas A. Harris

3.  ^aProduction and dissemination of cultural goods and
     services : cultural industries^bedited by James C.W. Chien

4.  ^aIntroducción a los problemas económicos de Guatemala

5.  ^aBaukunst der Romanik in Europa^bherausgegeben von
    Harald Busch und Bernd Lohse; Einleitung und
    Bilderläuterungen von Hans Weigert

6.  ^aHenry Osmond : a novel^bby Thackery%^aBleak House : a
    novel^bby Charles Dickens

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

210  PARALLEL TITLE AND STATEMENT OF RESPONSIBILITY

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Parallel title
	^b  Statement of responsibility

RULES FOR ENTRY

1.  If the title is given on the title page in another language (besides the one entered in field 200), it may be entered in subfield a.

2.  Separate the subtitle, if any, by means of a space, colon and space.

3.  Enter the statement of responsibility associated with the parallel title in subfield b.  This consists of any name(s) or phrase(s) relating to persons responsible for the intellectual or artistic content of the document, or to corporate bodies from which the content emanates.  Follow the form and sequence of the original, but not necessarily the punctuation or capitalization.

4.  If more than one parallel title for a document is recorded, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aCastell Caerffili, Morgannwg Ganol   [main title is in English]

2.  ^aMéthodes d'analyse des graisses et huiles fixes%^aUntersuchungs verfahren für Fette und Fettöle  [main title is in English. Parallel
                                 titles in French and German]

3.  ^aNua-bhàrdachd Ghàidhlig : duanaire da-theagach^ble Somhairle McGill-Eain...[et al.]; deasaichte le roimh-radha aig Domhnall MacAmhlaigh                          [main title is in English]

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

230  OTHER TITLE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Other variant title

RULES FOR ENTRY

1.  Any other title or part of a title for which it is useful to provide access may be entered here.  This may include spine titles, cover titles, added title-page titles, running titles, or subtitles which also appear as part of subfield a in field 200.

EXAMPLES

1.  ^aHighlands and Islands comprehensive transport timetable
							[Spine title.  Main title is 
							"Getting around the Highlands &
							Islands"]

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

240  UNIFORM TITLE

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Uniform title
	^b  Number of part(s)
	^c  Name of part(s)
	^d  Form subheading
	^e  Language of item (as part of uniform title)
	^f  Version
	^g  Date of version

RULES FOR ENTRY

1.  The purpose of uniform titles is to bring together different editions or versions of the same work which would otherwise be separated under their own titles.  The most common form of uniform title is the original title of a translated work.  "Collective titles", used to order entries in a catalogue or bibliography when there are large numbers of works under the same heading, may also be entered here.

2.  Enter the uniform title itself (without additional qualifiers such as date, form subheading, etc.) in subfield a.

3.  When the item consists of one or more numbered parts of the work identified by the uniform title, enter the designation and number(s) of the part(s) in subfield b and/or the name(s) of the part(s) in subfield c.

4.  If required, a term may be entered in subfield d to distinguish the form of the item.

5.  If the language is required as part of the uniform heading, it should be entered in subfield e.

6.  A word or phrase indicating the version of the work included in the item may be entered in subfield f.

7.  The version of the work included in the item may be identified by its original date of publication.  This should be entered in subfield g.

EXAMPLES

1.  ^aBible^cN.T.^eFrench^dSelections
						[Title of item is "Le premier Nöel"]

2.  ^aKoran^cJuz' 'Amma

3.  ^aBφrnene ved Yangtze Kiang^eEnglish
						[Title of book is "Children of the 
						Yangtze River"]

4.  ^a[Treaties, etc.]		[Used to bring together treaties or
						other agreements under the name of a
						country.]

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

260  EDITION STATEMENT AND STATEMENT OF RESPONSIBILITY

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS

	^a  Edition statement
	^b  Statement of responsibility

RULES FOR ENTRY

1.  Enter the details of the edition in subfield a.  This should normally be as given in the item.

2.  Standard abbreviations may be used, e.g. "ed." for edition and "rev." for revised.  Numbered editions may be converted from script to numeric form.

3.  Editions may be denoted numerically, chronologically, or geographically, or may relate to the physical form of the item.

4.  The details of any persons or corporate bodies responsible for the intellectual or artistic content of this particular edition may be entered in subfield b.

EXAMPLES

1.	^a5th ed. rev.				[Document states "Fifth edition 
							revised"]

2.	^a2nd ed^bby A.B. Piternick	[1st ed. was edited by John C.N.
							Slater]
3.	^aMusic ed.

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

300  NAME OF PERSON

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Family name
	^b  Forenames
	^c  Additional elements to name
	^d  Date(s)
	^f  Role (non-coded)

RULES FOR ENTRY

1.  Enter the name(s) of person(s) responsible for or contributing to the creation of the intellectual or artistic content of the document.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that.  If you do not have an authority file, enter the name following the rules in Section 10.8.

3.  Additional elements of the name, e.g. honorific titles, words indicating family relationships, or the term 'pseudonym', may be entered in subfield c.  It is not usual to include titles like 'Mr', 'Mrs', 'Señor', etc., when following AACR2, except that 'Mrs' and its equivalents in other languages may be used for a married woman known by her husband's name.

4.  A date or dates relating to the person (e.g. to distinguish persons with the same name) may be entered in subfield d.

5.  The function of the person in relation to the item for which he/she is responsible may be entered in subfield f.

6.  If there are several persons responsible for or contributing to a document, enter their names in repeated fields (separated by percent signs).

EXAMPLES

1.	^aJones^bJohn^d1942-

2.	^aWatson^bA.G.^feditor

3.	^aMarivaux^bPierre Carlet de Chamblain de

4.	^aLee^bHon-ling

5.	^aMujica Lainez^bManuel

6.	^aAmat i de Ferrer^bAgusti

7.	^aSantana^bPaulo Henrique de Assis

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

310  NAME OF CORPORATE BODY

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^g  Role (non-coded)
	^x  Acronym

RULES FOR ENTRY

1.  Enter here the name of a corporate body responsible for or contributing to the creation of the intellectual or artistic content of a document.

2.  A corporate body is any organization or group of persons identified by a name.

3.  The name of a meeting that is a subordinate part of a corporate body should be regarded as a meeting, and entered in field 320.

4.  Enter the name as you would in the heading on a catalogue card.  If you have a corporate name authority file, then be consistent with that.  If you do not have an authority file, enter the name according to the rules in Section 11.

5.  In general, the institution should be entered under its own name.  This should be entered in subfield a.  However, in certain cases the Anglo-American Cataloguing Rules require it to be entered as a subheading under the name of the parent body (see section 11).  In these cases the parent body should be entered in subfield a and the subordinate body should be entered in subfield b.  If more than one level in the hierarchy needs to be given in subfield b, separate the levels by a full stop and space.  (CDS/ISIS does not allow the ^b marker to be repeated.)

6.  It may be necessary to add further information to the name to aid in identification, e.g. when there is more than one institution with the same name, or the nature of the institution is not clear from the name.  The additional information should be entered in subfield c.

7.  The function of the corporate body in relation to the item for which it is responsible may be entered in subfield g.

8.  If the full form of name has been entered in subfield a, access can also be provided from an acronym by entering it in subfield x.

9.  If there are several corporate bodies responsible for or contributing to the document, enter their names in repeated fields (separated by percent signs).

EXAMPLES

1.	^aUnesco^gSponsor

2.	^aInternational Geographical Union^bCommission on Geographical 
	Education

3.	^aUniversiteit van Amsterdam^bEuropa Instituut

4.	^aInstituto Latinoamericano de Investigaciones Sociales

5.	^aMusée des beaux-arts^cBéziers, France

6.	^aInternational Monetary Fund^xIMF

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

320  NAME OF MEETING

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^e  Country
	^g  Location of meeting
	^i  Date of meeting (in free format)
	^j  Number of meeting

RULES FOR ENTRY

1.  Enter here the name of a meeting responsible for or contributing to the creation of the intellectual or artistic content of a work contained in the document.

2.  A meeting is any occasional group: it includes congresses, symposia, conferences, festivals, exhibitions, workshops, etc.

3.  The name of a meeting that is a subordinate part of a corporate body should be entered here.

4.  Enter the name as you would in the heading on a catalogue card.  If you have a meeting name authority file, then be consistent with that.  If you do not have an authority file, enter the name as below.

5.  Enter the name of the meeting, as found on the item, in subfield a.  Omit terms indicating the frequency of the meeting, such as "annual" or "biennial".  Do not enter the number of the meeting, e.g. "second", here: it should be entered in subfield j.  Do not enter the year of the meeting here: it should be entered in subfield i.

6.  If the meeting name contains the name of a subordinate body, enter the subordinate body's name in subfield b.

7.  It may be necessary to add further information to the name to aid in identification, e.g. when there is more than one meeting with the same name, or it is not clear from the name that it relates to a meeting.  This additional information should be entered in subfield c.

8.  The country in which the meeting was held may be entered in subfield e.  Use one of the codes as outlined in Section 13.

9.  Enter the name of the place or other location in which the meeting was held in subfield g.  Give the place name in its English form (alternatively in your preferred language) if there is one in general use.

10.  Enter the year(s) of the meeting in subfield i.  Add the specific dates if it is necessary to distinguish between two or more meetings held in the same year.

11.  If the meeting belongs to a numbered series, enter the number in its English form, e.g. 3rd, 7th (alternatively in your preferred language) in subfield j.

12.  If there are several meetings responsible for or contributing to the work, enter their names in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aInternational Symposium on Bibliographic Exchange Formats
^gTaormina, Italy^i1978^eIT

2.  ^aInternational Conference on Co-operative Thrift and Credit^gRio de Janeiro, Brazil^i1977^j4th

3.  ^aMaterials Research Society^bMeeting^gBoston, Mass.^i1981

4.  ^aOlympic Games^gMontreal, Quebec^i1976^j21st^eCA

5.  ^aAssociation pour le Perfectionnement des Approvisionnements dans les Services Publics^bSession d'études^i1989^j82nd^eFR

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

400  PLACE OF PUBLICATION AND PUBLISHER

This field is:

-  Mandatory (except for analytics)
-  Not repeatable

SUBFIELDS

	^a  Place of publication
	^b  Name of publisher
	^d  Country of publisher

RULES FOR ENTRY

1.  The place (normally the town), or one of the places, where the document is published may be entered in subfield a.  If you wish to record more than one place, separate the places with a semi-colon and space.  (CDS/ISIS will not allow the ^a marker to be repeated.)

2.  Enter the name of the publisher as shown on the item in subfield b.  The name may be shortened provided that this does not cause ambiguity.

3.  The country or countries where the publisher is located may be entered in subfield d.  Use one of the codes as outlined in Section 13.  If there is more than one country, separate the codes with a comma and space.  (CDS/ISIS will not allow the ^d marker to be repeated.)

EXAMPLES

1.	^aMontvale, NJ^bAFIPS Press^dUS

2.	^aLondon; Oxford; Melbourne; Delhi^bOxford University Press

3.	^aCaracas^bUnesco

4.	^aRennes^bOuest France

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

440  DATE OF PUBLICATION

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS

	^a  Date in formalized form
	^b  Date in non-formalized form

RULES FOR ENTRY

1.  Enter here the date of publication or, if not available, the date of copyright or approximate date of publication.

2.  If the document being described is an analytic in a monograph, do not enter the date of the monograph here but in field 1440.  If the document is an analytic in a serial, enter the date of the relevant issue of the serial here.

3.  Enter the date in subfield a in accordance with ISO 8601, i.e. four figures for the year, two for the month, and two for the day.  If the month or day are not known, use 00.  Any digit may be replaced by a question mark when an approximate date is given.

4.  If the document was published over a range of dates, separate the beginning and end dates with a hyphen.

5.  If it is desired to enter a date not in the ISO format, e.g. a non-Gregorian date, or a date including a term such as 'Winter', enter the date as it appears on the item in subfield b.  Do not use both subfield a and subfield b in the same record.

EXAMPLES

1.	^a19890000		[Date appears on item as 1989]

2.	^a196?0000		[Last figure of year uncertain]

3.	^a19870900		[Date appears as September 1987]

4.	^a19850000-19870000	[Monograph published in three volumes from 
					1985 to 1987]

5.	^bSpring 1989

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

460  PHYSICAL DESCRIPTION

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Number of pieces and designation
	^b  Other descriptive details
	^c  Dimensions
	^d  Accompanying material

RULES FOR ENTRY

1.  The number of volumes in the document and/or the number of pages may be entered in subfield a.

2.  Other physical data about the document (apart from dimensions) may be entered in subfield b.  For example, details of the illustrations in a book may be recorded here.

3.  The height of the document may be entered in subfield c.

4.  Any item accompanying the document being described, issued at the same time as that item and intended to be used with it, may be recorded in subfield d.

EXAMPLES

1.	^a2 vols.^c25cm

2.	^a257p^bill

3.	^a100p, [4]p of plates^bill, facsims, maps^c22cm

4.	^a257p^bill^c23cm^d4 slides

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

465  PRICE AND BINDING

This field is:

-  Optional
-  Repeatable

SUBFIELDS
	^a  Price
	^b  Binding

RULES FOR ENTRY

1.  The price, or other terms of availability, of the document may be entered in subfield a.  The currency may be represented by a symbol in accordance with ISO 4217, reproduced in Section 14.

2.  The binding to which the price shown in subfield a refers may be entered in subfield b.  The abbreviation "pbk." may be used for paperback.

3.  If there are several prices or terms of availability, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aUSD 10^bpbk          [Price is 10 US dollars for paperback 
                           edition]

2.  ^aPrivate circulation

3.  ^aFree

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

480  SERIES STATEMENT AND ASSOCIATED STATEMENT OF RESPONSIBILITY

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Series statement
	^b  Statement of responsibility associated with series statement
	^c  Numbering within series
	^d  ISSN

RULES FOR ENTRY

1.  The title or other designation of a series to which the document belongs may be entered in subfield a.  The form and sequence should be as found on the document, although the document need not be followed for punctuation or capitalization.

2.  The person(s) or corporate body/bodies responsible for or contributing to the creation of the series may be entered in subfield b.  The form and sequence should be as found on the document, although the item need not be followed for punctuation or capitalization.

3.  The number or other identification of the document, together with its designation if any (e.g. no., vol., part) within the series, should be entered in subfield c.  Numbers recorded as words should be converted to Arabic numerals.

4.  The ISSN of the series may be entered in subfield d.

5.  If there are several series statements, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aInaugural lectures^bUniversity of Oxford

2.	^aSymposia : new series^bCiba Foundation^c37

3.	^aSozialmedizinische und pädagogische Jugendkunde^c11

4.	^aLecture note series^bLondon Mathematical Society^c16^d0076-0552

_____________________________________________________________________

4  DOCUMENTS (ANALYTICS)
_____________________________________________________________________

490  PART STATEMENT

This field is:

-  Mandatory (for analytics)
-  Repeatable

SUBFIELDS

	^a  Volume/part numeration and designation
	^b  Pagination defining a part
	^c  Other data defining a part

RULES FOR ENTRY

1.  These data should be entered if the item being described is a "component part" as defined in Section 4.1.

2.  The designation, pagination, etc. which defines the part should be entered in this field.

3.  At least one of the subfields a, b or c should be used.

4.  The designation of the volume, issue, part, etc. should be entered in subfield a.

5.  Pagination which defines the limits of the component part should be entered in subfield b.

6.  Any data which define the part, other than volume/part numeration, pagination, or date, should be entered in subfield c.

7.  If there are several part designations, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.    ^aVol. 14

2.    ^b120-129                   [Contribution occupying pages 120
                                  to 129 in a monograph]

3.    ^aVol. 36, no. 3^b255-260   [Record is for an article which
                                  appears on pages 255 to 260 in vol.
                                  36, number 3 of a periodical.]

4.    ^cSupplement                [Record is for the supplement to a
                                  monograph.]

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

500  NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  This field may be used to record any kind of note about the document for which no specific field is provided.

2.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aParallel Spanish text and English translation

2.	^a'... published under the auspices of the Dumbarton District Quality of Life Experiment' - title page verso

3.	^aThesis (Ph.D.) - University of the West Indies, 1987

4.	^aPierced for binder

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

510  NOTE ON BIBLIOGRAPHIC RELATIONSHIP

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  A note may be entered in subfield a describing a bibliographic relationship between this document and another item.

2.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aPrevious ed.: 1980

2.	^aOriginally published: London: Evans Bros, 1955

3.	^a'... re-edited selection of articles ... in "Architectural Record" during the last few years' - Preface

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

530  CONTENTS NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^ a  Contents note

RULES FOR ENTRY

1.  A description or list of the works, parts or pieces contained in the document may be entered in subfield a.

2.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aContents: Mazeppa / by Henry Milner - The factory lad / by John  Walker - Nick of the woods / by Louisa Hamblin - The drunkard / by 
William Henry Sedley - The Corsican brothers / by Dion Boucicault - 
The lady of the Camellias / adapted from Alexandre Dumas fils - London by night

2.  ^aIncludes the text of the Paris Agreement, 1973

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

550  LEGAL CITATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Legal citation

RULES FOR ENTRY

1.  This field may be used to record a citation to any law referred to in the document being recorded.

2.  If there are several citations, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aCopyright Act 1911
	^aCopyright Act 1956

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

600  ABSTRACT

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Abstract
	^l  Language

RULES FOR ENTRY

1.  A brief description of the content of the document may be entered in subfield a.

2.  <.....>  may be used within the abstract to delimit index terms (for searching purposes).

3.  If it is desired to include more than one abstract (e.g. in different languages), enter them in repeated fields (separated by percent signs). Enter after each repeat the code for the language in ^l.

EXAMPLE

1.  ^a<Cultural heritage> includes not only monuments, sites and
    movable objects to be collected by <museums>, but includes the
    origins, meanings and symbols conveyed by art and literature,
    languages and <oral traditions>, <arts and crafts> and <folklore>
    beliefs, rites and games, in the sense that cultural heritage
    embraces both the physical presences and <spiritual values> of
    <artists> and <writers>.

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

610  CLASSIFICATION SCHEME NOTATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Notation

RULES FOR ENTRY

1.  A classification number or code corresponding to the subject of the document may be entered in subfield a.

2.  If more than one number, etc., is used, enter them in repeated fields (separated by percent signs).

EXAMPLES
1.	^a400				[Number for linguistics
						in Dewey Classification]

2.	^a342.83				[Number for women in society
						in Universal Decimal Classification]

_____________________________________________________________________

4  DOCUMENTS
_____________________________________________________________________

620  SUBJECT DESCRIPTOR

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Subject descriptor

RULES FOR ENTRY

1.  A descriptor corresponding to the subject of the document may be entered in subfield a.

2.  If more than one descriptor is used, enter them in repeated fields (separated by percent signs).

3.  The descriptors may be controlled according to a subject system, e.g. selected from a thesaurus or a list of subject headings.

EXAMPLES

1.   ^aCommunication policy%^aSocial change%^aCommunication impact

2.   ^aOral tradition%^aTaboo%^aSongs
_____________________________________________________________________

4  DOCUMENTS  (ANALYTICS)
_____________________________________________________________________

1015  BIBLIOGRAPHIC LEVEL - HOST ITEM

This field is:

-  Mandatory (for analytics)
-  Not repeatable

NB  The subfield identifier is not used in this fixed length subfield in this implementation. 

	Bibliographic level

RULES FOR ENTRY

1.  One of the following codes should be entered to denote the bibliographic level of the host item:

If the correct worksheet is used (CLTAS, CLTAM), the appropriate code is the default and pressing carriage return will cause the correct code to be entered in the field.

	m		Monograph
	s		Serial

EXAMPLES

1.	m

2.	s

_____________________________________________________________________

4 DOCUMENTS  (ANALYTICS)
_____________________________________________________________________

1200  TITLE AND STATEMENT OF RESPONSIBILITY - HOST ITEM

This field is:

-  Mandatory  (for analytics)
-  Repeatable

SUBFIELDS

	^a  Title
	^b  Statement of responsibility associated with title

RULES FOR ENTRY

1.  Enter the title of the host item in subfield a.

2.  Separate the subtitle, if any, by means of a space, colon and space.

3.  You may enter the statement of responsibility in subfield b.  This consists of any name(s) or phrase(s) relating to persons responsible for the intellectual or artistic content of the document, or to corporate bodies from which the content emanates.  Follow the form and sequence of the original, but not necessarily the punctuation or capitalization.

EXAMPLES

1.	^aText retrieval : the state of the art^bedited by Peter Gillman

2.	^aNature

3.	^aACM transactions on database systems

_________________________________________________________________

4  DOCUMENTS  (ANALYTICS)
_________________________________________________________________

1260  EDITION AND STATEMENT OF RESPONSIBILITY - HOST ITEM

This field is:

-  Mandatory  (for analytics)
-  Repeatable

SUBFIELDS

	^a  Edition statement
	^b  Statement of responsibility

RULES FOR ENTRY

1.  Enter the details of the edition of the host item in subfield a.  These should normally be as given in the item.

2.  Standard abbreviations may be used.  Numbered editions may be converted from script to numeric form.

3.  Editions may be denoted numerically, chronologically, or geographically, or may relate to the physical form of the item.

4.  Enter in subfield b the details of any persons or corporate bodies responsible for the intellectual or artistic content of this particular edition.

EXAMPLES

1.	^a3rd ed

_____________________________________________________________________

4  DOCUMENTS  (ANALYTICS)
_____________________________________________________________________

1300  NAME OF PERSON - HOST ITEM

This field is:

-  Mandatory  (for analytics)
-  Repeatable

SUBFIELDS

	^a  Family name
	^b  Forenames
	^c  Additional elements to name
	^d  Date(s)
	^f  Role (non-coded)

RULES FOR ENTRY

1.  This field will not normally be used when the host item is a serial.

2.  Enter the name(s) of the editor(s) of the host item.

3.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that.  If you do not have an authority file, enter the name following the rules in Section 10.8.

4.  Additional elements of the name, e.g. honorific titles, words indicating family relationships, or the term 'pseudonym', may be entered in subfield c.  It is not usual to include titles like 'Mr', 'Mrs', 'Señor', etc., when following AACR2, except that 'Mrs' and its equivalent in other languages may be used for a married woman known by her husband's name.

5.  A date or dates relating to the person (e.g. to distinguish persons with the same name) may be entered in subfield d.

6.  The function of the person in relation to the item for which he/she is responsible may be entered in subfield f.

7.  If there are several persons responsible for or contributing to the creation of the host item, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aJones^bJohn^d1942-

2.	^aWatson^bA.G.^feditor

3.	^aMarivaux^bPierre Carlet de Chamblain de

4.	^aLee^bHon-ling%^aChin^bKin-wah

5.	^aMujica Lainez^bManuel

_____________________________________________________________________

4  DOCUMENTS  (ANALYTICS)
_____________________________________________________________________

1310  NAME OF CORPORATE BODY - HOST ITEM

This field is:

-  Mandatory  (for analytics)
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^g  Role (non-coded)
	^x  Acronym

RULES FOR ENTRY

1.  Enter here the name of a corporate body from which the host item emanates.

2.  A corporate body is any organization or group of persons identified by a name.

3.  The name of a meeting that is a subordinate part of a corporate body should be regarded as a meeting, and entered in field 1320.

4.  Enter the name as you would in the heading on a catalogue card.  If you have a corporate name authority file, then be consistent with that.  If you do not have an authority file, enter the name according to the rules in Section 11.

5.  In general, the corporate body should be entered under its own name.  This should be entered in subfield a.  However, in certain cases the Anglo-American Cataloguing Rules require it to be entered as a subheading under the name of the parent body (see section 11).  In these cases the parent body should be entered in subfield a and the subordinate body should be entered in subfield b.  If more than one level in the hierarchy needs to be given in subfield b, separate the levels by a full stop and space.  (CDS/ISIS does not allow the ^b marker to be repeated.)

6.  It may be necessary to add further information to the name to aid in identification, e.g. when there is more than one institution with the same name, or the nature of the institution is not clear from the name.  The additional information should be entered in subfield c.

7.  The function of the corporate body in relation to the item for which it is responsible may be entered in subfield g.

8.  If the full form of name has been entered in subfield a, access can also be provided from an acronym by entering it in subfield x.

9.  If there are several corporate bodies responsible for the host item, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aUnesco^gSponsor

2.	^aInternational Geographical Union^bCommission on Geographical 
	Education

3.	^aUniversiteit van Amsterdam^bEuropa Instituut

4.	^aInstituto Latinoamericano de Investigaciones Sociales

5.	^aInternational Monetary Fund^xIMF

_____________________________________________________________________

4  DOCUMENTS  (ANALYTICS)
_____________________________________________________________________

1320  NAME OF MEETING

This field is:

-  Mandatory  (for analytics)
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^e  Country
	^g  Location of meeting
	^i  Date of meeting (in free format)
	^j  Number of meeting

RULES FOR ENTRY

1.  If the host item emanates from a meeting (e.g. it is a conference proceedings) enter here the name of the meeting.

2.  A meeting is any occasional group: it includes congresses, symposia, conferences, festivals, exhibitions, workshops, etc.

3.  The name of a meeting that is a subordinate part of a corporate body should be entered here.

4.  Enter the name as you would in the heading on a catalogue card.  If you have a meeting name authority file, then be consistent with that.  If you do not have an authority file, enter the name as below.

5.  Enter the name of the meeting, as found on the item, in subfield a.  Omit terms indicating the frequency of the meeting, such as "annual" or "biennial".  Do not enter the number of the meeting, e.g. "second", here.  It should be entered in subfield j.

6.  If the meeting name contains the name of a subordinate body, enter the subordinate body's name in subfield b.

7.  It may be necessary to add further information to the name to aid in identification, e.g. when there is more than one meeting with the same name, or it is not clear from the name that it relates to a meeting.  This additional information should be entered in subfield c.

8.  The country in which the meeting was held may be entered in subfield e.  Use one of the codes as outlined in Section 13.

9.  Enter the name of the place or other location in which the meeting was held in subfield g.  Give the place name in its English form (alternatively in your preferred language) if there is one in general use.

10.  Enter the year(s) of the meeting in subfield i.  Add the specific dates if it is necessary to distinguish between two or more meetings held in the same year.

11.  If the meeting belongs to a numbered series, enter the number in its English form, e.g. 3rd, 7th (alternatively in your preferred language) in subfield j.

12.  If there are several meetings responsible for the host item, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aInternational Symposium on Bibliographic Exchange Formats
^gTaormina, Italy^i1978^eIT

2.  ^aInternational Conference on Co-operative Thrift and Credit^gRio
 de Janeiro, Brazil^i1977^j4th

3.  ^aMaterials Research Society^bMeeting^gBoston, Mass.^i1981

4.  ^aOlympic Games^gMontreal, Quebec^i1976^j21st^eCA

5.  ^aAssociation pour le Perfectionnement des Approvisionnements dans les Services Publics^bSession d'études^i1989^j82^eFR

_____________________________________________________________________

4  DOCUMENTS  (ANALYTICS)
_____________________________________________________________________

1400  PLACE OF PUBLICATION AND PUBLISHER - HOST ITEM

This field is:

-  Mandatory  (for analytics in monographs)
-  Not repeatable

SUBFIELDS

	^a  Place of publication
	^b  Name of publisher
	^d  Country of publisher

RULES FOR ENTRY

1.  This field will not normally be used when the host item is a serial.

2.  The place (normally the town), or one of the places, where the item is published may be recorded in subfield a.  If you wish to record more than one place, separate the places with a semi-colon and space.  (CDS/ISIS will not allow the ^a marker to be repeated.)

2.  Enter the name of the publisher as shown on the item in subfield b.  The name may be shortened provided that this does not cause ambiguity.

3.  The country or countries where the publisher is located may be entered in subfield d.  Use one of the codes as outlined in Section 13.  If there is more than one country, separate the codes with a comma and space.  (CDS/ISIS will not allow the ^d marker to be repeated.)

EXAMPLES

1.	^aMontvale, NJ^bAFIPS Press^dUS

2.	^aLondon; Oxford; Melbourne; Delhi^bOxford University Press

3.	^aCaracas^bUnesco

_____________________________________________________________________

4  DOCUMENTS   (ANALYTICS)
_____________________________________________________________________

1440  DATE OF PUBLICATION - HOST ITEM

This field is:

-  Mandatory (for analytics in monographs)
-  Not repeatable

SUBFIELDS

	^a  Date in formalized form
	^b  Date in non-formalized form

RULES FOR ENTRY

1.  If the host item is a serial, do not use this field but enter the date in field 440.

2. If the host item is a monograph, enter the date of publication of the host item here.

3.  If the date of publication is not available, enter the date of copyright or approximate date of publication.

4.  Enter the date in subfield a in accordance with ISO 8601, i.e. four figures for the year, two for the month, and two for the day.  If the month or day are not known, use 00.  Any digit may be replaced by a question mark when an approximate date is given.

5.  If the host item indicates a range of dates, separate the beginning and end dates with a hyphen.

6.  If the date cannot be converted to the ISO format, e.g. a non-Gregorian date, or a date including a term such as 'Winter', enter the date as it appears on the item in subfield b.  Do not use both subfield a and subfield b in the same record.

EXAMPLES

1.	^a19850000			[Date appears on item as 1985]

2.	^a196?0000			[Last figure of year uncertain]

3.	^a19870900			[Date appears as September 1987]

4.	^bSpring 1989			[Date appears as Spring 1989]

5. CREATING RECORDS FOR PERSONS

To create records for persons select the worksheet CLTPE.

____________________________________________________________________

5  PERSONS
_____________________________________________________________________

022  DATE ENTERED ON FILE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD
	^a  Date

RULES FOR ENTRY

1.  Enter here the date when the record was added to the file.

2.  If the program DATE.PAS has been installed, the date can be entered by pressing function key 9.

3.  The date should be constructed in accordance with ISO 8601, i.e. the year in full, two figures for the month, and two figures for the day.  Do not use any punctuation or spaces within the date.

4.  If your organization distributes records to other organization, it may choose to substitute the date of distribution in this field.

5.  If your organization takes records from other organizations, this field should contain the date that the record was originally created, if that is available.  Otherwise it may contain the date that the record was entered into your system.

EXAMPLES

1.	^a19870917				[17th September, 1987]

2.	^a19901130				[30th November, 1990]

NOTE FOR SYSTEMS ANALYSTS

If necessary, add an extra subfield to allow for greater detail, e.g. when records are taken from other organizations.

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

040  WORKING LANGUAGES

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Language

RULES FOR ENTRY

1.  The language or languages in which the person is fluent may be entered here.

2.  Use the language codes from Section 12.

3.  If the person is fluent in more than one language, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aspa					[person is fluent is Spanish]

2.  ^adut%^aeng%^ager		[person is fluent in Dutch, English and
						German]

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

062  TYPE OF FACTUAL INFORMATION (RECORD TYPE)

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

NB  The subfield identifier is not used in this fixed length field in this implementation.

	  Type of factual information

RULES FOR ENTRY

1.  For PERSONS records, this field should contain the value PER.  Press RETURN to accept the default value.

EXAMPLE

1.   PER

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

300  NAME OF PERSON

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS
	^a  Family name
	^b  Forenames
	^c  Additional elements to name
	^d  Date(s)

RULES FOR ENTRY

1.  Enter the name of the person to whom this record relates.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that,  but add the person's title in subfield c.  If you do not have an authority file, enter the name following the rules in Section 10.8.

3.  The form of title may be entered in subfield c.  It should be that which would be used in addressing a letter to the person.

4.  The year of birth followed by a hyphen may be entered in subfield d.  If it is desired to include deceased persons in the file, the date of death may be added.

EXAMPLES

1.	^aJones^bJohn^cDr^d1942-

2.	^aWatson^bA.G.^cProf.

3.	^aPasteur Valléry-Radot^bLouis^cM.

4.	^aLee^bHon-ling^c1930-

5.	^aGarcia Campos^bJuan^cSr

6.	^aAmat i de Ferrer^bAgusti^cDr^d1910-1985

7.	^aSchwabe^bGünther^cHerr

8.	^aSantana^bPaulo Henrique de Assis^cDr

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

301  SEX

This field is:

-  Optional
-  Not repeatable

SUBFIELD

	^a  Sex

RULES FOR ENTRY

1.  The person's sex may be entered in subfield a as "m" for male or "f" for female.

EXAMPLES

1.   ^af

2.   ^am

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

430  ADDRESS

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Building / institution
	^b  Street address
	^c  Locality, town or city
	^d  State, county or region
	^e  Country
	^f  Postal code
	^g  Post Office Box number
	^h  Telephone number
	^i  Telegraphic address
	^j  Telex number
	^k  FAX number
	^l  Electronic mail address

RULES FOR ENTRY

1.  A contact address for the person may be entered here.  It may be a work or home address as appropriate.

2.  The order of items in the address varies between countries.  Enter the subfields in the order in which they should be written on an envelope.

3.  Enter the name of the building (and office, floor, etc.) and/or the name of the institution in subfield a, if required as part of the person's address.

4.  Enter the street and house/building number in subfield b.  The number may come before or after the street according to national practice.

5.  Enter the town, village or locality in subfield c.  If more than one place needs to be included, separate each by means of a comma and space.

6.  Enter the name of the state, county or region, if needed as part of the address, in subfield d.  Abbreviations may be used if recognized by the postal authority.

7.  Enter the name of the country, in the form used for postal purposes, in subfield e.

8.  Enter the postal code in subfield f.

9.  If the address is for a Post Office Box Number, enter this in subfield g.

10.  Enter the telephone number of the person (with extension if known) in subfield h.  Use the international form of the number.  This begins with a plus sign, indicating that the caller should add a prefix signifying an international call.  Spaces may be used to make the number more legible.

11.  Enter the telegraphic address in subfield i.

12.  Enter the telex number, with Answerback code, in subfield j.

13.  Enter the facsimile number in subfield k.  Use the same form as in rule 10.

14.  Enter any electronic mail address(es) in subfield l.  The name of the system should be given, followed by the address, number or code.  If there is more than one address, separate each with a comma and space.

EXAMPLES

1.  ^aHotel de Sully^b62 rue Sainte-Antoine^cParis^f75004^eFrance
^h+33 42-74-22-22

2.  ^aDepartment of Chemistry, Leicester University^bUniversity
Road^cLeicester^eEngland^fLE1 7RH^h+44 533 522522 ext. 5478
^j347250 LEICUN G^k+44 533 522200^lJANET: jes@uk.ac.le.vax

4.  ^bBallester, 8^cBarcelona^eSpain^f08023

5.  ^aESCAP^bJI. Merdeka 145^cBogor^f16111^eIndonesia^h+251 26290
^iLITANAN BOGOR^j48369 AARDIA

6.  ^aUIE^f2000^cHamburg 13^gPostfach 132153^bFeldbrunnenstrasse 58
^eWest Germany^h+49 40 447843^j2164146 UIE D

7.  ^aUnited Nations University, Toho Seimei Building (29th floor)
^b15-1 Shibuya 2-chome, Shibuya-ku^cTokyo^f150^eJapan^h+81 3 499 2811
^iUNATUNIV TOKYO^j25442 J^k+81 3 499 2828^lECONET: UNU, BITNET: 
DELLATA@JPNUNUOO

8.  ^aInstitute of Development Studies, University of Sussex
^cBrighton^eEngland^fBN1 9RE^h+44 273 606261^iDEVELOPMENT BRIGHTON
^j877997 IDSBTN G^k+44 273 678420^lJANET: qdfd0@uk.ac.sussex.cluster

9.	^aSchool of Information and Computer Science, Georgia Institute of Technology^cAtlanta^dGA^f30332^eUSA

NOTE FOR SYSTEMS ANALYSTS

Different countries have different preferred orders for elements in an address.  If the database is used to produce address labels, a print format should be developed which bases its order of elements on the country name.  In this case special attention should be made to enter country names consistently.

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

500  NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  This field may be used to record any relevant information about the person for which no specific field is provided.

2.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aMarried.  3 children

2.	^aUnable to travel by air

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

610  CLASSIFICATION SCHEME NOTATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Notation

RULES FOR ENTRY

1.  One or more classification numbers, codes, etc., which correspond to the person's area(s) of expertise may be entered in subfield a.

2.  If more than one number, etc., is used, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^a400				[Number for linguistics
						in Dewey Classification]

2.	^a342.83				[Number for women in society
						in Universal Decimal Classification]

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

620  SUBJECT DESCRIPTOR

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Subject descriptor

RULES FOR ENTRY

1.  One or more descriptors which correspond to the person's area(s) of expertise may be entered in subfield a.

2.  If more than one descriptor is used, enter them in repeated fields (separated by percent signs).

3.  The descriptors can be controlled according to a subject system, e.g. selected from a thesaurus or a list of subject headings.

EXAMPLES

1.	^aTelecommunications%^aIntegrated Services Digital Network
	%^aCommunications protocols

2.   ^aOral tradition%^aTaboo%^aSongs
_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

800  NATIONALITY

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Nationality

RULES FOR ENTRY

1.  The person's nationality may be entered in subfield a using one or more codes as outlined in Section 13.

2.  If the person has dual or multiple nationality, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.	^aGT						[Guatemalan]

2.	^aAU%^aGB					[Australian and British]

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

810 EDUCATIONAL QUALIFICATIONS

This field is:

-  Optional
-  Not repeatable

SUBFIELD

	^a  Educational qualifications

RULES FOR ENTRY

1.  The formal educational qualifications of the person may be entered in subfield a.

2.   Details of the subject(s), awarding institution (in brief form) and year may be added if required.

3.  If the person has more than one qualification, separate each with a comma and space.

EXAMPLES

1.	^aBSc, PhD					[person has BSc and PhD 
								degrees]

2.	^aLic. (Univ. de Barcelona, 1985)	[Licenciado, Universidad de 
								Barcelona awarded 1985]

3.	^aBA (Chemistry, Oxford, 1972) 	[BA in chemistry, awarded by
								University of Oxford, 1972]

_____________________________________________________________________

5  PERSONS
_____________________________________________________________________

820  EXPERIENCE OF PERSON

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Dates
	^b  Institution
	^c  Responsibilities
	^d  Additional information
	^e  Country

RULES FOR ENTRY

1.  Details of the present and relevant former positions held by the person may be entered in this field.

2.  For each position held, enter the start and end years, separated by a hyphen, in subfield a.  Enter the name of the institution in subfield b.  Enter the title of the position in subfield c and, if desired, brief details of responsibilities and number of staff supervised.  Any additional information may be added in subfield d.  The country of the position may be shown in subfield e by means of a code as outlined in Section 13.

3.  If the person has held several positions, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^a1982-1985^bUniversity of Prague^cResearch Assistant^eCS%
^a1985-1989^bHarvard University^cProfessor^eUS%^a1989-^bCentre for
 Atomic Research, Bangkok^cDirector of Research (12 research 
staff)^dSalary 40,000 THB per month^eTH

2.  ^a1970-1984^bLe Monde^cScience Correspondent^eFR%^a1984-1989
^cFreelance technical author^eIT%^a1989-^bBritish Broadcasting 
Corporation^cScriptwriter^eGB

3.  ^a1989-^bPapeles y Tintas, S.A.^cDirector de mercadotecnia
 (formulation of distribution and sales strategies: 15 staff)^eVE

6. CREATING RECORDS FOR INSTITUTIONS

To create records for institutions select the worksheet CLTIN.

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

022  DATE ENTERED ON FILE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS
	^a  Date

RULES FOR ENTRY

1.  Enter here the date when the record was added to the file.

2.  If the program DATE.PAS has been installed, the date can be entered by pressing function key 9.

3.  The date should be constructed in accordance with ISO 8601, i.e. the year in full, two figures for the month, and two figures for the day.  Do not use any punctuation or spaces within the date.

4.  If your organization distributes records to other organization, it may choose to substitute the date of distribution in this field.

5.  If your organization takes records from other organizations, this field should contain the date that the record was originally created, if that is available.  Otherwise it may contain the date that the record was entered into your system.

EXAMPLES

1.	^a19870917				[17th September, 1987]

2.	^a19901130				[30th November, 1990]

NOTE FOR SYSTEMS ANALYSTS

If necessary, add an extra subfield to allow for greater detail, e.g. when records are taken from other organizations.

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

040  WORKING LANGUAGE

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Language

RULES FOR ENTRY

1.  The language or languages in which the institution operates may be entered here.

2.  Use the language codes from Section 12.

3.  If the institution operates in more than one language, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aspa				[institution operates in Spanish]
2.  ^adut%^afre		[institution operates in Dutch and
					French]
_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

062  TYPE OF FACTUAL INFORMATION (RECORD TYPE)

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS

NB  The subfield identifier is not used in this fixed length field in this implementation.

    Type of factual information

RULES FOR ENTRY

1.  For INSTITUTION records, this field should contain the value INS.

2.  Press RETURN to accept the default value.

EXAMPLE

1.   INS

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

064  TYPE OF INSTITUTION

This field is:

- Optional
- Repeatable

SUBFIELDS

	^a  Type of institution

RULES FOR ENTRY

1.  The following terms are suggested for recording the type of institution:

     Governmental
     Semi-governmental
     Statutory
     Public sector               [not one of above]
     Private
     University                  [or similar institution of higher
                                 education]
     University research centre  [Research centre closely
                                 associated with university]
     Academy/research council    [Institution attached to academy of
                                 science and/or national research
                                 centre or council]
     Non-production              [Research institution not integrated 
                                 with production, wholly or partly 
                                 serving a productive sector of the
                                 economy, a branch of industry or a 
                                 public service]
     Production                  [Research laboratory integrated with 
                                 production]

2.  If more than one term applies, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.     ^aGovernmental

2.     ^aSemi-governmental%^aResearch council
                                 [Semi-governmental institution 
                                 belonging to research council]

3.     ^aPrivate

4.     ^aPublic sector%^aUniversity
                                 [University supported by public 
                                 funding but with own charter]

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

300  OTHER PERSONNEL

This field is:

-  Optional
-  Repeatable

SUBFIELDS

     ^a  Family name
     ^b  Forenames or initials
     ^c  Additional elements to name
     ^f  Role (non-coded)

RULES FOR ENTRY

1.  Separate fields (391 and 392) are provided for the name(s) of the director of the institution and the contact person.  Use this field only if you wish to include the names of other people in the institution.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but add the person's role in subfield f.  If you do not have an authority file, enter the name following the rules in Section 10.

3. The position of the person within the institution may be entered in subfield f.

4.  If more than one person is recorded here, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.     ^aArmstrong^bChris^fTreasurer

2.     ^aPoncet^bJean-François^cM.^fINTERMAN Coordinator

3.     ^aDorofeyev^bV.^cMr^fProcurement Officer

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

310  NAME OF INSTITUTION

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^x  Acronym

RULES FOR ENTRY

1.  Enter here the name of the institution.  If you have a corporate name authority file, then be consistent with that.  If there is no authority file, enter the name according to rules in Section 11.

2.  In general, the institution should be entered under its own name.  This should be entered in subfield a.  However, in certain cases the Anglo-American Cataloguing Rules require it to be entered as a subheading under the name of the parent body (see Section 11).  In these cases the parent body should be entered in subfield a and the subordinate body should be entered in subfield b.  If more than one level in the hierarchy needs to be given in subfield b, separate the levels by a full stop and space.  (CDS/ISIS does not allow the ^b marker to be repeated.)

3.  It may be necessary to add additional information to the name to aid in identification, e.g. when there is more than one institution (perhaps in different countries) with the same name, or the nature of the institution is not clear from the name.  This additional information should be entered in subfield c.

4.  When the institution is well known by an acronym, but the full name is used in subfield a, the acronym may be entered in subfield x.

EXAMPLES

1.  ^aAmnesty International

2.  ^aInstituto Salvadoreño de Administracíon Municipal^bDepartamento
    de Cuscatalán

3.  ^aPunjab University^bDepartment of Agriculture

4.  ^aRegional Co-ordination Centre for Research and Development of
    Coarse Grains, Pulses, Roots and Tuber Crops^xCGPRT

5.  ^aUniversity of London^bSchool of Oriental and African Studies
    ^xSOAS

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

391  DIRECTOR OR HEAD OF INSTITUTION

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Family name
	^b  Forenames or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY

1.  The name of the director or head of the organization may be entered in this field.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10..

3.  The title which should be used in addressing a letter to that person may be entered in subfield c.

4.  In subfield f, enter the title of the person's position in the organization, if it is not "director".

5.  If there are joint heads, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aEl-Zanati^bA.G.^cMr^fChief

2.  ^aCastañón^bInés^fGerente

3.  ^aGurunlian^bJean^cMr^fOfficer-in-Charge

4.  ^aIzquierdo^bMaría Lourdes de

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

392  CONTACT PERSON

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Family name
	^b  Forename or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY

1.  The name of one contact person at the organization may be entered in this field, unless it is the same as the director entered in field 391.

2.  The contact person is the person to whom the address information in field 430 applies.

3.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

4.  In subfield c, enter the title which should be used in addressing a letter to that person.

5.  The title of the person's position in the organization may be entered in subfield f.

EXAMPLES

1.	^aLee^bHon-ling^cMr^fSystems manager

2.	^aKanchanasut^bKanchana

3.	^aWeatherwax^bJ.R.^cMr^fNutrition Officer

____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

430  ADDRESS

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Building/institution
	^b  Street address
	^c  Locality, town or city
	^d  State, county or region
	^e  Country
	^f  Postal code
	^g  Post Office Box number
	^h  Telephone number
	^i  Telegraphic address
	^j  Telex number
	^k  FAX number
	^l  Electronic mail address

RULES FOR ENTRY

1.  The address of the contact person may be entered here if one has been recorded in field 392.  Otherwise use the address of the head or director recorded in field 391.  Do not enter any other addresses from which the institution operates.

2.  The order of items in the address varies between countries.  Enter the subfields in the order in which they should be written on an envelope.

3.  Enter the name of the building (and office, floor, etc.) in subfield a, if required as part of the contact person's address.

4.  Enter the street and number (if any) in subfield b. The number may come before or after the street according to national practice.

5.  Enter the town, village or locality in subfield c.  If more than one place needs to be included, separate each by means of a comma and space.

7.  Enter the name of the state, county or region, if needed as part of the address, in subfield d.  Abbreviations may be used if recognized by the postal authority.

8.  Enter the name of the country, in the form used for postal purposes, in subfield e.

9.  Enter the postal code in subfield f.

10. If the address is for a Post Office Box Number, enter this in subfield g.

11.  Enter the telephone number of the contact person (with extension if known) in subfield h.  Use the international form of the number.  This begins with a plus sign, indicating that the caller should add a prefix signifying an international call.  Spaces may be used to make the number more legible.

12. Enter the telegraphic address in subfield i.

13. Enter the telex number, with Answerback code, in subfield j.

14.  Enter the facsimile number in subfield k.  Use the same form as in rule 11.

15.  Enter any electronic mail address(es) for the contact person in subfield l.  The name of the system should be given, followed by the address, number or code.  If there is more than one address, separate them with a comma and space.

EXAMPLES

1.  ^b19 Phra Atit Road^cBangkok^f10200^eThailand^h+66 2 282 3121

2.  ^bUniversity Road^cLeicester^eEngland^fLE1 7RH^h+44 533 522522
    ext. 5478^j347250 LEICUN G^k+44 533 522200^lJANET: jes@uk.ac.
    le.vax

3.  ^bGran via de les Cortes Catalanes, 812^cBarcelona^eSpain^f08007 

4.  ^f7325^cBad Boll^gPostfach 14^eWest Germany

5.  ^fApartado 10071^f1000^cSan Jose^eCosta Rica^h+506 551080^iILANUD
    ^j2849 ILANU CR^k+50 6 337175

6.  ^cBrighton^eEngland^fBN1 9RE^h+44 273 606261^iDEVELOPMENT
    BRIGHTON^j877997 IDSBTN G^k+44 273 678420^lJANET: qdfd0
    @uk.ac.sussex.cluster

7.  ^b525 Twenty-third Street NW^cWashington^dDC^f20037^eUnited
    States

NOTE FOR SYSTEMS ANALYSTS

Different countries have different preferred orders for elements in an address.  If the database is used to produce address labels, a print format should be developed which bases its order of elements on the country name.  In this case, special efforts should be made to enter country names consistently.

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

448  START AND END DATES

This field is:

-  Optional
-  Repeatable

SUBFIELDS
	^a  Date in formalized form
	^b  Date in non-formalized form
	^c  Duration

RULES FOR ENTRY

1.  The date when the institution came into being and, if it no longer exists, the date when it ceased may be entered in this field.

2.  Dates may be entered either in free format or in a formalized style in accordance with ISO 8601, or both.  The formalized style is recommended if it will be required to search on these dates.

3.  Formalized dates should be entered in subfield a.  Non-formalized dates should be entered in subfield b.

4.  Formalized dates should consist of the year in full, two figures for the month (if known: otherwise write 00), and two figures for the day (if known: otherwise enter 00). The start date should be separated from the end date by a hyphen

5.  If the organization ceased and was then reinstated, this field may be repeated.  Enter the data in repeated fields (separated by percent signs).

6.  Further information about the duration of the project may be given in subfield c.

EXAMPLES

1.  ^a19780125           [Institution started on 25 January, 1978] 

2.  ^a19820000-19880300^c4 years 3 months [Institution existed from
                         1982 to March 1988]

3.  ^b1964               [Institution started in 1964]

4.  ^b1 April 1920-31 December 1985%^b1 August 1989
                         [Institution existed from 1 April 1920 to 31
                         December 1985, and was then reinstated on 1
                         August 1989]

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

500  NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  This field may be used to record any relevant information about the institution or its activities for which no specific field is provided, e.g. the history of the institution.

2.  Notes may be made here about the source of information.

3.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aActivities: fundamental research; technical information, testing, and quality control; education and training.

2.   ^aCommittee of Privy Council, 1839-1899.  Board of Education 1899-1944.  Education Act of 1944 established Ministry of Education.  In April 1964, office of Minister of Science was combined with the Ministry to form Department of Education and Science.

3.   ^aThought to be no longer functioning

4.   ^aInformation taken from Whitaker's Almanack, 1989.

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

600  DESCRIPTION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Description
	^l  Language

RULES FOR ENTRY

1.  This field may be used for a free-text description of the institution and its activities.

2.  If there is more than one paragraph in the description, enter them in repeated fields (separated by percent signs).

3.  <.....>  may be used within the description to delimit index terms (for searching purposes).

4.  If it is desired to enter the description in different languages,  enter each in a repeated field and after each repeat the code for the language in ^l.

EXAMPLES

1.  ^aHolds national records since the Norman Conquest from <Courts of Law> and <Government Departments>.  Museum contains "Domesday Book" (2 vols.) made in 1085, Gunpowder Plot papers (1605), and bull of Pope Clement VII confirming Henry VIII as Fidei Defensor (1524).

2.  ^aThe Board exists to assist the people of the <Highlands and Islands> to improve their <economic> and social conditions, and to enable the Highlands and Islands to play a more effective part in the economic and <social development> of the nation.  To this end, the Board concerts, promotes, assists or undertakes measures for economic and social development.

3.  ^aCo-ordinates inter-library lending in the country, and maintains national union list of serials.

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

610  CLASSIFICATION SCHEME NOTATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Notation

RULES FOR ENTRY

1.  One or more classification numbers, codes, etc., may be entered in subfield a which correspond to the institution's area(s) of interest.

2.  If more than one number, etc., is used, enter them in repeated fields (separated by percent signs).

EXAMPLES
1.	^a400				[Number for linguistics
						in Dewey Classification]

2.	^a342.83				[Number for women in society
						in Universal Decimal Classification]

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

620  SUBJECT DESCRIPTOR

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Subject descriptor

RULES FOR ENTRY

1.  One or more descriptors which correspond to the institution's area(s) of expertise may be entered in subfield a.

2.  If more than one descriptor is used, enter them in repeated fields (separated by percent signs).

3.  If the institution is concerned with a particular geographical area, this may be identified here by appropriate descriptors.

4.  The descriptors may be controlled according to a subject system, e.g. selected from a thesaurus or a list of subject headings.

EXAMPLES

1.	^aEducation%^aEducational innovations

2.	^aLatin America

3.	^aCommunication policy%^aSocial change%^aCommunication impact

4.	^aOral tradition%^aTaboo%^aSongs

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

700  HUMAN RESOURCES

This field is:

-  Optional
-  Not repeatable

SUBFIELD
	^a  Numbers of persons and positions

RULES FOR ENTRY

1.  This field may be used to record details of the number of staff or persons belonging to the organization.

2.  Enter the numbers of persons with their level of responsibility.

3.  Separate data for each level of responsibility with a comma and space.

EXAMPLES

1.  ^a1 director, 1 reader, 1 senior lecturer, 5 lecturers, 2 secretaries

2.  ^a12 committee members, approx. 800 members

3.  ^a2 scientists, 6 technicians, 3 auxiliary personnel

4.  ^a5 staff

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

705  EQUIPMENT AND OTHER RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a Equipment and other resources

RULES FOR ENTRY

1.  This field may be used to record details of equipment (e.g. computers), buildings, land, or other physical resources at the disposal of the organization.

EXAMPLES

1.  ^aHP 3000 minicomputer, 26 IBM XT microcomputers

2.  ^a2 research laboratories, 1 administrative building

3.  ^a100 ha arable land, 1 tractor

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

706  INFORMATION RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Information resources

RULES FOR ENTRY

1.  This field may be used to record details of information resources held by the organization, e.g. libraries, databases.  Numbers of books, reports, journal subscriptions, etc. may be included.

EXAMPLES

1.  ^aDatabase of 3,000 soil analyses

2.  ^aLibrary: 15,000 monographs, 820 serial titles

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

710  FINANCIAL RESOURCES

This field is:

- Optional
- Repeatable

SUBFIELDS

	^a  Financial resources

RULES FOR ENTRY

1.  This field may be used to record any details about financial resources other than income and expenditure.

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

715  INCOME COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Source of funding
	^b  Amount of funding
	^c  Time period
	^d  Note

RULES FOR ENTRY

1.  This field may be used to record details of the organization's sources of income.

2.  Enter the source of income in subfield a and the amount in subfield b.  In subfield c, enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several sources of funding, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aODA^b1.5 million GBP^c1987-88%^aTuition and training fees
^b521,000 GBP^c1987-88%^aFunded research^b530,000 GBP^c1987-88%
^aInvestments^b170,000 GBP^c1987-88

2.  ^aTotal income^b150,000 USD^c1989-90

3.  ^aMinistry of Education^b75 per cent%^aPublications and fees^b25
    per cent

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

716  EXPENDITURE COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Type of component
	^b  Amount
	^c  Time period
	^d  Additional information

RULES FOR ENTRY

1. This field may be used to record details of the organization's expenditure.

2.  Enter the type of expenditure in subfield a and the amount in subfield b.  In subfield c enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign as CDS/ISIS will replace it by semi-colon when printing.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several expenditure components, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aSalaries^b1,540,000 GBP^c1987-88%^aLibrary acquisitions
^b561,000 GBP^c1987-88%^aProject expenditure^b347,000 GBP^c1987-88

2.  ^aTotal expenditure^b145,900 USD^c1989-90

3.  ^aStaff^b75 per cent%^aEquipment^b10 per cent

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

902  LINKED PUBLICATIONS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  MFN of publication

RULES FOR ENTRY

1.  This field may be used to link the record for the institution to any records for publications emanating from that institution which are in the same database.

2.  Enter the Master File Number (MFN) of the publication record in subfield a.

3.  If there are several publications from that institution, enter the MFNs in repeated fields (separated by percent signs).

EXAMPLES

1.	^a1689

2.	^a1760%^a2098%^a7032

_____________________________________________________________________

6  INSTITUTIONS
_____________________________________________________________________

903  REGULAR PUBLICATIONS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Title of publication
	^b  Additional information on publication

RULES FOR ENTRY

1.  This field may be used to enter brief details of regular publications of the institution, such as newsletters, annual reports, etc., which do not merit separate DOCUMENTS records in the database.

2.  The title of the publication should be entered in subfield a.

3.  Any additional information, e.g. price, frequency, may be entered in subfield b.

4.  If there are several publications, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aViewfinder^b3 issues per year

2.  ^aAnnual report%^aNewsletter^birregular

7.  CREATING RECORDS FOR PROJECTS

To create records for projects select the worksheet CLTPR.

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

022  DATE ENTERED ON FILE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD
	^a  Date

RULES FOR ENTRY

1.  Enter here the date when the record was added to the file.

2.  If the program DATE.PAS has been installed, the date can be entered by pressing function key 9.

3.  The date should be constructed in accordance with ISO 8601, i.e. the year in full, two figures for the month, and two figures for the day.  Do not use any punctuation or spaces within the date.

4.  If your organization distributes records to other organizations, it may choose to substitute the date of distribution in this field.

5.  If your organization takes records from other organizations, this field should contain the date when the record was originally created, if that is available.  Otherwise it may contain the date when the record was entered into your system.

EXAMPLES

1.	^a19870917				[17th September, 1987]

2.	^a19901130				[30th November, 1990]

NOTE FOR SYSTEMS ANALYSTS

If necessary, add an extra subfield to allow for greater detail, e.g. if records are taken from other organizations.

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

040  WORKING LANGUAGES

This field is:

-  Optional
-  Repeatable

SUBFIELD
	^a  Language

RULES FOR ENTRY

1.  The language or languages in which the project operates may be recorded here.

2.  Use the language codes from Section 12.

3.  If the project operates in more than one language, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aspa						[project operates in Spanish]

2.  ^adut%^afre				[project operates in Dutch and
							French]

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

062  TYPE OF FACTUAL INFORMATION (RECORD TYPE)

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

NB  The subfield identifier is not used in this fixed length field in this implementation.

	 Type of factual information

RULES FOR ENTRY

1.  For PROJECT records, this field should contain the value PRO.

2.  Press RETURN to accept the default value.

EXAMPLE

1.   PRO

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

064  TYPE OF PROJECT

This field is:

- Optional
- Repeatable

SUBFIELD

	^a  Type of project

RULES FOR ENTRY

1.  The following terms are suggested for recording the type of project:

	Fundamental research
	Applied research
	Experimental development
	Artistic project

2.  If more than one type applies, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aApplied research

2.	^aApplied research%^aExperimental development

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

125  PROJECT NUMBER

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

	^a  Project number

RULES FOR ENTRY

1.   Enter the number assigned to the project by the institution where it is being carried out.

2.   The number should be entered in the same form, including all punctuation and spaces, as used by the organization which is responsible for the execution of the project.

3.   This number should not be confused with the grant or contract number (field 130).

4.   It is essential to enter a project number in this field if it is desired to link another project to this project.

EXAMPLES

1.  ^a4839C

2.  ^aIE/060300/74/0887

3.  ^a3-P-77-0129

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

130  CONTRACT NUMBER

This field is:

-  Optional
-  Repeatable

SUBFIELD

	 ^a  Contract number

RULES FOR ENTRY

1.  The number of the contract under which the project is conducted may be entered here.

2.  The contract number should be entered in the same form, including all punctuation and spaces, as that used by the organization which commissioned the work.

3.  This number should not be confused with the project number (field 125).

4.  If there is more than one contract number, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^a530083.8

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

200  TITLE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

	^a  Title of project

RULES FOR ENTRY

1.  Enter here the name or title of the project.

2.  Separate the subtitle (if any) from the main title by a space, colon, and space.

EXAMPLES

1    ^aGrain Legume Improvement Program

2.   ^aAprovechamiento de fluidos de baja entalpia : Experiencias en
     la zona fronteriza México

3.   ^aEvaluation of a community development health project in Oldham

4.   ^aOscillating wakes of bluff bodies by experiments in towing
     tanks and by numerical analysis

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

300  OTHER PERSONS ASSOCIATED WITH THE PROJECT

This field is:

-  Optional
-  Repeatable

SUBFIELDS

     ^a  Family name
     ^b  Forenames or initials
     ^c  Additional elements to name
     ^f  Role (non-coded)

RULES FOR ENTRY

1.  Separate fields (391 and 392) are provided for the names of the director of the project and the contact person.  Use this field only if you wish to include the names of other persons involved in the project.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c even though it would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

3. The position of the person within the project may be entered in subfield f.

4.  If more than one person is entered here, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aGarcia Campos^bJuan^cSr^fResearch fellow

2.	^aMcLaughlin^bS.M.^cMrs

3.	^aPawlotsky^bYves^fTechnicienne

____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

310  NAME OF INSTITUTION

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^g  Role
	^x  Acronym

RULES FOR ENTRY

1.  Enter here the name(s) of the institution or institutions involved in the project.  If you have a corporate name authority file, then be consistent with that.  If you do not have an authority file, enter the name according to the rules in Section 11.

2.  In general, an institution should be entered under its own name.  This should be entered in subfield a.  However, in certain cases the Anglo-American Cataloguing Rules require it to be entered as a subheading under the name of the parent body (see Section 11).  In these cases the parent body should be entered in subfield a and the subordinate body should be entered in subfield b.  If more than one level in the hierarchy needs to be given in subfield b, separate the levels by a full stop and space.  (CDS/ISIS does not allow the ^b marker to be repeated.)

3.  It may be necessary to add additional information to the name to aid in identification, e.g. when there are more than one institution (perhaps in different countries) with the same name, or the nature of the institution is not clear from the name.  This additional information should be entered in subfield c.

4.  The role of the institution (as regards the project) may be entered in subfield g.

5.  When the institution is well known by an acronym, but the full name is used in subfield a, the acronym should be entered in subfield x.

6.  If there is more than one institution to be entered, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aInstituto Lingüístico de Verano

2.  ^aPunjab University^bDepartment of Agriculture

3.  ^aInstitute for World Economics^cHungarian Academy of Sciences

4.  ^aInstitut français de recherche scientifique pour le
    développement en coopération

5.  ^aUniversity of Sussex^bInstitute of Development Studies^2IDS%
    ^aCentre for Integrated Rural Development for Asia and the
    Pacific^2CIRDAP
_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

391  DIRECTOR OR HEAD OF PROJECT

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Family name
	^b  Forenames or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY
 
1.  The name of the director or head of the project may be entered in this field.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

3.  In subfield c, enter the title which should be used in addressing a letter to that person.

4.  In subfield f, enter the title of the person's position in the project, if it is not "Project Director".

5.  If there are joint heads, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aMeadows^bA. Jack^cProfessor

2.   ^aCastañón^bInés^fProject co-ordinator

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

392  CONTACT PERSON

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Family name
	^b  Forename or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY

1.  The name of one contact person for the project may be entered in this field (unless the contact person is the director who has already been entered in field 391).

2.  The contact person is the person to whom the address information in field 430 applies.

3.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

4.  In subfield c, enter the title which should be used in addressing a letter to that person.

4.  The title of the person's position in the project may be entered in subfield f.

EXAMPLES

1.	^aLee^bHon-ling^cMr^fProgrammer

2.	^aKanchanasut^bKanchana

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

430  ADDRESS

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Building/institution
	^b  Street address
	^c  Locality, town or city
	^d  State, county or region
	^e  Country
	^f  Postal code
	^g  Post Office Box number
	^h  Telephone number
	^i  Telegraphic address
	^j  Telex number
	^k  FAX number
	^l  Electronic mail address

RULES FOR ENTRY

1.  The address of the contact person may be entered here if one has been recorded in field 392.  Otherwise use the address of the head of the project recorded in field 391.  Do not enter any other addresses at which the project is conducted.

2.  The order of items in the address varies between countries.  Enter the subfields in the order in which they should be written on an envelope.

3.  Enter the name of the building (and office, floor, etc.) in subfield a, if required as part of the contact person's address.  If there are several institutions listed in field 310, include the relevant institution name here.

4.  Enter the street and number (if any) in subfield b. The number may come before or after the street according to national practice.

5.  Enter the town, village or locality in subfield c.  If more than one place needs to be included, separate each by means of a comma and space.

6.  Enter the name of the state, county or region, if needed as part of the address, in subfield d.  Abbreviations may be used if recognized by the postal authority.

7.  Enter the name of the country, in the form used for postal purposes, in subfield e.

8.  Enter the postal code in subfield f.

9.  If the address is for a Post Office Box Number, enter this in subfield g.

10.  Enter the telephone number of the contact person (with extension if known) in subfield h.  Use the international form of the number.  This begins with a plus sign, indicating that the caller should add a prefix signifying an international call.  Spaces may be used to make the number more legible.

11.  Enter the telegraphic address in subfield i.

12.  Enter the telex number, with Answerback code, in subfield j.

13.  Enter the facsimile number in subfield k.  Use the same form as in rule 10.

14.  Enter any electronic mail address(es) for the contact person in subfield l.  The name of the system should be given, followed by the address, number or code.  If there is more than one address, separate them with a comma and space.

EXAMPLES

1.  ^aInternational Centre for Theoretical Physics^bStrada Costiera
    11^gPO Box 586^f34100^cTrieste^eItaly^h+39 40 22401^iCENTRATOM
    ^j460392 ICTP I^k+39 40 224163

2.  ^bUniversity Road^cLeicester^eEngland^fLE1 7RH^h+44 533 522522
    ext. 5478^j347250 LEICUN G^k+44 533 522200^lJANET: 
    jes@uk.ac.le.vax

3.  ^b125 Corso Unita d'Italia^f10127^cTurin^eItaly

4.  ^f1000^cBerlin^bPariser Strasse 44^eWest Germany^lInternet: 
    dfn-verein@zpl.dfn.dbp.de

5.  ^aInstitute of Development Studies, University of Sussex
    ^cBrighton^eEngland^fBN1 9RE^h+44 273 606261^iDEVELOPMENT
    BRIGHTON^j877997 IDSBTN G^k+44 273 678420^lJANET:
    qdfd0@uk.ac.sussex.cluster

6.  ^cAtlanta^dGA^f30332^eUSA

NOTE FOR SYSTEMS ANALYSTS

Different countries have different preferred orders for elements in an address.  If the database is used to produce address labels, a print format should be developed which bases its order of elements on the country name.  In this case special efforts should be made to enter country names consistently.

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

448  START AND END DATES

This field is:

-  Optional
-  Repeatable

SUBFIELDS
	^a  Date in formalized form
	^b  Date in non-formalized form
	^c  Duration

RULES FOR ENTRY

1.  The date when the project started and, if known, the date when it is expected to end (or has ended) may be entered in this field.

2.  Dates may be entered either in free format or in a formalized style in accordance with ISO 8601, or both.  The formalized style is recommended if it will be required to search on these dates.

3.  Formalized dates should be entered in subfield a.  Non-formalized dates should be entered in subfield.

4.  Formalized dates should consist of the year in full, two figures for the month (if known: otherwise write 00), and two figures for the day (if known: otherwise enter 00). Start and end dates should be separated by - (hyphen).

5.  If the project ceased and was then reinstated, this field may be repeated.  Enter the data in repeated fields (separated by percent signs).

6.  Further information about the duration of the project can be given in subfield ^c

EXAMPLES

1.  ^a19780125				[Project started on 25 January, 1978]

2.  ^a19820000-19880300	[Project ran from 1982 to March 1988]

3.  ^b1964^cDuration uncertain      [Project started in 1964]

4.  ^b1 April 1980-31 December 1985%^b1 August 1989^cProject ran from 
						1 April 1980 to 31 December 1985, 
						and was then reinstated on 1 August 
						1989

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

500  NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  This field may be used to record any relevant information about the project for which no specific field is provided.

2.  If the researcher, or one of the researchers, is carrying out the project in order to obtain a degree or other qualification, a note may be made to this effect.

3.  Notes may be made here about the source of information.

4.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aRaghubir Singh is working for Ph.D, University of Calcutta

2.   ^aThought to be no longer operating

3.   ^aInformation from Science Research Council Yearbook, 1979.

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

600  ABSTRACT

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Abstract

RULES FOR ENTRY

1.  This field may be used for a free-text abstract of the project.

2.  <.....>  may be used within the description to delimit index terms (for searching purposes).

3.  The abstract should include the objectives, methodology, and results of the project.

4.  If the abstract runs to more than one paragraph, enter the paragraphs in repeated fields (separated by percent signs).

5.  If it is desired to enter the description in different languages,  enter each in a repeated field and after each repeat the code for the language in ^l.

6.  This information should be revised as the project proceeds.

EXAMPLES

1.  ^aAims:  Exploratory research into factors which facilitate or inhibit the development of collective strategies to cope with social and economic change.%^aMethod:  Still to be decided as far as field research is concerned.  Probably combination of structured interviews and aide-memoire.  Focus: neighbourhood organizations and households in a selected locality.

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

610  CLASSIFICATION SCHEME NOTATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Notation

RULES FOR ENTRY

1.  One or more classification numbers, codes, etc., which correspond to the subject area of the project may be entered in subfield a.

2.  If more than one number, etc., is used, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^a400				[Number for linguistics
						in Dewey Classification]

2.	^a342.83				[Number for women in society
						in Universal Decimal Classification]

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

620  SUBJECT DESCRIPTOR

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Subject descriptor

RULES FOR ENTRY

1.  One or more descriptors which correspond to the subject area of the project may be entered in subfield a.

2.  If more than one descriptor is used, enter them in repeated fields (separated by percent signs).

3.  If the project is concerned with a particular geographical area, this should be identified here by appropriate descriptors.

4.  The descriptors may be controlled according to a subject system, e.g. selected from a thesaurus or a list of subject headings.

EXAMPLES

1.   ^aCommunication policy%^aSocial change%^aCommunication impact

2.   ^aOral tradition%^aTaboo%^aSongs

3.   ^aLatin America

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

700  HUMAN RESOURCES

This field is:

-  Optional
-  Not repeatable

SUBFIELD
	^a  Numbers of persons and positions

RULES FOR ENTRY

1.  This field may be used to record details of the number of staff or persons working on the project.

2.  Enter the numbers of persons with their level of responsibility.

3.  Separate data for each level of responsibility with a comma and space.

EXAMPLES

1.  ^a1 director, 1 research fellow, 1 research assistant, 2 research 
	students

2.  ^a1 professor, 1 assistant (part-time)

3.  ^a2 scientists 1 technician, 3 clerical assistants

4.  ^a2 staff

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

705  EQUIPMENT AND OTHER RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a Equipment and other resources

RULES FOR ENTRY

1.  This field may be used to record details of equipment (e.g. computers), buildings, land, or other physical resources at the disposal of the project.

EXAMPLES

1.  ^a2 IBM XT microcomputers

2.  ^aresearch laboratory, field station

3.  ^a100 ha arable land, 1 tractor

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

710  FINANCIAL RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a Financial resources

RULES FOR ENTRY

1.  This field may be used to record details of financial resources other than income and expenditure.

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

715  INCOME COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Source of funding
	^b  Amount of funding
	^c  Time period
	^d  Note

RULES FOR ENTRY

1.  This field may be used to record details of the project's sources of income.

2.  Enter the source of income in subfield a and the amount in subfield b.  In subfield c, enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several sources of funding, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aEuropean Foundation for the Improvement of Living and Working 
     Conditions (EFILWC)

2.   ^aScience and Engineering Research Council^b25,000 GBP^c3 years

3    ^aUnesco^b1,500 USD

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

716  EXPENDITURE COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Type of component
	^b  Amount
	^c  Time period
	^d  Additional information

RULES FOR ENTRY

1.  This field may be used to record details of the project's expenditure.

2.  Enter the type of expenditure in subfield a and the amount in subfield b.  In subfield c enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several components of expenditure, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.    ^aSalaries^b75 per cent%^aTravel^b20 per cent%^aMaterials^b5
      per cent

2.    ^aComputer equipment^b100,000 USD

_____________________________________________________________________
7  PROJECTS
_____________________________________________________________________

850  DURATION OF PROJECT

NO LONGER USED SEE 448 ^c
_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

860  PROJECT STATUS

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Project status

RULES FOR ENTRY

1.  The following terms are suggested for recording the current status of the project:

	Planning stage
	Operational
	Interrupted
	Abandoned
	Completed

EXAMPLES

1.	^aOperational

2.	^aCompleted

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

902  RELATED PUBLICATIONS

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  MFN of related publication

RULES FOR ENTRY

1.  This field may be used to link the record for the project to any records for publications deriving from that project which are in the same database.

2.  Enter the Master File Number (MFN) of the publication record in subfield a.

3.  If there are several publications from that project, enter the MFNs in repeated fields (separated by percent signs).

NOTE

This field should not be used if there is any likelihood that the records will be renumbered.

EXAMPLES

1.	^a156

2.	^a4561%^a2312%^a9453

_____________________________________________________________________

7  PROJECTS
_____________________________________________________________________

951  RELATED PROJECTS

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Identifier of related project

RULES FOR ENTRY

1.  This field may be used to link the record for the project to any records for related projects which are in the same database.

2.   A related project may be a predecessor or successor of the project described in the record, or a larger project of which the project described forms part, or a part of the project described.

2.  Enter the identifier of the project as entered in field 125 of the related project record in subfield a.

3.  If there are several related projects, enter the identifiers in repeated fields (separated by percent signs).

EXAMPLES

1.	^aUKG 651

2.	^aCLT-2006%^aCLT-2313%^aCLT-9419

8.  CREATING RECORDS FOR EVENTS

To create records for events select the worksheet CLTEV.

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

022  DATE ENTERED ON FILE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD
	^a  Date

RULES FOR ENTRY

1.  Enter here the date when the record was added to the file.

2.  If the program DATE.PAS has been installed, the date can be entered by pressing function key 9.

3.  The date should be constructed in accordance with ISO 8601, i.e. the year in full, two figures for the month, and two figures for the day.  Do not use any punctuation or spaces within the date.

4.  If your organization distributes records to other organizations, it may choose to substitute the date of distribution in this field.

5.  If your organization takes records from other organizations, this field should contain the date when the record was originally created, if that is available.  Otherwise it may contain the date when the record was entered into your system.

EXAMPLES

1.	^a19890917				[17th September, 1989]

2.	^a19901130				[30th November, 1990]

NOTE FOR SYSTEMS ANALYSTS

If necessary, add an extra subfield to allow for greater detail, e.g. if records are taken from other organizations.

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

040  WORKING LANGUAGES

This field is:

-  Optional
-  Repeatable

SUBFIELD
	^a  Language

RULES FOR ENTRY

1.  The language or languages in which the event operates may be recorded here.

2.  Use the language codes from Section 12.

3.  If the event operates in more than one language, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aspa						[event operates in Spanish]

2.  ^adut%^afre				[event operates in Dutch and
							French]

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

062  TYPE OF FACTUAL INFORMATION (RECORD TYPE)

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

NB  The subfield identifier is not used in this fixed length field in this implementation.

	 Type of factual information

RULES FOR ENTRY

1.  For EVENT records, this field should contain the value EVE.

2.  Press RETURN to accept the default value.

EXAMPLE

1.   EVE

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

125  PROJECT NUMBER

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

	^a  Project number

RULES FOR ENTRY

1.  Enter the number assigned to the event by the institution where it is being carried out.

2.  The number should be entered in the same form, including all punctuation and spaces, as used by the organization which is responsible for the execution of the event.

3.   This number should not be confused with the grant or contract number (field 130).

EXAMPLES

1.  ^a4839C

2.  ^aIE/060300/74/0887

3.  ^a3-P-77-0129

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

130  CONTRACT NUMBER

This field is:

-  Optional
-  Repeatable

SUBFIELD

	 ^a  Contract number

RULES FOR ENTRY

1.  The number of the contract under which the event is conducted may be entered here.

2.  The contract number should be entered in the same form, including all punctuation and spaces, as that used by the organization which commissioned the work.

3.  This number should not be confused with the project number (field 125).

4.  If there is more than one contract number, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^a530083.8

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

200  TITLE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELD

	^a  Title of event

RULES FOR ENTRY

1.  Enter here the name or title of the event.

2.  Separate the subtitle (if any) from the main title by a space, colon, and space.

EXAMPLES

1    ^aOn classic ground

2.   ^aDuane Hanson : Skulpturen

3.   ^aCultural development and information [this the title of a 
                                               meeting]

4.   ^aLibraries - Information for Knowledge [this is the title of
                        [the Annual general Conference of IFLA, 1990]

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

300  OTHER PERSONS ASSOCIATED WITH THE EVENT

This field is:

-  Optional
-  Repeatable

SUBFIELDS

     ^a  Family name
     ^b  Forenames or initials
     ^c  Additional elements to name
     ^f  Role (non-coded)

RULES FOR ENTRY

1.  Separate fields (391 and 392) are provided for the names of the director of the event and the contact person.  Use this field only if you wish to include the names of other persons involved in the event.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c even though it would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

3. The position of the person within the event may be entered in subfield f.

4.  If more than one person is entered here, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^aGarcia Campos^bJuan^cSr^fCoordinator

2.	^aMcLaughlin^bS.M.^cMrs

3.	^aPawlotsky^bYves^fTechnical co-ordinator

____________________________________________________________________

8  EVENTS
_____________________________________________________________________

310  NAME OF INSTITUTION

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^g  Role
	^x  Acronym

RULES FOR ENTRY

1.  Enter here the name(s) of the institution or institutions involved in the event.  If you have a corporate name authority file, then be consistent with that.  If you do not have an authority file, enter the name according to the rules in Section 11.

2.  In general, an institution should be entered under its own name.  This should be entered in subfield a.  However, in certain cases the Anglo-American Cataloguing Rules require it to be entered as a subheading under the name of the parent body (see Section 11).  In these cases the parent body should be entered in subfield a and the subordinate body should be entered in subfield b.  If more than one level in the hierarchy needs to be given in subfield b, separate the levels by a full stop and space.  (CDS/ISIS does not allow the ^b marker to be repeated.)

3.  It may be necessary to add additional information to the name to aid in identification, e.g. when there are more than one institution (perhaps in different countries) with the same name, or the nature of the institution is not clear from the name.  This additional information should be entered in subfield c.

4.  The role of the institution (as regards the event) may be entered in subfield g.

5.  When the institution is well known by an acronym, but the full name is used in subfield a, the acronym should be entered in subfield x.

6.  If there is more than one institution to be entered, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aInstituto Lingüístico de Verano

2.  ^aInstitute for Development and International Relations^xIRMO
    ^bDepartment for Culture and Communications

3.  ^aEuropean Cultural Foundation

4.  ^aInstitut français de recherche scientifique pour le
    développement en coopération

5.  ^aMuseum für Geschichte der Stadt^cLeipzig
    ^aArt and Exhibition Hall of the Federal Republic of Germany
    ^cBonn

____________________________________________________________________

4  EVENTS
_____________________________________________________________________

320  NAME OF EVENT

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^e  Country
	^g  Location of event
	^j  Number of event

RULES FOR ENTRY

1.  Enter here the name of the event.

2.  Enter the name as you would in the heading on a catalogue card.  If you have an event name authority file, then be consistent with that.  If you do not have an authority file, enter the name as below.

3.  Enter the name of the event in subfield a.  Do not enter the number of the meeting, e.g. "second", here: it should be entered in subfield j.  Do not enter the date of the meeting here unless it is an integral part of the title.  The date should nevertheless be entered in field 448.

4.  If the name of the event contains the name of a subordinate body, enter the subordinate body's name in subfield b.

5.  It may be necessary to add further information to the name to aid in identification, e.g. when there is more than one event with the same name, or it is not clear from the name that it relates to an event.  This additional information should be entered in subfield c.

6.  The country in which the event was held may optionally be entered in subfield e.  Use one of the codes as outlined in Section 13.

7.  Enter the name of the place or other location in which the event was held in subfield g.  Give the place name in its English form (alternatively in your preferred language) if there is one in general use.

8.  If the event belongs to a numbered series, enter the number in its English form, e.g. 3rd, 7th (alternatively in your preferred language) in subfield j.

EXAMPLES

1.  ^aInternational Symposium on Bibliographic Exchange Formats
    ^gTaormina, Italy^eIT

2.  ^aInternational Conference on Co-operative Thrift and Credit^gRio
      de Janeiro, Brazil^j4th

3.  ^aBiennale di Venezia^gVenice^j44th

4.  ^aOlympic Games^gMontreal, Quebec^j21st^eCA

5.  ^aNorth-South Media Meeting, 1992^j82nd^eFR

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

391  DIRECTOR OR HEAD OF EVENT

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Family name
	^b  Forenames or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY
 
1.  The name of the director or head of the event may be entered in this field.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

3.  In subfield c, enter the title which should be used in addressing a letter to that person.

4.  In subfield f, enter the title of the person's position in the event, if it is not "Director".

5.  If there are joint heads, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aParris^bLeslie

2.   ^aCastañón^bInés^fCo-ordinator

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

392  CONTACT PERSON

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Family name
	^b  Forename or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY

1.  The name of one contact person for the event may be entered in this field (unless the contact person is the director who has already been entered in field 391).

2.  The contact person is the person to whom the address information in field 430 applies.

3.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

4.  In subfield c, enter the title which should be used in addressing a letter to that person.

4.  The title of the person's position in the event may be entered in subfield f.

EXAMPLES

1.	^aLee^bHon-ling^cMr

2.	^aKanchanasut^bKanchana^fCurator

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

430  ADDRESS

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Building/institution
	^b  Street address
	^c  Locality, town or city
	^d  State, county or region
	^e  Country
	^f  Postal code
	^g  Post Office Box number
	^h  Telephone number
	^i  Telegraphic address
	^j  Telex number
	^k  FAX number
	^l  Electronic mail address

RULES FOR ENTRY

1.  The address of the contact person may be entered here if one has been recorded in field 392.  Otherwise use the address of the head of the event recorded in field 391.  Do not enter any other addresses at which the event is conducted.

2.  The order of items in the address varies between countries.  Enter the subfields in the order in which they should be written on an envelope.

3.  Enter the name of the building (and office, floor, etc.) in subfield a, if required as part of the contact person's address.  If there are several institutions listed in field 310, include the relevant institution name here.

4.  Enter the street and number (if any) in subfield b. The number may come before or after the street according to national practice.

5.  Enter the town, village or locality in subfield c.  If more than one place needs to be included, separate each by means of a comma and space.

6.  Enter the name of the state, county or region, if needed as part of the address, in subfield d.  Abbreviations may be used if recognized by the postal authority.

7.  Enter the name of the country, in the form used for postal purposes, in subfield e.

8.  Enter the postal code in subfield f.

9.  If the address is for a Post Office Box Number, enter this in subfield g.

10.  Enter the telephone number of the contact person (with extension if known) in subfield h.  Use the international form of the number.  This begins with a plus sign, indicating that the caller should add a prefix signifying an international call.  Spaces may be used to make the number more legible.

11.  Enter the telegraphic address in subfield i.

12.  Enter the telex number, with Answerback code, in subfield j.

13.  Enter the facsimile number in subfield k.  Use the same form as in rule 10.

14.  Enter any electronic mail address(es) for the contact person in subfield l.  The name of the system should be given, followed by the address, number or code.  If there is more than one address, separate them with a comma and space.

EXAMPLES

1.  ^aInternational Centre for Cultural Cooperation^bStrada Costiera
    11^gPO Box 586^f34100^cTrieste^eItaly^h+39 40 22401^iCENTRATOM
    ^j460392 ICTP I^k+39 40 224163

2.  ^bUniversity Road^cLeicester^eEngland^fLE1 7RH^h+44 533 522522
    ext. 5478^j347250 LEICUN G^k+44 533 522200^lJANET: 
    jes@uk.ac.le.vax

3.  ^b125 Corso Unita d'Italia^f10127^cTurin^eItaly

4.  ^f1000^cBerlin^bPariser Strasse 44^eWest Germany^lInternet: 
    dfn-verein@zpl.dfn.dbp.de

5.  ^aInstitute of Development Studies, University of Sussex
    ^cBrighton^eEngland^fBN1 9RE^h+44 273 606261^iDEVELOPMENT
    BRIGHTON^j877997 IDSBTN G^k+44 273 678420^lJANET:
    qdfd0@uk.ac.sussex.cluster

6.  ^cAtlanta^dGA^f30332^eUSA

NOTE FOR SYSTEMS ANALYSTS

Different countries have different preferred orders for elements in an address.  If the database is used to produce address labels, a print format should be developed which bases its order of elements on the country name.  In this case special efforts should be made to enter country names consistently.

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

448  START AND END DATES

This field is:

-  Optional
-  Repeatable

SUBFIELDS
	^a  Date in formalized form
	^b  Date in non-formalized form
	^c  Duration

RULES FOR ENTRY

1.  The date when the event started and, if known, the date when it is expected to end (or has ended) may be entered in this field.

2.  Dates may be entered either in free format or in a formalized style in accordance with ISO 8601, or both.  The formalized style is recommended if it will be required to search on these dates.

3.  Formalized dates should be entered in subfield a.  Non-formalized dates should be entered in subfield.

4.  Formalized dates should consist of the year in full, two figures for the month (if known: otherwise write 00), and two figures for the day (if known: otherwise enter 00). Start and end dates should be separated by - (hyphen).

5.  If the event ceased and was then reinstated, this field may be repeated.  Enter the data in repeated fields (separated by percent signs).

6.  Further information about the duration of the event can be given in subfield ^c

EXAMPLES

1.  ^a19920000-19930300	[Event ran from 1992 to March 1993]

3.  ^b1964^cDuration uncertain      [Event started in 1964]

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

500  NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  This field may be used to record any relevant information about the event for which no specific field is provided.

2.  Notes may be made here about the source of information.

3.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aTravelling to Van Gogh Museum, Amsterdam

2.   ^aMay become a permanent exhibition

3.   ^aInformation from Culturelink, Special Issue, 1991

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

600  ABSTRACT

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Abstract

RULES FOR ENTRY

1.  This field may be used for a free-text abstract of the event.

2.  <.....>  may be used within the description to delimit index terms (for searching purposes).

3.  The abstract should include the objectives, methodology, and results of the event.

4.  If the abstract runs to more than one paragraph, enter the paragraphs in repeated fields (separated by percent signs).

5.  If it is desired to enter the description in different languages,  enter each in a repeated field and after each repeat the code for the language in ^l.

6.  This information may be revised as the event proceeds.

EXAMPLES

1.  ^aThe libraries of today and tomorrow will play a key role in the lives of people as the need for knowledge grows.  To be able to retrieve the right information at the right time is one of the most important capabilities in modern society.  This role, linking libraries to their cultural importance, contributes to the explicit objectives laid down by Unesco for the World Decade promoting cultural development 1988-1997 (Source IFLA General Conference Programme)

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

610  CLASSIFICATION SCHEME NOTATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Notation

RULES FOR ENTRY

1.  One or more classification numbers, codes, etc., which correspond to the subject area of the event may be entered in subfield a.

2.  If more than one number, etc., is used, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^a400				[Number for linguistics
						in Dewey Classification]

2.	^a342.83				[Number for women in society
						in Universal Decimal Classification]

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

620  SUBJECT DESCRIPTOR

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Subject descriptor

RULES FOR ENTRY

1.  One or more descriptors which correspond to the subject area of the event may be entered in subfield a.

2.  If more than one descriptor is used, enter them in repeated fields (separated by percent signs).

3.  If the event is concerned with a particular geographical area, this should be identified here by appropriate descriptors.

4.  The descriptors may be controlled according to a subject system, e.g. selected from a thesaurus or a list of subject headings.

EXAMPLES

1.   ^aTelecommunications%^aIntegrated Services Digital Network%
     ^aCommunications protocols

2.   ^aLatin America

3.   ^aPopular belief and customs%^aFolklore
_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

700  HUMAN RESOURCES

This field is:

-  Optional
-  Not repeatable

SUBFIELD
	^a  Numbers of persons and positions

RULES FOR ENTRY

1.  This field may be used to record details of the number of staff or persons working on the event.

2.  Enter the numbers of persons with their level of responsibility.

3.  Separate data for each level of responsibility with a comma and space.

EXAMPLES

1.  ^a1 director, 1 curator, 6 volunteers

2.  ^a1 organizer, 1 assistant (part-time)

3.  ^a2 designers, 1 technician, 3 clerical assistants

4.  ^a2 staff

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

705  EQUIPMENT AND OTHER RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a Equipment and other resources

RULES FOR ENTRY

1.  This field may be used to record details of equipment (e.g. computers), buildings, land, or other physical resources at the disposal of the event.

EXAMPLES

1.  ^a2 IBM XT microcomputers

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

710  FINANCIAL RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a Financial resources

RULES FOR ENTRY

1.  This field may be used to record details of financial resources other than income and expenditure.

EXAMPLES

1.  ^aGenerous financial support for this exhibition was given by IBM

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

715  INCOME COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Source of funding
	^b  Amount of funding
	^c  Time period
	^d  Note

RULES FOR ENTRY

1.  This field may be used to record details of the event's sources of income.

2.  Enter the source of income in subfield a and the amount in subfield b.  In subfield c, enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several sources of funding, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aEuropean Foundation for the Improvement of Living and Working 
     Conditions (EFILWC)

2.   ^aUnesco^b12,500 USD^c3 years

3    ^aCouncil of Europe^b1,500 ECU

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

716  EXPENDITURE COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Type of component
	^b  Amount
	^c  Time period
	^d  Additional information

RULES FOR ENTRY

1.  This field may be used to record details of the event's expenditure.

2.  Enter the type of expenditure in subfield a and the amount in subfield b.  In subfield c enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several components of expenditure, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.    ^aSalaries^b75 per cent%^aTravel^b20 per cent%^aMaterials^b5
      per cent

2.    ^aComputer equipment^b100,000 USD

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

860  EVENT STATUS

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Event status

RULES FOR ENTRY

1.  The following terms are suggested for recording the current status of the event:

	Planning stage
	Operational
	Interrupted
	Abandoned
	Completed

EXAMPLES

1.	^aOperational

2.	^aCompleted

_____________________________________________________________________

8  EVENTS
_____________________________________________________________________

902  RELATED PUBLICATIONS

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  MFN of related publication

RULES FOR ENTRY

1.  This field may be used to link the record for the event to any records for publications deriving from that event which are in the same database.

2.  Enter the Master File Number (MFN) of the publication record in subfield a.

3.  If there are several publications from that event, enter the MFNs in repeated fields (separated by percent signs).

EXAMPLES

1.	^aUKG 156

2.	^aCLT-4561%^aCLT-2312%^aCLT-9453

9. CREATING RECORDS FOR TRAINING OPPORTUNITIES

To create records for training opportunities select the worksheet CLTTR.

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

022  DATE ENTERED ON FILE

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS
	^a  Date

RULES FOR ENTRY

1.  Enter here the date when the record was added to the file.

2.  If the program DATE.PAS has been installed, the date can be entered by pressing function key 9.

3.  The date should be constructed in accordance with ISO 8601, i.e. the year in full, two figures for the month, and two figures for the day.  Do not use any punctuation or spaces within the date.

4.  If your organization distributes records to other organization, it may choose to substitute the date of distribution in this field.

5.  If your organization takes records from other organizations, this field should contain the date that the record was originally created, if that is available.  Otherwise it may contain the date that the record was entered into your system.

EXAMPLES

1.	^a19870917				[17th September, 1987]

2.	^a19901130				[30th November, 1990]

NOTE FOR SYSTEMS ANALYSTS

If necessary, add an extra subfield to allow for greater detail, e.g. when records are taken from other organizations.

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

040  WORKING LANGUAGE

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Language

RULES FOR ENTRY

1.  The language or languages in which the training course or fellowship operates may be entered here.

2.  Use the language codes from Section 12.

3.  If more than one language applies, enter the codes in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aspa				[course is conducted in Spanish]
2.  ^adut%^afre		[course is in Dutch and French]
_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

062  TYPE OF FACTUAL INFORMATION (RECORD TYPE)

This field is:

-  Mandatory
-  Not repeatable

SUBFIELDS

NB  The subfield identifier is not used in this fixed length field in this implementation.

    Type of factual information

RULES FOR ENTRY

1.  For TRAINING OPPORTUNITIES, this field should contain the value TRA.

2.  Press RETURN to accept the default value.

EXAMPLE

1.   TRA

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

200  TITLE

This field is:

-  Optional
-  Not repeatable

SUBFIELD

	^a  Title of course, fellowship, etc

RULES FOR ENTRY

1.  Enter here the name or title of the course or fellowship

2.  Separate the subtitle (if any) from the main title by a space, colon, and space.

EXAMPLES

1    ^aGrain Legume Improvement Fellowship

2.   ^aABAST Diploma in Cultural development Administration : Part 1

3.   ^aDiploma Course

4.   ^aPoet in Residence : Summer Vacation Fellowship

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

300  OTHER PERSONNEL

This field is:

-  Optional
-  Repeatable

SUBFIELDS

     ^a  Family name
     ^b  Forenames or initials
     ^c  Additional elements to name
     ^f  Role (non-coded)

RULES FOR ENTRY

1.  Separate fields (391 and 392) are provided for the name(s) of the director of the training opportunity and the contact person.  Use this field only if you wish to include the names of other people involved.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but add the person's role in subfield f.  If you do not have an authority file, enter the name following the rules in Section 10.

3. The position of the person may be entered in subfield f.

4.  If more than one person is recorded here, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.     ^aArmstrong^bChris^fSecretary

2.     ^aPoncet^bJean-François^cM.^fCourse Coordinator

3.     ^aDorofeyev^bV.^cMr^fFellowship Coordinator

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

310  NAME OF INSTITUTION

This field is:

-  Mandatory
-  Repeatable

SUBFIELDS

	^a  Entry element
	^b  Subordinate body
	^c  Qualifier
	^x  Acronym

RULES FOR ENTRY

1.  Enter here the name of any institution involved in the training opportunity.  If you have a corporate name authority file, then be consistent with that.  If you do not have an authority file, enter the name according to rules in Section 11.

2.  In general, the institution should be entered under its own name.  This should be entered in subfield a.  However, in certain cases the Anglo-American Cataloguing Rules require it to be entered as a subheading under the name of the parent body (see Section 11).  In these cases the parent body should be entered in subfield a and the subordinate body should be entered in subfield b.  If more than one level in the hierarchy needs to be given in subfield b, separate the levels by a full stop and space.  (CDS/ISIS does not allow the ^b marker to be repeated.)

3.  It may be necessary to add additional information to the name to aid in identification, e.g. when there is more than one institution (perhaps in different countries) with the same name, or the nature of the institution is not clear from the name.  This additional information should be entered in subfield c.

4.  When the institution is well known by an acronym, but the full name is used in subfield a, the acronym may be entered in subfield x.

EXAMPLES

1.  ^aAmnesty International

2.  ^aInstituto Salvadoreño de Administracíon Municipal

3.  ^aPunjab University^bDepartment of Agriculture

4.  ^aUniversity of London^bSchool of Oriental and African Studies
    ^xSOAS

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

391  DIRECTOR OR HEAD OF TRAINING OPPORTUNITY

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Family name
	^b  Forenames or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY

1.  The name of the director or head of the course or fellowship may be entered in this field.

2.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

3.  The title which should be used in addressing a letter to that person may be entered in subfield c.

4.  In subfield f, enter the title of the person's position in the organization, if it is not "director".

5.  If there are joint heads, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aEl-Zanati^bA.G.^cMr^fChief

2.  ^aCastañón^bInés^fGerente

3.  ^aGurunlian^bJean^cMr^fOfficer-in-Charge

4.  ^aIzquierdo^bMaría Lourdes de

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

392  CONTACT PERSON

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Family name
	^b  Forename or initials
	^c  Additional elements to name
	^f  Role (non-coded)

RULES FOR ENTRY

1.  The name of one contact person at the organization may be entered in this field, unless it is the same as the director entered in field 391.

2.  The contact person is the person to whom the address information in field 430 applies.

3.  Enter the name as you would in the heading on a catalogue card.  If you have a personal name authority file, then be consistent with that, but you may add the person's title in subfield c and role in subfield f even though they would not be present in a bibliographic record.  If you do not have an authority file, enter the name following the rules in Section 10.

4.  In subfield c, enter the title which should be used in addressing a letter to that person.

5.  The title of the person's position in the organization may be entered in subfield f.

EXAMPLES

1.	^aLee^bHon-ling^cMr^fSystems manager

2.	^aKanchanasut^bKanchana

3.	^aWeatherwax^bJ.R.^cMr^fNutrition Officer

____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

430  ADDRESS

This field is:

-  Optional
-  Not repeatable

SUBFIELDS

	^a  Building/institution
	^b  Street address
	^c  Locality, town or city
	^d  State, county or region
	^e  Country
	^f  Postal code
	^g  Post Office Box number
	^h  Telephone number
	^i  Telegraphic address
	^j  Telex number
	^k  FAX number
	^l  Electronic mail address

RULES FOR ENTRY

1.  The address of the contact person may be entered here if one has been recorded in field 392.  Otherwise use the address of the head or director recorded in field 391.  Do not enter any other addresses from which the training opportunity operates.

2.  The order of items in the address varies between countries.  Enter the subfields in the order in which they should be written on an envelope.

3.  Enter the name of the building (and office, floor, etc.) in subfield a, if required as part of the contact person's address.

4.  Enter the street and number (if any) in subfield b. The number may come before or after the street according to national practice.

5.  Enter the town, village or locality in subfield c.  If more than one place needs to be included, separate each by means of a comma and space.

7.  Enter the name of the state, county or region, if needed as part of the address, in subfield d.  Abbreviations may be used if recognized by the postal authority.

8.  Enter the name of the country, in the form used for postal purposes, in subfield e.

9.  Enter the postal code in subfield f.

10. If the address is for a Post Office Box Number, enter this in subfield g.

11.  Enter the telephone number of the contact person (with extension if known) in subfield h.  Use the international form of the number.  This begins with a plus sign, indicating that the caller should add a prefix signifying an international call.  Spaces may be used to make the number more legible.

12. Enter the telegraphic address in subfield i.

13. Enter the telex number, with Answerback code, in subfield j.

14.  Enter the facsimile number in subfield k.  Use the same form as in rule 11.

15.  Enter any electronic mail address(es) for the contact person in subfield l.  The name of the system should be given, followed by the address, number or code.  If there is more than one address, separate them with a comma and space.

EXAMPLES

1.  ^b19 Phra Atit Road^cBangkok^f10200^eThailand^h+66 2 282 3121

2.  ^bUniversity Road^cLeicester^eEngland^fLE1 7RH^h+44 533 522522
    ext. 5478^j347250 LEICUN G^k+44 533 522200^lJANET: jes@uk.ac.
    le.vax

3.  ^bGran via de les Cortes Catalanes, 812^cBarcelona^eSpain^f08007 

4.  ^f7325^cBad Boll^gPostfach 14^eWest Germany

5.  ^fApartado 10071^f1000^cSan Jose^eCosta Rica^h+506 551080^iILANUD
    ^j2849 ILANU CR^k+50 6 337175

6.  ^cBrighton^eEngland^fBN1 9RE^h+44 273 606261^iDEVELOPMENT
    BRIGHTON^j877997 IDSBTN G^k+44 273 678420^lJANET: qdfd0
    @uk.ac.sussex.cluster

7.  ^b525 Twenty-third Street NW^cWashington^dDC^f20037^eUnited
    States

NOTE FOR SYSTEMS ANALYSTS

Different countries have different preferred orders for elements in an address.  If the database is used to produce address labels, a print format should be developed which bases its order of elements on the country name.  In this case, special efforts should be made to enter country names consistently.

_____________________________________________________________________

6  TRAINING OPPORTUNITIES
_____________________________________________________________________

448  START AND END DATES AND DURATION

This field is:

-  Optional
-  Repeatable

SUBFIELDS
	^a  Date in formalized form
	^b  Date in non-formalized form
	^c  Duration

RULES FOR ENTRY

1.  The date when the training opportunity came into being and, if it no longer exists, the date when it ceased may be entered in this field.

2.  Dates may be entered either in free format or in a formalized style in accordance with ISO 8601, or both.  The formalized style is recommended if it will be required to search on these dates.

3.  Formalized dates should be entered in subfield a.  Non-formalized dates should be entered in subfield b.

4.  Formalized dates should consist of the year in full, two figures for the month (if known: otherwise write 00), and two figures for the day (if known: otherwise enter 00). The start date should be separated from the end date by a hyphen

5.  If the organization ceased and was then reinstated, this field may be repeated.  Enter the data in repeated fields (separated by percent signs).

6.  Further information about the duration of the event may be given in subfield c.

EXAMPLES

1.  ^a19930125           [Course started on 25 January, 1993] 

2.  ^a19920102-19920331^c3 months [Course due to take place
                         from 2 Jan 1992 to 31 March 1992]

3.  ^aOne year           [Course takes place each year]

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

500  NOTE

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note

RULES FOR ENTRY

1.  This field may be used to record any relevant information about the training opportunity or its activities for which no specific field is provided, e.g. the history of the training opportunity.

2.  Notes may be made here about the source of information.

3.  If there are several notes, enter them in repeated fields (separated by percent signs).

4.  Note that course requirements should be entered in field 850.

5.  It may be preferred to enter all data in field 600 (Description)

EXAMPLES

1.   ^aNot suitable for absolute beginners

2.   ^aInformation taken from Professional Managers for the Arts and Culture? Arts Council of Finland, 1992

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

600  DESCRIPTION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Description
	^l  Language

RULES FOR ENTRY

1.  This field may be used for a free-text description of the training opportunity.  Include Objectives and a Brief description of a course or fellowship. Teaching methods may also be included, but degree should be entered in field 810 (Educational Qualifications).

2.  If there is more than one paragraph in the description, enter them in repeated fields (separated by percent signs).

3.  <.....>  may be used within the description to delimit index terms (for searching purposes).

4.  If it is desired to enter the description in different languages,  enter each in a repeated field and after each repeat the code for the language in ^l.

EXAMPLES

1.  ^aObjectives: To train museum curators (for national museums) and heritage site inspectors, allowing them to supplement their practical and professional knowledge%^aFocuses on museology and cultural heritage as well as administration and management.

2.  ^aObjective: To provide training in cultural management%^aA part time programme completes studies of students majoring in other fields

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

610  CLASSIFICATION SCHEME NOTATION

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Notation

RULES FOR ENTRY

1.  One or more classification numbers, codes, etc., may be entered in subfield a which correspond to the training opportunity's area(s) of interest.

2.  If more than one number, etc., is used, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.	^a400				[Number for linguistics
						in Dewey Classification]

2.	^a342.83				[Number for women in society
						in Universal Decimal Classification]

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

620  SUBJECT DESCRIPTOR

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Subject descriptor

RULES FOR ENTRY

1.  One or more descriptors which correspond to the training opportunity's area(s) of expertise may be entered in subfield a.

2.  If more than one descriptor is used, enter them in repeated fields (separated by percent signs).

3.  If the training opportunity is concerned with a particular geographical area, this may be identified here by appropriate descriptors.

4.  The descriptors may be controlled according to a subject system, e.g. selected from a thesaurus or a list of subject headings.

EXAMPLES

1.	^aEducation%^aEducational innovations

2.	^aLatin America

3.	^aCultural domination%^aMulticulturalism

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

700  HUMAN RESOURCES

This field is:

-  Optional
-  Not repeatable

SUBFIELD
	^a  Numbers of persons and positions

RULES FOR ENTRY

1.  This field may be used to record details of the number of staff or persons involved in the training activity.

2.  Enter the numbers of persons with their level of responsibility.

3.  Separate data for each level of responsibility with a comma and space.

EXAMPLES

1.  ^a1 director, 1 reader, 1 senior lecturer, 5 lecturers, 2 secretaries

2.  ^a3 lecturers

3.  ^a12 trainers, 6 technicians, 3 auxiliary personnel

4.  ^a5 staff

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

705  EQUIPMENT AND OTHER RESOURCES

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a Equipment and other resources

RULES FOR ENTRY

1.  This field may be used to record details of equipment (e.g. computers), buildings, training rooms at the disposal of a course.

EXAMPLES

1.  ^aHP 3000 minicomputer, 26 IBM XT microcomputers

2.  ^a2 research laboratories, 1 administrative building

3.  ^a25 places in a language laboratory

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

710  FINANCIAL RESOURCES

This field is:

- Optional
- Repeatable

SUBFIELDS

	^a  Financial resources

RULES FOR ENTRY

1.  This field may be used to record any details about financial resources other than income and expenditure.

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

715  INCOME COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Source of funding
	^b  Amount of funding
	^c  Time period
	^d  Note

RULES FOR ENTRY

1.  This field may be used to record details of the organization's sources of income.

2.  Enter the source of income in subfield a and the amount in subfield b.  In subfield c, enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several sources of funding, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aStudents fees^b15,000 GBP^c1993-94%^aGovernment subsidy
^b21,000 GBP^c1993-94%^aOther sources^b53,000 GBP^c1993-94

2.  ^aTotal income^b150,000 USD^c1989-90

3.  ^aMinistry of Education^b75 per cent%^aCourse fees^b25
    per cent

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

716  EXPENDITURE COMPONENTS

This field is:

-  Optional
-  Repeatable

SUBFIELDS

	^a  Type of component
	^b  Amount
	^c  Time period
	^d  Additional information

RULES FOR ENTRY

1. This field may be used to record details of the organization's expenditure.

2.  Enter the type of expenditure in subfield a and the amount in subfield b.  In subfield c enter the time period to which this applies.  Any other information may be recorded in subfield d.

3.  Amounts may be specified in monetary or percentage terms.  In the latter case write out "per cent" - do not use a percent sign as CDS/ISIS will replace it by semi-colon when printing.

4.  Currency should be specified using abbreviations taken from ISO 4217 (see Section 14).

5.  If there are several expenditure components, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.  ^aSalaries^b1,540,000 GBP^c1987-88%^aLibrary acquisitions
^b561,000 GBP^c1987-88%^aexpenditure^b347,000 GBP^c1987-88

2.  ^aTotal expenditure^b145,900 USD^c1989-90

3.  ^aStaff^b75 per cent%^aEquipment^b10 per cent

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

810 EDUCATIONAL QUALIFICATIONS

This field is:

-  Optional
-  Not repeatable

SUBFIELD

	^a  Educational qualifications gained from training opportunity

RULES FOR ENTRY

1.  Any formal educational qualifications gained by undertaking the course may be entered in subfield a.

EXAMPLES

1.	^aMA (Language and Literature Science

2.	^aLic. (Univ. de Barcelona)		[Licenciado, Universidad de 
								Barcelona awarded]

_____________________________________________________________________

9  TRAINING OPPORTUNITIES
_____________________________________________________________________

850  COURSE ENTRANCE REQUIREMENTS

This field is:

-  Optional
-  Repeatable

SUBFIELD

	^a  Note of requirements

RULES FOR ENTRY

1.  This field may be used to record any relevant information about the requirements for participating in training.

2.  If there are several notes, enter them in repeated fields (separated by percent signs).

EXAMPLES

1.   ^aFor three year Arts Management and Arts Policy programme a BA is required.

2.   ^aThe one-year postgraduate course requires at least two years' employment in a senior position

10. HOW TO ENTER PERSONAL NAMES

10.1  Application

The following rules relate to the entry of personal names where they are to be used as search terms, i.e. as authors, investigators, directors, organizers, trainers, etc.

10.2  Authority file

If your library or information centre frequently has to cope with complex personal names, it is recommended that you keep a personal name authority file to make sure that the names are entered consistently.  This file could be in the form of a card index, or a separate file on CDS/ISIS.

The file should have records showing the correct form of name, and see cross-references from other forms of the name.  If it is on cards, the card for the preferred form should have "tracings" to show from what other forms of name references have been made.

EXAMPLE

1.  Post, Laurens van der
        use for  Der Post, Laurens van
        use for  Van der Post, Laurens van der

    Der Post, Laurens van
        see  Post, Laurens van der

    Van der Post, Laurens van der
        see  Post, Laurens van der

10.3  General rule

If the name falls into the pattern of surname or family name and forenames or initials, then enter the surname or family name of the person in subfield a and enter the remaining parts of the name (forenames, initials, etc.) in subfield b.  Other subfields may be used to enter honorific titles, roles, dates, etc., as specified for the particular field.

EXAMPLES

1.   ^aSimenon^bGeorges

2.   ^aSmith^bL.C.

3.   ^aWong^bYuen-sang

10.4  Determining the entry element

If the person's name consists of several parts, first try to determine which part is the family name or surname from the source itself, e.g. by looking for the name in the contents list, bibliography or preface.  Otherwise it may be possible to determine this from the national bibliography or other authoritative list of the author's country.

If it is still not possible to determine which part of the name to use as surname or family name, follow the rules below.

10.5  Compound surnames

Compound surnames are surnames consisting of two or more proper names.  Except for Portuguese names, and names of married women whose surname consists of their surname before marriage and their husband's surname, the whole surname should be entered in subfield a.  If the compound surname is hyphenated, then keep the words together and retain the hyphen.

EXAMPLES

1.   ^aLloyd Webber^bAndrew

2.   ^aSoulez Larivière^bDaniel

3.   ^aLeprince de Beaumont^bJeanne-Marie

4.   ^aDroste-Hülshoff^bAnnette von

5.   ^aWebb-Bowen^bVictoria

10.5.1  Married women whose surname consists of their surname before marriage and their husband's surname

Enter the whole of the compound surname in subfield a if the person's language is Czech, French, Hungarian, Italian or Spanish.  In all other cases, enter the husband's surname in subfield a and the rest of the name in subfield b.  (For hyphenated names see above.)

EXAMPLES

1.   ^aBonacci Brunamonti^bAlinda                    [Italian]

2.   ^aMolina y Vedia de Bastianini^bDelfina         [Spanish]

3.   ^aStowe^bHarriet Beecher                        [English]

10.5.2  Portuguese names

If the person's language is Portuguese, enter the last element of the name in subfield a and the remainder in subfield b. 

EXAMPLE

1.   ^aFigueiredo^bAdelpha Silva Rodrigues de

2.   ^aLongato^bVilma dos Santos   [a Brazilian of Italian ancestry]

10.6  Surnames with prefixed articles or prepositions

If possible, determine the entry element from the source, or directories etc. in the person's language or country.  Otherwise use the rules below, which summarize practice according to language or language group.

10.6.1  Afrikaans

Include the prefix in subfield a.

EXAMPLE

1.   ^aVan der Merwe^bC.V.

10.6.2  Dutch (Flemish)

Include the prefix 'ver' in subfield a, but enter other prefixes in subfield b.

EXAMPLES

1.   ^aVer Bruggen^bP.

2.   ^aDijk^bTeun Adrianus van

10.6.3  English

Include the prefix in subfield a.

EXAMPLES

1.   ^aDe Beer^bGavin

2.   ^aVon Wartburg^bUrsula

3.   ^aL'Amour^bLouis

10.6.4  French

If the prefix consists of an article ("le", "la", "l'", "les") or a contraction of an article and a preposition ("du", "des") include this in subfield a.

EXAMPLES

1.   ^aLa Plante^bRichard

2.   ^aDu Mont^bMadeleine

Otherwise include the prefix in subfield b.

EXAMPLE

1.   ^aBeauvoir^bSimone de

10.6.5 German

If the prefix consists of an article or a contraction of an article and a preposition (e.g. "am", "vom", "zum", "zur") include this in subfield a.

EXAMPLES

1.   ^aVom Höfe^bP.

2.   ^aZur Hausen^bHarald

Otherwise include the prefix in subfield b.

EXAMPLES

1.   ^aGoethe^bJohann Wolfgang von

2.   ^aHeyde^bHelmut Heinrich von der

10.6.6 Italian

Include the prefix in subfield a.

EXAMPLES

1.   ^aDel Bianco^bRenato

2.   ^aDi Gregorio^bLamberto

3.   ^aLo Cascio^bFerdinando

10.6.7 Portuguese

Include the prefix in subfield b.

EXAMPLES

1.   ^aAzevedo^bAmândio Anes de

2.   ^aSantos^bTheotonio dos

10.6.8 Scandinavian languages

Include the prefix in subfield b.

EXAMPLES

1.  ^aPlaten^bMagnus von

2.  ^aEynden^bJo van der

10.6.9 Spanish

If the prefix consists of an article only ("el", "la", "las", "los"), include it in subfield a.

EXAMPLE

1.  ^aLas Heras^bR.J.

Include other prefixes in subfield b.

EXAMPLE

1.  ^aPrado y Muñoz^bJavier Moscoso del

10.7 Other prefixes

If a prefix is not an article, preposition, or combination of the two, include it in subfield a.

EXAMPLES

1.   ^aAbd el Ghaffar^bAhmed

2.   ^aAbu Deeb^bKamal Michael

3.   ^aAp Simon^bHuw

4.   ^aMac An Abhluaird^bRuileamh

5.   ^aO Riain^bFlann

10.8 Hyphenated or combined prefixes

If the prefix is hyphenated or combined (without a space) with the surname, include it in subfield a.

EXAMPLES

1.   ^aDubois^bC.P.R.

2.   ^aMcIlwaine^bJohn

10.9  Names including a patronymic

If a name consists of one or more given names plus a patronymic, enter the given name in subfield a followed by the rest of the name.

EXAMPLE

1.   ^aSolomon Gebre Christos  ['Solomon' is given name; 'Gebre'
                               Christos' is patronymic]

10.10  Special rules for names in certain languages

The following rules give guidance on names in certain non-European languages and languages which are not written in the Roman alphabet.  For more details, please refer to Names of persons: national usages for entries in catalogues, compiled by the IFLA International Office for UBC, 3rd ed., London, The Office, 1977.

10.10.1  Arabic names

In general, the last element of the name should be entered in subfield a and other parts of the name in subfield b.

If the name includes a family name beginning with the prefix 'Al', 'El', 'Abou', 'Abun', 'Abdul', 'Abdel', 'Ben' or 'Ibn', include the prefix in subfield a.

EXAMPLES

1.  ^aBachir^bImad

2.  ^aAbdul Maguid^bMohammad Bahr

3.  ^aAbou-Rabia^bHassan

4.  ^aAl-Saleh^bFaiqa

5.  ^aEl-Shazly^bSaad

6.  ^aIbn Idris^bHassan Ahmed

Note, however, that the phrase 'El-Din(e)' or 'al-Din' is not a prefix but a suffix that may follow either a forename or a family name.

EXAMPLE

1.  ^aEz El-Din^bAmin

10.10.2  Burmese and Karen names

If the first element is a Western forename, enter the vernacular name in subfield a and the forename in subfield b.  Otherwise, enter the whole name in subfield a.  Terms of address, such as 'U', 'Daw', 'Ko', 'Ma', 'Maung', 'Bo' and 'Saya' should be entered in subfield c.

EXAMPLES

1.  ^aAung^bStanley

2.  ^aThant^cU

3.  ^aAung Kyaw Myint^cU

4.  ^aCho^cMaung

5.  ^aHtin Aung^cMaung

10.10.3 Chinese names

The family name is the first element of the name, but Chinese living abroad frequently reverse the traditional order.  Enter the family name in subfield a, and other parts of the name in subfield b.  If a non-Chinese name appears in front of the Chinese name, include this forename in subfield b.

EXAMPLES

1.  ^aVoon^bChoon-King

2.  ^aChin^bKin Wah

3.  ^aLi^bSimon Kwok Cheang

10.10.4  Indic names

10.10.4.1  Punjabi names

Punjabi names characteristically include the element 'Singh'.  Enter the whole name in subfield a.

EXAMPLES

1.  ^aRao Birendra Singh

2.  ^aPiara Singh Sambhi

10.10.4.2  Other names

When parts of the name have been reduced to initials, enter the part of the name written in full in subfield a.  If it cannot be established which part of the name should be the entry element, enter the last element in subfield a and the remainder in subfield b.

EXAMPLES

1.  ^aRao^bS.C.

2.  ^aGhani Khan Chaudhury^bA.B.A.

3.  ^aReddy^bVijay Bhaskara

10.10.5  Indonesian names

If the name contains terms of relationship, such as 'bin' (son of), 'binte' or 'binti' (daughter of), ' or 'ibni' (son of - royalty), enter the whole name in direct order in subfield a.

EXAMPLE

1.  ^aM.S. bin Mahfooz

Otherwise, enter the last element of the name in subfield a and the remainder of the name in subfield b.

EXAMPLE

1.  ^aDjajadiningrat^bIdrus Nasir

10.10.6  Malay names

If it is known which element of the name the person treats as surname, then enter that in subfield a and the remainder of the name in subfield b.  Otherwise enter the first element of the name in subfield a and the remainder in subfield b.

EXAMPLES

1.  ^aMerican^bFaridah

2.  ^aLuat anak Jabu

10.10.7  Thai names

Enter the whole name in subfield a.

EXAMPLES

1.  ^aKrisana Kitiyadisai

2.  ^aPreeda Pathanathabutr

11.  HOW TO ENTER CORPORATE NAMES

11.1 Application

The following rules relate to the entry of names of corporate bodies where they are to be used as search terms, i.e. as names in PROJECTS, INSTITUTIONS, EVENTS, TRAINING OPPORTUNITIES records, corporate authors of documents, etc.  A corporate body is an organization or a group of persons that is identified by a particular name and that acts, or may act, as an entity.  Typical examples of corporate bodies are associations, institutions, business firms, governments, government agencies, and educational establishments.  The examples given here are general examples and are not intended to represent the kind of body which would be found on a database on cultural development.

11.2  Authority file

If your library or information centre frequently has to cope with complex corporate names, it is recommended that you keep a corporate name authority file to make sure that the names are entered consistently.  This file could be in the form of a card index, or a separate file on CDS/ISIS.  It could be combined with the personal name authority file (see Section 10.2).

The file should have records showing the correct form of name, and see cross-references from other forms of the name.  If it is on cards, the card for the preferred form should have "tracings" to show from what other forms of name references have been made.

EXAMPLE

1.   Slade School of Fine Arts
           see University College London.  Slade School of Fine Arts

     University College London.  Slade School of Fine Arts
           use for Slade School of Fine Arts

Although the formats defined in the previous sections do not make provision for references from non-preferred forms of name, it is possible to provide access from an acronym when this is the non-preferred form by entering it in subfield x.

EXAMPLE

1.   ^aWorld Health Organization^2WHO

11.3  General rule

Enter a corporate body in subfield a under the name by which it is commonly identified, except when the rules below require it to be entered under the name of a higher or related body, or under the name of a government.

The name by which the corporate body is commonly identified should be determined from items issued by it in its language, or, if this is not possible, from reference sources.

11.3.1  Punctuation

If the name of the corporate body consists of or contains initials, use punctuation according to the usage of the body.  In case of doubt, omit the punctuation.  Do not leave a space between a full stop, etc., and an initial following it.

EXAMPLES

1.   ^aAssociation française de normalisation

2.   ^aBanco de Guatemala

3.   ^aJoint Working Group on the Rotation of the Earth

4.   ^aUNICEF

11.4  Variant names

If variant spellings of the name appear, use the form resulting from an official change in orthography or otherwise the predominant spelling.  If there are variant forms of name, use the form which is predominant in items issued by the body.  If there is no predominant form, use a brief form that differentiates the body from others with similar brief names.  Note the provision for acronyms as non-preferred forms in subfield x.

EXAMPLES

1.   ^aEuratom               [not 'European Atomic Energy Community']

2.   ^aUnesco                [not 'United Nations Educational,
                             Scientific and Cultural Organization']

11.4.1  Language

If the name appears in different languages, use the form in the official language of the body.  If there is more than one official language and one of these is English, use the English form.  (Alternatively use the form in your preferred language, if available.)

EXAMPLE

1.   ^aEuropean Economic Community
                       [not 'Communauté économique européenne']

2.   ^aInternational Labour Organization
                       [not 'Organización Internacional del Trabajo']

11.4.2  Governments

Use the conventional name of a government unless the official name is in common use.  The conventional name is the geographic name of the area over which the government exercises jurisdiction.

EXAMPLE

1.   ^aJordan             [not 'The Hashemite Kingdom of the Jordan']

2.   ^aGuatemala          [not 'República de Guatemala']

11.5  Additions to names

If the name does not convey the idea of a corporate body, add a general designation in English (alternatively in your preferred language) in subfield c.

EXAMPLES

1.   ^aTerre des Hommes^cOrganization

2.   ^aBelfast^bShip

If two or more bodies have the same name, or names so similar that they may be confused, add the name of the place where the body is located or another distinguishing designation in subfield c.  Give the English (alternatively your preferred language) form of place name if there is one in common use.

EXAMPLES

1.   ^aMuseo Arqueológico^cBurgos, Spain

2.   ^aMuseo Arqueológico^cCusco, Peru

3.   ^aMagdalen College^cOxford, England

4.   ^aMagdalene College^cCambridge, England

11.5.1  Governments

If the government has jurisdiction over an area other than a city or town, but bears the same name as the city or town, include the type of area in subfield c.  Separate this  from other additions by a space, colon, and space.  Use the English term (alternatively the term in your preferred language) if possible, otherwise the vernacular.

EXAMPLES

1.   ^aBern^cSwitzerland

2.   ^aBern^cSwitzerland : Canton

11.6  Omissions from names

Omit an initial article unless the article is part of the name of a person or place.

EXAMPLES

1.   ^aCity University         [not 'The City University']

2.   ^aLa Jolla Museum of Contemporary Art

Omit terms or abbreviations indicating incorporation, type of incorporation, or state ownership of a corporate body, e.g. GmbH, Inc., Ltd., plc, S.A., VEB, unless they are needed to make clear that the name is that of a corporate body.

EXAMPLES

1.   ^aMilder Kaiser Engenharia               [omit SA]

2.   ^aTechnische Werke der Stadt Stuttgart   [omit AG]

3.   ^aBechtel Power                          [omit Corp.]

4.   ^aSoftware Ltd.                          [retain Ltd.]

11.7  Subordinate and related bodies

Unless the name of the subordinate body is one of the following types, enter the body under its own name in subfield a.  If you have an authority file (see Section 11.2) make a reference from the name of the higher body with the appropriate subheading to the name of the subordinate body.

The following bodies should be entered subordinately, i.e. the higher body should be entered in subfield a and the subordinate body in subfield b:

(a) A branch, department, division, office, section or unit of the higher body.

EXAMPLES

1.   ^aCompañia Española de Motores^bDivisión Comercial

2.   ^aBritish Library^bCopyright Receipt Office

3.   ^aSoutheast Asian Ceramic Society^bWest Malaysia Chapter

(b) A faculty, school, college, institute, laboratory, etc.,  of a university, whose name simply indicates the field of study.

EXAMPLES

1.   ^aUniversity of Oxford^bInorganic Chemistry Laboratory

2.   ^aUniversidad de Granada^bEscuela Universitaria de Profesorado 
     de Educación General Básica

(c) A committee or commission set up by a higher body.

EXAMPLES

1.   ^aInternational Geographical Union^bCommission on Geographical
     Education

2.  ^aChurch of Scotland^bCommittee on Public Worship and Aids to
    Devotion

(d) A name that includes the entire name of the higher or related body.

EXAMPLE

1.  ^aCambridge University^bLibrary     [name: Cambridge University 
                                        Library]

11.7.1  More than two levels

If there are several hierarchical levels in the name of the body, omit the intermediate levels unless they are needed to identify the body.

EXAMPLE

1.   ^aUniversity of Sussex^bArmament and Disarmament Information
     Unit                               [omit intermediate level:
                                        Science Policy Research Unit]

11.7.2  Joint committees, commissions, etc.

Enter a body made up of representatives of two or more bodies under its own name.

EXAMPLE

1.   ^aJoint Working Group on the Rotation of the Earth

If the parent bodies are entered as subheadings of a common higher body, enter the higher body in subfield a and the joint unit in subfiled b.

EXAMPLE

1.   ^aAmerican Library Association^bJoint Committee to Compile a
     List of International Subscription Agents  
                                                  [A joint committee
     of the Acquisitions and Serials sections of the American Library
     Association's Resources and Technical Services Division]

11.8  Government bodies

A government body is one created or controlled by a government.

Unless the name is one of the following types, enter the body under its own name in subfield a.

EXAMPLES

1.   ^aConsejo Superior de Investigaciones Científicas
                                        [Not under 'Spain']

2.   ^aLand Authority for Wales         [Not under 'Great Britain']

(a) The name contains a word implying subordination, such as 'department', 'division', 'office', 'committee', 'commission'.

EXAMPLES

1.   ^aBrazil^bDepartamento de Saude

2.   ^aUnited States^bAtomic Energy Commission

3.   ^aCanada^bNational Advisory Committee on AIDS

(b) The name of a ministry or other highest-level agency.

EXAMPLES

1.   ^aItaly^bMinistero del bilancio e della programmazione economica

2.   ^aGreat Britain^bMinistry of Agriculture, Fisheries and Food

3.   ^aSpain^bMinisterio de Fomento

(c) The name of a legislative body.

EXAMPLES

1.   ^aJamaica^bSenate

2.   ^aIceland^bAlthing

(d)  The name of a court.  If the name of the place or area served is needed to distinguish the court from others of the same name, enter it in subfield c.

EXAMPLE

1.   ^aOntario^bHigh Court of Justice

2.   ^aGreat Britain^bCrown Court^cSnaresbrook

(d)  The name of a principal service of the armed forces.

EXAMPLE

1.   ^aUnited States^bArmy

(e)  The name of an embassy or consulate.  Enter the country to which it is accredited in subfield c, and, in the case of a consulate, the location.

EXAMPLES

1.   ^aBrazil^bEmbaixada^cGreat Britain

2.   ^aYugoslavia^bPoslanstvo^cU.S.

3.   ^aGreat Britain^bConsulate^cCasablanca, Morocco

(f) The name of a delegation to an international or intergovernmental body.

EXAMPLE

1.   ^aUruguay^bDelegación en las Naciones Unidas

11.8.1  Indirect subheadings

If the name of the agency is, or is likely to be, used by another agency of the same government then add the name of the lowest body in the hierarchy which will distinguish between the agencies.  Add this in subfield c, followed by a full stop.

EXAMPLES

1.   ^aNigeria^bMinistry of Education. General Publications Section
            [Other ministries may have General Publications Sections]
2.   ^aGreat Britain^bCentral Office of Information. Reference
     Division
            [Other bodies have a Reference Division]

12. CODES FOR LANGUAGES

At present there is no suitable, internationally-accepted code for names of languages. A list of codes, taken from the ISDS manual, is found in the CCF manual and should be used here. For technical reasons, only a selection is reproduced here. The full list may be found in section 4.1 of CCF/B and of CCF/F.

Arabic              ara                      Tibetan             tib
Bengali             ben                      Turkish             tur
Bulgarian           bul                      Ukrainian           ukr
Burmese             bur                      Urdu                urd
Chinese             chi                      Vietnamese          vie
Croatian            scr                      Zulu                zul
Czech               cze
Danish              dan
Dutch, Flemish      dut
English             eng
Finnish             fin
French              fre
German              ger
Greek, classical    grc
Greek, modern       gre
Gujarati            guj
Hausa               hau
Hebrew              heb
Hindi               hin
Hungarian           hun
Icelandic           ice
Indonesian          ind
Italian             ita
Japanese            jpn
Korean              kor
Latin               lat
Latvian             lav
Lithuanian          lit
Malagasy            mla
Malay               may
Nepali              nep
Norwegian           nor
Panjabi             pan
Persian             per
Polish              pol
Portuguese          por
Romanian            rum
Russian             rus
Serbian             scc
Sinhalese           snh
Slovak              slo
Slovenian           slv
Somali              som
Spanish             spa
Swahili             swa
Swedish             swe
Tagalog             tag
Tamil               tam
Thai                tha

13. CODES FOR COUNTRIES

The two-digit Codes for the Names of Countries found in international standard ISO 3166 are recommended for use in the CCF.  They are reproduced in section 4.3 of CCF: the Common Communication Format.

They are frequently updated, and the most up-to-date listing should be available from your national standards organization.  In case of difficulty, contact:

International Organization for Standardization
Case postale 56
CH-1211 GENEVA 20
Switzerland

14.  CODES FOR THE REPRESENTATION OF CURRENCIES

The following codes may be used to represent currencies.  The list is based on International Standard ISO 4217-1981.  It is intended to show the correct code for a given currency: it does not show all countries, nor all currencies used in the countries listed.

Country or entity				Currency				Code
_____________________________________________________________________

Afghanistan					Afghani				AFA
Albania						Lek					ALL
Algeria						Algerian Dinar			DZD
Angola						Kwanza				AOK
Argentina						Argentine Peso			ARP
Australia						Australian Dollar		AUD
Austria						Schilling				ATS
Bahamas						Bahamian Dollar		BSD
Bahrain						Bahraini Dinar			BHD
Bangladesh					Taka					BDT
Barbados						Barbados Dollar		BBD
Belgium						Belgian Franc			BEF
Belize						Belize Dollar			BZD
Bermuda						Bermudan Dollar		BMD
Bolivia						Bolivian Peso			BOP
Botswana						Pula					BWP
Brazil						Cruzeiro				BRC
Brunei						Brunei Dollar			BND
Bulgaria						Lev					BGL
Burma						Kyat					BUK
Burundi						Burundi Franc			BIF
Canada						Canadian Dollar		CAD
Cape Verde					Cape Verde Escudo		CVE
Cayman Islands					Cayman Islands Dollar	KYD
Central Africa					CFA Franc BEAC			XAF
Chile						Chilean Peso			CLP
China						Yuan Renminbi			CNY
Colombia						Colombian Peso			CLP
Comoros						Comoros Franc			KMF
Costa Rica					Costa Rican Colon		CRC
Cuba							Cuban Peso			CUP
Cyprus						Cyprus Pound			CYP
Czechoslovakia					Koruna				CSK
Denmark						Danish Krone			DKK
Djibouti						Djibouti Franc			DJF
Dominican Republic				Dominican Peso			DOP
East Caribbean					East Caribbean Dollar	XCD
East Timor					Timor Escudo			TPE
Ecuador						Sucre				ECS
Egypt						Egyptian Pound			EGP
El Salvador					El Salvador Colon		SVC
Equatorial Guinea				Ekwele				GQE
Ethiopia						Ethiopian Birr			ETB
European Monetary Cooperation	European Currency		XUE
	Fund (EMCF)				Unit (ECU)
Falkland Islands (Malvinas)		Falkland Islands Pound	FKP
Fiji							Fiji Dollar			FJD
Finland						Markka				FIM
Country or entity				Currency				Code
_____________________________________________________________________

France						French Franc			FRF
French Overseas Territories		CFP Franc				XPF
Gambia						Dalasi				GMD
Germany						Deutsche Mark			DEM
Ghana						Cedi					GHC
Gibraltar						Gibraltar Pound		GIP
Greece						Drachma				GRD
Guatemala						Quetzal				GTQ
Guinea						Syli					GNS
Guinea-Bissau					Guinea-Bissau Peso		GWP
Guyana						Guyana Dollar			GYD
Haiti						Gourde				HTG
Honduras						Lempira				HNL
Hong Kong						Hong Kong Dollar		HKD
Hungary						Forint				HUF
Iceland						Iceland Krona			ISK
India						Indian Rupee			INR
Indonesia						Rupiah				IDR
International Monetary Fund		Special Drawing Rights	XDR
	(IMF)					(SDR)
Iran							Iranian Rial			IRR
Iraq							Iraqi Dinar			IQD
Ireland						Irish Pound			IEP
Israel						Shekel				ILS
Italy						Lira					ITL
Jamaica						Jamaican Dollar		JMD
Japan						Yen					JPY
Jordan						Jordanian Dinar		JOD
Kampuchea, Democratic			Riel					KHR
Kenya						Kenyan Shilling		KES
Korea, Democratic People's		North Korean Won		KPW
	Republic of
Korea, Republic of				Won					KRW
Kuwait						Kuwaiti Dinar			KWD
Lao People's Democratic Republic	Kip					LAK
Lebanon						Lebanese Pound			LBP
Lesotho						Maloti				LSM
Liberia						Liberian Dollar		LRD
Libyan Arab Jamahiriya			Libyan Dinar			LYD
Luxembourg					Luxembourg Franc		LUF
Macau						Pataca				MOP
Madagascar					Malagasy Franc			MGF
Malawi						Kwacha				MWK
Malaysia						Malaysian Ringgit		MYR
Maldives						Maldive Rupee			MVR
Mali							Mali Franc			MLF
Malta						Maltese Pound			MTP
Mauritania					Oguiya				MRO
Mauritius						Mauritius Rupee		MUR
Mexico						Mexican Peso			MXP
Mongolia						Tugrik				MNT
Morocco						Moroccan Dirham		MAD
Mozambique					Metical				MZM
Nepal						Nepalese Rupee			NPR

Country or entity				Currency				Code
_____________________________________________________________________

Netherlands					Netherlands Guilder		NLG
Netherlands Antilles			Netherlands Antillian	ANG
							Guilder
New Zealand					New Zealand Dollar		NZD
Nicaragua						Cordoba				NIC
Nigeria						Naira				NGN
Norway						Norwegian Krone		NOK
Oman							Rial Omani			OMR
Pakistan						Pakistan Rupee			PKR
Panama						Balboa				PAB
Papua New Guinea				Kina					PGK
Paraguay						Guarani				PYG
Peru							Sol					PES
Phillipines					Phillipine Peso		PHP
Poland						Zloty				PLZ
Portugal						Portuguese Escudo		PTE
Qatar						Qatari Rial			QAR
Romania						Leu					ROL
Rwanda						Rwanda Franc			RWF
St. Helena					St. Helena Pound		SHP
Samoa						Tala					WST
Sao Tome and Principe			Dobra				STD
Saudia Arabia					Saudi Riyal			SAR
Seychelles					Seychelles Rupee		SCR
Sierra Leone					Leone				SLL
Singapore						Singapore Dollar		SGD
Solomon Islands				Solomon Islands Dollar	SBD
Somalia						Somali Shilling		SOS
South Africa					Rand					ZAR
Spain						Spanish Peseta			ESP
Sri Lanka						Sri Lanka Rupee		LKR
Sudan						Sudanese Pound			SDP
Suriname						Suriname Guilder		SRG
Swaziland						Lilangeni				SZL
Sweden						Swedish Krona			SEK
Switzerland					Swiss Franc			CHF
Syrian Arab Republic			Syrian Pound			SYP
Taiwan, Province of China		New Taiwan Dollar		TWD
Tanzania, United Republic of		Tanzanian Shilling		TZS
Thailand						Baht					THB
Tonga						Pa'anga				TOP
Trinidad and Tobago				Trinidad and Tobago		TTD
							Dollar
Tunisia						Tunisian Dinar			TND
Turkey						Turkish Lira			TRL
Uganda						Uganda Shilling		UGS
United Arab Emirates			UAE Dirham			AED
United Kingdom					Pound sterling			GBP
United States					US Dollar				USD
Uruguay						Uruguayan Peso			UYP
Vanuatu						Vatu					VUV
Venezuela						Bolivar				VEB

Country or entity				Currency				Code
_____________________________________________________________________

Viet Nam						Dong					VND
Yemen						Yemeni Rial			YER
Yemen, Democratic				Yemeni Dinar			YDD
Yugoslavia					New Yugoslavian Dinar	YUD
Zaire						Zaire				ZRZ
Zambia						Kwacha				ZMK
Zimbabwe						Zimbabwe Dollar		ZWD

15.  THE SAMPLE DATABASE

The diskette supplied with this manual contains a database called CLT containing 40 sample records.  Records 1-10 are for documents, 11-20 are for persons, 21-30 are for institutions, and 31-40 are for projects.

To avoid any embarrassment or any problems with data protection legislation, all persons appearing in these records are fictitious.  Many of the records, though relating to recognisable entities, have been embellished to enhance their role as examples.

16.  REFERENCES

16.1 ISO standards referred to in the text.

ISO 2108-1978. International Standard Book Numbering (ISBN) 

ISO 2146-1988. Documentation - Directories of libraries, archives, information and documentation centres, and their data bases 

ISO 2709-1981. Format for Bibliographic Information Interchange on Magnetic Tape

ISO 3166-1988. Codes for the Representation of Names of Countries

ISO 3297-1986. International Standard Serial Numbering (ISSN)

ISO 4217-1981. Codes for the representation of currencies

ISO 8601-1988. Data elements and exchange formats -- Information interchange - Representation of dates and times

16.2 General references

Anglo-American Cataloguing Rules, 2nd ed. London, Library Association, 1978

CCF : the Common Communication Format. 2nd ed. Paris, Unesco, 1988 (PGI-88/WS/2)

CCF/B : the Common Communication Format for Bibliographic Information. Paris: Unesco, 1992 (PGI-92/WS/9)

CCF/F : the Common Communication Format for Factual Information. Paris: Unesco, 1992 (PGI-92/WS/8)

Dierickx, H. Reference Manual for machine-readable descriptions of research projects and institutions. Paris, Unesco, 1982

Di Lauro, Anne. IDIN manual for the creation and management of a bibliographic database using Micro-ISIS. Paris, OECD, 1988

FIIR : Formato de Intercambio de Información Referencial. Paris, Unesco, 1989

Hopkinson, Alan. Implementation notes for users of the CCF. Paris, Unesco, 1990

Hopkinson, Alan. Implementation notes for users of the Common Communication Format for Bibliographic Information (CCF/B). Paris: Unesco, 1993

Hopkinson, Alan. Implementation notes for users of the Common Communication Format for Factual Information (CCF/F). Paris: Unesco, 1993

International Federation of Library Associations and Institutions. ISBD(G) : General International Standard Bibliographic Description: Annotated text. IFLA International Office for UBC, 1977  

International Federation of Library Associations and Institutions.
IFLA Committee on Cataloguing. ISBD(M) : International Standard Bibliographic Description for Monographic Publications, First standard edition. London, IFLA UBC Office, 1974 

International Federation of Library Associations and Institutions. Names of persons: national usages for entries in catalogues, compiled by the IFLA International Office for UBC, 3rd ed., London, The Office, 1977

International Federation of Library Associations and Institutions. Committee on Cataloguing. Statement of Principles Adopted at the International Conference on Cataloguing Principles, Paris, October 1961. London, IFLA Committee on Cataloguing, 1971

International ISBN Agency.  The ISBN System Users' Manual.  2nd ed. Berlin: The Agency, 1978

International Serials Data System.  ISDS Manual. Paris: ISDS International Centre, 1983