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
Thinking out lout about removing items from the profile here...
Would it make sense to have items automatically be deleted (e.g. here)? Any cases, where this could cause trouble?
At least a "Remove from ORCID.org profile" button would be nice to have on the export screen, so that users and admins could delete items from the profile, e.g. if they have serious errors like a wrong identifier, that would prevent other items from beeing exported. EDIT: We have some code for this already, but I guess it would make more sense to implement this in the course of #20.
The text was updated successfully, but these errors were encountered:
dennmuel
added a commit
to dennmuel/orcid_support_advance
that referenced
this issue
Jul 31, 2019
I was just about to add this issue when I see it has already been here for a few weeks! I agree we need something like this, and an extension of the existing export screen sounds like a sensible place to put it (as we'd only be able to delete records we've previously exported anyway.
And as you say we should see if we can automatically delete records from orcid.org when we retire or delete records in EPrints. I think we may be able to do this with the EP_TRIGGER_STATUS_CHANGE and EP_TRIGGER_REMOVED triggers.
Thinking out lout about removing items from the profile here...
Would it make sense to have items automatically be deleted (e.g. here)? Any cases, where this could cause trouble?
At least a "Remove from ORCID.org profile" button would be nice to have on the export screen, so that users and admins could delete items from the profile, e.g. if they have serious errors like a wrong identifier, that would prevent other items from beeing exported. EDIT: We have some code for this already, but I guess it would make more sense to implement this in the course of #20.
The text was updated successfully, but these errors were encountered: