[ckan-dev] publisher model

[Richard Cyganiak]

On 27 Apr 2011, at 18:07, Seb Bacon wrote:
>> A part of the story is still missing from the picture you're painting: ckan.net is a wiki-like site. Many people can make small contributions towards making a good package. This, I think, is a useful and important part of the story.
> 
> I agree.  On the other hand, curating the data, wiki-style, is quite a
> specialist role.  I feel we are too optimised for that case when it's
> not very mainstream.

Well, it's a main part of the appeal of CKAN to me.

It is hard to make a good “half wiki, half individually-owned content” system.

> I agree, but also think we need to make it easy for users to put C's
> resources in many different packages, and conversely to list all the
> packages that C's resources are used in.  I suspect the
> copy-and-edit-this-data-story workflow is a more common case than the
> directly-edit-this-data-story, and therefore one that it would be
> better to optimise for in the UI.  It allows very similar yet
> importantly different packages to be grouped together -- a data
> stories around "UK spending in the last 12 months", "Wales spending in
> the last 12 months", "Wales spending over £10k in the last 12 months"
> would all have their own pages yet have nearly identical sets of
> resources.

+1 to all this. But why do you think that sharing resources between packages (be it by cheap copying, or by reference) can't work with the current model/terminology?

Best,
Richard