We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I noticed an issue with mapping CSVs, where if different CSV files use the same column name as primary key, then the foreign key resolution fails.
To reproduce, simply rename the CODE column in the artist example to ID, in both the CSV and artist-map.ttl.
The output becomes:
ns1:rna29 a ns1:Person ; ns1:birth_date "1929-12-06" ; ns1:birth_place ns1:rna29 ; ns1:fullName "Ronald Anderson" . ns1:rtm19 a ns1:Person ; ns1:birth_date "1919-12-23" ; ns1:birth_place ns1:rtm19 ; ns1:fullName "Robert Theodore McCall" .
As you can see, the birth_place objects are incorrect, as they refer to the artists themselves, instead of the places.
birth_place
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I noticed an issue with mapping CSVs, where if different CSV files use the same column name as primary key, then the foreign key resolution fails.
To reproduce, simply rename the CODE column in the artist example to ID, in both the CSV and artist-map.ttl.
The output becomes:
As you can see, the
birth_place
objects are incorrect, as they refer to the artists themselves, instead of the places.The text was updated successfully, but these errors were encountered: