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

[Robert Sparks <[e-mail]>]

IESG :

Cindy and I stumbled over what we first thought was a bug, but it turned 
out to be a surprising
feature/side-effect of the conversion effort.

The data we've been collecting on the edit-info-form (what we have been 
using to add a document to the
tracker or to change it's IESG state/telechat date, etc.) about which 
area a document belongs to is not being
used by any part of the production datatracker other than that form.



So, it will not appear on the form in the new system (and the data 
collected in the old system is
not being migrated I believe).

That really surprised me, but after digging through the code and 
discussing it with Ole, I'm convinced it's
correct.

If we find a need to start collecting that data again in the future, it 
won't be hard to add.

RjS


On 2/22/12 11:18 AM, Ole Laursen wrote:
> 2012/2/21 Robert Sparks <[e-mail] 
> <mailto:[e-mail]>>
>
>     The biggest is that the form didn't ask for the area the document
>     should be associated with.
>     It occasionally happens that an AD from outside the area takes the
>     shepherd role for a document, so
>     you can't infer this from which AD is assigned.
>
>
> Right. At the moment, we don't store an area at all. Grepping for it, 
> the only place I managed to find using the attribute apart from the 
> edit form is the agenda document template where the proxy wrapper will 
> infer the area from the WG (if there's a WG) or else from the 
> shepherding AD.
>
> The search page looks for the area of the WG in the old schema if you 
> do a search for area, not the area attribute which is perhaps not 
> surprising if it's only set for documents in the IESG process.
>
> So do you think this is a problem still?
<snip/>