[ECODP-dev] documentation of the CKAN model

[John Glover]

Hi Bert,

Yes, there are quite a few differences. We did not make any changes to the
internal CKAN model for this project. So for example some fields that
appear to be top-level dataset attributes in EUODP are actually stored in
CKAN's package extras table, and are automatically converted to and from
this table so that they meet the desired schema.

So you want this to map to database tables? Some fields will be columns in
dataset or resource tables, others will be rows in separate tables
(referenced by ID).

Regards,
John


On 14 October 2013 11:01, Bert Van Nuffelen
<bert.van.nuffelen at tenforce.com>wrote:

> Hi John,
>
> Are there differences between them?
>
> As I am only working with the api, I am not aware if there is difference
> internally and in the db.
> With 'CKAN field in DB'  my intension was to document which field/column
> in a table contains that info.
>
> kind regards,
>
> Bert
>
>
>
> 2013/10/14 John Glover <john.glover at okfn.org>
>
>> Hi Bert,
>>
>> I am updating this document now. Just to clarify, is 'CKAN field in DB'
>> the name of the field in the CKAN application (so API, etc) or where this
>> is stored in the actual database?
>>
>> I will provide a mapping of CKAN fields to Solr fields separately.
>>
>> Regards,
>> John
>>
>>
>> On 9 October 2013 14:15, Bert Van Nuffelen <
>> bert.van.nuffelen at tenforce.com> wrote:
>>
>>> Hi John and Darwin,
>>>
>>> attached you find the mapping from the RDF model to the CKAN model used
>>> by RDF2CKAN.
>>>
>>> I would like you to complete the next columns:
>>>
>>> * CKAN value definition
>>>   The value restrictions imposed by CKAN on that field
>>> * CKAN field in DB
>>>   The name of the field in CKAN.
>>>
>>> I also looked into the SOLR scheme you pointed to in a previous email.
>>>
>>>
>>> https://github.com/okfn/ckanext-ecportal/blob/master/ckanext/ecportal/solr/schema.xml
>>>
>>> This provides the actual implementation state, but it does not provide
>>> insight w.r.t. the EU ODP setup. What I wonder is if all these fields are
>>> relevant: e.g.
>>>
>>> <field name="depends_on" type="text" indexed="true" stored="false"
>>> multiValued="true"/>
>>>     <field name="dependency_of" type="text" indexed="true" stored=
>>> "false" multiValued="true"/>
>>>     <field name="derives_from" type="text" indexed="true" stored="false"
>>> multiValued="true"/>
>>>     <field name="has_derivation" type="text" indexed="true" stored=
>>> "false" multiValued="true"/>
>>>     <field name="links_to" type="text" indexed="true" stored="false"
>>> multiValued="true"/>
>>>     <field name="linked_from" type="text" indexed="true" stored="false"
>>> multiValued="true"/>
>>>
>>> Also how the Field Name maps to the ckan json fields.
>>> E.g.
>>>  <field name="author" type="textgen" indexed="true" stored="true" />
>>>     <field name="author_email" type="textgen" indexed="true" stored=
>>> "true" />
>>>
>>> In none of the json that we use the word "author" is mentioned.
>>>
>>>
>>> Can you provide documentation on this?
>>>
>>> thanks,
>>>
>>> Bert
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Bert Van Nuffelen
>>>
>>> Semantic Technologies Software Architect at TenForce
>>> www.tenforce.be
>>>
>>> Bert.Van.Nuffelen at tenforce.com
>>> Office: +32 (0)16 31 48 60
>>> Mobile:+32 479 06 24 26
>>> skype: bert.van.nuffelen
>>>
>>> _______________________________________________
>>> Ecodp-dev mailing list
>>> Ecodp-dev at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>>>
>>>
>>
>> _______________________________________________
>> Ecodp-dev mailing list
>> Ecodp-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>>
>>
>
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20131014/423994b1/attachment.html>