-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
codemetapy fails to merge triples for the same person #43
Comments
@apirogov: The current compose in codemetapy is a simple overwrite on the triple level and triples for which are not in the new graph are removed than there is an rdf merge. There is no entity resolution implemented in codemetapy, but this is also stated in the readme. I can image that one can do better. A simple rdf merge could already be better (in some cases), but would not be enough, since it only works for objects with identifiers in both graphs. |
Correct, it overwrites the entire triple. This behaviour is by design so you
Yes. If you want a merge, the only way to do so currently is to ensure the authors However, merging multiple instances of persons is more tricky than it might Another challenge is when having a graph of multiple SoftwareSourceCode |
Closing as 'invalid' since it's not a bug but by design. But of course the question and discussion itself (feel free to continue here) is very valid, and a better solution may be devised. |
File
in1.json
:File
in2.json
:Run
codemetapy in1.json in2.json
Expected result:
Person will have both email and orcid
Actual result:
Person has only email (when passed in this order) or only orcid (when passing
in2.json
beforein1.json
)The text was updated successfully, but these errors were encountered: