Data Conversion
This is the first functionality to be implemented within the service. This functionality let the user create Linked Data from his own raw data.
Unfortunately, we are not able yet to automatically generate Linked Data, therefore the service needs to be helped to convert the generic data to Linked Data. Below is an illustration of the process to convert data to linked data.
So a quick explanation of the reasoning of the above image.
Load data set - The application needs to be able to interact with the data
Classify columns - The application needs to know which columns contain URI's and which contain Literals
Link data - The application needs to know the relation between columns/classes
Download result - The user is able to download and/or publish his data set
Which comes down to that the sub-components gather information/instructions needed for the next step of the process.
When comparing this functionality with the original software, (Open Refine), with the Google refine extension the classification and linking are put within one interface. The choice to use divide the steps within the application is in order to be able to enforce that literals are not able to be a subject within an ontology.
Openrefine is developed for handling and transforming large amounts of data. The Google Refine extension supplies you with a way to create a RDF-skeleton. Within this view, you need to create links in a row based structure. A better way to represent the structure is to use a linked graph.
The data conversion component exists of one main component and four sub-components
- DataCreation
The DataCreation component is responsible for handling the data which needs to persist and converting the data to formats its sub-components use.
The Data Creation component exists of a tab view populated with the four steps the user takes. The user is not able to click on a tab to navigate between stages completion because if the data changes the application cannot guarantee that the next steps are valid. The tabs give the user an idea of how far along he is in the process.
| name | type | required | description |
|---|---|---|---|
| executeQuery | function | ✔️ | function which calls a query on the datastore The function needs to be called with the query and a callback function |