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

Wed May 18 15:38:44 UTC 2011

On 18 May 2011 16:22, Seb Bacon <seb.bacon at gmail.com> wrote:
> Looks good to me.
>
> Two questions:
>
> 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?

That's my view. Works with existing vdm. @David Raznick what about the
new system?

> 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.  It would be nice to particularly highlight the notes
> function (which is effectively like a Wikipedia "talk" page) if there
> are some notes there.

It can be done, so let's do it. My only concern is there is a lot of
detail here and it's going to be hard to get right, but we can leave
tidy up until the end.

> 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.

They already display user comments and wikis. I think they are keen to
showing suggested corrections / improvements, as long as they are
clearly marked as from the user community. I think seeing a correction
right away is an important incentive for the correcter. But I can see
some CKAN customers not being comfortable with this level of openness.

> 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.
>
> 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.

I like these for future plans. Why not put these in a longterm ticket?

Dave

>
> Seb
>
>
>
> 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
>>
>
>
>
> --
> skype: seb.bacon
> mobile: 07790 939224
> land: 01531 671074
> web: http://baconconsulting.co.uk
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>