meca: manuscript exchange · meca: manuscript exchange common approach sally ubnoske, senior...

16

Upload: others

Post on 04-Jul-2020

8 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com
Page 2: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

MECA: Manuscript ExchangeCommon Approach

Sally Ubnoske, Senior Business Systems Analyst, [email protected]

Page 3: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

What’s the Problem?• Authorsareirritatedattime,effort,delayswhenre-submitting

articles• Reviewers’timeiswastedwhenreviewsarere-doneorreplicated• Newpublicationflowsdemandtransfersto/frompreprintservers• Eachworkflowsystemhastoimplementseparateinterfacesto

eachothersystem– inefficienttowork‘pairwise’

Opportunity• Acommonapproachtomovingmanuscriptssolvestheaboveuse

casesandcanalsosolvesomeadditionalworkflowproblems!• Allweneedisforagroupofcompetitorstocollaborate!

Page 4: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Metadata

Files

Destination

• Agroupofvendorsandpublisherso Aries:EditorialManagero Clarivate:ScholarOneo eJournalPress:eJPresso HighWire:BenchPresso PLOS:Aperta

• Developacommonapproacho Notsoftware,notacentralservice,notadatabaseo Recommendedbestpracticeso Non-proprietary,CC-BY

• Hopeforwideadoptiono Outreach,NISO,JATS4R,JATScon

Page 5: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Use Cases – Manuscript Transfers Across Boundaries

Journal• SubmissionSystemtoSubmissionSystem(primary)Preprint• PreprintSystemto/fromSubmissionSystem(primary)Syndication:Importfrom…• AuthoringSystemstoSubmissionSystem (primary)Syndication:Exportto…• SubmissionSystemtoVariousServices (secondary)

Page 6: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas

ü Vocabularyü Packagingü Taggingü PeerReviewü TransferInformationü Identityü Transmission

Page 7: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas – Vocabulary

• Goal:Toprovideastandardnomenclature• Providesabaselineforunderstanding• Includes4UseCases• IncludesTerm,Definition,Synonym,‘Often-confused-with’

alternatives,andExamples• Includes70+Terms

o Publishingtermslike‘Author’,‘Review’,‘DownstreamProcessing’o Technicaltermslike‘BITS’,‘Interoperability’,‘MimeType’

• Canbeupdatedovertime

Page 8: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas - Packaging• Goal:simple,flexible,standardwaytoassemblefiles• ZipFile• Teamwillregisteranew‘mimetype’andfileextensionforthepackage• Onemanuscriptperzipfile• Packagecontains:

o Manifest.xml*(newDTDforfilemanifest)o Transfer.xml*(newDTDforsource/destination,contact,and

securityinformation)o Article.xml(JATS-compliant)o PeerReview.xml(optional- JATS-like)o Sourcefiles

* Required Item

Page 9: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas - Tagging• Goal:Tobeabletopasssubmissioninformationfromsystemtosystem• Article.xml (fileinJATSformat– GreenDTDcompliant)• Definesminimalrequireddata*• OnlythehighestrevisionofthesubmissioniswrittentotheXML

o ArticleIdentifiers(ManuscriptNumber,UUID,DOI)o ArticleTitle*o ArticleType,Category,Classifications,Keywordso CorrespondingAuthor*andCo-Authors(withaffiliations)o Relatedarticles,Preprintso FundingInformation,CustomMetadatao Figures,tables,supplementarymaterial

Page 10: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas – Peer Review Data• Goal:Tobeabletopassreviewinformationfromsystemtosystem

o Questions/Answerso Ratingso Commentso Annotationso Redlines/Markedupfiles

• Privacyo Reviewernames/contactinformationcanberedactedo Basedonsendingjournal’sprivacypolicy

• Reviews.xml (fileissimilartoJATS)o Decidedinformationdoesnotbelonginarticle.xmlo Multiplereviews&revisionsinonefileo DTDhas~16tags/elements

Page 11: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas – Transfer Information• Goal:Tobeabletopasstransferinformationfromsystemtosystemo SourceInformation

§ ServiceProvider§ ContactInformation§ PublicationType,Title,Acronym

o DestinationInformation§ ServiceProvider§ ContactInformation§ PublicationType,Title,Acronym

o SecurityInformation§ AuthenticationCode

o ProcessingInstructions

• Transfer.xml (newDTD)

Page 12: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas - Identity• Goal:Unique,consistentidentity acrosssystems• Uniqueidentifier

o Whenmanuscriptsarepassedfromsystemtosystemo Articlenumber,butnotjournalspecific

• DOIwasconsideredo NeedforsomethingwithoutaDOI‘prefix’orimpliedsource

• Universallyuniqueidentifier- UUIDo Type1

§ Date,time,MACAddress,randomnumber§ d6bf8782-30f7-4cd7-82a8-94ff62352ac4§ Guaranteesnocollisionsacrossvendors§ Supportfoundinmanystandardcodinglibraries

Page 13: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Project Areas - Transmission

• Goal:Simple,consistentwaytosendtheinformation acrosssystems

• FTPuntilJanuary2018/SFTP(FTPoverSSH)in2018

o Phase1

o Asynchronous

• Potentialfuturedevelopment– movetoAPI(REST,SWORD)

o Providestatusmessagetosender

o Synchronous

o Influencedbyspecificusecases

Page 14: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Action Items & Timeline

2017

2018 • ExpandtheWorkingGroupo Lookingtoincludediversesetofstakeholderso Interested?Lookatmanuscriptexchange.orgoremailinfo@manuscriptexchange.org

• NISOapplication,ifappropriateo Willneedcommunityvolunteerstoparticipateinthatprocess

• VendorandSupplierImplementations

• Presenttoorganizationsandcommunitiesofinteresto JATS-Con,CASRAI,SSP,OASPA,Force11,STM,ISMTE,CSE,ALPSP…o Authoringplatforms,compositionvendors,repositories,preprintservers…

• Gatherinputfromtheseinterestedpartieso Inputviamanuscriptexchange.org

• HostInformationalWebinarso GeneralandTechnicalsessionsplannedforJuly/August

• Buildtrial/pilot/referenceimplementationo Refineapproachanddocumentation

Page 15: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com

Interested in Participating?

• Additional Information on our web page:

www.manuscriptexchange.org

• Contact us – comment on documents/plans, volunteer:

[email protected]

Page 16: MECA: Manuscript Exchange · MECA: Manuscript Exchange Common Approach Sally Ubnoske, Senior Business Systems Analyst, subnoske@ariessys.com