Re: [SLUG] RFC: Gradebook Project Database

From: Paul M Foster (paulf@quillandmouse.com)
Date: Tue Oct 15 2002 - 19:31:20 EDT


False administrivia bounce (w_h_i_c_h command)...

----- Forwarded message from slug@lists.nks.net -----

From: slug@lists.nks.net
Date: Tue, 15 Oct 2002 10:27:10 -0400
To: owner-slug@bart.nks.net
Subject: BOUNCE slug@lists.nks.net: Admin request of type /^\s*which\s+\S+\s*$/i at line 9
Message-Id: <200210151427.KAA29023@bart.nks.net>

>From owner-slug Tue Oct 15 10:27:10 2002
Received: from homer.nks.net (homer.nks.net [66.152.21.172])
        by bart.nks.net (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA29020
        for <slug@lists.nks.net>; Tue, 15 Oct 2002 10:27:10 -0400
Received: from smtp-server4.tampabay.rr.com (smtp-server4.tampabay.rr.com
[65.32.1.45])
        by homer.nks.net (8.9.3/8.9.3) with ESMTP id KAA03813
        for <slug@nks.net>; Tue, 15 Oct 2002 10:27:09 -0400
Received: from test01 (102bus18.tampabay.rr.com [24.94.102.18])
        by smtp-server4.tampabay.rr.com (8.12.2/8.12.2) with SMTP id
        g9FEQnlb003590
        for <slug@nks.net>; Tue, 15 Oct 2002 10:26:51 -0400 (EDT)
Message-ID: <046301c27456$f1647fa0$3249490a@test01>
From: "Robert Foxworth" <rfoxwor1@tampabay.rr.com>
To: <slug@nks.net>
References: <E181I43-00018a-00@localhost> <3DAC124D.5090901@iotcorp.com>
Subject: Re: [SLUG] RFC: Gradebook Project Database
Date: Tue, 15 Oct 2002 10:26:57 -0400
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

 You may find this to be a minor issue. But as long as you are recording the
date in any field, you may well come to a point where you wish to sort on
that date field. And when that happens, you will wish you had followed the
ISO standard on how to write the date, which is YYYYMMDD, thus your dates
in the example would be 19890323 and 19890214. This will give an unambiguous
sort even across century boundaries; years, then months, then days. In
additon it resolves the ambiguity between European and US format (is it
April 7 or 7 April) which some in Europe try to 'fix' by calling it 7 IV
w_h_i_c_h of
course doesn't work in an all-numerical date field. Bob F

<snip>

> You should really do two tables for
> this, one defines each item (such as "3/23/1989: Recitation of the
> prologue to the Canterbury Tales" or "2/14/1989: Dissection of fetal
> pig".) It might be nice to allow the teachers to assign weights
>
> --ronan

----- End forwarded message -----



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:14:06 EDT