Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update ORCID integration with contributor details #7922

Closed
withanage opened this issue May 11, 2022 · 8 comments
Closed

Update ORCID integration with contributor details #7922

withanage opened this issue May 11, 2022 · 8 comments
Assignees
Labels
Bug:2:Moderate A bug that is causing problems for a substantial minority of users. Community:2:Priority Any issue that has been identified through research or feedback as a major community priority.
Milestone

Comments

@withanage
Copy link
Member

withanage commented May 11, 2022

Describe the problem you would like to solve
The orcidProfile plugin integrates with the author form by modifying the orcid field, and adding checkboxes to send authorization requests. This will no longer work with the new forms in OJS/OPS 3.4.

Describe the solution you'd like

  • The field "Orcid ID" in publication->contributors should be read-only when the orcidProfile plugin is activated.
  • A mechanism to send emails to request authors enter and authenticate their orcids should be included where editors and submitting authors enter the contributor details.

Who is asking for this feature?
This preserves a plugin's feature since OJS 3.1, so it should be maintained.

Additional information

  • Until OJS 3.3., this functionality was achieved through the registerFilter function in the TemplateManager, which no longer works in the main branch.
  • @NateWr suggested adding a slot to the contributor panel as a temporary measure to integrate email functionality for the orcidProfile plugin. We plan to bring orcid support into core, but not in time for 3.4.
@NateWr NateWr changed the title Event-triggering button/functionality for the Contributors Panel Update ORCID integration with contributor details May 12, 2022
@NateWr NateWr added Community:2:Priority Any issue that has been identified through research or feedback as a major community priority. Bug:2:Moderate A bug that is causing problems for a substantial minority of users. labels May 12, 2022
@NateWr NateWr added this to the 3.4 milestone May 12, 2022
@NateWr NateWr moved this to Backlog in Editorial Workflow May 12, 2022
@NateWr NateWr moved this to Backlog in Plugins and Themes May 12, 2022
@NateWr NateWr moved this from Backlog to Todo in Plugins and Themes May 12, 2022
@bozana
Copy link
Collaborator

bozana commented Feb 12, 2023

@withanage, what is the status of this issue? Would you be able to do it?

@withanage
Copy link
Member Author

@bozana I am on it as a sub-task of the update to 3.4. Currently it is disabled for editing, but without modifying it with a Vuejs component, the "override" button is there, allowing the button to still be edited.

Therefore, it does not yet exactly implement according to the specification in the ticket description.

Screenshot from 2023-02-12 16-20-42

I will check tomorrow with Nate , if he has an idea there. Otherwise, I think will not be able to finish this ticket before 15th.

@withanage
Copy link
Member Author

@bozana

The field "Orcid ID" in publication->contributors should be read-only when the orcidProfile plugin is activated.

I have updated the orcid consortium parters about the current implementation and this can be marked as done.

A mechanism to send emails to request authors enter and authenticate their orcids should be included where editors and submitting authors enter the contributor details.

This I think would not get before 3.4 release.

@asmecher
Copy link
Member

@withanage, is this issue ready to be deferred from 3.4.0?

@withanage
Copy link
Member Author

@asmecher yes, we need a form component that specifically shows contributors correctly, like in 3.3, I would postpone it until we implement this feature in forms.
As I understood correctly from @NateWr's Mattermost discussion.

  • The HTML form content cannot does not have the value.
  • We can activate another form component if the value matches a truthful value, but not check if another component doesn't have the truthful value.

So I would defer it and not close it, because ORCID will not be satisfied until we show the ORCID symbol there as in the following image for co-authors.

Screenshot from 2023-02-28 21-31-18

@asmecher asmecher modified the milestones: 3.4.0-0, 3.4.0-x Feb 28, 2023
@asmecher
Copy link
Member

OK, I've moved it to 3.4.0-x.

@bozana
Copy link
Collaborator

bozana commented Jun 24, 2024

@ewhanson, can this issue be closed?

@ewhanson
Copy link
Collaborator

Yes, completed as part of #9771.

@github-project-automation github-project-automation bot moved this from Todo to Done in Plugins and Themes Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug:2:Moderate A bug that is causing problems for a substantial minority of users. Community:2:Priority Any issue that has been identified through research or feedback as a major community priority.
Projects
Development

No branches or pull requests

6 participants