[ckan-discuss] Architecture Best Practice

[Marina S. Martin]

To be clear, I could be talking about 1200+ custom fields... each
organization has **its own* *custom fields. So far, only one organization
has 300, but I anticipate a trend in that direction. Trying to gauge
upfront when it makes sense (if ever) to break organizations into their own
individual CKANs, especially for things like faceted search.

Speaking of validation, is there any documentation I'm missing on
validators.py? I couldn't quite tell how those validations are currently
being called. (For example I tried to work backwards in the code how
default CKAN stops you if you try to enter a name under 2 characters for a
dataset, but I couldn't clearly find where it was being called.)

Thank you

Marina


On Sun, Apr 28, 2013 at 2:56 AM, Sean Hammond <sean.hammond at okfn.org> wrote:

> > deployment. But wouldn't 300 custom fields x X agencies still equal a
> > tremendous number of fields in a single table, just conditionally
> displayed?
>
> That is a lot of fields, yes. I think the speed of it may depend on a
> couple of things. First, as Ian says, it depends which methods you use
> to store and retrieve those fields. Second, it depends on what
> validation and conversion you do when storing those fields. I don't see
> any reason why validating 300 fields can't be done very quickly, on the
> other hand, I've no doubt it _could_ be very slow, depending on the
> validation functions used.
>
> I think storing this many custom fields is somewhat new territory and is
> also heavily dependent on just what those fields are, so the upshot is
> that you'll have to try it to find out how well it works, and may need
> to experiment with different approaches to find one that works well.
>
> _______________________________________________
> ckan-discuss mailing list
> ckan-discuss at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-discuss
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-discuss/attachments/20130428/2c307360/attachment.htm>