Open Journal Systems, DOIs, and DataCite

Open Journal Systems, DOIs, andDataCite A Webinar from the Public Knowledge Project (PKP) and DataCite. Mike Nason Open Scholarship & Publishing Librarian @ UNB Libraries Open Scholarly Infrastructure Advisor @ Public Knowledge Project (PKP) 1 A Brief Intro to PKP 2 About PKP PKP is a software development and research facility at Simon Fraser University. We conduct researchinto issues impacting scholarly communication. We develop free and open source software(FOSS) towards a more diverse, inclusive, and accessible model for scholarly publishing. 3 Our Mission Since 1998, PKP's mission has been to research, develop, and support open infrastructureto increase the quality, diversity, and reach of scholarly publishing. 4 Our Software The Public Knowledge Project develops open source software which is used around the world for scholar-led, community driven publishing of journals, preprints, and monographs. 5 Global use of OJS 55,000+ active journals world-wide publishing across 150 countries journals publishing in 60 languages 6 PKP is best known for the development of OJS – the world's most widely used journal management and publishing system. 7 OJS for Authors A system for authors to submit to a scholarly journal, track their submission through the editorial process, upload revisions, and publish, often open access. 8 OJS for Editors A system for editors to manage submissions at different stages, track manuscript versions, and manage comms between authors, editors, and reviewers. 9 Open Journal Systems Out of the box, Open Journal Systems is hugely supportive of open scholarly infrastructure. In fact, OJS is an example of open scholarly infrastructure. Things will vary a bit depending on the version of OJS you're running. If you're leveraging PIDs and other connections to open infrastructure, it's likely best to stay updated to, at least, the latest Long Term Support (LTS) version. 16 Versions // General OJS 3.3.X // (LTS) MOST RECENT LTS VERSION  LARGE INSTALL BASE  BIG SELECTION OF 3RD PARTY PLUGINS  DOI DEPOSIT BY PLUGIN  WILL BE FLAGGED FOR EOL WITHIN A YEAR AFTER OJS 3.5 GETS LTS DISIGNATION OJS 3.5 MOST RECENT RELEASE  WILL BE THE NEXT LTS  SIGNIFICANT IMPROVEMENT TO PUBLISHING WORKFLOW  SIGNIFICANT UI IMPROVEMENTS  OJS 3.4.X BROUGHT A NUMBER OF CHANGES TO STATISTICS, USER MANAGEMENT, AND SUBMISSION WORKFLOWS  MORE ITERATIVE FEATURES  DOI MANAGEMENT/DEPOSIT WORKFLOWS OVERHAULED  OJS 3.4.X BROUGHT A NUMBER OF CHANGES TO STATISTICS, USER MANAGEMENT, AND SUBMISSION WORKFLOWS  MORE ITERATIVE FEATURES  DOI MANAGEMENT/DEPOSIT WORKFLOWS OVERHAULED  17 Versions // Pid-ciderations OJS 3.3.X // (LTS) DOI MANAGEMENT TIED TO REGISTRATION AGENCY PLUGINS  ROR SUPPORT  ORCID SUPPORT OJS 3.5 LEVERAGES NEW DOI MANAGEMENT FROM 3.4  IMPROVED ROR INTEGRATION  IMPROVED ORCID INTEGRATION  UPDATES TO PID METADATA SCHEMAS FOR BETTER METADATA FIDELITY OJS 3.4.X DOI MANAGEMENT MOVED TO CORE CODE AND OVERHAULED  NO ROR SUPPORT  ORCID SUPPORT 18 What version should I use? At an absolute minimum, I'd recommend running the latest version of OJS 3.3.Xto make sure you've got all the latest patches and security updates. Staying up to date on the LTS version is good practice and will help ensure a stable, secure platform for your journal. 19 That depends! Your experience with the software will be different depending on the version you have installed. Often, the tradeoff for newer versions of a platform is that you get the best, newest features but also need to apply more frequent updates to keep things secure and bug-free.  Does it matter? What version should I use? 20 However, if you're currently on a version of OJS 3.2 or older , it matters a great deal. You should denitely – at least – upgrade to the latest version of OJS 3.3.X.  OJS 3.2 is no longer supported and you'll be missing out on security updates and bug xes.  Does it matter? What version should I use? 21 If you're on 3.3.X and are happy with how things are, you can safely wait until OJS 3.5 gets it's long term support (LTS) designation before upgrading.  If you're on 3.4.x and are happy, you can also wait!  Once 3.5 gets LTS, you'll have ~ a year to upgrade from 3.3.X. Does it matter? What version should I use? Do I need to upgrade? 22 Intro to DataCite... 23 Let's talk DOIs 24 Open Journal Systems I'll also note that everything we'll be going over in this section can be found in more detail in the PKP docs hub or in the readme.txt les for any individual plugin in the plugin gallery. (DataCite works basically the same way, but a new DataCite-specic guide is also currently in development) DOI Plugin Crossref Manual ORCiD Plugin Guide ROR Plugin Guide ORCiD Prole Plugin QuickSubmit Plugin and DOIs 25 Assigning DOIs 32 Assigning DOIs 33 A Gentle Reminder Assigning DOIsand Registering DOIswith a Registration Agency are two different things. People often combine these two steps together and call it "minting".  If you only assign a DOI but don't register it with a DOI registration agency, it will not work.  This is more common than you might imagine. 34 In OJS 3.3.x Assigning DOIs 35 DOIs in OJS 3.3.x (LTS) No matter which DOI registration agency you have a membership with,the process of assigning DOIs is the same.  In 3.3.x, you will need to start by conguring your DOI plugin. You can nd the DOI plugin and it's settings under Installed Pluginsand the subheading "Public Identier Plugins". 36 DOIs in OJS 3.3.x (LTS) There's a space to put your prex here. You'll be given a prex by your registration agency or by your parent organization/publisher.  You can also choose which things to assign DOIs to. You might be tempted to click all of them. I recommend just assigning DOIs to Articles . 37 DOIs in OJS 3.3.x (LTS) Next, are the suxes. I more or less beg you to not think of these as meaning anything to readers or users. A DOI sux shouldn't contain metadata. They ought to be opaque.   I recommend either using the default patterns here and just ignoring what they say, or creating a custom pattern with the bottom option that is even more simple than the default. 38 DOIs in OJS 3.3.x (LTS) You cannot correct or change a DOI after it has been registered.If you register a DOI with a typo in it,that isn't a solvable problem.  You can edit registered metadata. You cannot edit the DOI itself.  Take typos right out of the equation!  %j.%ais a great custom option. 39 DOIs in OJS 3.3.x (LTS) These are the nal two options. They should be treated with caution.  Reassign DOIswill unassign all DOIs for your journal and reassign DOIs based on whatever your prex settings are. If you've registered anything , do not click this.  Assign DOIswill assign a DOI to anything in your journal that does not already have one .40 DOIs in OJS 3.3.x (LTS) Lastly, you can make sure a DOI will be assigned at the article level. In the Publicationtab for any submission, you can click on "Identiers" in the sidebar and see DOI information.  You'll see an "assign" button to automatically generate a DOI based on your prex settings. You can modify a DOI here until it is published. 41 DOIs in OJS 3.4.X - 3.5.X In OJS 3.4 and up, DOI management has been overhauled.  You can now nd your DOI plugin settings in the left sidebar under the option Distribution.  You can set your prexes, sux patterns (now with opaque string generation), as well as choose your registration agency from a dropdown menu. 48 In OJS 3.3.x Registering DOIs 49 In 3.3.x, you can nd the registration options in the left sidebar of the dashboard, at the bottom, by clicking on the Toolslink.  From here, choose either the Crossref or DataCite Export/Registration plugins.  They both operate very similarly! DOIs in OJS 3.3.X (LTS) 50 Each plugin starts with a settings page with a few options and your credentials for your membership. These credentials will always be your login credentials for DataCite or Crossref, not for this OJS install. DOIs in OJS3.3.X (LTS) 51 Each plugin has the same registration menu under the tab labelled "Articles". It shows you the article ID, author/title, issue, DOI to be registered, and a status.  "Active" means a DOI has been registered and is resolving.  If your plugin is set to automatic, you can basically ignore this. It will register for you within a few hours. DOIs in OJS 3.3.X (LTS) 52 In OJS 3.4.x - 3.5.x Registering DOIs 53 In OJS 3.4, all DOI management and registration can be accessed from the DOIsmenu on the sidebar, in the top left.   DOIs in OJS 3.4.x 54 In OJS 3.5, all DOI management and registration can be accessed from the DOIsmenu on the sidebar, below "Issues" and before "Settings" menus.   DOIs in OJS 3.5.x 55 This DOI manager has signicantly more features, including ags for DOIs that need updating (when their metadata has changed). You can also assign DOIs per article here if you wish, without having to navigate to an individual publication.  You can also cue up bulk updates or bulk registrations. DOIs in OJS 3.4.X - 3.5.X 56 You can see that the plugin assigns labels like "needs doi" for works that have yet to be assigned one.  You can also see the operations available as bulk actions. DOIs in OJS 3.4.X - 3.5.X 57 ROR in OJS 3.5.X You can nd the ROR plugin in the gallery with the name: Research Organization Registry (ROR) Plugin.  This plugin will allow for autocomplete against the ROR API within the "aliation" metadata element for submissions.  It will also display ROR links on article landing pages. . Navigate to the plugin gallery and install the ROR plugin. . Navigate to your installed plugins and enable the ROR plugin.  End of list! ROR is also in the process of being integrated into the Funding Metadata plugin. 64 ORCID 65 ORCiD has two different APIs. 66 Public API ORCiD's public API allows any journal to pull public metadata from ORCiD. In OJS, the public API option fascilitates: Authors can connect their ORCiD ID with their publications. ORCiDs recorded as metadata will be deposited in DOI registrations with Crossref and Datacite. Author ORCiDs will be linked on article landing pages. ORCiD's member API allows journals to push metadata to ORCiD . The member API allows for all of the capability of the public, and also: Peer-review activity can be pushed to author's ORCiD prole. Article records can be pushed directly to ORCiD proles. Member API 67 It is totally ne to use the public API, and you'll still get a signicant interaction with ORCiD this way.  The most important piece for authors here is the link to their prole. If you're using DOIs and proles are congured for automatic addition, works will still be added to their ORCiD automatically. The member API's strongest asset is the ability to push peer review work to ORCiD.  Memberships to ORCiD tend to be institutional and aren't cheap. If you aren't concerned about automatic population of peer-review work to ORCiD, the public API will meet your needs plenty. 68 In the Interest of Brevity I recommend you read the ORCiD plugin documentation.  The plugin is pretty straightforward to set up if you are a single journal .  However, if you are installing on a shared, multi-journal instance of OJS you will need access to your cong le. You may require technical assistance for this, depending on your comfort level.  You'll need an ORCiD account and will need to procure at least a public API key (this is free). Of the three PID integrations, this one has the most steps.  It is, however, very much worth the time to support your authors! https://docs.pkp.sfu.ca/orcid/ 69 Bonus Round I nishedthis deck and started thinking about, like... you know all of this documentation exists, and now you have these slides, and maybe I don't need to go clean through it all step-by-step. Or, maybe I've just gone through it all step-by-step and would like to leave you with something to think about on your own steam. 70 Forgive me... ...for being presumptive, but there is a general expectation that you want people to see the products of your hard work. You want your work to be known and discoverable ; accessible to the folks who might benet from it.  I would think (hope).  And, you'd probably like it to be attributed to you, since you did the work and also since the implications of its value will have some impact on your career or the career of your authors. 71 It's possible... this may seem weird because, depending on where you are in your career, you are maybe not used to doing this . After all, most of the experience of dissemination as a student (for example) is submitting papers to one person who grades them.  It is certainly neif this is the case. It's very normal. Fun fact, plenty of established researchers don't really think too hard about where and how their work is shared, either. 72 For students, this is what "disseminating your research" mostly looks like. 73 journal am ir datacite vor peer-review self-archiving Every   is, potentially, a new DOI. 80 The Reality Publishing is more iterative (and tied to a wider range of accessible outputs) than it's ever been. submission still happens, but users might post their work on a preprint server before peer review a funder mandate might require open access or, at least, an open access version of the work if you're publishing in a major subscription journal, lots of people cannot read your work data management might require publication of a data set 81 arxiv ir datacitewebpage journal 82 ir crossref ir handle am ir pubmedir datacite zenodo dataset vor shareyourpaper openaire zenodo dataverse Every   is, potentially, a new DOI. THESE ARE ALL PLACES YOUR METADATA CAN/WILL GO! 83 If you jam, "Editors, The" into the name eld for something that doesn't have an actual author, guess where that will end up? 84 If you manage a journal, you are standing at the nozzle of a metadata rehose. 85 This is important stuff for both a journal and for authors. 86 Authors will know what they worked on, for example, but people (researchers, funders, institutions, employers) looking for their work might not. 87 Maybe they share a name with another researcher and their results are always co-mingled. Or their eld only uses rst name initials in metadata.  88 Or, maybe they changed their name for any number of incredibly valid reasons and it's painful or unpleasant that all their old publications require others to know it.  89 This has been, frankly, an astounding amount of content. I'd like to congratulate you for enduring it. 96 It's ok! I am comfortable with myself, please refer to this deck whenever you need to!  Please also read our documentation! 97 Thank You. 98