[ckan-dev] ckanext-scheming vs tag vocabularies

[Ian Ward]

Hello Armin,

I use scheming multiple-choice fields because my controlled
vocabularies are very tied to my metadata schemas (and I want
multilingual labels). Scheming also lets me take those choices from a
datastore table, an external skos file or anything you can access from
a helper function. It doesn't mirror the vocabulary in postgres
because that hasn't been required.

On Tue, Dec 6, 2016 at 5:24 AM, Armin Retterath
<armin.retterath at gmail.com> wrote:
> hi together,
>
> if you want to define custom categories, the two different options
> "ckanext-scheming with choices" and "tag vocabularies" are possible. is
> there an idea to merge them into one concept? maybe to use links to
> distributed skos files (maybe also multilingual) in the json-schema
> alternative to define the choices by hand? or maybe the choices array will
> be automatically be transformed in a tag vocabulary in the postgres
> database?
>
> best regards from germany
> armin
>
> _______________________________________________
> 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
>