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

Add indicator of sponsored/not sponsored payment status on first page of submission #2293

Open
bryanmgee opened this issue Feb 14, 2023 · 0 comments · May be fixed by datadryad/dryad-app#1891

Comments

@bryanmgee
Copy link

Priority: medium
Affected: authors, Helpdesk

General issue: Because the payment statement is so far removed from the journal metadata field, authors often don't make the connection that they have to correctly input metadata for sponsored journals to avoid being billed. It's also evident from a variety of emails that authors are also just skimming the last page, if even that, and some completely miss the payment statement when they there is no sponsorship from journal or institution. This can lead to issues where they say "well I can't pay, so withdraw my dataset," but we don't do that in the normal workflow, so we basically have to give them a one-time waiver and just admonish them lightly.

General solution (requires brainstorming/discussion): We (me and Jess) are wondering if there is some way to add a short statement or visual indicator (e.g., green check mark to the right of the field) for when a sponsored journal is matched and the cost is covered. That would probably warrant a counterpart indicator when a journal is matched to a non-sponsored journal or isn't matched at all to indicate the author is going to be billed for publishing with us (something less dramatic than a red X or exclamation point). We're open to suggestions on what seems most technically feasible and user-friendly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants