[ckan-dev] New CREP: Moderated Edits User Interface

[James Gardner]

Hi Seb,

David and John will chip in but my immediate views are as follows (feel 
free to ignore if after discussion there are better ways)...

> 1) I'm thinking about the fact that internally we have separate
> revisions for resources, extras and package metadata.  From a user's
> point of view this could be confusing to expose so I would want to be
> sure that conceptually, everything that they see on a package form
> when they hit save is a single "revision".  Is that right?
>

Yes, they should all be treated together in my view. Whatever is being 
displayed on that form is what is conceptually what the user treats as a 
revision (resources, tags, extras etc).

> 2) I think a "revision" (in the above sense) should have its own
> revision log field that appears when you select a revision in the
> right hand side.

Sounds sensible, John and David, can this be easily included?

> It would be nice to particularly highlight the notes
> function (which is effectively like a Wikipedia "talk" page) if there
> are some notes there.

I think we decided that using the todo extension in the first instance 
would make more sense (it allows notes to be assigned a category such as 
bad description, broken link etc), and only to look at per-field notes 
later if it became obvious we needed them.

> 3) For CKAN.net, we would certainly show all the moderated and
> unmoderated edits to the general public.  I imagine a client like DGU
> would want the unmoderated edits to be only visible to logged in
> users.

Agreed.

> 4) While I think the moderated version (btw I like "approved") should
> be the default view for a package, we should have a great big banner
> at the top of the page when there are outstanding suggested changes,
> saying something like "this data might be out of date -- there are
> unapproved changes suggested by the community that we've not yet
> moderated -- click here to see" or something like that.

Agreed.

> 5) Longer term, if/when we have an active contributor community, we
> will need Wikipedia-like functions such as: recent changes, user
> contributions, user talk pages (for sending a message to a user).
> Similarly, we should integrate the follower extension so that when a
> user edits a package it adds it to their follow list -- to encourage
> regular reviewing.

Yes, but let's not overload ourselves, first step is to get a simple 
"leave a todo note", we can prioritise more advanced features when we 
get feedback from real users. I'd certainly hope to see this sort of 
functionality in phases 2 and 3.

By the way, we are aiming to have an initial cut of this in 3-4 weeks so 
we can't do too much in the first pass. We can then make further 
improvements from there though.

Cheers,

James


> On 18 May 2011 15:57, John Glover<glover.john at gmail.com>  wrote:
>> Hi all,
>>
>> I'm interested in any feedback on this, it depends heavily on some
>> work that David Raznick is doing so I'll be working closely with him
>> and David Read on this next week. Cheers.
>>
>> http://trac.ckan.org/ticket/1141
>>
>>
>> John
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>
>
>