[ckan-dev] FIxing the DataStore vs FileStore duality confusion
Dominik Moritz
dominik.moritz at okfn.org
Thu Mar 14 17:19:49 UTC 2013
On 14 Mar 2013, at 14:06, Mark Wainwright <mark.wainwright at okfn.org> wrote:
> This is great! thanks Sean.
>
>> I've since convinced myself that this is a bad idea because it's too
>> confusing from the user's point of view (see questions below the
>> suggestion on the wiki page)
>>
>> - "Alternative Suggestion: FileStore and DataStore as one resource type"
>> is an alternative idea that might be much less work to implement and
>> may cover everything while also being simpler from the user's point of
>> view, I've just written this but no one has looked at/criticised it
>> yet.
>
> I am very strongly in favour of this Alternative Suggestion.
>
> By the way, I admit my user stories covered functionality beyond the
> basic datastore/filestore - I included them because I think they all
> nevertheless bear on what kind of behaviour users will expect from
> CKAN's storage, and in all cases, this is that the user just wants to
> know 'Have you got the data or not?' not 'Have you got it in your pink
> folder? How about your purple folder?' So I agree that the 'suggested
> behaviour' is far too complicated and confusing (and so is the current
> behaviour).
>
> I think Sean's 'alternative suggestion' really well combines meeting
> user expectations of comprehensibility with providing all the
> functions people want and giving people control over their data.
>
> One comment: I appreciate that datastore versioning, nice though it
> might be, is a long way off. But how feasible is it to at least keep a
> list of edit time + user for each (editable) datastore resource? I
> think edited data with no paper trail at all would make most people
> too nervous to use the possibilities created by updating via
> datastore.
I don't think that there is much difference between versions and just storing an activity stream for datstore resources compared to the advantage of real versions. I would also love to implement versions. Maybe this summer after I have finished my studies ;-)
>
> Mark
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
More information about the ckan-dev
mailing list