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

HDV Integrations: Editorial Manager #291

Open
sbarbosadataverse opened this issue Jul 18, 2024 · 1 comment
Open

HDV Integrations: Editorial Manager #291

sbarbosadataverse opened this issue Jul 18, 2024 · 1 comment
Assignees

Comments

@sbarbosadataverse
Copy link

sbarbosadataverse commented Jul 18, 2024

Objective:

Adopting an integration with Editorial Manager:

Additional information on editorial manager from our meeting:

They work with Dryad and Figshare. Helping journals to meet their targets and objectives.

Two paths to integration:

  1. Aries API embedded into submission workflow or

  2. Link out to repository for user to deposit data and complete the workflow

  3. Dataverse requires an account to deposit data. Does the embedding option support this?
    The embedded workflow does not have a firm authorization layer. The Editorial Manager does not guarantee that the data deposited are the most recent data available, etc. There is no control over who deposits data.

  4. Single sign-on is an "optional" feature for editorial manager sign-on via ORCID only, which is authenticated.
    They have clear examples of what we ran into with the OJS plugin, where authors push in articles and documentation but no data. This creates a lot of work on our end.

Possibility to use their interface to ensure Dataverse only shows up when "Datasets" are selected from the Item TYPE on editorial manager.

Other Issues/Workflow concerns

We need to update our OJS plugin and have also met with Editorial Manager on an integration. With OJS we saw more non-data deposits than data and this issue also exists as a potential with the Editorial Manager.

We need to discuss how to improve the workflow with these integrations. What sort of interventions can we employ to ensure deposits are data?

Editorial Manager has this step where authors must select what they are depositing. Can we set up any controls on this end? To ensure DV is only available when "Dataset" is selected?

Screen Shot 2024-07-18 at 12 36 20 PM

@sbarbosadataverse sbarbosadataverse changed the title HDV Integrations: Preventing non-data deposits with plugins like OJS and Editorial Manager HDV Integrations: Editorial Manager Jul 18, 2024
@cmbz
Copy link
Collaborator

cmbz commented Jul 24, 2024

2024/07/24

  • Sized at 33 for the investigation, resize or open another issue to implement the feature (if necessary)
  • Note, implementing this feature requires that Editorial Manager ensure that datasets only are pushed to Harvard Dataverse. See previous comment showing UI and options.
  • Related: OJS plugin: https://groups.google.com/u/1/g/dataverse-community/c/-NrEoqXPFx8/m/q26uaTpiAAAJ
  • Next steps:
    • Find out what is needed on Editorial Manager side for them to use our APIs to implement their plugin to support Dataverse.

@cmbz cmbz added the Size: 33 A percentage of a sprint. label Jul 24, 2024
@cmbz cmbz moved this to SPRINT READY in IQSS Dataverse Project Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: SPRINT READY
Development

No branches or pull requests

4 participants