Avis juridique important

|

31991H0337

91/337/EEC: Commission Recommendation of 6 May 1991 concerning the harmonization within the Community of research and technological development databases

Official Journal L 189 , 13/07/1991 P. 0001 - 0034

COMMISSION  RECOMMENDATIONof 6 May 1991concerning the harmonization within the Community of research and  technologicaldevelopment databases(91/337/CEE)THE COMMISSION OF THE EUROPEAN  COMMUNITIES, Having regard to the Treaty establishing the European Economic Community, Whereas the Commission, in close cooperation with the Member States, may take any necessary action  in orderto promote the coordination of national policies and programmes for research and  technological developments; Whereas the Commission considers that in order to strengthen the scientific and technological bases  of European industry and make the Community more competitive internationally there has to be  continuous and rapid exchange of information between Member States; Whereas the Member States already have structures capable of meeting this need, in particular  national databases for research and technological development; Whereas Community initiatives have been taken in such related fields as the expansion of the  dissemination of information on Community research and technological development, pressure for  standards on information exchange via computers and telecommunications networks and the setting-up  of an integrated European telecommunications network; Whereas, however, databases set up on the basis of national requirements are not fully compatible  with each other; whereas harmonization is necessary to meet Community requirements; Whereas measures to this end must be adopted with an eye to the completion of the internal market  by 1 January 1993; Whereas the Scientific and Technical Research Committee (CREST) has been consulted, HAS FORMULATED THIS RECOMMENDATION: Article 1Member States are hereby  recommended to ensure that, progressively by 1 January 1993, bodies responsible for disseminating  information on research and technological development activities at national level: 1)  harmonize existing national databases in the field of research and technological development so  as to attain the Community's objectives in this area and in particular to promote the coordination  of policies and researchand technological development programmes between Member States; 2)  introduce into the databases referred to in point 1 information on scientific and technological  research projects carried out in undertakings and research institutes in the Member States. The  technical specifications for describing the projects are set out in Annex I; 3)  adopt a multilingual and multidisciplinary common classification system for setting up the  nationaldatabases referred to in point 1. This system must be flexible enough to allow regular  adaptation to changing science and technology requirements. The classification system referred to  is set out in Annex II; 4)  adopt, at a later stage, a dynamic, multilingualand multidisciplinary common thesaurus  (structured language). Article 21.  Member States shall coordinate jointly the action referred to  in Article 1. 2.  They shall inform the Commission of any measures taken in execution of this Recommendation. 3.  The Scientific and Technical Research Committee (CREST) shall monitor the implementation of  this Recommendation and it shall hold a regular exchangeof views on this matter at least every two  years. Article 3This Recommendation is addressed to the Member States.Done at  Brussels, 6 May 1991. For the CommissionFilippo M. PANDOLFIVice-President ANNEX I MANUALCERIFCommon European Research Information FormatFormat developed on  behalf of the planned network of European Research DatabasesContentsPage1.  Scope and use .  42.  Definitions . 43.  Standards and references . 54.  Project definition . 65.  Data  structure: List of data elements . 6II.  Essential data elements . 71.  Administrative labels  . 72.  Relating to the recording of the research project . 83.  Relating to the research  project contents . 94.  Relating to the recording of the contact address . 125.  Relating to  research identification (indexing and retrieving) . 156.  Relating to the 'critical mass` of the  research project . 16II.  Optional data elements . 19Data element index . 206.  References  . 22CERIFCommon European Research Information Format1. Scope and useThe Common European Research project Information Format (Cerif) (;) is designed to  provide a standard format for two major purposes: 1.  to permit the exchange of records with information on research projects between the different  member countries of the European Community; 2.  to serve as the basis for the format for setting up the aimed network between research  databases. The Cerif has been designed with the aim of retaining the highest degree of flexibility for  manipulating with a number of different types of research projects received from the different  existing databases with information on research activities in their country. Therefore a national research database agency may choose for local implementation any format or  formats which are convertible by computer program to Cerif. One goal in creating Cerif was to design a suitable format which might be used directly by national  (or other) agencies starting up a database with information on research activities. The second goal  was to facilitate research information data exchange. This common format provides: - a list of essential data elements (core data elements), - a number of optional data elements which may be useful to describe items further according to the  significance for the project. These provisions allow the agencies to include non-standard elements which are considered useful  within its system, even though if they are not used by other agencies, according to the practices  of the agency which creates the record. 2. DefinitionsData element: the smallest unit of information that is explicitely identified. Field: a portion of a record containing a particular category of data. A field may contain one or more  subfields. A field is characterized by: - the kind: unique-key key non-keya key field is a field on which a search possibility is  required, a unique-key field is a field on which on the one hand a search possibility is required, and on the  other hand must be unique: it is not allowed to have two records with the same value in this  field, - the type: text decimal date, - restrictions: must match to another field in another file or not, - obligation: must be filled out or not. File: a number of records with the same record structure. Record: a collection of specifically defined fields. Subfield: a separately identified part of a field containing a defined element of information. (;) The structure of this manual is based on the 'CCF: The Common Communication Format`, General  Information Programme and Unisist, Unesco, 1984. 3. Standards and referencesThe use of the standardized codes might be controlled by the use of  'must-match fields`. 3.1. Codes for languages  usedDanishDADutchNLEnglishENFrenchFRGermanDEGreekELItalianITPortuguesePTSpanishESSource:  ISO/DIS 6393.2. Codes for countriesSource: ISO 3166Member countries of the European  CommunityBelgiumBEDenmarkDKFranceFRFederal Republic of  GermanyDEGreeceGRIrelandIEItalyITLuxembourgLUNetherlandsNLPortugalPTSpainESUnited  KingdomGBFor the European Community as a whole, an additional 'country code` is adopted: European CommunityEURemark: A list of the overseas areas, with their country codes, of the member countries of the European  Community might be a useful tool to link the research activities carried out in the related  countries. 3.3. Codes for the national currenciesEuropeECUBelgiumBEFDenmarkDKKFranceFFRFederal Republic of  GermanyDEMGreeceGRDIrelandIEPItalyITLLuxembourgLUFNetherlandsNLGPortugalPTESpainESPUnited  KingdomGBPSource: ISO 4217-19783.4. Standard for addressesN° international standard was found for the formats of addresses. 4. Project definition'A research project is any research or development activity with a specific  objective, having a date of start and an expected ending date, carried out within a certain  research unit, with or without a certain amount of external funds.`The proposed dataset is divided  in two main parts: - a part which has to be formatted in a common way, - a part to fill out other relevant information. PART I. ESSENTIAL ELEMENTS: MAIN DATASET- Title, - Abstract (bilinguality of title and abstract will be recommended), - Address (including name of the research unit, department, institute), - Project director (definition: name of the 'holder` of the contract), - Name(s) of the principal investigator(s), - Starting date and expected ending date, - Identification items: - free key words, - controlled terms (Research Thesaurus: optionally) (;)- codes of a classification scheme ($)  (Research Classification Scheme: recommended), - Funding directly related to the project: - funding source, - budget yearly, optionally: breakdown into personnel, functioning, equipment, - Personnel: number of full-time equivalent (FTE) researchers. PART II. ADDITIONAL NOTES: OPTIONAL DATA ITEMSOne should also include some information if  essential for the research project; e.g. concerning: - incorporation in programmes, links with other projects, - cooperation with other institutes, - results (e.g. the number of publications) already produced by the research project, - special equipment whose mention is essential for a proper understanding of the project's scope. 5. Data structure: List of data elements (=)This chapter constitutes of a complete reference list of  the essential (obligatory) and supplementary (optional) data elements. Definition of the two categories:1.  'Essential` data (or 'core` data): any data element so designated must be included in the  description if it is known or derivable from the information supplied by the research project. (It  may happen that an essential data element is absent.)2.  'Supplementary` or 'optional` data: - any data element so designated is regarded as being relevant and worthy of inclusion in the  record describing the project, - the data element is not, however, an absolute requirement for a complete and unambiguous  description and its inclusion is, therefore, optional, at the discretion of the individual  information system. (;) Recommended Research Thesaurus (list of controlled terms): Annex II. ($) Recommended Research Classification Scheme: Annex I. (=) Mainly based on the 'Reference manual for machine-readable descriptions of research projects  and institutions`, General Information Programme and Unisist, Unesco, 1982. It should be noted that a data field which is rated as 'essential` may include optional subfields.  The detailed data element definition will indicate what constitutes the essential portion of each  field. Some users may find that information which is regularly included in their own descriptions is not  present among the essential and supplementary data elements listed in this chapter. In this  connection it should be clear that this document is not intended to be restrictive: it is expected  that users will define additional data fields for local use, as well as harmonizing the 'core` data  according to the basic set of common data elements as given in this document. For the practical dataset several options are possible: - fixed field lengths or variable field length, - fixed field definition (may be used only once for each record) or repeatable fields. In this manual the most flexible option has been taken, without any preliminary restriction: - variable data field lengths, - repetition of data fields is allowed. Depending on the technical characteristics of the systems in use modifications should be made in  such a way that the data fields are compatible. 1.  ESSENTIAL DATA ELEMENTS1.  ADMINISTRATIVE LABELSField 00: Database owner- Data description: a code and/or the name of the database owner (or inputting organization) is necessary for the  identification of the information origin, - Field description- Name: 'Database owner`, - Key field, - Any character may be used, - Obligatory, - Not repeatable. The possibility might be foreseen of adding this field automatically. Field 01: Date of last updating of the record- Data description: the date of the last updating of the record should be entered in this field according to the format  ISO 2014 (YYYYMMDD, where YYYY=year, MM=month, DD=day). - Field description- Name: 'Updating date`, - Key field, - Date field (all numerical - YYYYMMDD), - Obligatory, - Not repeatable. Might be automatically generated. Field 02: Level of completeness code- Data description: a code defining the completeness of the record. The following codes are used: A = all obligatory elements (core data elements) and optional elements are provided, B=all core data are provided, C=Less than the core data are provided. - Field description: - Name = 'Completeness of record`, - Key field, - Only the codes defined in the previous data description are allowed, - Obligatory, - Not repeatable. 2.  DATA ELEMENTS RELATING TO THE RECORDING OF THE RESEARCH PROJECTField 10: Provided for future  usage - character sets used in the recordField 10 is provided to enter the code for the character  set used in the records. Since this should be the same over a whole national research database, it  might be filled out automatically when necessary. Field 11: Record control number- Data description: the record control number identifies the record access; - Field description: - Name: 'Record control number`, - Unique key field (not repeatable and obligatory), - The record control number may include any character. Field 12: Project identifier- Data description: the project identifier identifies the project and should be entered according to the requirements  of the database organization or the information network in which it is participating (national).  This identifier should be preceded by the two-character code of the country which provides the  record (required to avoid duplication of record control numbers by several countries), - Field description: - Name: 'Project identifier`, - Unique key field (not repeatable and obligatory), - The project identifier may include any character. Other reference numbers may be entered in other (local) fields. Field 13: Original working language of the record- Data description: Field 13 is intended for entering the original working language of the record (the language in  which the information in the record is written). The language should be entered in the form of a two-letter language code (ISO/DIS 639 - see point  3.1. of this manual), - Field description: - Name: 'Original working language`, - Key field, - Two-letter code, - Obligatory, - Not repeatable. Field 14: Other languages of the record- Data description: Field 14 is used to record the supplementary working languages of the record (the languages in  which a translated title and abstract of the project are available). Translation of the title and  abstract in at least one additional Community language which is commonly used in the discipline of  the recorded research project, is strongly recommended. The languages in which the information is available should be entered in the form of a two-letter  language code (ISO/DIS 639 - see point 3.1. of this Cerif-manual), - Field description- Name: 'Additional working language`, - Key field, - Two-letter code, - Obligatory, - Repeatable - In databases where repetition of fields is not possible, the additional languages  used should be entered in such a way that the codes for the different languages in use are  separated by a semi-colon. 3.  DATA ELEMENTS RELATING TO THE RESEARCH PROJECT CONTENTSThis part of the core data set contains  fields for entering: - title and abstract in more than one Community language, - names of project director and principal researcher(s), - starting and expected ending date of the project. Two general remarks concerning the data elements related to title and abstract: 1.  Mention of the languages used: since the data elements containing information on the activities related to the research project in  principle may be given in any of the nine official languages of the European Community, all these  data elements are coupled with a subfield in which the two-letter code of the language used should  be entered. 2.  Searching on title and abstract: for database systems which allow 'full text searching`, it is recommended that title and abstract  be full-text-searchable fields. Field 21: Project title in original language- Data description: the official title of the project (in the original language as indicated in field 13) should be  entered. The title may include any character. Special instruction: the text of the title should be typed without breaking words at the end of a  line, - Field description: Subfield 21.1.: - Name: 'Original language`, - Subfield 21.1. = Field 13, - Two-letter code, - Obligatory; Subfield 21.2: - Name: 'Original project title`, - Obligatory. Field 22: Project title - other language(s)- Data description: Field 22 is provided for entry of the translated title(s) of the project, together with the  two-letter code of the language used. The title may include any character. Special instructions: the text of a title should be typed without breaking words at the end of a  line. At least one translated title is recommended. Field 22 (as the whole consisting of subfield 22.1.  and subfield 22.2.) is repeatable, i.e. translation in more than one of the other Community  languages may be entered; - Field description: Subfield 22.1. - Name: 'Language of translated title,`- Two-character code (ISO/DIS 639), - Obligatory for each translated title; Subfield 22.2. Translated title of the project should be entered. The title may include any character. - Name: 'Translated title,`- Obligatory (at least one additional title). Field 23: Project abstract in original language- Data description: The abstract of the project in the original language should be entered in Field 23. The abstract may include any character. Special instructions: the text of the abstract should be typed without breaking words at the end of  a line. - Field description: Subfield 23.1.: - Name: 'Original language`, - Subfield 23.1. = field 13, - Two-letter code, - Obligatory; Subfield 23.2: - Name: 'Original abstract`, - Obligatory. Field 24: Project abstract in other language(s)- Data description: translated abstract of the project (in one or more Community languages other than the original  language) should be entered. The abstract(s) may include any character. At least one translated  abstract is recommended. Special instructions: the text of the abstract should be typed without breaking words at the end of  a line. Field 24 (as the whole consisting of subfield 24.1. and subfield 24.2.) is repeatable, i.e.  translation in more than one of the other Community languages may be entered; - Field description: Subfield 24.1. - Name: 'Language of translated abstract`, - Two-character code (ISO/DIS 639), - Obligatory, Subfield 24.2. - Name: 'Translated abstract`, - Obligatory (at least one additional abstract), - Repeatable (subfield 24.1. together with subfield 24.2.). Field 31: Project director- Data description: the name should be entered of the person who is the project leader (the person asking for and  responsible for the research contract). If details on the qualifications etc. of persons are to be provided in the files, one should create  additional fields near to the common data fields to enter them. The name should be entered in its full form when known. The name should be entered family name  (surname) first, followed by personal names (forenames), for example: Browne, John Henry. The  family name should be followed by a comma and each forename should be preceeded by a space. If family name and initials only are known, the initials should be entered followed by a full stop  in place of a full forename. Initials are not separated from each other by a space, but a space  must occur between any initial and a family name or part of a family name (e.g. a prefix). Titles which are part of the name (Sir, Lord, etc.) should be entered in parentheses following the  forenames or the initials. Titles or additions to names which are often used in addresses (e.g. Mr, Mrs, Prof., Dr) may be  entered in the same way. Titles representing qualifications such as degrees or membership of learned societies, or military  honours (e.g. MA, PhD, FLA), should not be entered. Remark: Certain names may cause problems because it is not always clear which part of the name is the  family name and which the forenames. This category includes double-barrelled names and names  containing prefixes such as de, del, de la, van, von, etc. N° international standard governing the  entry of names in computerized information systems exists. In such cases the national standards may  be used. - Field description- Name: 'Project director`, - Key field, - Obligatory, - Not repeatable. Field 32: Principal researcher(s)- Data description: the name(s) of other researcher(s) involved in the research projects. If several names, the name of  the project leader should be entered first. This name might be the same as the name in field 31 (project director). If details on the qualifications etc. of persons are to be provided in the files, one should create  additional fields near to the common data fields to enter them. The name should be entered in its full form when known. The name should be entered family name  (surname) first, followed by personal names (forenames), for example: Browne, John Henry. The  family name should be followed by a comma and each forename should be preceeded by a space. If family name and initials only are known, the initials should be entered followed by a full stop  in place of a full forename. Initials are not separated from each other by a space, but a space  must occur between any initial and a family name or part of a family name (e.g. a prefix). Titles which are part of the name (Sir, Lord, etc.) should be entered in parentheses following the  forenames or the initials. Titles or additions to names which are often used in addresses (e.g. Mr, Mrs, Prof., Dr) may be  entered in the same way. Titles representing qualifications such as degrees or membership of learned societies, or military  honours (e.g. MA, PhD, FLA), should not be entered. Certain names may cause problems because it is not always clear which part of the name is the  family name and which the forenames. This category includes double-barrelled names and names  containing prefixes such as de, del, de la, van, von, etc. N° international standard governing the entry of names in computerized information systems exists.  In such cases the national standards may be used; - Field description: - Name: 'Principal researchers`, - Key field, - Recommended, - Repeatable - in databases where repeating of fields is not possible, eventually repeating should  be entered in such a way that the different names are separated by a semi-colon. Field 40: Starting date of the project- Data description: Field 40 is used to record the starting date of the project. The date should be entered in  accordance with ISO 2014. The day, month and year should be entered in the form YYYYMMDD. The month may be entered as 00 if it is not known precisely. The day may always be entered as 00; - Field description: - Name: 'Starting date`, - Key field, - Date (all numerical - YYYYMMDD), - Obligatory, - Not repeatable. Field 41: Expected ending date of the project- Data description: Field 41 is used to record the expected ending date (completion date) of the project. The date  should be entered in accordance with ISO 2014. The day, month and year should be entered in the  form YYYYMMDD. The month may be entered as 00 if it is not known precisely. The day may always be entered as 00. In the case of 'free research projects` (carried out on the initiative of the research group and  with own funds) no expected ending date might be known. In this case one should enter the 'expected  ending date` as: 99990000; - Field description: - Name: 'Expected ending date`, - Key field, - Date field (all numerical - YYYYMMDD), - Obligatory, - Not repeatable. 4.  RELATING TO THE RECORDING OF THE CONTACT ADDRESSField 50 and Field 51 are used to enter the  name of the institution where the research is conducted, the address, the country code and the  acronym or other abbreviated form or institution name. These fields are obligatory. Field 50: Name of the research unit- Data description: Field 50 is provided for entering the name of the institution (or performing organization), i.e.  the research group carrying out the project. Where several levels of the organization exist, the name of the lowest-level unit within the  organization that is concerned with the research should be mentioned in any case. The name of the  units should be entered from the largest to the smallest. For large and complex organizations,  intermediate levels, the inclusion of which does not add significant information to the entry, may  be omitted, provided always that the most specific unit is entered and that the entry provides an  unambiguous identification of the organization. It is obligatory to enter the full name of the institution in subfield 50.1., even if an  abbreviated form of the name is entered in subfield 50.2. The name of the institution should always be entered in its official or working language. Perhaps an additional field could be foreseen for entering the name in the second working  language. The field with the name of the institution is provided to enter the names of the several levels of  the institution concerned, in several subfields: Field 50.1.: name of the institution (parent organization), Field 50.2.: name of the parent organization: acronym, Field 50.3.: name of the department (intermediate levels), Field 50.4.: name of the research unit (most specific): Field 50.5.: name of the research unit (most specific): acronym; - Field description: Subfield 50.1. - Name: 'name of the parent organization`, - Any character is allowed, - Key field, - Not repeatable, - Obligatory if applicable; Subfield 50.2. - Name: 'name of the parent organization: acronym`, - Any character is allowed, - Key field, - Optional; Subfield 50.3. - Name: 'Research unit: intermediate levels`, - Any character is allowed, - Key field, - Not repeatable (the names of the several intermediate levels of the research institute should be  entered from the largest to the most specific level higher than the research unit, possibly  separated by a semi-colon); Subfield 50.4. - Name: 'Research unit (most specific)`, - Any character is allowed, - Key field, - Not repeatable, - Obligatory; Subfield 50.5.- Name: 'Research unit (most specific): acronym`, - Any character is allowed, - Key field, - Not repeatable. Field 51: Address of the institution- Data description: the address or location of the institution should be entered in Field 51 in the complete form  required for the user to make contact with the research group. However, an incomplete address may  be entered when no fuller information is available. Other useful details such as telephone, facsimile and telex number may be entered in Field 60. To fulfil the several conventions in the different countries each national database should contain  the addresses following the national PTT conventions. Since it is the aim to provide the database users with a contact address the addresses may be  entered in such a way that all the required information is available. The input format may be  organized following the local needs (e.g. split into several fields as street, number, postcode,  place). Only the output is important: the address should be presented to the user in such a way  that he gets the right and unambiguous information to make contact with the research group. (It is  not the objective to recommend the use of an address format which is suitable for mailing lists.); - Field description: Subfield 51.1.: AddressThe address may be entered according to the requirements of the country  involved. The address must be entered following the national PTT convention, and must contain all elements  which are necessary (street and number in the street, postcode, place - town). - Name: 'address`, - Any character is allowed, - Non-key field, - Not repeatable, - Obligatory; Subfield 51.2.: Place (town)There is a user need for a searching possibility on the place (town). Therefore, perhaps in an additional field, the indication of place should be entered in the natural  language of the place, as a key field. - Name: 'place`, - Key field, - Obligatory, - Not repeatable; Subfield 51.3.: Country code- Name: 'country code`, - Key field, - Two-letter code (ISO 3166 - see point 3.2. of this manual), - Obligatory, - Not repeatable. Additional fields can be created according to national needs (e.g. providing fields for entering  the region, etc.). Field 60: telephone, facsimile and telex- Data descriptionan option can be taken for entering the  telephone and facsimile number as used within the country; - Field description: Subfield 60.1.: Telephone numberA telephone number must be entered as such: the country number  peceded by a plus-sign, followed by the local zone number, followed by the telephone number, e.g.  +32 2 512 91 10 as international telephone number, which means (02) 512 91 10 within the country. If the mention of an extension is necessary, it should follow the number, preceded by an indication  that it is an extension, e.g. +32 2 512 91 10 ext. 324. - Name: 'telephone number,`- Non-key field, - Any character is allowed, - Recommended; Subfield 60.2.: Facsimile numbersimilar to subfield 60.1- Name: 'facsimile number`, - Non-key field, - Any character is allowed, - Optional; Subfield 60.3.: Telex number- Name: 'Telex number`, - Non-key field, - Any character is allowed, - Optional; Subfield 60.4.: Provided for electronic mail address (future usage)In view of the international  harmonization of electronic mail addresses, this subfield is provided for entering such addresses. Non-standardized electronic mail addresses should be included in (local) fields additional to the  common dataset. - Name: 'Electronic mail address`, - Non-key field, - Any character is allowed, - Optional. 5.  DATA ELEMENTS RELATING TO RESEARCH IDENTIFICATION(INDEXING AND RETRIEVING)Three levels of  searching are foreseen by Fields 70 to 72: - Field 70: Free key words, - Field 71: Controlled terms (Common Research Thesaurus), - Field 72: Disciplines (codes of the Common Research Classification Scheme). Field 70: Free key words- Data description: free key words can be entered to indicate the work of the research projects. The key words may be  determined by the researchers, by the inputting organization or by automatic extraction from title  and abstract. To allow the searchers to use free key words as a searching instrument, it is necessary for them to  know in which language the key words are recorded. To cover this need the language code (see  ISO/DIS 639 - two-letter code) should be entered in another subfield; - Field description (subfields): subfield 70.1.: Free key word- Name: 'key word`, - Key field, - Optional; subfield 70.2.: Language of key word- Name 'language of key word`, - Key field, - Two-letter code, - Obligatory if subfield 70.1. is filled in. Field 70 (as the whole of subfield 70.1. and 70.2.): - Optional- Repeatable. Field 71: controlled terms (only terms of the Research Thesaurus are allowed)- Data description: the use of the thesaurus is recommended to overcome the problems generated by the use of all the  Community languages, in particular for the user of the information systems. In this field only terms of the Research Thesaurus may be added. A list of this thesaurus is  annexed to this manual. If another thesaurus is used, one should enter the controlled terms of the  locally used thesaurus in another field (see note below). The Research Thesaurus may be used either in text form or in code form, since the terms may be  converted automatically into the associated codes. To avoid difficulties for the user, which may arise from the use of accents, controlled terms  should be entered upper case. One requirement must be fulfilled when the thesaurus is used in text form without the associated  codes, that all the terms are mentioned in the same language. In this case the language used should  be mentioned. However it is recommended to use the codes associated with the terms (subfield 71.1.). To control  the input, one could provide automatically for filling up subfield 71.2. to display the term which  is associated with the code mentioned in subfield 71.1.; - Field description: Field 71 consists of several subfields: One should use Subfield 71.1. (encoded terms) and/or  subfield 71.2. together with subfield 71.3. Field 71 (the whole of the subfields 71.1., 71.2., 71.3.) is repeatable. Subfield 71.1.: Encoded controlled term- Name: 'encoded controlled term`, - Key field, - Repeatable, - Optional (but recommended); Subfield 71.2.: Controlled term- Name: 'controlled term`, - Key field, - Optional; Subfield 71.3.: Language of controlled term- Name: 'language of controlled term`, - Key field, - Necessary if subfield 71.2. (term) is used where subfield 71.1. is not, - The codes must be entered following the ISO/DIS 639 standard (two-letter code). Important note: For the use of terms of another thesaurus one should provide another (local) field: terms from  different thesauri may never be mixed! Field 71 is reserved for controlled terms from the common  European Research Thesaurus (Annex II). To enter the terms from another nationally used thesaurus creation of a Field 73 is recommended. Field 72: Common subject classification codes - Common European Research Classification Scheme-  Data description: Field 72 is provided to enter a classification code applied to the research project in accordance  with the common classification scheme (Annex I). For any other classification scheme individual services may wish to use, including 'in-house`  unpublished schedules and local adaptations of published schemes, additional (local) fields should  be added to the common set of fields (see note below); - Field description: - Name: 'classification code`, - Key field, - Repeatable, - Obligatory. For local use one might add an extra field with a verbal description of the classification code as  a tool for controlling inputs in Field 72. Important note: For other classification schemes other fields must be used: codes from different schemes may never  be mixed! Field 72 is reserved for codes from the common European Research Classification scheme  (Annex I). To enter the codes from another nationally used scheme creation of Field 74 is recommended. 6.  RELATING TO THE 'CRITICAL MASS` OF THE RESEARCH PROJECTThe 'critical mass` of a research  project is determined by the financial and personnel background. (a)  Data elements relating to the financial supportFields 80 and 81 are used for details relating  to the financial support of the research project. - Field 80: Name and code of the funding organization, - Field 81: Amount of the financial support and budget breakdown. If a project is funded by different sources Field 80 and Field 81 might be repeated. Field 80: Financing source- Data description: the name of the organization supporting the research project should be entered in the first  subfield of Field 80. A structured list of codes indicating financial sources may be made up to allow encoding of and  searching on research financing sources. A code indicating the financial support should be entered in subfield 80.2.; - Field description: Subfield 80.1.: Name of the funding organization- Name: 'Name of the funding organization`, - Any character is allowed, - Key field, - Obligatory, - Repeatable (together with field 80.2. and Field 81); Subfield 80.2.: Code for the funding organization (;)The code of the organization mentioned in  Subfield 80.1. must be entered. This code is required for several purposes: - to group research funded under the same heading for e.g. statistical analysis. As such an  automatic search on government funded research or on privately financed research should be  possible, - the codes can also be used to make the link with the address of the organization, which might be  added in additional files to the research database. - Name: 'code for funding organization`, - Any character is allowed, - Key field, - Recommended, - Repeatable (together with Field 80.1. and Field 81). Field 81: Amount- Data description: the total amount of the financial support for the entire project should be entered in the national  currency in Subfield 1. The total annual amount of the financial support should be entered in the national currency in  Subfield 2. The budget breakdown (the composition of the budget) should be entered in Subfields 81.3. to 81.5.  The annual amount of the personnel costs and the working costs should be entered. The equipment  budget should be entered as foreseen for the entire project (since this budget is mostly used with  the starting of the project). The national currency should be entered in subfield 81.2. (ISO 4217). This code could be  automatically linked with the country code (Field 51.5.). It is possible to express the budget in ecus (in this case ECU must be entered in Field 81.2.)-  Field description: Subfield 81.1.: Total amount for the entire project- Name: 'Total amount`, - Essential data element, - Key, - Decimal, - Repeatable (together with Field 80 and the other Subfields 81.x.)Subfield 81.2.: Currency-  Name: 'Currency`, - Essential data element, (;) Each of the Member States might use their own acronyms or codes for the funding organizations,  in a consistent way. - Key, - The currency used may be the national currency, or ecu, and should be entered following the  standard ISO-4217-1978, which is described in point 3.3. of this manual. (N° repetition in several  currencies is allowed.); if available, the following information should be added (;): Subfield 81.3.: 'Average amount per year`, Subfield 81.4.: 'Personnel cost` (annual), Subfield 81.5.: 'Working cost` (annual), Subfield 81.6.: 'Equipment cost` (total equipment budget foreseen for the entire project); Subfields 81.3. to 81.6. are: - Optional (but recommended if available), - Key fields, - Decimal, - Repeatable (together with Field 80 and the other Subfields 81.x). (b)  Relating to the personnelField 82: Number of researchers- Data description: Field 82 is used to enter the number of full-time-equivalent researchers working on the research  project. Rule: the number of full-time equivalent researchers should be entered as: 'full time equivalent researchers`/'period in months.`To avoid confusion some examples are given  below: - 1 person for three months is written as: '1` in subfield 82.1., '3` in subfield 82.2.; - 3 persons for one month is written as: '3` in subfield 82.1., '1` in subfield 82.2.; - 12 persons for two years is written as: '12` in subfield 82.1., '24` in subfield 82.2. The average of FTE per year can easily be calculated with the formula: average FTE/year = Subfield 82.1. × Subfield 82.2./12- Field description: -Name 'full time equivalents`, -Numerical field, -Two subfields: Subfield 82.1.: Number of full time researchers, Subfield 82.2.: Period in number of months, -Obligatory, -Not repeatable. A third subfield might be given automatically: Subfield 82.3.: 'Average of FTE per year` Subfield 82.3. = Subfield 82.1. × Subfield 82.2./12(;)  For the definitions, see Frascati Manual 1980 - 'The measurement of scientific and technical  activities, a proposed standard practice for surveys of research and experimental development.`  Edited by the OECD, 2 rue Pascal, 75775 Paris Cedex 16, France, in 1981. II.  OPTIONAL ELEMENTSOptional elements are foreseen to record some information which is not  indicated in the first part of the dataset, but which might be essential information related to the  project considered. Fields 91 to 95 are foreseen to enter possible additional essential information. Field 99 is provided for indicating the kind of information which is added for the recorded project  in one of the fields from 91 to 95, if any. This is to allow a display of the presence of  additional information for the user. Fields 91 to 95: Additional informationThis part contains five fields which may contain any  character. The information covered by Fields 91 to 95 should contain any information which is seen  as really essential for the project. Note: the fields of Part II may only be entered if there is special information which is considered to be  essential for the user to understand the research project. This should be information on: - the incorporation of the project in a research programme, - cooperation, - interim results, - special equipment, - others. Field 91: Related to research programmesField 91 is provided for entering if the project is  incorporated in a research programme, or if there are close links with other projects. If a project is part of a research programme (e.g. one of the European Community programmes) the  name of the programme should be mentioned in Field 91. Subfield 91.1.: 'research programme: name`, Subfield 91.2.: 'research programme: acronym`. Field 92: Related to cooperationIn Field 92 one should mention crucial cooperation with other  researchers or institutes (the address of the other group and the kind of cooperation can be  mentioned)Field 92 is provided to enter essential cooperation within the research activities of  the project. It should be noted that it is not the purpose to list all the cooperative relations of the  researchers or the research group involved: only the cooperation in the framework of the project  considered in this record should be entered. Field 93: Interim resultsIn Field 93 one should enter significant results obtained so far. Such  results should be mentioned very briefly. For example: - The number of publications arising from the project so far, - Any patents obtained, - Any prototypes that have been constructed. It must be clear that it is not the purpose to get lists of results other than those obtained  within the project considered in this record. The aim is to provide this additional information to  the user, to let him know what is going on. If the publications or other results are briefly  mentioned here, the interested user can contact the project leader directly to get more details.Field 94: Special equipmentSpecial equipment, mention of which is essential for the information  user to understand the scope of the project should be entered very briefly. For example: 'an NMR-spectrometer equipped with gradient coils is used`It is not the aim to  include in this field a list of all special equipment available in the research centres, but merely  to give additional information which might be necessary for understanding the project activities  described in title and abstract. An additional database giving an inventory of research equipment available in Europe might be  constructed at a later date. Field 95: Other relevant informationOther information which might be considered to be necessary to  be available to the user should be entered in Field 95. - Fields 91 to 95 are optional fields, - Any character is allowed. Field 99: Indication of the kind of additional informationTo create a searching instrument for  this additional information, a field is added containing information on the contents of Fields 91  to 95. If additional items are entered, it is required to indicate which kind of information is added. - Data description: The kind of information can be indicated by an associated code, as given below. Only numbers are  allowed. Codelist for the indication of the nature of extra information included in the record: - Programme1, - Cooperation2, - Results3, - Equipment4, - Other5; - Field Description: - Name: 'type of additional information`, - Only numbers are allowed (see previous codelist), - Key field, - Obligatory if any of fields 91 to 95 exist, - Repeatable (for cases with comments of several kinds). In databases where repetition of fields  isnot possible, items should be entered in such a way that separate values are separated by a  semi-colon. E.g. in a case where additional information is added in Field 91 (programme information) and in  Field 95 (other additional essential information) one should enter in Field 99: 1:5. DATA ELEMENT INDEXCodes usedR: RepeatableK: Key fieldU: Unique-key field (the entering of two identical values is not allowed)S: If possible, full text search would be recommended(S): One might foresee a full text searching possibility, but this is not requiredP: Reserved for future use or for well defined additional local fieldsI.  Essential data elements1.   Administrative labelsField 00: Database ownerKField 01: Date of last updating of the  recordKField 02: Level of completeness codeK2.  Data elements relating to the recording of  the research projectField 10: Provided for future usage - character sets used in the  recordKField 11: Record control numberUField 12: Project identifierUField 13: Original  working language of the recordKField 14: Other languages of the recordKR3.  Data elements  relating to the research project contentsField 21: Project title in original language- Subfield  21.1.: Original language (= Field 13)K- Subfield 21.2.: Original project titleSField 22:  Project title - other language(s)R- Subfield 22.1.: Language of translated titleK- Subfield  22.2.: Translated titleSField 23: Project abstract in original language- Subfield 23.1.:  Original language (= Field 13)K- Subfield 23.2.: Original abstractSField 24: Project abstract  in other language(s)R- Subfield 24.1.: Language of translated abstractK- Subfield 24.2.:  Translated abstractSField 31: Project directorKField 32: Principal researcher(s)KRField  40: Starting date of the projectKField 41: Expected ending date of the projectK4.  Relating  to the recording of the contact addressField 50: Name of the research unit- Subfield 50.1.:  Name of the parent organizationS- Subfield 50.2.: Parent organization: acronymS- Subfield  50.3.: Research unit: intermediate levelsS- Subfield 50.4.: Research unit (most specific)S-  Subfield 50.5.: Research unit (most specific): acronymSField 51: Address of the institution-  Subfield 51.1.: Address- Subfield 51.2.: Place (town)K- Subfield 51.3.: Country codeKField  60: Telephone, facsimile and telex- Subfield 60.1.: Telephone number- Subfield 60.2.:  Facsimile number- Subfield 60.3.: Telex number- Subfield 60.4.: Provided for electronic mail  address (future usage)P5.  Data elements relating to research identification(indexing and  retrieving)Field 70: Free key wordR- Subfield 70.1.: Free key wordK- Subfield 70.2.:  Language of key wordKField 71: Controlled terms (Research Thesaurus)R- Subfield 71.1.:  Encoded controlled termK- Subfield 71.2.: Controlled termK- Subfield 71.3.: Language of  controlled termKField 72: Classification code (Research Classification Scheme)KRField 73:  Provided for other thesauri than the Research ThesaurusPField 74: Provided for other (locally  used) classification schemesP6.  Relating to the 'critical mass` of the research project(a)   Data elements relating to the financial supportRField 80: Financing source- Subfield 80.1.:  Name of the funding organizationK- Subfield 80.2.: Code for the funding organizationKField  81: Amount- Subfield 81.1.: Total amount for the entire projectK- Subfield 81.2.:  CurrencyK- Subfield 81.3.: Average amount per yearK- Subfield 81.4.: Personnel cost  (annual)K- Subfield 81.5.: Working cost (annual)K- Subfield 81.6.: Equipment costK(b)   Relating to the personnelField 82: Number of researchers (full time equivalents)- Subfield  82.1.: Number of full time scientistsK- Subfield 82.2.: Period in number monthsK- Subfield  82.3.: 'Average of FTE per year`KII.  Optional elementsField 91 to 95: Additional  information- Field 91: Related to research programmes(S)- Field 92: Related to  cooperations(S)- Field 93: Interim results(S)- Field 94: Special equipment(S)- Field 95:  Other relevant information(S)Field 99: Type of additional informationKR6. References- 'CCF: The common communication format`; Peter Simmons and Alan Hopkinson, General  Information Programme and Unisist, Unesco, Paris 1984. - 'Reference manual for machine-readable descriptions of research projects and institutions`;  Harold Dierickx and Alan Hopkinson, General Information Programme and Unisist, Unesco, 1982.  ANNEX II SCIENCES CLASSIFICATION (¹) Table of contentsPageHUMANITIES  Philosophy . 24  Theology . 24  History and arts . 24  Philology . 25SOCIAL SCIENCES  Juridical sciences . 26  Political sciences . 26  Economics . 27  Sociology . 27  Psychology . 27  Pedagogy and didactics . 27PHYSICAL SCIENCES  Mathematics . 28  Physics . 28  Chemistry . 29  Physical chemistry . 29  Biochemistry, metabolism . 29  Earth sciences, geophysics . 29  Paleontology . 30  Space sciences . 30BIOMEDICAL SCIENCES  General biomedical sciences . 30  Biophysics . 30  Genetics . 30  Microbiology . 30  Ecology . 31  Botany . 31  Zoology . 31  Agronomics . 31  Medicine, man and vertebrates . 31  Diagnosis . 32TECHNOLOGICAL SCIENCES  Materials technology . 33  Electronic and electrical technology . 33  Construction technology . 34  Transport technology . 34  Chemical technology . 34(¹) On the Belgian national level the SPPS, the FNRS/NFWO and the IWETO of the Flemish  Community make joint useof it. HUMANITIES H 000H 100 Documentation, information, library science,  archivisticsH105BibliographyH110Paleography, bibliology, epigraphy, papyrologyPhilosophy H  001H 120 Systematic philosophy, ethics, aesthetics, metaphysics, epistemology,  ideologyH125Philosophical anthropologyH130History of  philosophyH135PhenomenologyH140Philosophical logicxxxMathematical logic: see P  110xxxArtificial intelligence: see P 176H150Philosophy of special sciencesxxxEpistemology:  see H 120xxxPhilosophy of social sciences: see S 100xxxPhilosophy of technological sciences:  see T 100xxxPhilosophy of biomedical sciences: see B 100H155Moral scienceTheology H 002H 160  General, systematic and practical Christian theologyxxxPhilosophy of theology: see H  150xxxHistory of the Christian church: see H 180H165Canon lawH170BibleH180History of the  Christian churchH190Non-Christian religionsHistory and Arts H 003History H 005H 200 Theory of  historyxxxPhilosophy of history: see H 150H210Ancient historyH220Medieval  historyH230Modern history (up to circa 1800)H240Contemporary history (circa 1800 to  1914)H250Contemporary history (since 1914)H260History of sciencexxxHistory of thought: see  H 130xxxHistory of technology: see T 100xxxHistory of social sciences: see S 100xxxHistory of  biomedical sciences: see B 100xxxHistory of language: see H 355xxxHistory of agriculture: see B  435H270Social and economic historyxxxFor a classification into periods: see from H 210 to H  250H271Political historyH280Local and regional history, historical geography since the Middle  AgesH290Colonial historyxxxFor a classification into periods: see from H 230 to H  250H300History of lawxxxHistory of religions: see H 180 and H 190H310Art  historyH311PaintingH312Sculpture and architectureH313Art criticismxxxLiterary criticism:  see H 390H314Preservation and restoration of art worksH315AestheticsxxxPhilosophical  aesthetics: see H 120H320MusicologyH330Dramatic  artH340ArchaeologyH341PrehistoryxxxChronology, dating techniques: see T  510H345EgyptologyH346Numismatics and sigillographyH347Genealogy and heraldryPhilology H  004H350LinguisticsxxxPhilosophy of language: see H 150H351Phonetics,  phonologyH352Grammar, semantics, semiotics, syntaxH353LexicologyH355History of  languageH360Applied linguistics, foreign languages teaching,  sociolinguisticsH361NeurolinguisticsH365TranslationH370OnomasticsH380Comparative  linguisticsH390General and comparative literature, literary criticism, literary  theoryxxxDramatic art: see H 330H400FolkloreH401DialectologyH410Indo-European languages  and literatures of Asia Minor, Indo-IranianH420Greek languageH430Greek literatureH440Latin  languageH450Latin literatureH460French languageH470French literatureH480Italian  language and literatureH490Spanish and Portuguese language and literatureH500Other Romance  languages and literaturesH510Celtic languages and literaturesH520Germanic philologyxxx     00H 530 German language and literatureH540Dutch languagexxxFlemish language: see H 401  and H 540H550Dutch literaturexxxFlemish literature: see H 550H 560 Frisian language and  literatureH570English language and literatureH580Scandinavian languages and  literaturesH590Baltic and Slavonic languages and literaturesH595Russian language and  literatureH600Languages and literatures of Asia Minor, Caucasian languages and literatures,  Basque, SumerianxxxFor Indo-European languages: see H 410H610Hamito-Semitic languages and  literaturesH620Uralian and Altaic languages and literaturesH630Paleo-Siberian languages and  literatures, Korean, JapaneseH640Languages and literatures of South and South-East Asia,  ChineseH650Austronesian and Papuan languages and literaturesH660African languages and  literaturesH670American languages and literatures: Creole languagesxxxFor American English:  see H 570Social Sciences S 000S 100 History and philosophy of the social sciencesS110Juridical  sciencesS111Administrative lawS112Human rightsS114Comparative lawS115Philosophy and  theory of lawxxxHistory of law: see H 300S120Environmental lawS121Juvenile lawS122Media  lawS123Informatics lawS124Patents, copyrights, trademarksS130Civil law: persons, family,  marriage contract, successions, gifts, property, obligations, guaranteesS136Transportation  lawS137Insurance lawS140Public lawS141Fiscal lawS142Judicial lawS143Social  lawS144Industrial and commercial lawS145Notarial lawS146Labour lawS148Constitutional  lawS149Criminal law, criminal proceedingsS150International private and public  lawS151Aerial, maritime and space lawS155European lawxxxCanon law: see H  165S160CriminologyS170Political and administrative sciencesxxxPolitical history: see H  271S175PolemologyxxxPress and communication sciences: see S 265S180Economics, econometrics,  economic theory, economic systems, economic policyS181Financial sciencexxxAccounting: see S  192S 182 Actuarial sciencexxxActuarial mathematics: see P 160S183Cyclical  economicsS184Economic planningS185Commercial and industrial economicsS186International  commerceS187Agricultural economicsS188Economics of developmentS189Organizational  scienceS190Management of enterprisesS191Market studyS192AccountingS195Development  cooperationS196Social economicsxxxEconomic history: see H 270S210SociologyS211Sociology  of scienceS212Sociology of labour, sociology of enterpriseS213Social structuresS214Social  changes, theory of social workS215Social problems and welfare, national insurancexxxSocial  medicine: see S 290xxxSocial pedagogy: see S 285xxxSocial law: see S 143S216Care and help to  handicappedxxxOrthopedagogy: see S 286S 220 Cultural anthropology,  ethnologyxxxSociolinguistics: see H 360S230Social geographyxxxSocial psychology: see S  263xxxPress and communication sciences: see S 265xxxCriminology: see S 160xxxSocial  economics: see S 196xxxSocial history: see H 270S240Town and country planningxxxPhysical  planning: see T 260xxxLandscape design: see T 250S250DemographyS260PsychologyxxxHuman  ethology: see B 381xxxPsychonomics: see B 760xxxArtificial intelligence: see P  176xxxPsycholinguistics: see H 361S261Differential and individual psychologyS262Development  psychologyS263Social psychologyS264Applied and experimental psychologyS265Press and  communication sciencesS266Industrial psychologyxxxPsychopathology: see B 650S270Pedagogy  and didacticsS271Special didacticsS272Teacher educationS273Physical training, motorial  learning, sportxxxSkeleton, muscle system: see B 580xxxBiomechanics, biometrics: see B 110 and  B 115S274Research methodology in scienceS280Adult education, permanent  educationS281Computer-assisted educationxxxForeign languages teaching: see H  360S282Comparative and historical pedagogyS283PsychopedagogyS284Experimental  pedagogyS285Social pedagogyS286OrthopedagogyxxxCare and help to handicapped: see S  216xxxPhysical medicine, revalidation, rehabilitation: see B 710S290Social  medicinexxxSociolinguistics: see H 360xxxSocial history: see H 270xxxSocial psychology: see S  263PHYSICAL SCIENCES P 000xxxHistory and philosophy of sciences and medicine: see H 260 and H  150Mathematics P 001P 110 Mathematical logic, set theory, combinatoriesP120Number theory,  field theory, algebraic geometry, algebra, group theoryP130Functions, differential  equationsP140Series, Fourier analysis, functional analysisP150Geometry, algebraic  topologyxxxTopological groups: see P 120P160Statistics, operations research, programming,  actuarial mathematicsxxxActuarial science: see S 182P170Computer science, numerical analysis,  systems, controlxxxBiomathematics, cybernetics: see B 110 and B 115P175Informatics, systems  theoryP176Artificial intelligencexxxComputer technology: see T 120xxxBioinformatics: see B  110xxxMathematical logic: see P 110xxxMathematical physics: see P 190Physics P  002P180Metrology, physical instrumentationxxxMedical instrumentation: see B  140P190Mathematical and general theoretical physics, classical mechanics, quantum mechanics,  relativity, gravitation, statistical physics, thermodynamicsP200Electromagnetism, optics,  acousticsP210Elementary particle physics, quantum field theoryP211High energy interactions,  cosmic raysP220Nuclear physicsxxxNuclear technology: see T 160P230Atomic and molecular  physicsxxxLaser technology: see T 165P240Gases, fluid dynamics, plasmasxxxLiquid and solid  helium: see P 250P250Condensed matter: structure, thermal and mechanical properties,  crystallography, phase equilibriaP260Condensed matter: electronic structure, electrical,  magnetic and optical properties, supraconductors, magnetic resonance, relaxation,  spectroscopyP265Semiconductory physicsxxxAstrophysics: see P 520xxxGeophysics: see P  500xxxPhysical chemistry: see P 400xxxBiophysics: see B 002xxxMolecular biophysics: see B  120xxxPhysiological biophysics: see B 130xxxClinical physics, tomography, radiology, medical  instrumentation: see B 140xxxRadiobiology and nuclear medicine: see B 145Chemistry P  003P300Analytical chemistryP305Environmental chemistryP351Structure  chemistryP352Surface and boundary layery chemistryP360Inorganic  chemistryP370Macromolecular chemistryP380Nuclear chemistryP390Organic  chemistryP395Organometallic chemistryP400Physical chemistryxxxCrystallography: see P  250P401ElectrochemistryP402PhotochemistryxxxLaser technology: see T 165P410Theoretical  chemistry, quantum chemistryxxxCosmic chemistry: see P 520xxxAgrochemistry: see B  434xxxClinical chemistry: see B 190Biochemistry, Metabolism P 004P310Proteins,  enzymologyP320Nucleic acids, protein synthesisP330BioenergeticsP340Lipids, steroids,  membranesxxxBiopolymers: see T 390Geology, physical geography P 005P420Petrology, mineralogy,  geochemistryxxxCrystallography: see P 250P430Mineral deposits, economic  geologyP440TectonicsP450StratigraphyP460SedimentologyP470Hydrogeology, geographical and  geological engineeringP500Geophysics, physical oceanography, meteorologyP510Physical  geography, geomorphology, pedology, cartography, climatologyxxxHistorical geography: see H  280P515GeodesyPalaeontology P 006P 520    xxxPalaeobotany, palynology: see B  300xxxPalaeozoology: see B 330xxxChronology, dating technics: see T 510Astronomy P 007P 520  Astonomy, space research, cosmic chemistryxxxCosmic rays: see P 211xxxRemote sensing: see T  181BIOMEDICAL SCIENCES B 000General biomedical sciences B 001B 100 History and philosophy of  biomedical sciences, theoretical biology, general aspects of evolutionB110Bioinformatics,  medical informatics, biomathematics biometricsB115Biomechanics, cyberneticsBiophysics B 002B  120 Molecular biophysicsB130Physiological biophysicsB140Clinical physics, radiology,  tomography, medical instrumentationB145Nuclear medicine, radiobiologyxxxRadiopharmaceutical  technology: see T 411xxxGenetic effects: see B 220xxxBiochemistry, metabolism: see P  004xxxProteins, enzymology: see P 310xxxNucleic acids, protein synthesis: see P  320xxxBioenergetics: see P 330xxxLipids, steroids, membranes: see P 340xxxBiopolymers: see T  390B190Clinical chemistryxxxHormones: see B 370 and B 480xxxEndocrinology: see B  480xxxSerology: see B 500B191Plant biochemistryxxxBiotechnology: see T 490xxxFixation of  nitrogen: see B 433B200Cytology, oncology, cancerologyxxxPathological anatomy: see B  520B210Histology, cytochemistry, histochemistry, tissue cultureB220Genetics,  cytogeneticsxxxClinical genetics: see B 790xxxAnimal breeding: see B 400xxxPlant breeding:  see B 390B225Plant geneticsB230Microbiology, bacteriology, virology, mycologyxxxFixation of  nitrogen: see B 433xxxPlant parasitology: see B 250xxxParasitology (human and animal): see B  240B235ProtozoologyB240Parasitology (human and animal)B250Entomology, plant  parasitologyxxxPhytopathology: see B 390B260Hydrobiology, marine biology, aquatic ecology,  limnologyEcology B 003B 270 Plant ecologyxxxAquatic ecology: see B 260xxxPaleoecology: see B  300 und B 330B280Animal ecologyBotany B 004B 290 Systematic botany, taxonomy, morphology,  phytogeography, chemotaxonomy. Physiology of nonvascular plantsxxxPhysiology of vascular plants:  see B 310B300Palaeobotany, phylogeny, palynologyB310Physiology of vascular plantsZoology B  005B 320 Systematic zoology, taxonomy, zoogeopraphyB330Palaeozoology, phylogenyB340Animal  anatomy, animal morphologyxxxGrowth (animal): see B 350B350Development biology, growth  (animal), ontogeny, embryologyB360Animal physiologyxxxBiochemistry: see P  004xxxDevelopmental physiology: see B 350B361Physiology of invertebratesxxxBiochemistry: see  P 004B370Endocrinology of invertebratesxxxEndocrinology of vertebrates: see B 480B380Animal  ethology and psychologyB381Human ethologyAgronomics B 006B 390 Phytotechny, horticulture, crop  protection, phytopathologyxxxPlant genetics: see B 225B400Zootechny, animal husbandry,  breedingxxxVeterinarian medicine: see B 750B401AvicultureB402Aquaculture,  piscicultureB410Soil science, agricultural hydrologyxxxPedology: see P  510B420NutritionxxxFood technology: see T 430B430Sylviculture, forestry, forestry  technologyB431Tropical agricultureB432Ornamental plantsB433Fixation of  nitrogenB434AgrochemistryB435History of agriculturexxxAgricultural engineering: see T  420xxxAgricultural economics: see S 187Medicine (human and vertebrates) B 007xxxGeneral  biomedical sciences: see from B 100 to B 240B 440 Human anatomy and morphologyxxxAnimal anatomy  and morphology: see B 340B450Development biology, teratology, ontogeny, embryology  (human)xxxDevelopment biology, teratology, ontogeny, embryology (animal): see B 350xxxDental  development: see B 730B460Physical anthropologyxxxHuman genetics: see B  220B470PhysiologyxxxBiochemistry: see P 004xxxNeurophysiology: see B 640xxxNutrition: see  B 420B480Endocrinology, secreting systems, diabetologyB490Haematology, extracellular  fluidsB500Immunology, serology, transplantationB510InfectionsxxxMicrobiology: see B  230B520General pathology, pathological anatomyxxxCancerology, oncology: see B 200xxxNuclear  medicine: see B 145B530Cardiovascular systemB540Respiratory  systemB550Gastro-enterologyB560Urology, nephrologyB570Obstetrics, gynaecology, andrology,  reproduction, sexualityB580Skeleton, muscle system, rheumatology locomotionxxxOrthopaedics:  see B 600B590Anaesthesiology, intensive careB600Surgery, orthopaedics,  traumatologyxxxNeurosurgery: see B 640B610Otorhinolaryngology, audiology, auditive system and  speechB620OphtalmologyB630Dermatology, venereologyB640Neurology, neuropsychology,  neurophysiologyxxxNeurolinguistics: see H 361B650Psychiatry, clinical psychology,  psychosomaticsB660PediatricsxxxDevelopmental biology, teratology: see B 450xxxChild  psychiatry: see B 650B670GerontologyB680Public health, epidemiologyxxxSocial medicine: see  S 290B685Hospital science and managementB690Occupational health, industrial  medicineB700Environmental healthB710Physical medicine, kinesitherapy, revalidation,  rehabilitationxxxPhysical training, motorial learning, sport: see S 273xxxOrthopedagogy: see S  286B720General practice, medical trainingB 725 DiagnosticsxxxRadiology, NMR, tomography: see  B 140xxxClinical genetics: see B 790xxxNuclear medicine: see B 145xxxRadiopharmaceutical  technology: see T 411B 726 Clinical biologyxxxClinical chemistry: see B 190xxxSerology: see B  500xxxPathological anatomy: see B 520B 730 Odontology, stomatologyB740Pharmacological  sciences, pharmacognosy, pharmacy, toxicologyxxxClinical biology: see B  726xxxRadiopharmaceutical technology: see T 411B750Veterinary medicine: surgery, physiology,  pathology, clinical studiesB760PsychonomicsB770Legal medicineB780Tropical  medicineB790Clinical geneticsTECHNOLOGICAL SCIENCES T 000T 100 History and philosophy of  technologyT110Instrumentation technologyxxxPhysical instrumentation: see P 180T111Imaging,  image processingxxxRadiology, NMR, tomography: see B 140T115Medical  technologyxxxBiomechanics: see B 115xxxMedical instrumentation: see B 140T120Systems  engineering, computer technologyT121Signal processingxxxImage processing: see T  111xxxSystems theory: see P 175xxxCybernetics: see B 115xxxComputer science: see P  170T125Automation, robotics, control engineeringT130Production technologyT140Energy  researchT150Material technologyT151Optical materialsxxxLaser technology: see T  165T152Composite materialsT153Ceramic materials and powdersxxxAmorphous materials: see P  265 and T 171xxxPolymers: see T 390xxxMetallic materials: see T 450T155Coatings and surface  treatmentT160Nuclear engineering and technologyT165Laser technologyElectronics and  Electrical technology T 001T170ElectronicsT171MicroelectronicsxxxComputer science: see P  170xxxComputer technology: see T 120xxxInformatics: see P 175T180Telecommunication  engineeringT181Remote sensingT190Electrical engineeringxxxRegulation: see T 125T191High  frequency technology, microwavesT200Thermal engineering, applied thermodynamicsT210Mechanical  engineering, hydraulics, vacuum technology, vibration and acoustic engineeringxxxMotors and  propulsion systems: see T 455Construction technology T 002T220Civil engineering, hydraulic  engineering, offshore technology, soil mechanicsT230Building constructionT240Architecture,  interior designT250Landscape designT260Physical planningxxxTown and country planning: see S  240T270Environmental technology, pollution controlxxxEnvironmental chemistry: see P  305xxxEnvironmental health: see B 700Transport technology T 003T280Road transport  technologyT290Railway transport technologyT300Water transport technologyT310Air transport  technologyxxxConstruction technology: see T 002xxxMotors and propulsion systems: see T  455T320Space technologyxxxSpace science: see P 520T330Military science and  technologyT340MiningT350Chemical technology and engineeringT360Biochemical  technologyT370Carbochemistry, petrochemistry, fuels and explosives technologyxxxMotors and  propulsion systems: see T 455T380Natural oils, fats and waxes technologyT390Polymer  technology, biopolymersT400Fine chemicals technology, coloursxxxAgrochemistry: see B  434T410Pharmaceuticals and related technologiesT411Radiopharmaceutical  technologyT420Agricultural engineering, agricultural machines, farmhouse constructionT430Food  and drink technologyT440Non-metallic mineral technologyT450Metal technology, metallurgy,  metal productsT455Motors and propulsion systemsT460Wood, pulp and paper  technologyT470Textiles technologyT490BiotechnologyT500Safety technologyT510Chronology,  dating techniquesT480Technology of other products


				|

		52013PC0387

			Recommendation for a COUNCIL DECISION abrogating Decision 2009/588/EC on the existence of an excessive deficit in Lithuania /* COM/2013/0387 final */

			   	Recommendation for a
COUNCIL DECISION
abrogating Decision 2009/588/EC on the
existence of an excessive deficit in Lithuania
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on the Functioning of the European Union,
and in particular Article 126(12) thereof,
Having regard to the recommendation from
the Commission,
Whereas:
(1)       By Council Decision 2009/588/EC
of 7 July 2009[1],
following a recommendation from the Commission in accordance with Article 104(6)
of the Treaty establishing the European Community (TEC), it was decided that an
excessive deficit existed in Lithuania. The Council noted that the general
government deficit reached 3.2% of GDP in 2008, above the 3% of GDP Treaty
reference value and would according to the Commission services’ 2009 spring
forecast widen to 5.4% of GDP in 2009 and further to 8% of GDP in 2010. The
general government gross debt was 15.6% of GDP in 2008, well below the 60% of
GDP Treaty reference value.
(2)       On 7 July 2009, in
accordance with Article 104(7) TEC and Article 3(4) of Council Regulation
(EC) No 1467/97 of 7 July 1997 on speeding up and clarifying the implementation
of the excessive deficit procedure[2],
the Council, based on a recommendation from the Commission, addressed a
recommendation to Lithuania with a view to bringing the excessive deficit
situation to an end by 2011 at the latest. The recommendation was made public.
(3)       On 9 February 2010, in
accordance with Article 126(7) of the Treaty on the Functioning of the
European Union (TFEU) and Article 3(4) of Council Regulation (EC) No 1467/97 of
7 July 1997 on speeding up and clarifying the implementation of the excessive
deficit procedure, the Council, based on a recommendation from the Commission,
acknowledging that the Lithuanian authorities had taken effective action in
compliance with the Council Recommendation of 7 July 2009 and that unexpected
adverse economic events with major unfavourable consequences for government
finances had occurred in Lithuania, addressed a revised recommendation to Lithuania
with a view to bringing the excessive deficit situation to an end by 2012 at
the latest. This recommendation was made public.
(4)       In accordance with Article
4 of the Protocol on the excessive deficit procedure annexed to the Treaties,
the Commission provides the data for the implementation of the procedure. As
part of the application of this Protocol, Member States are to notify data on
government deficits and debt and other associated variables twice a year,
namely before 1 April and before 1 October, in accordance with Article 3 of
Council Regulation (EC) No 479/2009 of 25 May 2009 on the application of the
Protocol on the excessive deficit procedure annexed to the Treaty establishing
the European Community[3].

(5)       When considering whether a
decision on the existence of an excessive deficit should be abrogated, the
Council should take a decision on the basis of notified data. Moreover, a
decision on the existence of an excessive deficit should be abrogated only if
the Commission services’ forecasts indicate that the deficit will not exceed
the 3% of GDP threshold over the forecast horizon[4].
(6)       Based on data provided by
the Commission (Eurostat) in accordance with Article 14 of Regulation (EC) No 479/2009
following the notification by Lithuania before 1 April 2013 and on the
Commission services’ 2013 spring forecast, the following conclusions are
warranted:
–
Having peaked at 9.4% of GDP in 2009 the general
government deficit in Lithuania has been brought down to 7.2% of GDP in 2010, then
to 5.5% of GDP in 2011 and to 3.2% of GDP in 2012. This improvement was driven by
consolidation measures on the expenditure side, in particular a continued
restriction of expenditure growth in accordance with Lithuania’s Law on Fiscal
Discipline, and favourable cyclical conditions.
–
Since the deficit of 3.2% of GDP can be
considered to be close to the reference value and Lithuania's debt-to-GDP ratio
is below the 60% of GDP reference value in a sustained manner, Lithuania is eligible
to the Stability and Growth Pact provisions in the Regulation 1467/97 regarding
systemic pension reforms. Thus, the direct net cost of the pension reform should
be taken into account when assessing the correction of the excessive deficit. As
the net costs of Lithuania's systemic pension reform have been 0.2% of GDP in
2012, as confirmed by the Commission (Eurostat), they explain the excess over the
3 % of GDP Treaty reference value in 2012.
–
Lithuania's 2013 convergence programme projects
the general government deficit to continue falling to 2.5% of GDP in 2013 and 1.5%
of GDP in 2014, while the Commission services’ 2013 spring forecast projects an
improvement, albeit a slower one, of the general government deficit to 2.9% of
GDP in 2013 and to 2.4% of GDP in 2014, based on a no-policy-change assumption.
Thus, the deficit is set to remain below the reference value of 3% of GDP over
the forecast horizon.
–
The Commission services' 2013
spring forecast project the general government gross debt to decrease slightly
from 40.7% of GDP in 2013 to 40.1% of GDP in 2014.
(7)       The Council recalls that,
starting from 2013, which is the year following the correction of the excessive
deficit, Lithuania should progress towards its medium-term objective at an
appropriate pace, including respecting the expenditure benchmark.
(8)       In accordance with Article
126(12) of the Treaty, a Council Decision on the existence of an excessive
deficit is to be abrogated when the excessive deficit in the Member State
concerned has, in the view of the Council, been corrected.
(9)       In the view of the
Council, the excessive deficit in Lithuania has been corrected and Decision 2009/588/EC
should therefore be abrogated,
HAS ADOPTED THIS DECISION:
Article 1
From an overall assessment it follows that the
excessive deficit situation in Lithuania has been corrected.
Article 2
Decision 2009/588/EC is hereby abrogated.
Article 3
This Decision is addressed to the Republic
of Lithuania.
Done at Brussels,
                                                                       For
the Council
                                                                       The
President
[1]               OJ L 202, 4.8.2009, p. 44.
[2]               OJ L 209, 2.8.1997, p. 6.
[3]               OJ L 145, 10.6.2009, p. 1.
[4]               In line with the “Specifications on the
implementation of the Stability and Growth Pact and Guidelines on the format
and content of Stability and Convergence Programmes”, of 3 September2012. See:
http://ec.europa.eu/economy_finance/economic_governance/sgp/pdf/coc/code_of_conduct_en.pdf