[ckan-dev] Relationships between Datasets and Organizations
David Read
david.read at hackneyworkshop.com
Mon Aug 12 11:37:12 UTC 2013
As I understand it (since there are no docs or tests for
organizations...), a dataset in an organizations needs both owner_org
set and the Member created to work properly. I guess that it was
decided that although it breaks the DRY principle, it makes stuff
faster. I could be wrong.
David
On 8 August 2013 22:33, Vitor Baptista <vitor at vitorbaptista.com> wrote:
> Hi all,
>
> I'm trying to understand how the relationship between datasets and
> organizations works. For Groups, as far as I can see, the relationship is
> something like:
>
> Dataset -> Member -> Group
>
> Member is a many-to-many association between Dataset and Group. At first I
> thought it was the same for Organizations, but I think there's something
> else. They have these associations, with entries in Member, with activity =
> 'organization', but there's also an owner_org column in Dataset itself.
> Basically, we have both:
>
> Dataset -> Member -> Organization
>
> and:
>
> Dataset -> Organization (through owner_org field).
>
> What's the difference between these two ways?
>
> Cheers,
>
> Vítor Baptista
>
> Developer | http://vitorbaptista.com | LinkedIn | @vitorbaptista
>
> The Open Knowledge Foundation
>
> Empowering through Open Knowledge
>
> http://okfn.org/ | @okfn | OKF on Facebook | Blog | Newsletter
>
>
> _______________________________________________
> 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