Message info
 
To:Adam Roach From:Henrik Levkowetz Subject:Re: [Tools-discuss] Fwd: Re: Difficulty using DocumentInfo Date:Thu, 05 Apr 2012 23:22:36 +0200
 

Hi Adam, Ryan,

See the longer email I just sent in reply to Adam's first post -- the
use of the external_url field doesn't match the original intentions
for it, and sorting this out will need some cleanup. We still will
need a way to get at both url and filename for a document, but the
external_url field was *only* intended to provide that for documents
which doesn't reside on the local file system.

Again, I consider the current mix-up a failure on my part to make clear
the intentions for that field.


Best regards,

Henrik

On 2012-04-05 19:51 Adam Roach said the following:
> Forwarding back to the tools mailing list, since we need to come to some
> kind of consensus on this.
>
> /a
>
> -------- Original Message --------
> Subject: Re: [Tools-discuss] Difficulty using DocumentInfo
> Date: Thu, 5 Apr 2012 10:48:04 -0700
> From: Ryan Cross <rcross@amsl.com>
> To: Adam Roach <adam@nostrum.com>
>
>
>
> Yes, I agree the field name is inconsistent with how it's used and it should be fixed. "filename" would be better. I'll have to defer to Henrik to respond to model change requests (or he may have another solution).
>
> On Apr 5, 2012, at 10:33 AM, Adam Roach wrote:
>
>> On 4/5/12 12:11 PM, Ryan Cross wrote:
>>> Hi Adam,
>>>
>>> You are correct that meeting material documents (slides, agenda, and minutes) contain just a filename not a qualified URL in the external_url field.
>>
>> Which is a fine bit of data to store, but -- um -- look at the field name and tell me how that makes any sense. This really makes what is otherwise a nice clean model difficult for beginners to get into.
>>
>>> When converting the Meeting Material Manager tool I followed the precedent of the migration in the use of this field because we needed a place to store the disk filename 1) because it might differ from the Document.name and 2) to save the file extension.
>>
>> Can we rename the field -- perhaps to something like "filename" -- before too much code gets written around it? This is the kind of crazy legacy hack we were trying to get away from with the migration.
>>
>>> The method get_absolute_url() should return the information you are looking for.
>>
>> Aha! Yes, that looks exactly like the option (c) I describe below. I'm a bit perplexed about why it is present on Document rather than DocumentInfo. It never even occurred to me to look there.
>>
>> /a
>>
>
>
>
>
>
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss