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.
As an repository manager i might not want the user to set their orcid sync settings for projects, patents or products, because my repository does not have that entity configured or does have too poor data the fulfill the minimal requirements for this entity in future (e.g. funding identifier missing)
Is your feature request related to a problem? Please describe.
As an repository manager i might not want the user to set their orcid sync settings for projects, patents or products, because my repository does not have that entity configured or does have too poor data the fulfill the minimal requirements for this entity in future (e.g. funding identifier missing)
Describe the solution you'd like
We would like the synchronization settings on the frontend to be shown based on some Authorization Feature checking if the synchronization is currently enabled for the specific entity type, similar to the https://github.com/4Science/DSpace/blob/main-cris/dspace-server-webapp/src/main/java/org/dspace/app/rest/authorization/impl/CanSynchronizeWithORCID.java Feature.
We also would like some addtional check in the
OrcidHistoryServiceImpl.synchronizeWithOrcid
https://github.com/4Science/DSpace/blob/f768bbe0f1017a198262e7bc3aaa86aa332ba1d2/dspace-api/src/main/java/org/dspace/orcid/service/impl/OrcidHistoryServiceImpl.java#L178 checking if the synchronization is currently enabled for the Type of the OrcidQueue which is being pushed.Describe alternatives or workarounds you've considered
Current workaround is to comment out the corresponding entity on the orcid sync component the
dspace-angular/src/app/item-page/orcid-page/orcid-sync-settings/orcid-sync-settings.component.html
Line 74 in e270018
Additional context
The text was updated successfully, but these errors were encountered: