Skip to content

Conversion cockpit

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

Conversion cockpit is a metaphor that refers to the directories from which you should perform conversions.

What does a conversion cockpit look like?

If SSS, DDD, and VVV are the identifiers that you establish to name the source, dataset, and version of the data files collected and converted, then the following directory structure is the dataset's conversion cockpit:

source/SSS/DDD/version/VVV

What is in a conversion cockpit?

Conversion cockpit directories contain the following directories:

  • source/
  • manual/
  • automatic/
  • publish/

They also contain the conversion trigger script:

  • convert-*.sh

When should I be in a conversion cockpit?

(always)

A conversion cockpit directory should be your working directory every time you do work with the data.

When publishing, the bin/publish/*.sh scripts should be run from conversion cockpit directories.

Conversion cockpit directories are situated within the source/, dataset/, version/ hierarchy that corresponds to how datasets are named. For more information, see conversion process phase: name. Example conversion cockpit directories include:

/source/epa-gov/dataset/air-quality-system/version/2011-Jan-31/
/Users/timrdf/Desktop/source/epa-gov/dataset/air-quality-system/version/2011-Jan-31/

/source/census-gov/dataset/census-2011/version/2011-Jan-31/
/Users/timrdf/Desktop/source/census-gov/dataset/census-2011/version/2011-Jan-31/

The goofy /Users/timrdf/Desktop examples are used to demonstrate that the stuff before source/ does not matter. You get to put your [data root](csv2rdf4lod automation data root) where you want, and you can have multiples hanging around different places.

See also

See also

Clone this wiki locally