<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic SYSTEM "../../../../lib/pkp/dtd/helpTopic.dtd">

<!--
  * 000003.xml
  *
  * Copyright (c) 2013-2019 Simon Fraser University
  * Copyright (c) 2003-2019 John Willinsky
  * Distributed under the GNU GPL v2. For full terms see the file docs/COPYING.
  *
  * Site Administration - Administration Functions 
  *
  -->

<topic id="site/topic/000003" locale="en_US" title="Administrative Functions" toc="site/toc/000000" key="site.administrativeFunctions">
	<section>
		<![CDATA[<p>Several administrative functions are available in the site administration area. These functions should generally be used with caution, as improper use could lead to unexpected results.</p>]]>
	</section>

	<section title="System Information">
		<![CDATA[<p>General information about the server environment and OJS version history (including past upgrades). A web-based interface to view the OJS configuration file is also provided.</p>]]>
	</section>

	<section title="Expire User Sessions">
		<![CDATA[<p>Clears all active user sessions in the system, requiring any user that is currently logged in to sign in to the system again.</p>]]>
	</section>

	<section title="Clear Data Caches">
		<![CDATA[<p>Clears all cached data, including locale information, help cache, and search cache.</p>]]>
	</section>

	<section title="Clear Template Cache">
		<![CDATA[<p>Clears all cached versions of HTML templates. This function may be useful to force templates to be reloaded after customizations have been made.</p>]]>
	</section>

	<section title="Merge Users">
		<![CDATA[<p>The Merge Users feature allows the Site Administrator to merge two user accounts into a single account, transferring edit assignments, submissions, and numerous other records from one account to the other and effectively deleting the first.</p>
		<p>Unlike the Merge Users feature available to a Journal Manager, which is limited to merging user accounts for a particular journal, the Merge Users feature under Site Administration allows the Site Administrator to merge any two user accounts, even across different journals.</p>
		<p>The following items are transferred:</p>
			<ul>
				<li>Article authorship</li>
				<li>Public comments on articles</li>
				<li>Article notes</li>
				<li>Editor assignments and decisions</li>
				<li>Review assignments</li>
				<li>Layout editor assignments</li>
				<li>Proofreader assignments</li>
				<li>Article email and event log entries</li>
				<li>Reviewer access keys</li>
				<li>Roles</li>
				<li>Subscriptions (please see below)</li>
			</ul>
		<p>The following items are <strong>not</strong> transferred:</p>
			<ul>
				<li>Sessions</li>
				<li>Notification status (i.e. whether the user has signed up to receive notifications about journal news)</li>
				<li>Editorial team memberships</li>
				<li>Section Editor status on sections</li>
				<li>User profile information (e.g. first name, last name, etc.)</li>
			</ul>
		<p>This feature should be used with caution, as it is not reversible and involves the transfer of records from one user to another.</p>
		<p>For subscriptions, the merge feature performs the following actions: For Individual Subscriptions, the second user's subscription is transferred to the first user only if is valid and if the first user does not already have a valid subscription for a given journal. For Institutional Subscriptions, all of the subscriptions for which the second user is identified as the contact person are transferred to the first user, who becomes the new contact person for the subscriptions.</p>]]>
	</section>
</topic>
