HDV Integrations: Editorial Manager #291
Labels
Curation for Harvard Collection
enhancement
New feature or request
Feature: External Tool
Size: 33
A percentage of a sprint.
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:
Aries API embedded into submission workflow or
Link out to repository for user to deposit data and complete the workflow
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.
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?
The text was updated successfully, but these errors were encountered: