Medical Subject Headings MeSH - German Version
Version 27.0 
2022

Issued by the
ZB MED - Information Centre for Life Sciences
Gleueler Strasse 60
50931 Cologne, Germany

The German-language MeSH is a bilingual version and was published by DIMDI until 2019. 

Since the beginning of 2020, the copyright for the German translation of the MeSH is held by ZB MED - Information Center for Life Sciences. 
The use of the German MeSH terms is subject to the CC BY 4.0 license: 
https://creativecommons.org/licenses/by/4.0/deed.de  
under consideration of the attached terms of use.

The copyright for the English MeSH terms is held by the U. S. National Library of Medicine (NLM) in Bethesda MD/USA. 
The use of the English version is subject to the NLM Terms of Use:
https://www.nlm.nih.gov/databases/download/terms_and_conditions_mesh.html

This work was supported by the BMBF-funded de.NBI Cloud within the German Network for Bioinformatics Infrastructure (de.NBI) (031A532B, 031A533A, 031A533B, 031A534A, 031A535A, 031A537A, 031A537B, 031A537C, 031A537D, 031A538A).

------------------------------------------------------------------------------------------------------------
Files:

readme_MeSH_2022.txt  - this file



\xml - XML-based
	* MeSH_DE_2022.owl  - Complete Data File in RDF/XML-Format
	* MeSH_DE_2022.ttl  - Complete Data File in Turtle-Format
	* MeSH_DE_2022.nt   - Complete Data File in N-Triples-Format
        * MeSH_DE_2022.xml  - Complete Data File in XML-Format
        * desc2022.dtd   - XML Document Type Definition

\json - JSON-based Version
	* MeSH_DE_2022.jsonld - Complete Data File in JSON-LD-Format
     
\database - MeSH_DE_2022_Database Version 
	* ANN.TXT - Annotations (only in English)
	* CC.TXT  - Classification Codes 
        * ET.TXT  - Entry Terms
        * ETD.TXT - Entry Terms German
        * ETE.TXT - Entry Terms English
	* MH.TXT  - Main Headings 
        * QF.TXT  - Subheadings
        * RT.TXT  - Related Terms
        * SCN.TXT - Scope Notes (only in English)

DEMO-File_MeSH_DE_2022_XML-Version
        * desc2022.dtd - XML Document Type Definition
        * MeSH_DE_DEMO2022.xml

DEMO-Files_MeSH_DE_2022_Database Version
	* ANN-DEMO.TXT - Annotations (only in English)
	* CC-DEMO.TXT  - Classification Codes 
        * ET-DEMO.TXT  - Entry Terms
        * ETD-DEMO.TXT - Entry Terms German
        * ETE-DEMO.TXT - Entry Terms English
	* MH-DEMO.TXT  - Main Headings 
        * QF-DEMO.TXT  - Subheadings
        * RT-DEMO.TXT  - Related Terms
        * SCN-DEMO.TXT - Scope Notes (only in English)



------------------------------------------------------------------------------------------------------------
References to the different versions of the German-language MeSH:
------------------------------------------------------------------------------------------------------------

1. XML - Versions

(a) MeSH_DE_2022.owl

The used entities(properties + resources) are documented in a vocabulary file of the NLM. Accessible via the following link:
ftp://ftp.nlm.nih.gov/online/mesh/vocabulary_0.9.3.ttl

The MeSH data stored in the MeSH_DE_2022.owl file is quite large and can only be edited sensibly with RDF/XML-compliant software. 



The German translation of the Main Headings is in the mesh:TopicalDescriptor elements 

<rdf:Description rdf:about="http://id.nlm.nih.gov/mesh/D000006">
                    <rdfs:label xml:lang="de">Abdomen, akutes</rdfs:label>
                    <mesh:preferredTerm>http://id.zbmed.de/mesh/de/2022/ger0000006</mesh:preferredTerm>
</rdf:Description>



And it is also in the mesh:Concept elements 

<rdf:Description rdf:about="http://id.nlm.nih.gov/mesh/M0000006">
                    <rdfs:label xml:lang="de">Abdomen, akutes</rdfs:label>
                    <mesh:preferredTerm>http://id.zbmed.de/mesh/de/2022/ger0000006</mesh:preferredTerm>
                    <mesh:term>http://id.zbmed.de/mesh/de/2022/ger0021845</mesh:term>
</rdf:Description>

Additionally the mesh:Concept provides a connection to other related terms of the concept.

<rdfs:label xml:lang="de"> contains the label of the preferred German term.
<mesh:preferredTerm> links to the IRI(Internationalized Resource Identifier) of the preferred German term.
<mesh:term> links to the IRI of a related German term of this concept. 



The German translation of the Entry Terms is in the elements 

<rdf:Description rdf:about="http://id.zbmed.de/mesh/de/2022/ger0000006">
		    <mesh:dateCreated rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2003-04-25</mesh:dateCreated>
                    <mesh:prefLabel xml:lang="de">Abdomen, akutes</mesh:prefLabel>
                    <mesh:seeAlso>http://id.nlm.nih.gov/mesh/T000013</mesh:seeAlso>
</rdf:Description>

<mesh:prefLabel xml:lang="de"> contains the German term. German Strings are identified by the language tag xml:lang="de". The local identifier also begin with "ger".
<mesh:seeAlso> provides the connection between the German and the English term.


(b) MeSH_DE_2022.ttl

The used entities(properties + resources) are documented in a vocabulary file of the NLM. Accessible via the following link:
ftp://ftp.nlm.nih.gov/online/mesh/vocabulary_0.9.3.ttl

The MeSH data stored in the MeSH_DE_2022.ttl file is quite large and can only be edited sensibly with RDF/XML-compliant software. The syntax of a Terse RDF Triple Language (Turtle)(.ttl) file is similar to that of SPARQL queries.



The German translation of the Main Headings is in the mesh:TopicalDescriptor elements 

<http://id.nlm.nih.gov/mesh/D000006>
        <http://www.w3.org/2000/01/rdf-schema#label>
                "Abdomen, Acute"@en , "Abdomen, akutes"@de ;
        <http://id.nlm.nih.gov/mesh/vocab#preferredTerm>
                <http://id.zbmed.de/mesh/de/2022/ger0000006> .



And it is also in the mesh:Concept elements 

<http://id.nlm.nih.gov/mesh/M0000006>
        a       <http://id.nlm.nih.gov/mesh/vocab#Concept> ;
        <http://www.w3.org/2000/01/rdf-schema#label>
                "Abdomen, akutes"@de ;
        <http://id.nlm.nih.gov/mesh/vocab#preferredTerm>
                <http://id.zbmed.de/mesh/de/2022/ger0000006> ;
        <http://id.nlm.nih.gov/mesh/vocab#term>
                <http://id.zbmed.de/mesh/de/2022/ger0021845> .

Additionally the mesh:Concept provides a connection to other related terms of the concept.

<http://www.w3.org/2000/01/rdf-schema#label> "Label"@de contains the label of the preferred German term.
<http://id.nlm.nih.gov/mesh/vocab#preferredTerm> links to the IRI(Internationalized Resource Identifier) of the preferred German term.
<http://id.nlm.nih.gov/mesh/vocab#term> links to the IRI of a related German term of this concept. 



The German translation of the Entry Terms is in the elements 

<http://id.zbmed.de/mesh/de/2022/ger0000006>
        <http://id.nlm.nih.gov/mesh/vocab#dateCreated>
                "2003-04-25"^^<http://www.w3.org/2001/XMLSchema#date> ;
        <http://id.nlm.nih.gov/mesh/vocab#prefLabel>
                "Abdomen, akutes"@de ;
        <http://id.nlm.nih.gov/mesh/vocab#seeAlso>
                <http://id.nlm.nih.gov/mesh/T000013> .

<http://id.nlm.nih.gov/mesh/vocab#prefLabel> "Label"@de contains the German term. German Strings are identified by the language tag xml:lang="de". The local identifier also begin with "ger".
<http://id.nlm.nih.gov/mesh/vocab#seeAlso> provides the connection between the German and the English term.


(c) MeSH_DE_2022.nt

The used entities(properties + resources) are documented in a vocabulary file of the NLM. Accessible via the following link:
ftp://ftp.nlm.nih.gov/online/mesh/vocabulary_0.9.3.ttl

The MeSH data stored in the MeSH_DE_2022.nt file is quite large and can only be edited sensibly with RDF/XML-compliant software. A N-Triples(.nt) file is a line-based, plain text serialisation format for RDF graphs.



The German translation of the Main Headings is in the mesh:TopicalDescriptor elements 

<http://id.nlm.nih.gov/mesh/D000006>	<http://www.w3.org/2000/01/rdf-schema#label>	"Abdomen, akutes"@de .
<http://id.nlm.nih.gov/mesh/D000006>	<http://id.nlm.nih.gov/mesh/vocab#preferredTerm>	<http://id.zbmed.de/mesh/de/2022/ger0000006> .



And it is also in the mesh:Concept elements 

<http://id.nlm.nih.gov/mesh/M0000006>	<http://www.w3.org/2000/01/rdf-schema#label>	"Abdomen, akutes"@de .
<http://id.nlm.nih.gov/mesh/M0000006>	<http://id.nlm.nih.gov/mesh/vocab#preferredTerm>	<http://id.zbmed.de/mesh/de/2022/ger0000006> .
<http://id.nlm.nih.gov/mesh/M0000006>	<http://id.nlm.nih.gov/mesh/vocab#term>	<http://id.zbmed.de/mesh/de/2022/ger0021845> .

Additionally the mesh:Concept provides a connection to other related terms of the concept.

<http://www.w3.org/2000/01/rdf-schema#label> "Label"@de contains the label of the preferred German term.
<http://id.nlm.nih.gov/mesh/vocab#preferredTerm> links to the IRI(Internationalized Resource Identifier) of the preferred German term.
<http://id.nlm.nih.gov/mesh/vocab#term> links to the IRI of a related German term of this concept. 



The German translation of the Entry Terms is in the elements 

<http://id.zbmed.de/mesh/de/2022/ger0000006>	<http://id.nlm.nih.gov/mesh/vocab#prefLabel>	"Abdomen, akutes"@de .
<http://id.zbmed.de/mesh/de/2022/ger0000006>	<http://id.nlm.nih.gov/mesh/vocab#dateCreated>	"2003-04-25"^^<http://www.w3.org/2001/XMLSchema#date> .
<http://id.zbmed.de/mesh/de/2022/ger0000006>	<http://id.nlm.nih.gov/mesh/vocab#seeAlso>	<http://id.nlm.nih.gov/mesh/T000013> .

<http://id.nlm.nih.gov/mesh/vocab#prefLabel> "Label"@de contains the German term. German Strings are identified by the language tag xml:lang="de". The local identifier also begin with "ger".
<http://id.nlm.nih.gov/mesh/vocab#seeAlso> provides the connection between the German and the English term.


(d) MeSH_DE_2022.xml

The data structure of the desc2022.dtd Document Type Definition file is XML.
The MeSH data stored in the MeSH_DE_2022.xml file is quite large
and can only be edited sensibly with xml-compliant software. To do this you must
e.g. extract the data elements that are essential for your own application with XSLT. 

The DEMO-File MeSH_DE_DEMO2022.xml contains two data set examples and can be opened and viewed with any editor - even with MS-Word. 

The DTD originates from the US National Library of Medicine and contains no structures to
illustrate multilingualism. However, the German terms are marked within the document.

   
The German translation of the Main Headings is in the elements 

<DescriptorName>
   <String>Calcimycin[Calcimycin]</String>
</de/2022scriptorName>

<String> contains first the German term and then the English term in square brackets.

The German translation of the Entry Terms is in the elements 

<Term  ConceptPreferredTermYN="Y"  IsPermutedTermYN="N"  PrintFlagYN="Y"  RecordPreferredTermYN="Y">
  <TermUI>ger0000001</TermUI>
  <String>Calcimycin</String>
  <DateCreated><Year>2003</Year><Month>04</Month><Day>25</Day></DateCreated>
</Term>

German Strings are identified by TermUI beginning with "ger".




--------------------------------------------------------------------------------------------------------------

2. JSON-LD - Version

The used entities(properties + resources) are documented in a vocabulary file of the NLM. Accessible via the following link:
ftp://ftp.nlm.nih.gov/online/mesh/vocabulary_0.9.3.ttl

The MeSH data stored in the MeSH_DE_2022.jsonld file is quite large. The used entities are also listed in the "@context" part of the MeSH_DE_2022.jsonld file. There is some general information about the format JSON-LD at wikipedia (https://en.wikipedia.org/wiki/JSON-LD)



The German translation of the Main Headings is in the mesh:TopicalDescriptor elements 

{
  "@id" : "http://id.nlm.nih.gov/mesh/D000006",
  "preferredTerm" : "http://id.zbmed.de/mesh/de/2022/ger0000006",
  "label" : {
    "@language" : "de",
    "@value" : "Abdomen, akutes"
  },
  "@context" : {
    "label" : {
      "@id" : "http://www.w3.org/2000/01/rdf-schema#label"
    },
    "preferredTerm" : {
      "@id" : "http://id.nlm.nih.gov/mesh/vocab#preferredTerm",
      "@type" : "@id"
    }
  }
}



And it is also in the mesh:Concept elements 

{
  "@id" : "http://id.nlm.nih.gov/mesh/M0000006",
  "preferredTerm" : "http://id.zbmed.de/mesh/de/2022/ger0000006",
  "term" : "http://id.zbmed.de/mesh/de/2022/ger0021845",
  "label" : {
    "@language" : "de",
    "@value" : "Abdomen, akutes"
  },
  "@context" : {
    "preferredTerm" : {
      "@id" : "http://id.nlm.nih.gov/mesh/vocab#preferredTerm",
      "@type" : "@id"
    },
    "term" : {
      "@id" : "http://id.nlm.nih.gov/mesh/vocab#term",
      "@type" : "@id"
    },
    "label" : {
      "@id" : "http://www.w3.org/2000/01/rdf-schema#label"
    }
  }
}

Additionally the mesh:Concept provides a connection to other related terms of the concept.

"label" contains a JSON-LD object which contains the "@value" and the "@language" of the preferred German term.
"preferredTerm" links to the IRI(Internationalized Resource Identifier) of the preferred German term.
"term" links to the IRI of a related German term of this concept. 



The German translation of the Entry Terms is in the elements 

{
  "@id" : "http://id.zbmed.de/mesh/de/2022/ger0000006",
  "dateCreated" : "2003-04-25",
  "prefLabel" : {
    "@language" : "de",
    "@value" : "Abdomen, akutes"
  },
  "seeAlso" : "http://id.nlm.nih.gov/mesh/T000013",
  "@context" : {
    "seeAlso" : {
      "@id" : "http://id.nlm.nih.gov/mesh/vocab#seeAlso",
      "@type" : "@id"
    },
    "dateCreated" : {
      "@id" : "http://id.nlm.nih.gov/mesh/vocab#dateCreated",
      "@type" : "http://www.w3.org/2001/XMLSchema#date"
    },
    "prefLabel" : {
      "@id" : "http://id.nlm.nih.gov/mesh/vocab#prefLabel"
    }
  }
}

"prefLabel" contains the German term. German Strings are identified by the key:value pair "@language" : "de". The local identifier also begin with "ger".
"seeAlso" provides the connection between the German and the English term.


--------------------------------------------------------------------------------------------------------------

3. Database - Database Version

This version is designed for the import into rational database systems.
Knowledge in dealing with such systems and knowledge of the 
Structured Query Language SQL are requirement. The files are normalised
(Boyce-Codd-Normalform) and are available as hyphenated Text-Files
in ISO 8859-1 (Latin-1).

The DEMO-Files of the database version only contain parts of the stored data: 
All Main Headings for Category A (Anatomy), the corresponding Entry Terms and 
the equivalent Classification Codes.

In section 3b. (Microsoft Access - Database Set-up) and 3d. (PostgreSQL - Database Set-up) you find a description of the database structure and
SQL statements to build a MeSH database. Under 3c. (Microsoft Access - Sample queries) examples for queries in
this database are given.

The database made up of single tables linked via foreign
keys and some inquiry examples are described here with
SQL (Structured Query Language). It was tested with PostgreSQL respectively Microsoft Access.
You might possibly have to adapt these instructions for a different
rational database system since the realisation of SQL-Standards differ
from system to system.


3a. Index of Tables

--> Main Headings table, MH.TXT file

Main Headings of MeSH are included herein. 
Fields:

  ENR       - unique Main Heading identification number
  MHD       - German Main Heading
  MHE       - English Main Heading
  AQString  - Allowed Qualifiers: two letters. Abbreviations of the Subheadings
              allowed for this Main Heading

  The relationship between Main Headings and allowed Subheadings is an
  n:m-relationship. The MeSH-Database is deliberately not normalised here on
  account of the storage space.


--> RelatedTerms table, RT.TXT file

Contains the Related Terms for Main Headings.
Fields:

  MHENR   - ENR of the Main Headings, from where the Related Terms starts
  RTENR   - ENR of the Main Headings, at which the Related Terms aims


--> EntryTerms table, ET.TXT file

Contains the synonyms (Entry Terms) for the Main Headings. Not every
English Entry Term has a strictly synonymous German equivalent, not every
German Entry Term reverts to an English translation. 
Felder:

  ETD     - German Entry Term (Synonym):
		 If a German Entry Term is available,
                 the English Entry Term field is empty
  ETE     - English Entry Term (Synonym): 
		 If an English Entry Term is available,
                 the German Entry Term field is empty
  ENR     - Cross-reference to the Main Heading synonymous to this entry


--> EntryTerms table, ETE.TXT file

Contains the English synonyms (Entry Terms) for the Main Headings.
Fields:

  ETE     - English Entry Term
  ENR     - Cross-reference to the Main Heading synonymous to this entry


--> EntryTerms table, ETD.TXT file

Contains German synonyms (Entry Terms) for the Main Headings. 
Fields:

  ETD     - German Entry Term (Synonym)
  ENR     - Cross-Reference to the Main Heading synonymous to this entry


--> ClassificationCodes table, CC.TXT file

Contains alphanumberical codes which show the MeSH tree structure. The
MeSH is a polyhierarchical Thesaurus, i.e. a Main Heading can appear in
several places of the tree structure. 
Fields:

  CC      - Classification Code
  ENR     - Cross-reference to the Main Heading appearing here in the tree structure



--> Subheadings table, QF.TXT file

MeSH permits you to get a better description of the subject matter of certain Main Headings 
by using Subheadings (Qualifiers), e.g. Liver diseases/Therapy,
to show that you do not mean liver diseases in general but especially
the therapy of liver diseases. This table contains the individual Subheadings. 
Fields:

  QFAbk    - two-letter abbreviation for Subheading; conforms
             to the English-language Subheading
  QFD      - German Subheading
  QFE      - English Subheading


--> Annotations Table, ANN.TXT file

Instructions for indexing with MeSH descriptors. This
Information is only available in English. 
Fields:

  ENR     - ENR of Main Headings to which the Annotation refers
  ANN     - Annotation Text
 

-> Tabelle Scope Notes, SCN.TXT file

Definition of then Main Headings. This information is only available
in English.
Fields:

  ENR     - ENR of Main Headings to which the Annotation refers
  SCN     - Scope Note Text




3b. Microsoft Access - Database Set-up

The tables are equipped with references for each text field
(Main Headings, Entry Terms, Subheadings). This accelerates the 
database queries considerably, yet it increases storage space
as well. Depending on your own application, you can do without the
references e.g. on all English fields if you do not have any English
queries.

Please note that the files are normalised (Boyce-Codd-Normalform) and
are available as hyphenated Text-Files in ISO 8859-1 (Latin-1).

Please enter the following SQL instructions in sequence to setup
the individual tables:

CREATE TABLE MainHeadings (
  ENR      Text(10)   CONSTRAINT ENRX PRIMARY KEY,
  MHD      Text(255)  ,
  MHE      Text(255)  ,
  AQString Text(255)
) ;

CREATE TABLE EntryTerms (
  ETD   Text(255)   ,
  ETE   Text(255)   ,
  ENR   Text(10)    CONSTRAINT ETMH REFERENCES MainHeadings
) ;

CREATE TABLE EntryTermsGerm (
  ETD   Text(255)   ,
  ENR   Text(10)    CONSTRAINT GETMH REFERENCES MainHeadings
) ;

CREATE TABLE EntryTermsEngl (
  ETE   Text(255)   ,
  ENR   Text(10)    CONSTRAINT EETMH REFERENCES MainHeadings
) ;

CREATE TABLE RelatedTerms (
  MHENR Text(10)    CONSTRAINT ENRMH REFERENCES MainHeadings,
  RTENR Text(10)    CONSTRAINT ENRRT REFERENCES MainHeadings
) ;

CREATE TABLE ClassificationCodes (
  CC    Text(255)   ,
  ENR   Text(10)    CONSTRAINT CCMH REFERENCES MainHeadings
);

CREATE TABLE Subheadings (
  QFAbk Text(2)    CONSTRAINT QFAbk PRIMARY KEY,
  QFD   Text(255)  ,
  QFE   Text(255)  
) ;

CREATE TABLE Annotations (
  ENR   Text(10)    CONSTRAINT ANNMH REFERENCES MainHeadings,
  ANN   Memo
);

CREATE TABLE ScopeNotes (
  ENR   Text(10)    CONSTRAINT SCNMH REFERENCES MainHeadings,
  SCN   Memo
);

Then import die input files into the tables in the specified order.
Notify the database system that the individual values are separated
by using vertical lines (|) and semicolons (;).

MH.TXT   --> MainHeadings
ET.TXT   --> EntryTerms
ETD.TXT --> EntryTermsGerm
ETE.TXT --> EntryTermsEngl
RT.TXT   --> RelatedTerms
CC.TXT   --> ClassificationCodes
QF.TXT   --> Subheadings
ANN.TXT  --> Annotations
SCN.TXT  --> ScopeNotes



3c. Microsoft Access - Sample Queries

The following sample queries are to show how information can be 
extracted from the different tables. 


--> 1. Alphabetical List of all German Main Headings

SELECT MHD
FROM MainHeadings
ORDER BY MHD ;



--> 2. Alphabetical List of all German Terms
SELECT MHD As TERM
FROM MainHeadings
UNION ALL
SELECT ETD As TERM
FROM EntryTerms
WHERE ETD <> NULL
ORDER BY TERM;


--> 3. Alphabetical List of all Pairs of Terms (Main Headings und
       Entry Terms)

SELECT MHD As TermD, MHE As TermE
FROM MainHeadings
UNION ALL
SELECT ETD As TermD, ETE As TermE
FROM EntryTerms
WHERE ETD <> NULL AND ETE <> NULL
ORDER BY TermD ;


--> 4. Hierarchical List of the Main Headings (Tree structure)

SELECT CC, MHD
FROM ClassificationCodes C, MainHeadings M
WHERE C.ENR = M.ENR
ORDER BY CC ;


--> 5. Main Headings with allowed Subheadings

SELECT MHD, AQString
FROM MainHeadings M
ORDER BY MHD ;

--> 6. Main Headings with Related Terms

SELECT M.MHD, RTMH.MHD AS SIEHEAUCH
FROM MainHeadings M INNER JOIN 
  (RelatedTerms R INNER JOIN MainHeadings RTMH ON R.RTENR=RTMH.ENR) 
  ON M.ENR=R.MHENR 
ORDER BY M.MHD ;


3d. PostgreSQL - Database Set-up

The tables are equipped with references for each text field
(Main Headings, Entry Terms, Subheadings). This accelerates the 
database queries considerably, yet it increases storage space
as well. Depending on your own application, you can do without the
references e.g. on all English fields if you do not have any English
queries.

Please note that the files are normalised (Boyce-Codd-Normalform) and
are available as hyphenated Text-Files in ISO 8859-1 (Latin-1).

Please enter the following SQL instructions in sequence to setup
the individual tables:

CREATE TABLE mesh.MainHeadings (
  ENR      varchar(10)    CONSTRAINT ENRX PRIMARY KEY,
  MHD      varchar(255)  ,
  MHE      varchar(255)  ,
  AQString varchar(255)
) ;

CREATE TABLE mesh.EntryTerms (
  ETD   varchar(255)   ,
  ETE   varchar(255)   ,
  ENR   varchar(10)    CONSTRAINT ETMH REFERENCES mesh.MainHeadings,
  nix   varchar(1)
) ;

CREATE TABLE mesh.EntryTermsGerm (
  ETD   varchar(255)   ,
  ENR   varchar(10)    CONSTRAINT GETMH REFERENCES mesh.MainHeadings,
  nix   varchar(1)
) ;

CREATE TABLE mesh.EntryTermsEngl (
  ETE   varchar(255)   ,
  ENR   varchar(10)    CONSTRAINT EETMH REFERENCES mesh.MainHeadings,
  nix   varchar(1)
) ;

CREATE TABLE mesh.RelatedTerms (
  MHENR varchar(10)    CONSTRAINT ENRMH REFERENCES mesh.MainHeadings,
  RTENR varchar(10)    CONSTRAINT ENRRT REFERENCES mesh.MainHeadings,
  nix   varchar(1)
) ;

CREATE TABLE mesh.ClassificationCodes (
  CC    varchar(255)   ,
  ENR   varchar(10)    CONSTRAINT CCMH REFERENCES mesh.MainHeadings,
  nix   varchar(1)
);

CREATE TABLE mesh.Subheadings (
  QFAbk varchar(2)    CONSTRAINT QFAbk PRIMARY KEY,
  QFD   varchar(255)  ,
  QFE   varchar(255)  
) ;

CREATE TABLE mesh.Annotations (
  ENR   varchar(10)    CONSTRAINT ANNMH REFERENCES mesh.MainHeadings,
  ANN   varchar(5000)
);

CREATE TABLE mesh.ScopeNotes (
  ENR   varchar(10)    CONSTRAINT SCNMH REFERENCES mesh.MainHeadings,
  SCN   varchar(5000)
);

Then import die input files into the tables in the specified order.
Notify the database system that the individual values are separated
by using vertical lines (|) and semicolons (;).

--MH.TXT   --> MainHeadings
\COPY mesh.MainHeadings FROM 'MH.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--ET.TXT   --> EntryTerms
\COPY mesh.EntryTerms FROM 'ET.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--ETD.TXT --> EntryTermsGerm
\COPY mesh.EntryTermsGerm FROM 'ETD.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--ETE.TXT --> EntryTermsEngl
\COPY mesh.EntryTermsEngl FROM 'ETE.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--RT.TXT   --> RelatedTerms
\COPY mesh.RelatedTerms FROM 'RT.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--CC.TXT   --> ClassificationCodes
\COPY mesh.ClassificationCodes FROM 'CC.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--QF.TXT   --> Subheadings
\COPY mesh.Subheadings FROM 'QF.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--ANN.TXT  --> Annotations
\COPY mesh.Annotations FROM 'ANN.TXT' delimiter ';' quote '|' encoding 'latin1' csv;
--SCN.TXT  --> ScopeNotes
\COPY mesh.ScopeNotes FROM 'SCN.TXT' delimiter ';' quote '|' encoding 'latin1' csv;




