Re: [yaco-community-tool] Observations from my second attempt at using the community tool

"Emilio A. Sánchez" <esanchez@yaco.es> Thu, 15 December 2011 11:48 UTC

Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-community-tool@ietfa.amsl.com
Delivered-To: yaco-community-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E2E21F8490 for <yaco-community-tool@ietfa.amsl.com>; Thu, 15 Dec 2011 03:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.517
X-Spam-Level:
X-Spam-Status: No, score=-1.517 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRu9paa9C4Yc for <yaco-community-tool@ietfa.amsl.com>; Thu, 15 Dec 2011 03:48:34 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 88F6621F8468 for <yaco-community-tool@ietf.org>; Thu, 15 Dec 2011 03:48:34 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so3006319wgb.13 for <yaco-community-tool@ietf.org>; Thu, 15 Dec 2011 03:48:33 -0800 (PST)
Received: by 10.216.138.76 with SMTP id z54mr606279wei.17.1323949713382; Thu, 15 Dec 2011 03:48:33 -0800 (PST)
Received: from [192.168.0.193] ([77.227.215.107]) by mx.google.com with ESMTPS id fi11sm8861367wbb.9.2011.12.15.03.48.31 (version=SSLv3 cipher=OTHER); Thu, 15 Dec 2011 03:48:32 -0800 (PST)
Message-ID: <4EE9DE8F.8070508@yaco.es>
Date: Thu, 15 Dec 2011 12:48:31 +0100
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: yaco-community-tool@ietf.org
References: <4EE28025.5030307@nostrum.com>
In-Reply-To: <4EE28025.5030307@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-community-tool] Observations from my second attempt at using the community tool
X-BeenThere: yaco-community-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / Community ID Tracking and Notification Project <yaco-community-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-community-tool>
List-Post: <mailto:yaco-community-tool@ietf.org>
List-Help: <mailto:yaco-community-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-community-tool>, <mailto:yaco-community-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Dec 2011 11:48:38 -0000

    Hi Robert,

    I'll answer you inline.

El 09/12/11 22:39, Robert Sparks escribió:
> (The first attempt stopped abruptly with a crash).

    This was a bug. You didn't have an user to log in but your email 
address already was in the system. This bug is now fixed. Thanks for 
your notification.

> I spent some time trying to exercise this tool and ran into several
> problems.
>
> I want to ask about what the expectations of the current implementation
> and test instance were
> before asserting that these are bugs.

    Everything that do not work is a bug :)

> Should the search results be accurate? I set up a rule to search for all
> documents
> containing the text "location conveyance". It only found seven. There
> are many, many
> more.

    I'll check it.

> Should sorting work? - I tried the various sort options in the display
> customization section.
> Alphabetical by title or by filename worked. Publication date didn't.
> Sorting by change or
> significant change produced results that didn't make sense.

    I'll check the publication date sort.

    Sorting by significant/normal changes do not work cause in the 
database there is no information telling if the changes are significant. 
This information is added to the new changes, so when new changes get 
recorder this sorting will work.

    I'll try to get it fixed so at least it sorts by the last existing 
change.

> I could only subscribe to lists or feeds from the read-only view of the
> list.
> It is very unintuitive to look there for those options - why aren't they
> available to me on my regular view?

    I'll add this two links in the "Exports" tab of the list management 
view.

> The view URL itself is coding the username into the URL - why? I
> _assume_ you have coded policy
> that doesn't let me look at Adam's list just because I know his login.
> If that's the case, stopping at
> community/personal or using something like community/personal/mainlist
> and figuring out which
> list to look at by seeing who was logged in seems a lot safer.

    That's a great comment! You're right, the user name is not needed in 
the url, and of course you can't see the list management view of any 
person. I'll change this url.

> Similarly, the way this currently constructs the "read only" view
> necessarily makes all of the lists
> public. The intent of 6293 was that these be private by default and only
> exposed if the person
> wants to expose them. As it is now, I know I can see Adam's list by
> looking at
> http://beta.community.yaco.es/community/personal/adam%40nostrum.com/view/

    I'll replace the url of the public views with a super secret hash so 
you have to explicit share the link.

> I logged in as stream_user. It does not let me change any state on any
> documents, so I couldn't
> test the notification features.

    That was a missconfiguration of the beta server. I've fixed it.

> The option to list "changed within 1,2,7 days" as separate columns would
> be better met with
> just listing a column with the number of days since the last change
> actually in the column.

    I think that 6293 requires these three columns. I suppose that 
someone may want to add to their list just one of them.

> I forgot (and am subsequently surprised) that 6293 restricts users to
> only one list.
> I don't expect that restriction to survive actual use - I hope the code
> will be easy to adapt to the notion of
> multiple lists later.

    Is not trivial to adapt but of course it's easy. The model is not 
restricted to just one list per user but you'll need to do some changes 
like:

    * Add a name to the list model so you can differentiate your lists.
    * Add a view that list all of your ID lists so you can choose one to 
manage.

    Thanks for all your comments.

    Best,

> RjS
>
>
>
> _______________________________________________
> yaco-community-tool mailing list
> yaco-community-tool@ietf.org
> https://www.ietf.org/mailman/listinfo/yaco-community-tool