Here's an example of a simple use of the retrieval facility which illustrates
how you can get a list of recent articles contained in the NATIVE-L archive.
If you send a message containing the text:
// job echo=no
database search dd=rules
//rules dd *
select * in native-l since november
index
/*
to the address "listserv@tamvm1.tamu.edu" (that's the numeral "1" in "tamvm1"
and the letter "l" in "native-l"), you can expect to receive in return a list
of articles in the time range indicated. That list will be in the following
format:
009090 94/11/01 07:47 60 RED EARTH FILM/VIDEO CONTEST
009091 94/11/01 08:08 23 National Science Foundation (MIE)
009092 94/11/01 09:26 87 Health Conference
009093 94/11/01 17:18 90 Tehachapi Pass Questions
009094 94/11/02 10:34 72 NMAI Programs
009095 94/11/02 12:07 38 Job opening-Instit. of American Indian Arts
009096 94/11/02 12:09 20 Sports logo changed
The "since" clause of the select statement is optional. If, however, you
don't qualify your selection in some way, you will exceed the default CPU
time limit set for such jobs (which is only a few seconds). You can extend
the limit via the "CPULIM" clause of the "database search" statement, but
you may still exceed a reasonable time limit since the NATIVE-L archive is
so massive (approaching ten thousand articles as of the end of 1994).
There are a number of ways to specify a date or a date range. All of the
following are acceptable:
select * in native-l since 15 december
select * in native-l since 15-december-91
select * in native-l since 91/12/15
select * in native-l from 91/11/03 to 91/12/15
select * in native-l since today 11:30
and you can also limit selections based on the content of the article
sender and subject fields:
select * in native-l where subject contains publications
or
select * in native-l since nov where subject contains 'grass dancer'
(Single quotes cause case-insensitive searches, while double quotes specify
that upper/lower-case distinctions should be observed. Quotes are not
required if there are no embedded spaces in the search string.)
or
select 'leonard peltier' or 'wounded knee' in native-l where -
subject contains nanews since 6/93
Note that you must use a hyphen ("-") character at the end of a line if you
want to continue the command on the following line. Leading spaces in these
selection commands is ignored (but not so for the lines starting with "//").
To access a specific article, once you know its number, you can submit a
job to the LISTSERV as follows:
// job echo=no
database search dd=rules
//rules dd *
select * in native-l since november
print 9090,9094-9096
/*
(Note that there must be one or more spaces after the "//" in the "// job"
statement above and *NO* spaces after the "//" in the "//rules" line, and
that there must be no spaces at the beginning of any of the lines.)
IN ALL THE FOLLOWING EXAMPLES, YOU MUST USE THE "//" STATEMENTS INDICATED
ABOVE - THEY ARE NOT BEING REPEATED JUST TO EMPHASIZE WHAT COMES BETWEEN
THE "//rules" and "/*" LINES.
You can select based on the content of header lines:
select * in native-l since july where subject contains lubicon
index
or on article content:
select 'lubicon' in native-l since july
index
This latter command will scan the full text of articles, and not just subject
lines.
You can also retrieve articles directly, without having to first request an
index:
select 'crazy horse' in native-l from 93/11/01 to 94/6/31
print all
or:
select 'crazy horse' in native-l since 15 july
print all
or:
select 'crazy horse' in native-l from 15 july to 30 august 91
print all
For more information on how to access individual articles, send a message
containing the command "info database" to "listserv@tamvm1.tamu.edu"
The LISTSERV provides a facility for storing files which can be retrieved
selectively based on their names. These files represent information which
has never been sent to the mailing list, because it has been judged that
the information they contain is of limited interest relative to their length.
Following is a list of files, based upon the output returned from the command
"index native-l" sent to the "tamvm1.tamu.edu" address:
filename filetype rec date time Description
-------- -------- --- -------- -------- -------------
ITTO11TH ECOMAG-1 407 92/02/18 02:12:37 ITTO 11th Session, ECO-Magazine Issue 1
ITTO11TH ECOMAG-2 852 92/02/18 02:14:49 ITTO 11th Session, ECO-Magazine Issue 2
ITTO11TH ECOMAG-3 683 92/02/18 02:16:09 ITTO 11th Session, ECO-Magazine Issue 3
ITTO11TH ECOMAG-4 351 92/02/18 02:14:57 ITTO 11th Session, ECO-Magazine Issue 4
ITTO11TH NEWSLTRS 133 92/02/18 02:12:09 ITTO 11th Session - newsletters
YAKIMA TXT 967 92/02/16 23:40:50 County of Yakima v. Yakima Indian Nation
The column labelled "rec" indicates the number of lines (records) in each file.
In order to retrieve a given file, send a message to "tamvm1.tamu.edu" which
contain one or more commands of the form:
get <filename> native-l
where <filename> contains both components (filename/filetype) listed above.
For example, you could say:
get itto11th ecomag-4 native-l
(Again, make sure you use the letter "l" in "native-l" and the numeral "1"
in "tamvm1")
To get a current list of available files, send the command:
index native-l
I hope to periodically send out a bulletin advising NativeNet subscribers of
new files added to the archive and what they contain. The main purpose of
these archives is to store documents which are too large to conveniently send
to everyone on the list, or I feel that a given item is of limited interest.
For example, much material coming from APC tropical rainforest electronic
conferences is in this category. It may be highly relevant to issues per-
taining to indigenous peoples of those geographic regions, but a given item
may not mention the indigenous issues specifically, referring instead to some
highly specialized aspect of the rainforest subject, such as the proceedings
of a conference or meeting dealing with environmental or economic matters.
(At the present time there are no "filelist" files associated with any of
the lists besides NATIVE-L.)