We were exploring a feature request that one of our users had for the Hub:
"Can we update ORCID whenever the user puts works into our works database without claiming that it's us who are asserting the work?"
The separation of assertion origin and source seems made for this, but we see that:
1/ This appears to be member origin, member source only?
We imagined that assertion-origin-orcid would potentially be a person's ORCID iD, but seems to be to allow legacy clients.
2/ That's irrelevant as the token delegation which was to drive it is deprecated?
What's the planned future for this feature?
Ngā mihi | Thanks