The goal of the FAIRifier is to FAIRify tabular data. This tooling focuses on the I and R of FAIR, and achieves this by turning tabular data into RDF data.

The tool is based on a few pipelines defined in python files (under airflow/dags), which are responsible for different parts of the transformation. These pipelines include one to upload data to a LibreClinica instance.

The script fairstation_setup.sh contains code to setup all services of FAIRifier (Airflow, Postgres, triplifer, GraphDB, term-mapper) as docker containers. Based on the server you are running, the methods will have to be commented out in the script.

Here are the recommended steps:

• Copy the script to your machine.
• Avoid running the script as root user as docker containers might start throwing issues with file permissions.
• Run the command chmod +x fairstation_setup.sh.
• Update the .env.example with the necessary variables and values.
• Some commands might require sudo access, if password is required, the prompt will ask you for the same.
• Once the script is successfully executed, check if all the docker containers are running as expected.
• Airflow can be accessed on port https://localhost:5000, GraphDb on http://localhost:7200, Term-Mapper on http://localhost:5001

Configuration is mostly done through environment variables, which are loaded into the Airflow workers. .env.example has a list of all the necessary configuration options. Note that all of these can also be defined in Airflow itself, under Variables.

The code for all the DAGs is available under airflow/dags.

You can upload CSV's to a postgres database by placing a .zip file in the input directory. This file will automatically be uploaded to the defined postgres database.

The CSV's will be uploaded to tables in the database equal to their name (minues the .csv extension). The database used is defined by the Airflow Variable R2RML_DB_URL, by default this is set to a database data in the built-in postgres container.

If data has been inserted in a table before, a new upload can either replace said data or append to it. This is handled by the APPEND_CSV Airflow Variable.

After uploading, the DAG will trigger the generate_triples_dag automatically to refresh triples stored.

This DAG does the following things:

• Clone the repository defined by R2RML_REPO
• Go into subdirectory of that repo defined by R2RML_REPO_SUBDIR, by default it stays at the root
• Grab all .ttl files from that directory and assume they are R2RML files
• For each of the R2RML files grabbed this way:
  • Using database defined by R2RML_RDB_CONNSTR, R2RML_RDB_PASSWORD, and R2RML_RDB_USER
  • Using ontop
  • Generate a .ttl file containing RDF data. The file has the same filename as the input R2RML file
  • Upload this .ttl file to the GraphDB instance defined by SPARQL_ENDPOINT (in a graph with the same name as the .ttl file)
• Finally download any ontologies defined in the airflow/generate_triples_dag.py file and upload them to a graph in the GraphDB instance

It then cleans up all the intermediary steps.