You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fact that the Orcid / URL field vanishes for other contributors I reported in #45
but the other independent problem is that apparently something in the merge goes wrong - the url is expanded into another person object, leading to this weird and incorrect nested Person entry.
Expected: The url is not expanded into a nested Person. Either map it to @id, or keep it as url (because url could also be a homepage, and that is a bad @id if you merge from different sources could cause problems assuming that url is a good Person @id, unless its an ORCID), I don't know, but it should remain a string.
The text was updated successfully, but these errors were encountered:
Ouch, this is indeed problematic. Codemetapy is a bit eager to turn strings
into resource references if there is such @id in the graph. It's a bit hacky
but it removes a certain class of errors. This however is a clear case where it
goes wrong. I'll probably exempt the url property (and some more like it)
from this behaviour so that it will solve at least this case.
Inputs:
package.json
:extra_codemeta.json
:Output (
codemetapy package.json extra_codemeta.json
):The fact that the Orcid / URL field vanishes for other contributors I reported in #45
but the other independent problem is that apparently something in the merge goes wrong - the
url
is expanded into another person object, leading to this weird and incorrect nested Person entry.Expected: The
url
is not expanded into a nested Person. Either map it to@id
, or keep it asurl
(because url could also be a homepage, and that is a bad@id
if you merge from different sources could cause problems assuming thaturl
is a good Person@id
, unless its an ORCID), I don't know, but it should remain a string.The text was updated successfully, but these errors were encountered: