Re: [iola-conversion-tool] Bug when Adding a document to the tracker

Henrik Levkowetz <> Thu, 23 February 2012 15:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E181221F87B6; Thu, 23 Feb 2012 07:16:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Pj81rqhSduNq; Thu, 23 Feb 2012 07:16:56 -0800 (PST)
Received: from ( [IPv6:2a01:3f0:1:2::30]) by (Postfix) with ESMTP id 1933A21F8736; Thu, 23 Feb 2012 07:16:56 -0800 (PST)
Received: from [2a01:3f0:1:0:21e:c2ff:fe13:7e3e] (port=63478 by with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <>) id 1S0aPC-0001TC-N7; Thu, 23 Feb 2012 16:16:27 +0100
Message-ID: <>
Date: Thu, 23 Feb 2012 16:16:25 +0100
From: Henrik Levkowetz <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Ole Laursen <>
References: <> <> <> <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.3.5
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2D8844BEEBF30092B9866B00"
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on
Cc: Russ Housley <>, The IESG <>,, Robert Sparks <>
Subject: Re: [iola-conversion-tool] Bug when Adding a document to the tracker
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Feb 2012 15:16:57 -0000

Hi Ole,

On 2012-02-23 15:20 Ole Laursen said:
> 2012/2/23 Robert Sparks <>
>> 3.2.1 New Items   draft-snell-atompub-tombstones<>
>> [txt] <>
>> The Atom "deleted-entry" Element (Informational)
>> Token: Peter Saint-Andre (gen area)
> Ah, hang on there. This is actually the single place I was referring to
> before where the set area_acronym is used. So it says "gen" because "gen"
> was set when it was added. You can't see this elsewhere, and it won't work
> for searching either (actually, searching for gen area in the production
> system does find this document but this is because it's an invididual
> submission, and those are classified under gen for some reason).
> I think there used to be a special handling of area in the edit form in
> the Perl code base and the first port of it, that would put individual
> submissions in gen and hide the area if it had already been assigned. So if
> you're wondering why it's in gen and not in app, that may be the cause.

Ok, so if this is used by the IESG or some ADs during the IESG processing,
we should support it.  Do we have a straightforward way of associating a
non-WG document with an area independently of who the sponsoring AD is?

Since areas are groups, too, we should be able to have an association with
the area in the same way that wg documents are associated with a WG, I think.

Best regards,