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
Is your feature request related to a problem? Please describe.
Currently affiliation of people are a problem, since somesy does just allow for a name.
Describe the solution you'd like
If somesy would allow to specify an identifier for affiliation in the somesy.toml file, it could request the metadata from ror and add this. Therefore use the correct name of the affilation in the metadata files, as well as add richer information to codemeta.json. This ror lookup would there spare time.
The text was updated successfully, but these errors were encountered:
We do not have affiliation ids such as ROR in yet because Citation CFF has not introduced them yet, but they might be added. I would wait a bit on this one and see what CFF 1.3 will bring.
But using the ROR and Orcid APIs to pull and update authoritative metadata from upstream when an ID is available could be an interesting (optional) feature to avoid misspelled names of people and organizations.
apirogov
changed the title
To solve the affiliations, allow for ror id and fetch metadata.
Support retrieving/updating metadata from APIs such as OrcID and ROR if the corresponding ID is provided
Oct 31, 2023
Is your feature request related to a problem? Please describe.
Currently affiliation of people are a problem, since somesy does just allow for a name.
Describe the solution you'd like
If somesy would allow to specify an identifier for affiliation in the somesy.toml file, it could request the metadata from ror and add this. Therefore use the correct name of the affilation in the metadata files, as well as add richer information to codemeta.json. This ror lookup would there spare time.
The text was updated successfully, but these errors were encountered: