[ckan-dev] orgs more clarification

[Sean Hammond]

On Thu, Sep 27, 2012 at 01:10:48PM +0100, Toby Dacre wrote:
> On 27 September 2012 13:07, Sean Hammond <sean.hammond at okfn.org> wrote:
> > On Thu, Sep 27, 2012 at 01:00:15PM +0100, Toby Dacre wrote:
> >> On 27 September 2012 12:43, Sean Hammond <sean.hammond at okfn.org> wrote:
> >> > On Thu, Sep 27, 2012 at 12:18:02PM +0100, Rufus Pollock wrote:
> >> >> On 27 September 2012 11:11, Toby Dacre <toby.okfn at gmail.com> wrote:
> >> >>
> >> >> > * **Developers** can provide custom forms for groups and organizations, for
> >> >> >   example to add custom metadata fields to groups or organizations.
> >> >> >
> >> >> > 1) For orgs is this on a site wide level?  I think this should be or
> >> >> > else we are adding even deeper levels of complexity
> >> >> >
> >> >>
> >> >> Yes it is on a site-wide level.
> >> >>
> >> >>
> >> >> > 2) as I understand things this already exists for groups - can this be
> >> >> > confirmed
> >> >> >
> >> >>
> >> >>  Yes, I believe so -- though Sean may know more.
> >> >
> >> > Yes, this is IGroupController. It also exists for datasets with
> >> > IDatasetController. I think the CKAN 2.0 merge may have broken
> >> > IDatasetController, not sure about IGroupController (David reviewed this
> >> > part of the merge, the controllers).
> >> >
> >> > I actually implemented IOrganizationController plus an example extension
> >> > on Ross's organizations branch, you could look at that.
> >>
> >> I know of it existance but not implementing it keeps things cleaner
> >> and I don't know if it is something we require so I like rufus' don't
> >> bother approach - unless you are aware of a client need
> >
> > I think it's needed, basically most clients end up wanting to customise
> > the forms. Perhaps we can leave it for now and implement it when the
> > first client wants to use it, but I think David originally wanted it to
> > go in now.
> 
> They can customise the forms as I'm building things but it is site
> wise as there is only one type of organisation is this still
> problematic?

I don't know. I would guess that being able to customise site-wide fills
most use cases, and customise per organization type is less important,
but you would have to ask David. Arguably site-wide only does meet the
spec as written, even if it's less flexible than what we have for
datasets and groups.