Path: utzoo!utgpu!watmath!clyde!att!rutgers!ukma!uflorida!novavax!proxftl!twwells!comparc
From: comparc@twwells.uucp (comp.archives)
Newsgroups: comp.archives
Subject: Comp.archives database format
Message-ID: <234@twwells.uucp>
Date: 1 Dec 88 11:15:08 GMT
Reply-To: comparc@twwells.UUCP (comp.archives)
Organization: None, Ft. Lauderdale
Lines: 333
Approved: bill@twwells.uucp (T. William Wells)

This is the third attempt at the database structure.  Changes are
still possible, so send in any comments you might have.

Here is a short summary of the changes from the previous version:

    1) The definition of a site is somewhat vague. What I am going to
       do is to consider one set of archives under the control of a
       single administrator as an archive site.  This means that the
       site entry won't have different sets of data for archives
       located at the same site.  This also means that the archive
       name will be somewhat less related to the address of the
       archive.

    2) The access method and access tag of the CO fields have been
       swapped. The access method now comes first.

---

Comments in the databases begin with a #. They are retained with the
data but are otherwise ignored.

In the line oriented databases, if there is a line that is to be left
blank, that line should still be entered, but with everything but the
keyword left blank.

---

The site database contains a series of entries separated by blank
lines.  Each entry has the following lines:

NM 
EN 
TM 
TT 
AD 
MA 
CO 
IX 
KW 
DE 

Each of the lines from AD to DE may be repeated as often as necessary
to contain the data.

Following is a detailed description of each line.

NM 

   This name should be related to the address used to find the site,
   though it doesn't have to.  This should be kept fairly short.

EN @ () 

   This says who the person is who entered the database entry.  The
    is the output from the date command.

TM