Importing and Exporting Data in OJS 2

<!DOCTYPE html> <html lang="en-US"> <title>Importing and Exporting Data in OJS 2</title> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta property="og:title" content="Importing and Exporting Data in OJS 2" /> <meta property="og:site_name" content="PKP Docs"> <meta property="og:url" content="https://docs.pkp.sfu.ca/importing-exporting/en/"> <link type="text/css" href="/css/book.css" rel="stylesheet" media="all"> <script defer src="/assets/js/smooth-scroll.polyfills.min.js"></script> <script defer src="/assets/js/fontawesome.min.js"></script> <body class="body--withSidebar"> <div class="bookHeader"> <button id="sidebarControl" class="bookHeader__sidebarControl"> <span class="fa fa-bars" aria-hidden="true"></span> <span class="fa fa-times" aria-hidden="true"></span> <span class="-screenReader">Toggle Menu</span> </button> <a class="bookHeader__logo" href="/"> <img src="/img/logo-on-white.png" alt="PKP Docs" class="bookHeader__logoImage"> </a> <div class="bookHeaderTools"> </div> </div> <div class="book"> <a href="#sidebar" class="-screenReader"> Jump to table of contents </a> <div class="book__page"> <div class="book__content"> <div class="book__improve"> <a href="https://github.com/pkp/pkp-docs/edit/main/importing-exporting/en/index.md"> Edit this page </a> or <a href="https://pkp.sfu.ca/documentation-feedback/"> make a suggestion </a> </div> <h1 id="importing-and-exporting-data-in-ojs-2"> Importing and Exporting Data in OJS 2 </h1> <div class="book_page_toc"> <h2>Table of Contents</h2> <ul> <li><a href="#introduction">Introduction</a></li> <li><a href="#using-the-quick-submit-plugin">Using the Quick Submit Plugin</a></li> <li><a href="#using-the-web-based-expedited-submission-process-to-add-articles-quickly">Using the Web-based Expedited Submission Process to Add Articles Quickly</a></li> <li><a href="#articles-and-issues-xml-plugin">Articles and Issues XML Plugin</a> <ul> <li><a href="#importing-articles-and-issues">Importing Articles and Issues</a></li> <li><a href="#creating-the-xml-import-file">Creating the XML Import File</a></li> <li><a href="#importing-articles-and-issues-from-the-web">Importing Articles and Issues From the Web</a></li> <li><a href="#exporting-articles-and-issues-from-the-web">Exporting Articles and Issues From the Web</a></li> </ul> </li> <li><a href="#users-xml-plugin">Users XML Plugin</a> <ul> <li><a href="#importing-users">Importing Users</a></li> <li><a href="#creating-the-import-users-xml-file">Creating the Import Users XML File</a></li> <li><a href="#exporting-users-from-the-web">Exporting Users From the Web</a></li> </ul> </li> <li><a href="#crossref-xml-export-plugin">Crossref XML Export Plugin</a></li> <li><a href="#erudit-article-export-plugin">Erudit Article Export Plugin</a> <ul> <li><a href="#exporting-erudit-information-from-the-web">Exporting Erudit Information From the Web</a></li> </ul> </li> <li><a href="#pubmed-xml-export-plugin">PubMed XML Export Plugin</a> <ul> <li><a href="#exporting-pubmed-information-from-the-web">Exporting Pubmed Information From the Web</a></li> </ul> </li> <li><a href="#using-the-plugins-from-the-command-line">Using the Plugins from the Command Line</a></li> </ul> </div> <p>This guide is for OJS 2, which is an older version of OJS. For information about importing and exporting data in OJS 3, see the <a href="/learning-ojs/en/tools#importexport">Import/Export section of Learning OJS</a> or the <a href="/admin-guide/en/data-import-and-export">Data Import and Export chapter of the Administrator’s Guide</a>.</p> <h2 id="introduction"> Introduction <a href="#introduction" class="book_heading_anchor" title="Link to Introduction section">#</a> </h2> <p>Open Journal Systems 2 offers a variety of tools and Import/Export plugins which allow the Journal Manager to inject data into and extract data from OJS. More information can be found for each plugin’s documentation within OJS’ plugin directory (<code class="language-plaintext highlighter-rouge">plugins/</code>).</p> <p>Import/export functionality is also available as a command-line tool; see <code class="language-plaintext highlighter-rouge">tools/importExport.php</code> and the command line section for more information.</p> <h2 id="using-the-quick-submit-plugin"> Using the Quick Submit Plugin <a href="#using-the-quick-submit-plugin" class="book_heading_anchor" title="Link to Using the Quick Submit Plugin section">#</a> </h2> <p>The easiest way to import existing data into OJS is by using the Quick Submit plugin. This is used by journals that have a set of “ready-to-publish” files (usually PDFs), which need to be uploaded for immediate reader access.</p> <p>Use cases include:</p> <ul> <li>journals that are only using OJS to display their content and not using the editorial workflow</li> <li>journals that were published using another platform and are migrating to OJS</li> <li>journals that were originally published in print and have since been digitized</li> </ul> <p>To use this plugin, you will need:</p> <ul> <li>to be enrolled as an editor in the OJS journal, allowing you to create the issue for the new files</li> <li>to be enrolled as a journal manager in the OJS journal, allowing you to access the Quick Submit plugin</li> <li>a set of ready-to-publish files (e.g., PDFs)</li> <li>all of the metadata for the files (e.g., author names, titles, abstracts, etc.)</li> </ul> <p>First, log in as an Editor and <a href="/learning-ojs-2/en/issues">create the issues</a> (or issue) that will contain the new files.</p> <p>Next, log in as a Journal Manager and go to the Management Pages, choose Import/Export Data, and then choose Quick Submit plugin.</p> <p>In the resulting form, you can select the issue you created in the step above, and then add the appropriate publication date for the content (a past date if it was previously published, or today’s date if you are publishing it for the first time).</p> <p>Moving down the form, you must now choose the appropriate section for the journal, and then upload the “ready-to-publish” file.</p> <p>Next, enter all of the required fields:</p> <ul> <li>Author First Name</li> <li>Author Last name</li> <li>Author email – you can make something up if necessary – e.g., no@email.com</li> <li>Title</li> <li>Abstract (not always required)</li> </ul> <p>You may need to copy this data directly out of the “ready-to-publish” file and paste into the form. You can also fill in any of the non-required fields as necessary for your journal.</p> <p>Finally, hit the Save and Continue button (if you are just doing one file) or the Save and Create Another button if you have more to do.</p> <p>The file will now be immediately placed in the assigned issue. If the issue is already published, the files will be visible to your readers now. If the issue is not yet published, the files will not be visible.</p> <h2 id="using-the-web-based-expedited-submission-process-to-add-articles-quickly"> Using the Web-based Expedited Submission Process to Add Articles Quickly <a href="#using-the-web-based-expedited-submission-process-to-add-articles-quickly" class="book_heading_anchor" title="Link to Using the Web-based Expedited Submission Process to Add Articles Quickly section">#</a> </h2> <p>In addition to the Quick Submit plugin, there is another way to expedite the submissions, available to Journal Managers from the 5-step Author Submission process.</p> <p>First, make sure you are logged in as a user who is enrolled as both an Editor and an Author. From your User Home, choose the Author Role, and start a submission. Fill out the first two steps of the Author Submission Process as you normally would, keeping in mind that you may need to modify the author metadata information if you are not the original author.</p> <p>When you reach Step 3 of the submission Process (“Uploading the Submission”), you should upload a galley file, as the file you upload here will appear in the final copyediting queue as both an Initial Copyedit file, and as a Galley file. You will still be able to edit, add and remove any galley files at a later step, however. Please note, if you do not upload a file at this point, you will not have the option of expediting the submission process once you are done.</p> <p>Finish the rest of the submission process as normal. If you have uploaded a file, upon completion of Step 5 you will be presented with the option to move the submission directly to the last step of the Editing Queue. Clicking that link will take you from the submission process to the Editing queue.</p> <p>You will note that the file you uploaded appears both under Copyediting as an Initial Copyedit file, and under Layout, as a Galley file. For publishing’s sake it is the galley file you are interested in. Double-check that the file format has been correctly identified (normally either PDF or HTML), view the proof, and upload any other galley files at this time as well.</p> <p>You can then schedule the submission under Scheduling, as you would for any other reviewed, copyedited file, and it will appear as soon as the issue it has been assigned to is published. In the case of it being assigned to an already-published issue, it will appear immediately in that issue’s Table of Contents.</p> <h2 id="articles-and-issues-xml-plugin"> Articles and Issues XML Plugin <a href="#articles-and-issues-xml-plugin" class="book_heading_anchor" title="Link to Articles and Issues XML Plugin section">#</a> </h2> <h3 id="importing-articles-and-issues"> Importing Articles and Issues <a href="#importing-articles-and-issues" class="book_heading_anchor" title="Link to Importing Articles and Issues section">#</a> </h3> <p>OJS features the ability to directly import metadata describing articles and issues for your journal. This can be extremely useful when you are adding back issues to your journal, and do not want to go through the standard OJS editorial process. To do this, you will have to have a basic understanding of XML.</p> <p>Please note that there is another way to expedite the submission process and publish material quickly which does not depend on making XML files, and may be of use if you only have a handful of items to import. You can view complete instructions in the Expedited Submissions section on this page.</p> <h3 id="creating-the-xml-import-file"> Creating the XML Import File <a href="#creating-the-xml-import-file" class="book_heading_anchor" title="Link to Creating the XML Import File section">#</a> </h3> <p>The Articles and Issues XML Plugin is the primary method for batch importing and exporting article-level content. It can be used to import and export single or multiple issues and/or articles, including comprehensive metadata. You can view the complete DTD here: <code class="language-plaintext highlighter-rouge">plugins/importexport/native/native.dtd</code>. The DTD supports the following as root elements: <code class="language-plaintext highlighter-rouge"><article></code>, <code class="language-plaintext highlighter-rouge"><articles></code>, <code class="language-plaintext highlighter-rouge"><issue></code> and <code class="language-plaintext highlighter-rouge"><issues></code>.</p> <p>You can view a sample XML article import file in your OJS installation: <code class="language-plaintext highlighter-rouge">plugins/importexport/native/sample.xml</code>.</p> <p>There are a handful of things you should be mindful of when importing data.</p> <ul> <li>Be sure to define the document type appropriately using <code class="language-plaintext highlighter-rouge"><!DOCTYPE ...></code></li> <li>Your XML file should UTF8-encoded.</li> <li>Your XML file must validate. Most *nix systems have access to the <a href="https://gnome.pages.gitlab.gnome.org/libxml2/xmllint.html">xmllint</a> program for validation; there are also a number online XML validators, such as <a href="https://www.validome.org/xml-rpc-validator/">Validome</a>; and many XML editing tools such as <a href="https://www.liquid-technologies.com/xml-editor">Liquid XML Editor</a>, <a href="https://www.oxygenxml.com/">Oxygen XML</a> and <a href="https://www.altova.com/">XMLspy</a> can also validate XML files.</li> <li>Dates should be specified as YYYY-MM-DD.</li> <li>To import a file, you can use <code class="language-plaintext highlighter-rouge"><embed></code> to place a file directly within your XML document, or use <code class="language-plaintext highlighter-rouge"><href></code> to link to one.</li> </ul> <p>If you use the <code class="language-plaintext highlighter-rouge"><embed></code> tag you will have to base64-encode your files. Using <code class="language-plaintext highlighter-rouge"><embed></code> with a base64-encoded file would look something like this:</p> <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><galley></span> <span class="nt"><label></span>`PDF`<span class="nt"></label></span> <span class="nt"><file></span> <span class="nt"><embed</span> <span class="na">encoding=</span><span class="s">"base64"</span> <span class="na">filename=</span><span class="s">"my_file.pdf"</span> <span class="na">mime_type=</span><span class="s">"application/pdf"</span><span class="nt">></span> PGxpPjxCPlc8Zm9ukjfdaSD...(and so on) <span class="nt"></embed></span> <span class="nt"></file></span> <span class="nt"></galley></span> </code></pre></div></div> <p>You can link to full URLs as well as local files using <code class="language-plaintext highlighter-rouge"><href></code>. A full URL link would look like the following:</p> <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><galley></span> <span class="nt"><label></span>`PDF`<span class="nt"></label></span> <span class="nt"><file></span> <span class="nt"><href</span> <span class="na">src=</span><span class="s">"http://www.example.com/import_files/my_file.pdf"</span> <span class="na">mime_type=</span><span class="s">"application/pdf"</span><span class="nt">/></span> <span class="nt"></file></span> <span class="nt"></galley></span> </code></pre></div></div> <p>You can use local linking if your galleys are already stored on the destination machine, but in this case you need to launch the import from the command line. Importing a local file would look like the following:</p> <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><galley></span> <span class="nt"><label></span>`PDF`<span class="nt"></label></span> <span class="nt"><file></span> <span class="nt"><href</span> <span class="na">src=</span><span class="s">"/home/johndoe/import/my_file.pdf"</span><span class="nt">/></span> <span class="nt"></file></span> <span class="nt"></galley></span> </code></pre></div></div> <ul> <li>For importing HTML galleys, use the <code class="language-plaintext highlighter-rouge"><htmlgalley></code> element. Otherwise, use the <code class="language-plaintext highlighter-rouge"><galley></code> element (ie., for PDF/Postscript, audio, video and other files).</li> <li>Some elements can support embedded HTML tags, such as the abstract element. If you do embed HTML within your document, remember to wrap the HTML within <code class="language-plaintext highlighter-rouge"><![CDATA[]]></code> tags.</li> <li>To add empty data to required fields, you can add anything, for example a single space, so that the field is not null. See the following example, where Jane Doe does not have an email address:</li> </ul> <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><author</span> <span class="na">primary_contact=</span><span class="s">"true"</span><span class="nt">></span> <span class="nt"><firstname></span>`Jane`<span class="nt"></firstname></span> <span class="nt"><lastname></span>`Doe`<span class="nt"></lastname></span> <span class="nt"><email></span>` `<span class="nt"></email></span> <span class="nt"><biography</span> <span class="na">locale=</span><span class="s">"en_US"</span><span class="nt">></span>`Jane Doe's Bio statement...`<span class="nt"></biography></span> <span class="nt"></author></span> </code></pre></div></div> <ul> <li>To add more than one term per indexing type, include all terms in the same entry, separated by semi-colons:</li> </ul> <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><indexing></span> <span class="nt"><subject</span> <span class="na">locale=</span><span class="s">"en_US"</span><span class="nt">></span>`Term 1; Term 2; Term 3`<span class="nt"></subject></span> <span class="nt"></indexing></span> </code></pre></div></div> <ul> <li>If your journal supports more than one locale, you can include translated terms in a separate entry:</li> </ul> <div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt"><indexing></span> <span class="nt"><subject</span> <span class="na">locale=</span><span class="s">"en_US"</span><span class="nt">></span>`Term 1; Term 2; Term 3`<span class="nt"></subject></span> <span class="nt"><subject</span> <span class="na">locale=</span><span class="s">"fr_CA"</span><span class="nt">></span>`Translated Term 1; Translated Term 2; Translated Term 3`<span class="nt"></subject></span> <span class="nt"></indexing></span> </code></pre></div></div> <ul> <li>If you make any typographical errors in the data you are trying to import, you may end up with duplicate or split entries: for example, if your journal already has a section “Articles” with the initials ART, but you mistype in your XML file <code class="language-plaintext highlighter-rouge"><abbrev locale="en_US">`AR`</abbrev></code> instead of <code class="language-plaintext highlighter-rouge"><abbrev locale="en_US">`ART`</abbrev></code>, a new journal section with the initials AR will be created, and that one article will be added to it. This can be easily fixed pre-import, but difficult to clean up after.</li> </ul> <h3 id="importing-articles-and-issues-from-the-web"> Importing Articles and Issues From the Web <a href="#importing-articles-and-issues-from-the-web" class="book_heading_anchor" title="Link to Importing Articles and Issues From the Web section">#</a> </h3> <p>The Articles and Issues XML Plugin can be used from the web, from the Journal Manager’s User Home:</p> <ul> <li>Login as the Journal Manager and from your User Home choose Import/Export Data.</li> <li>Then, choose the Articles and Issues XML Plugin link.</li> <li>Upload your XML file (e.g., <code class="language-plaintext highlighter-rouge">ojsV1N1.xml</code>).</li> </ul> <p>You will be notified of any errors, or if the import was successful.</p> <h3 id="exporting-articles-and-issues-from-the-web"> Exporting Articles and Issues From the Web <a href="#exporting-articles-and-issues-from-the-web" class="book_heading_anchor" title="Link to Exporting Articles and Issues From the Web section">#</a> </h3> <p>You can export either single or multiple articles and/or issues from the Journal Manager’s User Home:</p> <ul> <li>Login as the Journal Manager and from your User Home choose Import/Export Data.</li> <li>Then, choose the Articles and Issues XML Plugin link.</li> <li>You will be provided with the options to Export Issues or Export Articles. Depending on what you choose, you will be able to export either single or multiple articles, or single or multiple issues at a time. These will be exported in XML format, and can be imported to this or another journal at a later date.</li> </ul> <blockquote> <p><strong>Note:</strong> Please note that using this plugin to export articles and issues will not only export all relevant metadata, but will include all article files (HTML, PDF, etc.) embedded within the XML document in Base64 encoding. This can result in large, cumbersome XML files, especially when multiple issues are exported at once. Opening them in an editor to view or change any XML data or metadata may be taxing for your computer, and it may take some time to download and/or upload said files, depending on your connection and the resources of the source server.</p> </blockquote> <h2 id="users-xml-plugin"> Users XML Plugin <a href="#users-xml-plugin" class="book_heading_anchor" title="Link to Users XML Plugin section">#</a> </h2> <p>The Users XML Plugin can be used to import and export users and their roles. See the XML DTD in <code class="language-plaintext highlighter-rouge">plugins/importexport/users/users.dtd</code> for more information, as well as the sample file in <code class="language-plaintext highlighter-rouge">plugins/importexport/users/sample.xml</code> and in Appendix B.</p> <h3 id="importing-users"> Importing Users <a href="#importing-users" class="book_heading_anchor" title="Link to Importing Users section">#</a> </h3> <p>You can import single or multiple users from the Journal Manager’s User Home:</p> <ul> <li>Login as the Journal Manager and from your User Home choose Import/Export Data.</li> <li>Then, choose the Users XML Plugin link.</li> <li>You will find the option to upload an XML User Data file underneath the Export Users section on the Users XML Plugin page.</li> </ul> <h3 id="creating-the-import-users-xml-file"> Creating the Import Users XML File <a href="#creating-the-import-users-xml-file" class="book_heading_anchor" title="Link to Creating the Import Users XML File section">#</a> </h3> <p>The Users XML Plugin can be used to import and export single or multiple users. You can view the complete DTD here: <code class="language-plaintext highlighter-rouge">plugins/importexport/users/users.dtd</code>. The root element is <code class="language-plaintext highlighter-rouge"><users></code>.</p> <p>You can view a sample XML user import file in Appendix B, and also in your OJS installation at <code class="language-plaintext highlighter-rouge">plugins/importexport/users/sample.xml</code>.</p> <p>There are a handful of things you should be mindful of when importing user data.</p> <ul> <li>Be sure to define the document type appropriately using <code class="language-plaintext highlighter-rouge"><!DOCTYPE ...></code></li> <li>Your XML file should UTF8-encoded.</li> <li>Your XML file must validate. Most *nix systems have access to the xmllint program for validation; there are also a number online XML validators, such as Validome; and many XML editing tools such as Oxygen XML and XMLspy can also validate XML files.</li> <li><code class="language-plaintext highlighter-rouge"><firstname></code>, <code class="language-plaintext highlighter-rouge"><lastname></code> and <code class="language-plaintext highlighter-rouge"><email></code> are mandatory.</li> <li>Usernames and passwords are optional, and will be generated automatically if omitted.</li> <li>If you allow the system to generate usernames and passwords for the users you are uploading, you can optionally allow the system to email the users with their account credentials. This option can be found on the Users XML Plugin Page (“Send a notification email to each imported user containing the user’s username and password.”). You can require the user change their password when they next log in by setting the password attribute “change” to “true”: <code class="language-plaintext highlighter-rouge"><password change="true">myoldpassword</password></code></li> <li>The default password encryption is “plaintext” (ie., none). Encrypted assumes it was encrypted by Validation::encryptCredentials() and is using the same encryption algorithm used by the system.</li> <li>If the imported file contains any usernames or email addresses that already exist in the system, the user data for those users will not be imported and any new roles to be created will be assigned to the existing users.</li> </ul> <h3 id="exporting-users-from-the-web"> Exporting Users From the Web <a href="#exporting-users-from-the-web" class="book_heading_anchor" title="Link to Exporting Users From the Web section">#</a> </h3> <p>You can export users by one or more roles, or export all users at once. To export one or more roles, simply choose the roles you want exported by clicking (or Ctrl-clicking, if more than one role) the role in the role list and then clicking Export Users. To export all users, click the Export All link.</p> <p>Please note that passwords will be encrypted using MD5 or SHA-1 encryption, depending on what system the journal is using.</p> <h2 id="crossref-xml-export-plugin"> Crossref XML Export Plugin <a href="#crossref-xml-export-plugin" class="book_heading_anchor" title="Link to Crossref XML Export Plugin section">#</a> </h2> <p>Please see the <a href="/crossref-ojs-manual/crossref-v1-deposit/en/">PKP Crossref Manual</a>.</p> <h2 id="erudit-article-export-plugin"> Erudit Article Export Plugin <a href="#erudit-article-export-plugin" class="book_heading_anchor" title="Link to Erudit Article Export Plugin section">#</a> </h2> <p>The Erudit Article Export Plugin implements single-article export for full-text indexing using Erudit’s XML DTD. See <a href="https://www.erudit.org/en/">https://www.erudit.org</a> for more information.</p> <h3 id="exporting-erudit-information-from-the-web"> Exporting Erudit Information From the Web <a href="#exporting-erudit-information-from-the-web" class="book_heading_anchor" title="Link to Exporting Erudit Information From the Web section">#</a> </h3> <p>The Erudit XML Plugin can be used from the web, from the Journal Manager’s User Home:</p> <ul> <li>Login as the Journal Manager and from your User Home choose Import/Export Data.</li> <li>Then, choose the <em>Erudit Article XML Export Plugin</em> link.</li> <li>You will then be presented with a list of published articles, and links to the XML export for each individual article galley. It is not currently possible to export whole articles or issues.</li> </ul> <h2 id="pubmed-xml-export-plugin"> PubMed XML Export Plugin <a href="#pubmed-xml-export-plugin" class="book_heading_anchor" title="Link to PubMed XML Export Plugin section">#</a> </h2> <p>The PubMed XML Export Plugin provides an import/export plugin to generate bibliographic information for articles in PubMed standard publisher data format XML for indexing in NLM PubMed/MEDLINE. Details on the XML format and data requirements is available at: <a href="https://www.ncbi.nlm.nih.gov/books/NBK3828/">https://www.ncbi.nlm.nih.gov/books/NBK3828/</a>. More information on this plugin can be found in <code class="language-plaintext highlighter-rouge">plugins/importexport/pubmed</code>.</p> <h3 id="exporting-pubmed-information-from-the-web"> Exporting Pubmed Information From the Web <a href="#exporting-pubmed-information-from-the-web" class="book_heading_anchor" title="Link to Exporting Pubmed Information From the Web section">#</a> </h3> <p>The Pubmed XML Plugin can be used from the web, from the Journal Manager’s User Home:</p> <ul> <li>Login as the Journal Manager and from your User Home choose <em>Import/Export Data</em>.</li> <li>Then, choose the <em>Pubmed XML Export Plugin</em> link.</li> <li>You will be provided with the options to <em>Export Issues</em> or <em>Export Articles</em>. Depending on what you choose, you will be able to export either single or multiple articles, or single or multiple issues at a time. These will be exported in XML format.</li> </ul> <h2 id="using-the-plugins-from-the-command-line"> Using the Plugins from the Command Line <a href="#using-the-plugins-from-the-command-line" class="book_heading_anchor" title="Link to Using the Plugins from the Command Line section">#</a> </h2> <p>Import/export plugins can normally also be run from the command line. You can view the applicable plugin names by running the following command:</p> <p><code class="language-plaintext highlighter-rouge">php tools/importExport.php list</code></p> <p>You can see usage parameters by running the following command:</p> <p><code class="language-plaintext highlighter-rouge">php tools/importExport.php [PluginName] usage</code></p> <hr> <p>Copyright: Simon Fraser University holds the copyright for work produced by the Public Knowledge Project and has placed its documentation under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.</p> <p><a href="https://creativecommons.org/licenses/by/4.0/"><img src="https://licensebuttons.net/l/by/4.0/88x31.png" alt="Creative Commons Attribution 4.0 International" title="Creative Commons Attribution 4.0 International" /></a></p> <div class="book__footer"> <div class="book__improve"> <a href="https://github.com/pkp/pkp-docs/edit/main/importing-exporting/en/index.md"> Edit this page </a> or <a href="https://pkp.sfu.ca/documentation-feedback/"> make a suggestion </a> </div> </div> </div> </div> <div class="book__sidebarScreen"></div> <div id="sidebar" class="book__sidebar"> <div class="book__summary"> <div class="book_page_toc"> <h2>Table of Contents</h2> <ul> <li><a href="#introduction">Introduction</a></li> <li><a href="#using-the-quick-submit-plugin">Using the Quick Submit Plugin</a></li> <li><a href="#using-the-web-based-expedited-submission-process-to-add-articles-quickly">Using the Web-based Expedited Submission Process to Add Articles Quickly</a></li> <li><a href="#articles-and-issues-xml-plugin">Articles and Issues XML Plugin</a> <ul> <li><a href="#importing-articles-and-issues">Importing Articles and Issues</a></li> <li><a href="#creating-the-xml-import-file">Creating the XML Import File</a></li> <li><a href="#importing-articles-and-issues-from-the-web">Importing Articles and Issues From the Web</a></li> <li><a href="#exporting-articles-and-issues-from-the-web">Exporting Articles and Issues From the Web</a></li> </ul> </li> <li><a href="#users-xml-plugin">Users XML Plugin</a> <ul> <li><a href="#importing-users">Importing Users</a></li> <li><a href="#creating-the-import-users-xml-file">Creating the Import Users XML File</a></li> <li><a href="#exporting-users-from-the-web">Exporting Users From the Web</a></li> </ul> </li> <li><a href="#crossref-xml-export-plugin">Crossref XML Export Plugin</a></li> <li><a href="#erudit-article-export-plugin">Erudit Article Export Plugin</a> <ul> <li><a href="#exporting-erudit-information-from-the-web">Exporting Erudit Information From the Web</a></li> </ul> </li> <li><a href="#pubmed-xml-export-plugin">PubMed XML Export Plugin</a> <ul> <li><a href="#exporting-pubmed-information-from-the-web">Exporting Pubmed Information From the Web</a></li> </ul> </li> <li><a href="#using-the-plugins-from-the-command-line">Using the Plugins from the Command Line</a></li> </ul> </div> </div> <div class="book__backToHub"> <span class="fa fa-long-arrow-alt-left" aria-hidden="true"></span> <p>Back to <a href="/">all documentation</a>.</p> </div> <div class="book__spacer"></div> </div> </div> <div class="book__footerWrapper"> <div class="siteFooter"> <nav class="siteFooter__container"> <div class="siteFooter__top"> <div class="siteFooter__nav"> <div class="siteFooter__navHeader"> Contact Us </div> <p>Have a question or suggestion about PKP’s documentation and user guides? <a href="https://pkp.sfu.ca/documentation-feedback/">Use our documentation contact form</a>.</p> <p>If your message is not about documentation, please use the general <a href="https://pkp.sfu.ca/contact-us/">contact form</a>.</p> </div> <div class="siteFooter__nav"> <div class="siteFooter__navHeader"> Community </div> <p><a href="https://pkp.sfu.ca/documentation-interest-group/">Documentation Interest Group</a></p> <p><a href="/contributing/en/">Contributing Documentation</a></p> <p><a href="/translating-guide/">Translating Guide</a></p> <p><a href="https://forum.pkp.sfu.ca">Community Forum</a></p> </div> <div class="siteFooter__nav"> <div class="siteFooter__navHeader"> About </div> <p><a href="https://pkp.sfu.ca">Public Knowledge Project</a></p> <p><a href="https://pkpservices.sfu.ca/">PKP|Publishing Services</a></p> </div> <div class="siteFooter__logo"> <a href="https://pkp.sfu.ca"> <img src="/img/logo-on-grey.png" alt="Public Knowledge Project"> </a> <p>The Public Knowledge Project is a Core Facility of Simon Fraser University</p> <p>888 University Drive, Burnaby, B.C., Canada V5A 1S6</p> <p>We respectfully acknowledge that SFU occupies the unceded traditional territories of the Coast Salish peoples of the Musqueam, Squamish, and Tsleil-Waututh Nations.</p> </div> </div> <div class="siteFooter__bottom"> <p class="footer-copyright"><span class="terms-text"><a href="https://www.sfu.ca/contact/terms-conditions.html" target="_blank">TERMS & CONDITIONS</a> © SIMON FRASER UNIVERSITY.</span><span class="copyright-text"><img src="/img/creativecommons.svg" alt="Creative Commons logo" /><img src="/img/attribution.svg" alt="Attribution icon" /><a href="https://creativecommons.org/licenses/by/2.0/" target="_blank">CC-BY 2.0</a></span><span class="footer-copyright-separator"> | </span><span class="ab-link">Website by <a target="_blank" href="https://www.affinitybridge.com">Affinity Bridge</a></span></p> </div> </div> </div> </div> <script type="text/javascript">/** * Toggle the sidebar open/closed */ (function() { var sidebar = document.getElementById('sidebar'); var sidebarControl = document.getElementById('sidebarControl'); var isOpen = false; var sidebarOpenClass = ' -sidebarIsOpen'; if (!sidebar || !sidebarControl) { return; } // Toggle sidebar function toggle() { if (isOpen) { document.body.className = document.body.className.replace(new RegExp(sidebarOpenClass, 'g'), ''); } else { document.body.className = document.body.className + sidebarOpenClass; } isOpen = !isOpen; } sidebarControl.addEventListener('click', toggle); })(); </script> <script type="text/javascript">/** * Initialize smooth scrolling to anchor links * * See: https://github.com/cferdinandi/smooth-scroll */ (function() { function init() { if (typeof SmoothScroll === 'undefined') { setTimeout(init, 500); } else { var scroll = new SmoothScroll('a[href*="#"]', {easing: 'easeInOutCubic', offset:80}); } } init(); })(); </script>  <script async src="https://www.googletagmanager.com/gtag/js?id=UA-130558797-1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-130558797-1'); </script>  <script> (function(h,o,t,j,a,r){ h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)}; h._hjSettings={hjid:2436159,hjsv:6}; a=o.getElementsByTagName('head')[0]; r=o.createElement('script');r.async=1; r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv; a.appendChild(r); })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv='); </script>  <script type="text/javascript"> var _paq = _paq || []; _paq.push(["setDocumentTitle", document.domain + "/" + document.title]); _paq.push(["setCookieDomain", "*.docs.pkp.sfu.ca"]); _paq.push(["setDomains", ["*.docs.pkp.sfu.ca"]]); _paq.push(["trackPageView"]); _paq.push(["enableLinkTracking"]); (function() { var u = (("https:" == document.location.protocol) ? "https" : "http") + "://" + "matomo.publicknowledgeproject.org/pkp/"; _paq.push(["setTrackerUrl", u + "piwik.php"]); _paq.push(["setSiteId", "40"]); var d = document, g = d.createElement("script"), s = d.getElementsByTagName("script")[0]; g.type = "text/javascript"; g.defer = true; g.async = true; g.src = u + "piwik.js"; s.parentNode.insertBefore(g, s); })(); </script>  </body> </html>

CINXE.COM

Importing and Exporting Data in OJS 2