Skip to content

Conversion process phase: tweak enhancement parameters

Timothy Lebo edited this page Feb 14, 2012 · 24 revisions
csv2rdf4lod-automation is licensed under the [Apache License, Version 2.0](https://github.com/timrdf/csv2rdf4lod-automation/wiki/License)

[up](Conversion process phases)

What's first?

How to tweak enhancement parameters.

When you pulled the conversion trigger the first time, the automation created the initial verbatim interpretations as RDF Turtle files in automatic/. It also saw that you didn't have any enhancement parameters available for each file you converted, so it created a template for you in manual/. Once these enhancement parameters are there, the automation will not modify them again -- the ball is in your court.

First, make sure you are in a conversion cockpit (using the example from A quick and easy conversion):

bash-3.2$ cd ~/Desktop/source/scraperwiki-com/uk-offshore-oil-wells/version/2011-Jan-24

Then change the enhancement parameters:

bash-3.2$ vi manual/uk-offshore-oil-wells.csv.e1.params.ttl 

change conversion:enhance [ ov:csvCol 7; ov:csvHeader "lng"; conversion:label "lng"; conversion:comment ""; conversion:range todo:Literal; ]; to: conversion:enhance [ ov:csvCol 7; ov:csvHeader "lng"; conversion:label "lng"; conversion:comment ""; conversion:equivalent_property wgs:long; conversion:range xsd:decimal; ];

Then pull the same conversion trigger:

bash-3.2$ ./convert-uk-offshore-oil-wells.sh

The conversion triggers sees 1) the initial conversions exist and 2) the enhancement parameters exist and 3) the enhancement parameters are different from the original template that it created for you earlier. So, it uses the enhancement parameters in manual/ to create a new conversion in automatic/.

Keep enhancing

conversion:Enhancement shows the changes that you can specify.

f2da7777 shows a good first step for enhancing the oil wells example. You can diff it with the initial template to see the changes.

What's next?

Clone this wiki locally