[ckan-dev] Storing JSON in resource metadata

[Ian Ward]

Would you share the code you're working on?

In my experience it's easier to store json in the resource extras because
they are all stored internally as elements in a json object instead of rows
in an extras table.
On 16 Jun 2015 6:50 am, "Hendrik Bunke" <bunke.hendrik at gmail.com> wrote:

> Hi,
>
> just a short question to make sure I haven't overseen anything.
>
> Since CKAN 2.3 it is possible to store JSON strings in custom
> fields, which make multiple values, attributes or even
> object-like values possible. That works fine for datasets, and
> it's a great leap forward for the flexibilty of custom metadata!
>
> If trying to implement the same for resources, however, CKAN
> validation still throws an error ('__junk').
>
> Am I right assuming that storing JSON string in custom fields of
> resources is still not supported? If so, what would be necessary
> to implement that in CKAN?
>
> regards
> hendrik
>
> --
> Dr. Hendrik Bunke
> http://gplus.to/hbunke
> http://twitter.com/hbunke
> http://www.hbxt.org
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150616/c73daf6c/attachment-0003.html>