Backup of slack entries

[jcolomb]

this is a issue to back up interesting slack messages (via the github app) to be sure they are not lost.
When the discussion move to a different issue or is finished, please delete the message.

[jcolomb]

Some experiences from eLife when they tried to collect all metadata in the submission form:

> Authors have a strong preference for working in Word and keeping things simple. Filling out lots of forms on a submission system is onerous, so we were making the submission process harder for them. When an author resubmits and updates their Word file, they don’t necessarily update the submission screens as well, so if metadata changes it has to be updated separately. [...] We are now in the process of reviewing the submission screen requirements and reducing them, to reduce the amount of input required from authors.
https://www.ncbi.nlm.nih.gov/books/NBK350147/

This is in part an argument for allowing users to upload externally generated XML that is independent of each submission system. More so, it is an argument to store this information with the preprint and have journal editorial systems pull the information from the external source to avoid having to reenter it with every new submission.

As we are now seeing first efforts to enable direct preprint-to-journal submissions, we may want to discuss tenzing-integration with those preprint services, no?
_{View in Slack}

[jcolomb]

from alex email:
Thanks for the call, guys!  A few sundry thoughts.

When Balazs was mentioning how long it might take someone to enter 100 authors and their CRediT info by hand into a journal submission system, it occurred to me that it shouldn’t be hard to calculate that amount of time, and we should be trumpeting that more in our paper and other communications, as that as the obvious truly large waste of time that journals really need to do something about. 

I suspect that pulling affiliation information from ORCiD is coming soon to journal submission platforms - Aries System’s Editorial Manager already does it for the logged-in author I think if you choose to log in with your ORCiD authentication, although it doesn’t yet do it for one’s co-authors (which you are allowed to do without authentication, I think). So, one alternative to allowing JATS-XML upload that they could use is Richard Wynne’s Rescognito. One may have authored a preprint associated with the manuscript on a preprint server, for example, and then enter that DOI into the journal submission system. Using Rescognito, one might have entered CRediT info for the preprint into ORCiD  https://www.youtube.com/watch?v=C4uMFz5wRZc&feature=youtu.be
Then the journal management system could fetch all that ORCiD info. And Rescognito’s user interface is perhaps better than the JMS’ interface or entering CRediT info, or is at least more agile to be improved, so we should probably talk to him about interfacing with Tenzing. For example, if he simply had a JATS-XML upload button to upload Tenzing output, authors would then never have to manually enter CRediT info into the JMS, once that JMS supports fetching CRediT from ORCiD if you give it a DOI. Am I right?

_{View in Slack}