[ Mini Kiebo ]
Server: Windows NT DESKTOP-5B8S0D4 6.2 build 9200 (Windows 8 Professional Edition) i586
Path:
D:
/
Backup
/
14082024
/
Data
/
htdocs
/
htdocs
/
ojs
/
248
/
locale
/
en_US
/
[
Home
]
File: manager.xml
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE locale SYSTEM "../../lib/pkp/dtd/locale.dtd"> <!-- * locale/en_US/manager.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. * * Localization strings. --> <locale name="en_US" full_name="U.S. English"> <message key="manager.emails.confirmResetAll">Are you sure you want to reset all email templates in this journal? You will lose any customizations you have made.</message> <message key="manager.files.note">Note: The Files Browser is an advanced feature that allows the files and directories associated with a journal to be viewed and manipulated directly.</message> <message key="manager.groups">Masthead</message> <message key="manager.groups.publishEmails">Publish member email addresses</message> <message key="manager.groups.context.editorialTeam">Have title appear under Editorial Team in People section of About the Journal (e.g. Editor)</message> <message key="manager.groups.context.editorialTeam.short">Editorial Team</message> <message key="manager.groups.context.people">Have title appear as its own category under People (e.g. Editorial Board)</message> <message key="manager.groups.create">Create Position Title</message> <message key="manager.groups.disableBoard">OJS lists people in Editorial Team under assigned roles (Journal Manager, Copyeditor, etc.)</message> <message key="manager.groups.enableBoard">The Journal Manager creates titles and adds people under each title.</message> <message key="manager.groups.enableBoard.description"><![CDATA[Under <a href="{$aboutEditorialTeamUrl}">People</a> in About the Journal:]]></message> <message key="manager.groups.noneCreated">No editorial team positions have been created.</message> <message key="manager.journalManagement">Journal Management</message> <message key="manager.language.ui">UI</message> <message key="manager.language.submissions">Submissions</message> <message key="manager.language.forms">Forms</message> <message key="manager.language.confirmDefaultSettingsOverwrite">This will replace any locale-specific journal settings you had for this locale</message> <message key="manager.language.reloadLocalizedDefaultSettings">Reload defaults</message> <message key="manager.languages.languageInstructions"><![CDATA[OJS can be made available to users in any of several supported languages. As well, OJS can operate as a multilingual system, providing users with an ability to toggle between languages on each page, and allowing certain data to be entered in several additional languages.<br /><br />If a language supported by OJS is not listed below, ask your site administrator to install the language from the site administration interface. For instructions on adding support for new languages, please consult the OJS documentation.]]></message> <message key="manager.languages.noneAvailable">Sorry, no additional languages are available. Contact your site administrator if you wish to use additional languages with this journal.</message> <message key="manager.languages.primaryLocaleInstructions">This will be the default language for the journal site.</message> <message key="manager.managementPages">Management Pages</message> <message key="manager.payment.action">Action</message> <message key="manager.payment.addPayment">Add Payment</message> <message key="manager.payment.amount">Amount</message> <message key="manager.payment.authorFees">Author Fees</message> <message key="manager.payment.authorFeesDescription">Selected options, along with their descriptions and fees (which can be edited below), will appear in Step 1 of the submission process and in About the Journal under Submissions, as well as at points where payment is required.</message> <message key="manager.payment.currency">Currency</message> <message key="manager.payment.currencymessage">OJS does not perform any currency conversions. If accepting payments for subscriptions, you must ensure that the subscription currency matches the one specified here.</message> <message key="manager.payment.description">Description</message> <message key="manager.payment.details">Details</message> <message key="manager.payment.editSubscription">Edit Subscription</message> <message key="manager.payment.enable">Enable</message> <message key="manager.payment.feePaymentOptions">Fee Payment Options</message> <message key="manager.payment.form.numeric">All costs must be positive numeric values (decimal points are allowed)</message> <message key="manager.payment.giftFees">Gift Fees</message> <message key="manager.payment.giftFeesDescription">A gift subscriptions link will appear on the Subscriptions page in About the Journal and as part of the subscriptions sidebar block.</message> <message key="manager.payment.generalFees">General Fees</message> <message key="manager.payment.generalFeesDescription">The Association Membership will appear in About the Journal under Policies, and the donations link will appear above the search function in the right-hand frame.</message> <message key="manager.payment.generalOptions">General Options</message> <message key="manager.payment.noPayments">No Payments</message> <message key="manager.payment.notFound">Not Found</message> <message key="manager.payment.options">Options</message> <message key="manager.payment.options.acceptSubscriptionPayments">This will activate payments for Subscriptions, where types, cost, duration and subscriptions are managed by the Journal (Subscription) Manager.</message> <message key="manager.payment.options.acceptGiftSubscriptionPayments">This will activate payments for gift subscriptions, allowing journal readers to buy gift subscriptions for other readers.</message> <message key="manager.payment.options.donationFee">Donations to journal</message> <message key="manager.payment.options.enablePayments">Click here to enable the Payments module. You must configure payment settings by filling in the form below. Note Users will be required to log in to make payments.</message> <message key="manager.payment.options.fastTrackFee">Fast-Track Review</message> <message key="manager.payment.options.fee">Fee</message> <message key="manager.payment.options.feeDescription">Fee Description</message> <message key="manager.payment.options.feeName">Fee Name</message> <message key="manager.payment.options.membershipFee">Association Membership</message> <message key="manager.payment.options.onlypdf">Only Restrict Access to PDF version of issues and articles</message> <message key="manager.payment.options.publicationFee">Article Publication</message> <message key="manager.payment.options.purchaseArticleFee">Purchase Article</message> <message key="manager.payment.options.purchaseIssueFee">Purchase Issue</message> <message key="manager.payment.options.submissionFee">Article Submission</message> <message key="manager.payment.options.text">Description of Payment Method</message> <message key="manager.payment.options.waiverPolicy">Waiver Policy</message> <message key="manager.payment.paymentId">Payment ID</message> <message key="manager.payment.paymentMethod">Payment Method</message> <message key="manager.payment.paymentMethod.description">You may configure any of the following Payment Method Plugins from this screen.</message> <message key="manager.payment.paymentMethods">Fee Payment Methods</message> <message key="manager.payment.paymentType">Payment Type</message> <message key="manager.payment.readerFees">Reader Fees</message> <message key="manager.payment.readerFeesDescription">Selected options, along with their descriptions and fees (which can be edited below), will appear in About the Journal under Policies, as well as at points where payment is required.</message> <message key="manager.payment.records">Records</message> <message key="manager.payments">Payments</message> <message key="manager.payment.userName">Payment ID</message> <message key="manager.people.allEnrolledUsers">Users Enrolled in this Journal</message> <message key="manager.people.allJournals">All Journals</message> <message key="manager.people.allSiteUsers">Enroll a User from this Site in this Journal</message> <message key="manager.people.showNoRole">Show users with no role</message> <message key="manager.people.allUsers">All Enrolled Users</message> <message key="manager.people.confirmRemove">Remove this user from this journal? This action will unenroll the user from all roles within this journal.</message> <message key="manager.people.emailUsers.selectTemplate">Select a template</message> <message key="manager.people.enrollExistingUser">Enroll an Existing User</message> <message key="manager.people.enrollSyncJournal">With journal</message> <message key="manager.people.mergeUsers.from.description">Select a user (or several) to merge into another user account (e.g., when someone has two user accounts). The account(s) selected first will be deleted and any submissions, assignments, etc. will be attributed to the second account.</message> <message key="manager.people.mergeUsers.into.description">Select a user to whom to attribute the previous users' authorships, editing assignments, etc.</message> <message key="manager.people.roleEnrollment">{$role} Enrollment</message> <message key="manager.people.syncUserDescription">Enrollment synchronization will enroll all users enrolled in the specified role in the specified journal into the same role in this journal. This function allows a common set of users (e.g., Reviewers) to be synchronized between journals.</message> <message key="manager.plugins.copyError">Plugin was not successfully copied. This may be a permissions problem. Please make sure that the web server is able to write to the plugins directory (including subdirectories) but don't forget to secure it again later.</message> <message key="manager.plugins.delete">Delete Plugin</message> <message key="manager.plugins.deleteConfirm">Are you sure you wish to delete this plugin from the system?</message> <message key="manager.plugins.deleteDescription">By clicking delete, you will delete the plugin from the server's file system.</message> <message key="manager.plugins.deleteError">Plugin could not be deleted from the file system. This may be a permissions problem. Please make sure that the web server is able to write to the plugins directory (including subdirectories) but don't forget to secure it again later.</message> <message key="manager.plugins.deleteSuccess">Plugin successfuly deleted</message> <message key="manager.plugins.description">This page allows the Journal Manager to review and potentially configure the plugins that are currently installed. Plugins are divided into categories, according to their function. The categories are listed below, and within each category, its current set of plugins.</message> <message key="manager.plugins.doesNotExist">Plugin does not exist</message> <message key="manager.plugins.fileSelectError">Please select a file first</message> <message key="manager.plugins.install">Install A New Plugin</message> <message key="manager.plugins.installDescription">This form allows you to upload and install a new plugin. Please ensure the plugin is compressed as a .tar.gz file.</message> <message key="manager.plugins.installedVersionNewer">Plugin already exists, and is newer or equal to installed version</message> <message key="manager.plugins.installedVersionOlder">Plugin already exists, and is older or equal to the installed version</message> <message key="manager.plugins.installFailed">Installation failed</message> <message key="manager.plugins.installSuccessful">Successfully installed version</message> <message key="manager.plugins.invalidPluginArchive">The uploaded plugin archive does not contain a folder that corresponds to the plugin name.</message> <message key="manager.plugins.wrongCategory">The uploaded plugin does not fit the category of the upgraded plugin.</message> <message key="manager.plugins.wrongName">The version.xml in the uploaded plugin contains a plugin name that does not fit the name of the upgraded plugin.</message> <message key="manager.plugins.pleaseInstall">Plugin does not exist. Please Install instead</message> <message key="manager.plugins.pleaseUpgrade">Plugin already exists, but is newer than installed version. Please upgrade instead</message> <message key="manager.plugins.settings">Settings</message> <message key="manager.plugins.tarCommandNotFound">The tar command is not available. Please correctly configure it in your "config.inc.php".</message> <message key="manager.plugins.upgrade">Upgrade Plugin</message> <message key="manager.plugins.upgradeDescription">This form allows you to upgrade a plugin. Please ensure the plugin is compressed as a .tar.gz file.</message> <message key="manager.plugins.upgradeFailed">Upgrade failed</message> <message key="manager.plugins.upgradeSuccessful">Successfully upgraded to version</message> <message key="manager.plugins.uploadError">Error uploading file</message> <message key="manager.plugins.uploadPluginDir">Select plugin file</message> <message key="manager.plugins.versionFileInvalid">version.xml in plugin directory contains invalid data.</message> <message key="manager.plugins.versionFileNotFound">version.xml not found in plugin directory</message> <message key="manager.reviewFormElement.changeType">Warning: Changing the review form element type from a multiple-choice type to an open-ended type will result in the deletion of the multiple choice options.</message> <message key="manager.reviewFormElements">Form Items</message> <message key="manager.reviewFormElements.addResponseItem">Add selection</message> <message key="manager.reviewFormElements.checkboxes">Checkboxes (you can choose one or more)</message> <message key="manager.reviewFormElements.chooseType">Choose item type</message> <message key="manager.reviewFormElements.confirmDelete">Are you sure you wish to delete an element of a published review form?</message> <message key="manager.reviewFormElements.copyTo">Copy to:</message> <message key="manager.reviewFormElements.create">Create New Item</message> <message key="manager.reviewFormElements.dropdownbox">Drop-down box</message> <message key="manager.reviewFormElements.edit">Edit Form Item</message> <message key="manager.reviewFormElements.elementType">Item type</message> <message key="manager.reviewFormElements.form.elementTypeRequired">An item type is required for the form item.</message> <message key="manager.reviewFormElements.form.questionRequired">A question is required for the form item.</message> <message key="manager.reviewFormElements.noneCreated">No form items have been created.</message> <message key="manager.reviewFormElements.possibleResponse">Selection</message> <message key="manager.reviewFormElements.question">Item</message> <message key="manager.reviewFormElements.radiobuttons">Radio buttons (you can only choose one)</message> <message key="manager.reviewFormElements.required">Reviewers required to complete item</message> <message key="manager.reviewFormElements.included">Included in message to author</message> <message key="manager.reviewFormElements.smalltextfield">Single word text box</message> <message key="manager.reviewFormElements.textarea">Extended text box</message> <message key="manager.reviewFormElements.textfield">Single line text box</message> <message key="manager.reviewForms">Review Forms</message> <message key="manager.reviewForms.completed">Completed</message> <message key="manager.reviewForms.confirmDeleteUnpublished">Are you sure you wish to delete this unpublished review form?</message> <message key="manager.reviewForms.create">Create Review Form</message> <message key="manager.reviewForms.description">Description and Instructions</message> <message key="manager.reviewForms.edit">Review Form</message> <message key="manager.reviewForms.form.titleRequired">A title is required for the review form.</message> <message key="manager.reviewForms.inReview">In Review</message> <message key="manager.reviewForms.list.description">The peer review forms created here will be presented to reviewers to complete, instead of the default form which consists of two open text boxes, the first "for author and editor," and the second "for editor." Review forms can be designated for a specific journal section, and editors will have the option to choose which form to use in assigning the review. In all cases, editors will have the option of including the reviews in corresponding with the author.</message> <message key="manager.reviewForms.noneChosen">None / Free Form Review</message> <message key="manager.reviewForms.noneCreated">No review forms have been created.</message> <message key="manager.reviewForms.preview">Preview Form</message> <message key="manager.reviewForms.title">Title</message> <message key="manager.sections.abstractsNotRequired">Do not require abstracts</message> <message key="manager.sections.assigned">This Section's Editors</message> <message key="manager.sections.confirmDelete">Are you sure you want to permanently delete this section?</message> <message key="manager.sections.alertDelete">Before this section can be deleted, you must move articles published within it into other sections.</message> <message key="manager.sections.create">Create Section</message> <message key="manager.sections.disableComments">Disable reader comments for this section.</message> <message key="manager.section.sectionEditorInstructions">Add a Section Editor to this section to have submissions automatically assigned to the Section Editor. (Otherwise, Section Editors can be assigned manually, after a submission comes in.) If added, a Section Editor can be automatically assigned to oversee the REVIEW (peer review) and/or the EDITING (copyediting, layout and proofreading) of submissions to this section. Section Editors are created by clicking Section Editors under Roles in Journal Management.</message> <message key="manager.sections.editorRestriction">Items can only be submitted by Editors and Section Editors.</message> <message key="manager.sections.editors">Section editors</message> <message key="manager.sections.form.abbrevRequired">An abbreviated title is required for the section</message> <message key="manager.sections.form.mustAllowPermission">Please ensure that at least one checkbox is checked for each Section Editor assignment.</message> <message key="manager.sections.form.reviewFormId">Please ensure that you have chosen a valid review form.</message> <message key="manager.sections.form.titleRequired">A title is required for the section.</message> <message key="manager.sections.hideAbout">Omit this section from About the Journal.</message> <message key="manager.sections.hideTocAuthor">Omit author names for section items from issues' table of contents.</message> <message key="manager.sections.hideTocTitle">Omit the title of this section from issues' table of contents.</message> <message key="manager.sections.identifyType">Identify items published in this section as a(n)</message> <message key="manager.sections.identifyTypeExamples">(For example, "Peer-reviewed Article", "Non-refereed Book Review", "Invited Commentary", etc.)</message> <message key="manager.sections.indexed">Indexed</message> <message key="manager.sections.noneCreated">No sections have been created.</message> <message key="manager.sections.open">Open Submissions</message> <message key="manager.sections.policy">Section Policy</message> <message key="manager.sections.readingTools">Reading Tools</message> <message key="manager.sections.reviewed">Peer Reviewed</message> <message key="manager.sections.submissionIndexing">Will not be included in the indexing of the journal</message> <message key="manager.sections.submissionReview">Will not be peer-reviewed</message> <message key="manager.section.submissionsToThisSection">Submissions made to this section of the journal</message> <message key="manager.sections.unassigned">Available Section Editors</message> <message key="manager.sections.wordCount">Word Count</message> <message key="manager.sections.wordCountInstructions">Limit abstract word counts for this section (0 for no limit): </message> <message key="manager.setup">Setup</message> <message key="manager.setup.aboutItemContent">Content</message> <message key="manager.setup.addAboutItem">Add About Item</message> <message key="manager.setup.addChecklistItem">Add Checklist Item</message> <message key="manager.setup.addContributor">Add Contributor</message> <message key="manager.setup.addItem">Add Item</message> <message key="manager.setup.addItemtoAboutJournal">Add Item to Appear in "About the Journal"</message> <message key="manager.setup.additionalContent">Additional Content</message> <message key="manager.setup.additionalContentDescription">Add the following content, using text/HTML, which will appear below the homepage image, if one is uploaded.</message> <message key="manager.setup.addNavItem">Add Item</message> <message key="manager.setup.addReviewerDatabaseLink">Add New Database Link</message> <message key="manager.setup.addSponsor">Add Sponsoring Organization</message> <message key="manager.setup.alternateHeader">Alternate Header</message> <message key="manager.setup.alternateHeaderDescription">Alternately, instead of title and logo, an HTML version of the header can be inserted into the text box below. Leave textbox blank if not required.</message> <message key="manager.setup.announcements">Announcements</message> <message key="manager.setup.announcementsDescription">Announcements may be published to inform readers of journal news and events. Published announcements will appear on the Announcements page.</message> <message key="manager.setup.announcementsIntroduction">Additional Information</message> <message key="manager.setup.announcementsIntroductionDescription">Enter any additional information that should be displayed to readers on the Announcements page.</message> <message key="manager.setup.appearInAboutJournal">(To appear in About the Journal) </message> <message key="manager.setup.authorCopyrightNotice">Copyright Notice</message> <message key="manager.setup.authorCopyrightNoticeAgree">Require authors to agree to the Copyright Notice in the submission process.</message> <message key="manager.setup.authorCopyrightNoticeDescription"><![CDATA[The Copyright Notice will appear in About the Journal. It should describe for readers and authors whether the copyright holder is the author, journal, or a third party. It should include additional licensing agreements (e.g. <a href="https://creativecommons.org" target="_new" class="action">Creative Commons</a> licenses) that grant rights to readers (see <a href="{$sampleCopyrightWordingUrl}" target="_new" class="action">examples</a>), and it should provide the means for securing permissions, if necessary, for the use of the journal's content.]]></message> <message key="manager.setup.authorGuidelines">Author Guidelines</message> <message key="manager.setup.authorGuidelinesDescription"><![CDATA[Set out for authors the bibliographic and formatting standards used for items submitted to the journal (e.g., <em>Publication Manual of the American Psychological Association</em>, 5th edition, 2001). It is often helpful to provide examples of the common citation formats for journals and books to be used in submissions. Also identify the types of appropriate Supplementary Files (e.g., data-sets, research instruments, etc.) which authors should be encouraged to upload, in addition to their submission, to enhance readers' engagement with their work.]]></message> <message key="manager.setup.competingInterests">Competing Interests</message> <message key="manager.setup.competingInterests.description"><![CDATA[Biomedical journals typically require authors and reviewers to declare if they have any competing interests with regard to their research (see <a href="http://www.plosbiology.org/static/competing.action" target="_new">PLoS Policy</a>).]]></message> <message key="manager.setup.competingInterests.guidelines">Guidelines for filing a Competing Interest statement</message> <message key="manager.setup.competingInterests.requireAuthors">Require submitting Authors to file a Competing Interest (CI) statement with their submission.</message> <message key="manager.setup.competingInterests.requireReviewers">Require Reviewers to file a CI statement with each peer review they submit.</message> <message key="manager.setup.contributor">Contributor</message> <message key="manager.setup.contributors">Sources of Support</message> <message key="manager.setup.contributorNoteDescription">This text will appear below the "Sources of Support" heading and above the list of names and urls for supporting organizations under "Journal Sponsorship" on the "About" page.</message> <message key="manager.setup.contributorsDescription">Additional agencies or organizations that provide financial or in-kind support for the journal will appear in About the Journal and may be accompanied by a note of acknowledgement.</message> <message key="manager.setup.history">Journal History</message> <message key="manager.setup.historyDescription">This text will appear in the "About" section of the journal website and can be used to describe changes in titles, editorial board, and other items of relevance to the journal's publication history.</message> <message key="manager.setup.copyediting">Copyeditors</message> <message key="manager.setup.copyeditInstructions">Copyedit Instructions</message> <message key="manager.setup.copyeditInstructionsDescription">The Copyedit Instructions will be made available to Copyeditors, Authors, and Section Editors in the Submission Editing stage. Below is a default set of instructions in HTML, which can be modified or replaced by the Journal Manager at any point (in HTML or plain text).</message> <message key="manager.setup.permissions.priorAgreement">Prior Agreement</message> <message key="manager.setup.permissions.display">Display</message> <message key="manager.setup.licenseURLDescription">Provide URL for license webpage, if available.</message> <message key="manager.setup.includeCopyrightStatement">Display the copyright statement with content (advisable for asserting an author-held copyright).</message> <message key="manager.setup.includeLicense">Display the license with published work.</message> <message key="manager.setup.resetPermissions">Reset Article Permissions</message> <message key="manager.setup.resetPermissions.description">Copyright statement and license information will be permanently attached to published content, ensuring that this data will not change in the case of a journal changing policies for new submissions. To reset stored permissions information already attached to published content, use the button below.</message> <message key="manager.setup.confirmResetLicense">Are you sure you wish to reset the license and copyright information attached to published content to the license configured in Journal Setup?</message> <message key="manager.setup.confirmResetLicenseChanged">You have changed the license and copyright information in Journal Setup. Please save these changes before resetting the permissions.</message> <message key="manager.setup.copyrightNotice">Copyright notice</message> <message key="manager.setup.copyrightYearBasis">Base new article's copyright year on</message> <message key="manager.setup.copyrightYearBasis.Article">Default year will be drawn from the article's publication date, as in "publish-as-you-go".</message> <message key="manager.setup.copyrightYearBasis.Issue">Default year will be drawn from the issue's publication date.</message> <message key="manager.setup.coverage">Coverage</message> <message key="manager.setup.coverageChronExamples">(E.g., European Renaissance; Jurassic Period; Third Trimester; etc.)</message> <message key="manager.setup.coverageChronProvideExamples">Provide examples of relevant chronological or historical terms for this field</message> <message key="manager.setup.coverageDescription">Refers to geo-spatial location, chronological or historical coverage, and/or characteristics of research sample.</message> <message key="manager.setup.coverageGeoExamples">(E.g., Iberian Peninsula; Stratosphere; Boreal Forest; etc.)</message> <message key="manager.setup.coverageGeoProvideExamples">Provide examples of relevant geo-spatial or geographical terms for this field</message> <message key="manager.setup.coverageResearchSampleExamples">(E.g., Age; Gender; Ethnicity; etc.)</message> <message key="manager.setup.coverageResearchSampleProvideExamples">Provide examples of research sample characteristics for this field</message> <message key="manager.setup.currentIssue">Current issue</message> <message key="manager.setup.customizingTheLook">Step 5. Customizing the Look</message> <message key="manager.setup.customTags">Custom tags</message> <message key="manager.setup.customTagsDescription">Custom HTML header tags to be inserted in the header of every page (e.g., META tags).</message> <message key="manager.setup.details">Details</message> <message key="manager.setup.details.description">Name of journal, ISSN, contacts, sponsors, and search engines.</message> <message key="manager.setup.disableUserRegistration">Journal Manager registers all users, with Editors or Section Editors able to register Reviewers alone.</message> <message key="manager.setup.discipline">Academic Discipline and Sub-Disciplines</message> <message key="manager.setup.disciplineDescription">Useful when journal crosses disciplinary boundaries and/or authors submit multidisciplinary items.</message> <message key="manager.setup.disciplineExamples">(E.g., History; Education; Sociology; Psychology; Cultural Studies; Law)</message> <message key="manager.setup.disciplineProvideExamples">Provide examples of relevant academic disciplines for this journal</message> <message key="manager.setup.displayCurrentIssue">Add the table of contents for the current issue (if available).</message> <message key="manager.setup.editorDecision">Editor Decision</message> <message key="manager.setup.editorialMembers">Go to Board Members and add Editorial Board and/or Review Board members. This can be done at any point in operating the journal.</message> <message key="manager.setup.editorialProcess1">One or more editors handle the basic steps without designated roles.</message> <message key="manager.setup.editorialProcess2">Managing Editor handles Submission Queue, and Table of Contents, while Section Editors handle Submission Review and Submission Editing.</message> <message key="manager.setup.editorialProcess3">Managing Editor handles Submission Queue, Submission Editing, and Table of Contents, while the Section Editors handle Submission Review.</message> <message key="manager.setup.editorialReviewBoard">Editorial / Review Board</message> <message key="manager.setup.editorialReviewBoardDescription">Journals have Editorial Boards to oversee the editorial direction of the journal, participate in the appointment of editors, and, by virtue of board members' reputations, give the journal some standing in the field. Review Boards play a similar role but in addition, they lead the peer review process. Review Board members will not have access to the journal's administrative system but will be added to the list of those available to do peer reviews.</message> <message key="manager.setup.emailBounceAddress">Bounce Address</message> <message key="manager.setup.emailBounceAddressDescription">Any undeliverable emails will result in an error message to this address.</message> <message key="manager.setup.emailBounceAddressDisabled"><![CDATA[<strong>Note:</strong> To activate this option, the site administrator must enable the <tt>allow_envelope_sender</tt> option in the OJS configuration file. Additional server configuration may be required to support this functionality (which may not be possible on all servers), as indicated in the OJS documentation.]]></message> <message key="manager.setup.emails">Email Identification</message> <message key="manager.setup.emailSignature">Signature</message> <message key="manager.setup.emailSignatureDescription">The prepared emails that are sent by the system on behalf of the journal will have the following signature added to the end. The body of the prepared emails are available for editing under Journal Management.</message> <message key="manager.setup.enableAnnouncements">Enable Journal Managers to add journal announcements.</message> <message key="manager.setup.enableAnnouncementsHomepage1">Display</message> <message key="manager.setup.enableAnnouncementsHomepage2">of the most recent announcements on the journal homepage.</message> <message key="manager.setup.enablePageNumber">Page numbers for items will be calculated and entered manually in the Table of Contents (e.g., 13-26).</message> <message key="manager.setup.enablePublicArticleId">Custom identifiers will be used to identify published items.</message> <message key="manager.setup.enablePublicGalleyId">Custom identifiers will be used to identify galleys (e.g. HTML or PDF files) for published items.</message> <message key="manager.setup.enablePublicIssueId">Custom identifiers will be used to identify issues.</message> <message key="manager.setup.enablePublicSuppFileId">Custom identifiers will be used to identify supplemental article files.</message> <message key="manager.setup.enableUserRegistration">Users can register themselves with the journal in one or more of the following roles:</message> <message key="manager.setup.enableUserRegistration.author">Authors (can submit materials to the journal)</message> <message key="manager.setup.enableUserRegistration.reader">Readers (will receive notifications and be counted as equivalent to a subscriber)</message> <message key="manager.setup.enableUserRegistration.reviewer">Reviewers (available for reviewing submissions)</message> <message key="manager.setup.focusAndScope">Focus and scope</message> <message key="manager.setup.focusAndScopeDescription">Enter a statement below, which will appear in About the Journal, that speaks to authors, readers, and librarians about the range of articles and other items which the journal will publish.</message> <message key="manager.setup.focusAndScopeOfJournal">Focus and Scope of Journal</message> <message key="manager.setup.focusScope">Focus and Scope</message> <message key="manager.setup.focusScopeDescription"><![CDATA[<strong>EXAMPLE HTML DATA</strong>]]></message> <message key="manager.setup.forAuthorsToIndexTheirWork">For Authors to Index Their Work</message> <message key="manager.setup.forAuthorsToIndexTheirWorkDescription"><![CDATA[OJS adheres to the <a href="http://www.openarchives.org/" target="_blank">Open Archives Initiative</a> Protocol for Metadata Harvesting, which is the emerging standard for providing well-indexed access to electronic research resources on a global scale. The authors will use a similar template to provide metadata for their submission. The Journal Manager should select the categories for indexing and present authors with relevant examples to assist them in indexing their work, separating terms with a semi-colon (e.g., term1; term2). The entries should be introduced as examples by using "E.g.," or "For example,".]]></message> <message key="manager.setup.form.contactEmailRequired">The primary contact email is required.</message> <message key="manager.setup.form.contactNameRequired">The primary contact name is required.</message> <message key="manager.setup.form.journalInitialsRequired">The journal initials are required.</message> <message key="manager.setup.form.journalTitleRequired">The journal title is required.</message> <message key="manager.setup.form.numReviewersPerSubmission">The number of reviewers per submission is required.</message> <message key="manager.setup.form.supportEmailRequired">The support email is required.</message> <message key="manager.setup.form.supportNameRequired">The support name is required.</message> <message key="manager.setup.frequencyOfPublication">Starting Point and Frequency</message> <message key="manager.setup.frequencyOfPublicationDescription">Set the initial issue/volume numbers and year for the first publication of the journal, as well as intended frequency for issue/volumes.</message> <message key="manager.setup.frequencyOfPublicationNote">Note: Leave items blank if not used with this journal, and editors can re-set numbers in the publishing process.</message> <message key="manager.setup.generalInformation">General Information</message> <message key="manager.setup.gettingDownTheDetails">Step 1. Getting Down the Details</message> <message key="manager.setup.guidelines">Guidelines</message> <message key="manager.setup.guidingSubmissions">Step 3. Guiding Submissions</message> <message key="manager.setup.homepageImage">Homepage image</message> <message key="manager.setup.homepageImageDescription">Add an image or graphic file to the middle of the page.</message> <message key="manager.setup.information">Information</message> <message key="manager.setup.information.description">Brief descriptions of the journal for librarians and prospective authors and readers are available in the "Information" section of the sidebar.</message> <message key="manager.setup.information.forAuthors">For Authors</message> <message key="manager.setup.information.forLibrarians">For Librarians</message> <message key="manager.setup.information.forReaders">For Readers</message> <message key="manager.setup.initialIssue">Initial issue</message> <message key="manager.setup.initialIssueDescription">Depending on the format selected, identify the issue, volume, and/or year of the first issue to be published with OJS:</message> <message key="manager.setup.institution">Institution</message> <message key="manager.setup.issnDescription"><![CDATA[The ISSN (International Standard Serial Number) is an eight-digit number which identifies periodical publications as such, including electronic serials. It is managed by a world wide network of National Centres coordinated by an International Centre based in Paris, backed by Unesco and the French Government. A number can be obtained from the <a href="http://www.issn.org" target="_new">ISSN web site</a>. This can be done at any point in operating the journal.]]></message> <message key="manager.setup.issuePerVolume">Issues per volume</message> <message key="manager.setup.itemsDescription">Navigation bar items can be added to the current set (Home, About, User Home, etc.) that appear at the top of the page.</message> <message key="manager.setup.itemsPerPage">Items per page</message> <message key="manager.setup.journalAbbreviation">Journal Abbreviation</message> <message key="manager.setup.journalArchiving">Journal Archiving</message> <message key="manager.setup.journalDescription">Journal Description</message> <message key="manager.setup.journalDescriptionDescription">Add a brief 20-25 word description in text/HTML which will appear just below the navigation links.</message> <message key="manager.setup.journalFavicon">Journal Favicon</message> <message key="manager.setup.journalFaviconDescription">Add a favicon for this journal to display alongside the navigation bar when users are visiting your site.</message> <message key="manager.setup.journalFaviconInvalid">Invalid favicon format. Accepted formats are .ico, .png, and .gif.</message> <message key="manager.setup.journalHomepageContent">Journal Homepage Content</message> <message key="manager.setup.journalHomepageContentDescription">By default, the homepage consists of navigation links. Additional homepage content can be appended by using one or all of the following options, which will appear in the order shown. Note that the current issue is always accessible through the Current link in the navigation bar.</message> <message key="manager.setup.journalHomepageHeader">Journal Homepage Header</message> <message key="manager.setup.journalHomepageHeader.altText">Journal Homepage Header</message> <message key="manager.setup.journalHomepageHeaderDescription">A graphic version of the journal's title and logo (as a .gif, .jpg, or .png file) can be uploaded for the homepage, which will replace the text version that otherwise appears.</message> <message key="manager.setup.journalInitials">Journal initials</message> <message key="manager.setup.journalLayout">Journal Layout</message> <message key="manager.setup.journalLayoutDescription">Choose a journal theme and select layout components here. A journal stylesheet may also be uploaded, which can be used to override style data in the system-wide stylesheets and theme stylesheet (if a theme is chosen).</message> <message key="manager.setup.journalLogo">Journal Logo</message> <message key="manager.setup.journalLogo.altText">Journal Logo</message> <message key="manager.setup.journalPageFooter">Journal Page Footer</message> <message key="manager.setup.journalPageFooterDescription">This is the footer of your journal. To change or update the footer, paste the HTML code in the textbox below. Examples could be another navigation bar, a counter, etc. This footer will appear on every page.</message> <message key="manager.setup.journalPageHeader">Journal Page Header</message> <message key="manager.setup.journalPageHeaderDescription">A graphic version of the journal's title and logo (.gif, .jpg, or .png file), possibly a smaller version of the one used on the homepage, can be uploaded to appear as a header on journal pages, which will replace the text version that otherwise appears.</message> <message key="manager.setup.journalPolicies">Step 2. Journal Policies</message> <message key="manager.setup.journalSetup">Journal Setup</message> <message key="manager.setup.journalSetupUpdated">Your journal setup has been updated.</message> <message key="manager.setup.journalStyleSheetInvalid">Invalid journal stylesheet format. Accepted format is .css.</message> <message key="manager.setup.journalTheme">Journal Theme</message> <message key="manager.setup.journalThumbnail">Journal thumbnail</message> <message key="manager.setup.journalTitle">Journal title</message> <message key="manager.setup.labelName">Label name</message> <message key="manager.setup.layoutAndGalleys">Layout Editors</message> <message key="manager.setup.layoutInstructions">Layout Instructions</message> <message key="manager.setup.layoutInstructionsDescription">Layout Instructions can be prepared for the formatting of publishing items in the journal and be entered below in HTML or plain text. They will be made available to the Layout Editor and Section Editor on the Editing page of each submission. (As each journal may employ its own file formats, bibliographic standards, style sheets, etc., a default set of instructions is not provided.)</message> <message key="manager.setup.layoutTemplates">Layout Templates</message> <message key="manager.setup.layoutTemplatesDescription">Templates can be uploaded to appear in Layout for each of the standard formats published in the journal (e.g., article, book review, etc.) using any file format (e.g., pdf, doc, etc.) with annotations added specifying font, size, margins, etc. to serve as a guide for Layout Editors and Proofreaders.</message> <message key="manager.setup.layoutTemplates.file">Template File</message> <message key="manager.setup.layoutTemplates.title">Title</message> <message key="manager.setup.lists">Lists</message> <message key="manager.setup.listsDescription">Enter the maximum number of items (for example, submissions, users, or editing assignments) that appear on each page of a list, and the number of pages links to display on each page.</message> <message key="manager.setup.lockssEnable"><![CDATA[Enable LOCKSS to store and distribute journal content at participating libraries via a LOCKSS <a href="{$lockssUrl}" target="_blank">Publisher Manifest</a> page. A LOCKSS license will appear in About the Journal under Archiving:]]></message> <message key="manager.setup.lockssLicenses"><![CDATA[See <a href="http://www.lockss.org/community/publishers-titles-gln/" target="_blank">other versions of a LOCKSS license</a>.]]></message> <message key="manager.setup.lockssRegister"><![CDATA[Identify 6-10 libraries that will register and cache the journal. For example, turn to institutions where editors or Board members work and/or institutions already participating in LOCKSS. See <a href="http://www.lockss.org/community/" target="_blank">the LOCKSS community</a>. Use the prepared invitations for (i) <a href="{$lockssExistingArchiveUrl}" target="_blank">libraries participating in LOCKSS</a> or (ii) <a href="{$lockssNewArchiveUrl}" target="_blank">libraries not yet participating in LOCKSS</a>.]]></message> <message key="manager.setup.look">The Look</message> <message key="manager.setup.look.description">Homepage header, content, journal header, footer, navigation bar, and style sheet.</message> <message key="manager.setup.mailingAddressDescription">The journal's physical location and mailing address.</message> <message key="manager.setup.management">Management</message> <message key="manager.setup.management.description">Access and security, scheduling, announcements, copyediting, layout, and proofreading.</message> <message key="manager.setup.managementOfBasicEditorialSteps">Management of Basic Editorial Steps</message> <message key="manager.setup.managingPublishingSetup">Management and Publishing Setup</message> <message key="manager.setup.managingTheJournal">Step 4. Managing the Journal</message> <message key="manager.setup.navigationBar">Navigation Bar</message> <message key="manager.setup.navigationBarDescription">Add or remove additional navigation bar items.</message> <message key="manager.setup.navItemIsAbsolute">URL is an absolute URL (e.g., "http://www.example.com") rather than a path relative to the site (e.g., "/manager/setup")</message> <message key="manager.setup.navItemIsLiteral">The label value is a literal string (e.g., "Journal Setup") rather than a localization message key (e.g., "manager.setup")</message> <message key="manager.setup.noImageFileUploaded">No image file uploaded.</message> <message key="manager.setup.noStyleSheetUploaded">No style sheet uploaded.</message> <message key="manager.setup.note">Note</message> <message key="manager.setup.notifications">Notification of Author Submission</message> <message key="manager.setup.notifications.copyPrimaryContact">Send a copy to the journal's primary contact, identified in Setup Step 1.</message> <message key="manager.setup.notifications.copySpecifiedAddress">Send a copy to this email address:</message> <message key="manager.setup.notifications.description">On completing the submission process, authors are automatically sent an acknowledgement email (which can be viewed and edited in Prepared Emails). In addition, a copy of the acknowledgement email can be sent as follows:</message> <message key="manager.setup.notifications.submissionAckDisabled"><![CDATA[<strong>Note:</strong> The submission acknowledgement email is currently disabled. To use this feature, enable the SUBMISSION_ACK email in <a class="action" href="{$preparedEmailsUrl}">Prepared Emails</a>.]]></message> <message key="manager.setup.notifyAllAuthorsOnDecision">When using the Notify Author email, include the email addresses of all co-authors for multiple-author submissions, and not just the submitting user.</message> <message key="manager.setup.noUseCopyeditors">Copyediting will be undertaken by an Editor or Section Editor assigned to the submission.</message> <message key="manager.setup.noUseLayoutEditors">An Editor or Section Editor assigned to the submission will prepare the HTML, PDF, etc., files.</message> <message key="manager.setup.noUseProofreaders">An Editor or Section Editor assigned to the submission will check the galleys.</message> <message key="manager.setup.numPageLinks">Page links</message> <message key="manager.setup.onlineAccessManagement">Access to Journal Content</message> <message key="manager.setup.onlineIssn">Online ISSN</message> <message key="manager.setup.openAccess">The journal will provide open access to its contents.</message> <message key="manager.setup.openAccessPolicy">Open Access Policy</message> <message key="manager.setup.openAccessPolicyDescription">If the journal will provide readers with immediate free access to all published content, enter an Open Access Policy which will appear in About the Journal under Policies.</message> <message key="manager.setup.pageNumberIdentifier">Page Number Option</message> <message key="manager.setup.peerReviewDescription">Outline the journal's peer review policy and processes for readers and authors, including the number of reviewers typically used in reviewing a submission, the criteria by which reviewers are asked to judge submissions, typical time taken to conduct the reviews, and the principles for recruiting reviewers. This will appear in About the Journal.</message> <message key="manager.setup.peerReviewPolicy">Peer Review</message> <message key="manager.setup.peerReviewPolicy2">Peer review policy</message> <message key="manager.setup.policies">Policies</message> <message key="manager.setup.policies.description">Focus, peer review, sections, privacy, security, and additional about items.</message> <message key="manager.setup.principalContact">Principal Contact</message> <message key="manager.setup.principalContactDescription">This position, which can be treated as a principal editorship, managing editorship, or administrative staff position, will be listed on the homepage of the journal under Contact, along with the Technical Support Contact.</message> <message key="manager.setup.printIssn">Print ISSN</message> <message key="manager.setup.privacyStatement">Privacy Statement</message> <message key="manager.setup.privacyStatement2">Privacy statement</message> <message key="manager.setup.privacyStatementDescription">This statement will appear in About the Journal, as well as on the Author Submission and Notification sign-up pages. Below is a recommended privacy policy, which can be revised at any point.</message> <message key="manager.setup.proofingInstructions">Proofing Instructions</message> <message key="manager.setup.proofingInstructionsDescription">The Proofreading Instructions will be made available to Proofreaders, Authors, Layout Editors, and Section Editors in the Submission Editing stage. Below is a default set of instructions in HTML, which can be edited or replaced by the Journal Manager at any point (in HTML or plain text).</message> <message key="manager.setup.proofreading">Proofreaders</message> <message key="manager.setup.provideRefLinkInstructions">Provide Layout Editors with instructions.</message> <message key="manager.setup.publicationFormat">Format</message> <message key="manager.setup.publicationFormatDescription">The journal will use the following elements to identify issues (which can be overridden for individual issues).</message> <message key="manager.setup.publicationFormatNumber">Number</message> <message key="manager.setup.publicationFormatTitle">Title</message> <message key="manager.setup.publicationFormatVolume">Volume</message> <message key="manager.setup.publicationFormatYear">Year</message> <message key="manager.setup.publicationSchedule">Publication Schedule</message> <message key="manager.setup.publicationScheduleDescription"><![CDATA[Journal items can be published collectively, as part of an issue with its own Table of Contents. Alternatively, individual items can be published as soon as they are ready, by adding them to the "current" volume's Table of Contents. Provide readers, in About the Journal, with a statement about the system this journal will use and its expected frequency of publication.]]></message> <message key="manager.setup.publicationScheduling">Publication Scheduling</message> <message key="manager.setup.publicIdentifier">Identification of Journal Content</message> <message key="manager.setup.publisher">Publisher</message> <message key="manager.setup.publisherNoteDescription">This text will appear below the "Publisher" heading and above the publisher name/url under "Journal Sponsorship" on the "About" page.</message> <message key="manager.setup.publisherDescription">The name of the organization publishing the journal will appear in About the Journal.</message> <message key="manager.setup.referenceLinking">Reference Linking</message> <message key="manager.setup.refLinkInstructions.description">Layout Instructions for Reference Linking</message> <message key="manager.setup.registerJournalForIndexing">Register Journal for Indexing (Metadata Harvesting)</message> <message key="manager.setup.restrictArticleAccess">Users must be registered and log in to view open access content.</message> <message key="manager.setup.restrictSiteAccess">Users must be registered and log in to view the journal site.</message> <message key="manager.setup.reviewerDatabaseLink">Potential Reviewer Database</message> <message key="manager.setup.reviewerDatabaseLink.desc">Add to the Select Reviewer page a link to a relevant literature database that can be searched for potential reviewers and is open to editors without subscription.</message> <message key="manager.setup.reviewGuidelines">Review Guidelines</message> <message key="manager.setup.reviewGuidelinesDescription"><![CDATA[The Review Guidelines will provide reviewers with criteria for judging a submission's suitability for publication in the journal, and can include any special instructions for preparing an effective and helpful review. In conducting the review, reviewers are presented with with two open text boxes, the first "for author and editor," and the second "for editor." Alternatively, the Journal Manager can create a peer review form under <a href="{$reviewFormsUrl}" class="action">Review Forms</a>. In all cases, editors will have the option of including the reviews in corresponding with the author.]]></message> <message key="manager.setup.reviewOptions">Review Options</message> <message key="manager.setup.reviewOptions.automatedReminders">Automated email reminders (available in OJS's default Emails) can be sent to reviewers at two points (while the editor can always email the reviewer directly as well)</message> <message key="manager.setup.reviewOptions.automatedRemindersDisabled"><![CDATA[<strong>Note:</strong> To activate these options, the site administrator must enable the <tt>scheduled_tasks</tt> option in the OJS configuration file. Additional server configuration may be required to support this functionality (which may not be possible on all servers), as indicated in the OJS documentation.]]></message> <message key="manager.setup.reviewOptions.blindReview">Blind Review</message> <message key="manager.setup.reviewOptions.noteOnModification">Can be modified during the editorial process.</message> <message key="manager.setup.reviewOptions.numWeeksPerReview">The typical period of time allowed for reviews</message> <message key="manager.setup.reviewOptions.onQuality">Editors will rate reviewers on a five-point quality scale after each review.</message> <message key="manager.setup.reviewOptions.remindForInvite1">If reviewer has not responded to a review request within</message> <message key="manager.setup.reviewOptions.remindForInvite2">days.</message> <message key="manager.setup.reviewOptions.remindForSubmit1">If reviewer has not submitted a recommendation within</message> <message key="manager.setup.reviewOptions.remindForSubmit2">days after review's due date.</message> <message key="manager.setup.reviewOptions.restrictReviewerFileAccess">Reviewers will have access to the submission file only after agreeing to review it.</message> <message key="manager.setup.reviewOptions.reviewerAccess">Reviewer Access</message> <message key="manager.setup.reviewOptions.reviewerAccessKeysEnabled">Enable one-click reviewer access.</message> <message key="manager.setup.reviewOptions.reviewerAccessKeysEnabled.description"><![CDATA[<strong>Note:</strong> The email invitation to reviewers will contain a special URL that takes invited reviewers directly to the Review page for the submission (with access to any other pages requiring them to log in). For security reasons with this option, editors are not able to modify email addresses or add CCs or BCCs prior to sending invitations to reviewers.]]></message> <message key="manager.setup.reviewOptions.reviewerRatings">Reviewer Ratings</message> <message key="manager.setup.reviewOptions.reviewerReminders">Reviewer Reminders</message> <message key="manager.setup.reviewOptions.reviewTime">Review Time</message> <message key="manager.setup.reviewOptions.showEnsuringLink"><![CDATA[Provide links to <a href="javascript:openHelp('{$blindReviewHelpId}')" class="action">Ensuring a Blind Review</a> on pages where authors and reviewers upload files.]]></message> <message key="manager.setup.reviewPolicy">Review Policy</message> <message key="manager.setup.reviewProcess">Review Process</message> <message key="manager.setup.reviewProcessDescription"><![CDATA[OJS supports two models for managing the review process. The Standard Review Process is recommended because it steps reviewers through the process, ensures a complete review history for each submission, and takes advantage of automatic reminder notification, and standard recommendations for submissions (Accept; Accept with revisions; Submit for review; Submit elsewhere; Decline; See comments).<br /><br />Select one of the following:]]></message> <message key="manager.setup.reviewProcessEmail">Email-Attachment Review Process</message> <message key="manager.setup.reviewProcessStandard">Standard Review Process</message> <message key="manager.setup.reviewProcessStandardDescription">Editors will email selected Reviewers the title and abstract of the submission, as well as an invitation to log into the journal web site to complete the review. Reviewers enter the journal web site to agree to do the review, to download submissions, submit their comments, and select a recommendation.</message> <message key="manager.setup.searchEngineIndexing">Search Engine Indexing</message> <message key="manager.setup.searchEngineIndexingDescription">To assist the users of search engines in discovering this journal, provide a brief description of the journal and relevant keywords (separated by semicolons).</message> <message key="manager.setup.sectionsAndSectionEditors">Sections and Section Editors</message> <message key="manager.setup.sectionsDefaultSectionDescription">(If sections are not added, then items are submitted to the Articles section by default.)</message> <message key="manager.setup.sectionsDescription"><![CDATA[To create or modify sections for the journal (e.g., Articles, Book Reviews, etc.), go to Section Management.<br /><br />Authors on submitting items to the journal will designate...]]></message> <message key="manager.setup.securitySettings">Access and Security Settings</message> <message key="manager.setup.securitySettingsDescription">OJS provides a number of security-related options that can be used to restrict the journal's contents, and maintain additional information about submissions for auditing purposes.</message> <message key="manager.setup.selectEditorDescription">The journal editor who will see it through the editorial process.</message> <message key="manager.setup.selectSectionDescription">The journal section for which the item will be considered.</message> <message key="manager.setup.showGalleyLinksDescription">Always show galley links and indicate restricted access.</message> <message key="manager.setup.siteAccess">Additional Site and Article Access Restrictions</message> <message key="manager.setup.sponsors">Sponsoring Organizations</message> <message key="manager.setup.sponsorNoteDescription">This text will appear below the "Sponsors" heading and above the list of sponsor names and urls under "Journal Sponsorship" on the "About" page.</message> <message key="manager.setup.sponsorsDescription">The name of the organizations (e.g., scholarly associations, university departments, cooperatives, etc.) sponsoring the journal will appear in About the Journal and may be accompanied by a note of acknowledgement.</message> <message key="manager.setup.stepsToJournalSite">Five Steps to a Journal Web Site</message> <message key="manager.setup.subjectClassification">Subject Classification</message> <message key="manager.setup.subjectClassificationExamples">(E.g., Mathematics Subject Classification; Library of Congress Classification)</message> <message key="manager.setup.subjectClassificationURLValid">Please provide a valid remote URL (include http://).</message> <message key="manager.setup.subjectExamples">(E.g., Photosynthesis; Black Holes; Four-Color Map Problem; Bayesian Theory)</message> <message key="manager.setup.subjectKeywordTopic">Keywords</message> <message key="manager.setup.subjectProvideExamples">Provide examples of keywords or topics as a guide for authors</message> <message key="manager.setup.submissionGuidelines">Submission guidelines</message> <message key="manager.setup.submissionPreparationChecklist">Submission Preparation Checklist</message> <message key="manager.setup.submissionPreparationChecklistDescription">On making a submission to the journal, authors are first asked to check each item on the Submission Preparation Checklist as completed, before proceeding. The checklist also appears in the Author Guidelines, under About the Journal. The list can be edited below, but all items on the list will require a checkmark before authors can proceed with their submission.</message> <message key="manager.setup.submissions">Submissions</message> <message key="manager.setup.submissions.description">Author guidelines, copyright, and indexing (including registration).</message> <message key="manager.setup.subscription">The journal will require subscriptions to access some or all of its contents.</message> <message key="manager.setup.subscriptionDescription">This requires the assignment of a Subscription Manager who has access to the subscription module, which includes additional open access, self-archiving, and email notification options.</message> <message key="manager.setup.noPublishing">OJS will not be used to publish the journal's contents online.</message> <message key="manager.setup.technicalSupportContact">Technical Support Contact</message> <message key="manager.setup.technicalSupportContactDescription">This person will be listed on the journal's Contact page for the use of editors, authors, and reviewers, and should have experience working through the system from the perspective of all of its roles. As this journal system requires very little technical support, this should be seen as a part-time assignment. There may be occasions, for example, when authors and reviewers have difficulties with the instructions or file formats, or there's a need to ensure that the journal is regularly backed up on the server.</message> <message key="manager.setup.typeExamples">(E.g., Historical Inquiry; Quasi-Experimental; Literary Analysis; Survey/Interview)</message> <message key="manager.setup.typeMethodApproach">Type (Method/Approach)</message> <message key="manager.setup.typeProvideExamples">Provide examples of relevant research types, methods, and approaches for this field</message> <message key="manager.setup.uniqueIdentifier">Unique Identifier</message> <message key="manager.setup.uniqueIdentifierDescription">Articles and issues can be tagged with an identification number or string, employing a registration system such as the Digital Object Identifier System (DOI).</message> <message key="manager.setup.useCopyeditors">A Copyeditor will be assigned to work with each submission.</message> <message key="manager.setup.useEditorialReviewBoard">An editorial/review board will be used by the journal.</message> <message key="manager.setup.useImageLogo">Logo image</message> <message key="manager.setup.useThumbnail">Thumbnail</message> <message key="manager.setup.useImageTitle">Title image</message> <message key="manager.setup.useJournalStyleSheet">Journal style sheet</message> <message key="manager.setup.useLayoutEditors">A Layout Editor will be assigned to prepare the HTML, PDF, etc., files for electronic publication.</message> <message key="manager.setup.useProofreaders">A Proofreader will be assigned to check (along with the authors) the galleys prior to publication.</message> <message key="manager.setup.userRegistration">User Registration</message> <message key="manager.setup.useTextTitle">Title text</message> <message key="manager.setup.volumePerYear">Volumes per year</message> <message key="manager.statistics.defaultMetricDescription"> Your journal is configured to record more than one usage metric. Usage statistics will be displayed in severeral contexts. There are cases where a single usage statistic must be used, e.g. to display an ordered list of most-used articles or to rank search results. Please select one of the configured metrics as a default. </message> <message key="manager.statistics.reports">Report Generator</message> <message key="manager.statistics.reports.aggregationColumns">Aggregate stats by:</message> <message key="manager.statistics.reports.optionalColumns.description">Items in italic and marked with * represent data that is optional to the current way of counting statistics in OJS (metric type). You might have that data or not, depending on your statistics plugin configuration.</message> <message key="manager.statistics.reports.defaultReportTemplates">Default report templates</message> <message key="manager.statistics.reports.defaultReport.articleDownloads">Article file downloads</message> <message key="manager.statistics.reports.defaultReport.articleAbstract">Article abstract page views</message> <message key="manager.statistics.reports.defaultReport.articleAbstractAndDownloads">Article abstract and downloads</message> <message key="manager.statistics.reports.defaultReport.issueDownloads">Issue file downloads</message> <message key="manager.statistics.reports.defaultReport.issueTableOfContents">Issue table of contents page views</message> <message key="manager.statistics.reports.defaultReport.issueTableOfContentsAndDownloads">Issue table of contents and downloads</message> <message key="manager.statistics.reports.defaultReport.journalIndexPageViews">Journal main page views</message> <message key="manager.statistics.reports.description">OJS generates reports that track the details associated with processing submissions to the journal from the perspective of submissions, editors, reviewers, and sections, over a given period of time. Reports are generated in CSV format which requires a spreadsheet application to view.</message> <message key="manager.statistics.reports.generateReport">Generate custom report</message> <message key="manager.statistics.reports.advancedOptions">Advanced Options</message> <message key="manager.statistics.reports.advancedOptions.label">Customize columns, filter and ordering options. Changing any of these options might change the expected report template result.</message> <message key="manager.statistics.reports.columns">Columns</message> <message key="manager.statistics.reports.columns.description">Define the columns that will be used to build the report. The columns you select here not only define which data will be presented inside the reports, but also defines the aggregation level of the statistics. For example, if you choose ID, Type and Month columns, the report will sum all views from an object from one month and will present that data in one row. If you choose Day instead of Month, each object will have a row for each day.</message> <message key="manager.statistics.reports.filters">Filters</message> <message key="manager.statistics.reports.objectNotFound">Object not found in database</message> <message key="manager.statistics.reports.objectType">Object Type</message> <message key="manager.statistics.reports.objectId">Object id</message> <message key="manager.statistics.reports.objectId.label">Define one or more object ids, comma separated (e.g. 1,2,3,4,5).</message> <message key="manager.statistics.reports.yesterday">Yesterday</message> <message key="manager.statistics.reports.currentMonth">Current month</message> <message key="manager.statistics.reports.orderBy">Order by</message> <message key="manager.statistics.reports.orderDir">Direction</message> <message key="manager.statistics.reports.orderDir.asc">Ascending</message> <message key="manager.statistics.reports.orderDir.desc">Descending</message> <message key="manager.statistics.reports.month.label">Use the YYYYMM format.</message> <message key="manager.statistics.reports.day.label">Use the YYYYMMDD format.</message> <message key="manager.statistics.reports.cities.label">One or more city names, comma separated (e.g. City Name 1,City Name 2)</message> <message key="manager.statistics.reports.form.columnsRequired">You have to select at least one column to generate the report.</message> <message key="manager.statistics.reports.reportUrl">Report URL</message> <message key="manager.statistics.reports.reportUrl.label">The following url can be used to generate the report with this current form settings. Just copy it, paste into your browser and enter. You can use your favorites to store your custom report url generator.</message> <message key="manager.statistics.reports.filters.byContext">By context</message> <message key="manager.statistics.reports.filters.byContext.description">Narrow results by context (issue and/or article).</message> <message key="manager.statistics.reports.filters.byObject">By object type and/or object id</message> <message key="manager.statistics.reports.filters.byObject.description">Narrow results by object type (journal, issue, article, pdf galleys, other galleys) and/or by one or more object id(s).</message> <message key="manager.statistics.reports.filters.byTime">Select report range</message> <message key="manager.statistics.reports.filters.byTime.dimensionSelector">Or select range by:</message> <message key="manager.statistics.reports.filters.byLocation">By geo location</message> <message key="manager.statistics.reports.filters.byLocation.description">Narrow results by country, region and/or city.</message> <message key="manager.statistics.statistics">Journal Statistics</message> <message key="manager.statistics.statistics.articleViews">Article View Counts (for Authors only)</message> <message key="manager.statistics.statistics.count.accept">Accept</message> <message key="manager.statistics.statistics.count.decline">Decline</message> <message key="manager.statistics.statistics.count.revise">Resubmit</message> <message key="manager.statistics.statistics.daysPerReview">Days to review</message> <message key="manager.statistics.statistics.daysToPublication">Days to publication</message> <message key="manager.statistics.statistics.description">OJS calculates the following statistics for each journal. The "days to review" is calculated from date of submission (or designation of Review Version) to the initial Editor Decision, while the "days to publish" is measured for accepted submissions from its original uploading to its publication.</message> <message key="manager.statistics.statistics.itemsPublished">Items published</message> <message key="manager.statistics.statistics.makePublic">Check items to be made available to readers in About the Journal.</message> <message key="manager.statistics.statistics.note">Note: Percentages for peer reviewed submissions may not add up to 100%, as items resubmitted are either accepted, declined, or still in process.</message> <message key="manager.statistics.statistics.numIssues">Issues published</message> <message key="manager.statistics.statistics.numSubmissions">Total submissions</message> <message key="manager.statistics.statistics.peerReviewed">Peer reviewed</message> <message key="manager.statistics.statistics.registeredReaders">Registered readers</message> <message key="manager.statistics.statistics.registeredUsers">Registered users</message> <message key="manager.statistics.statistics.reviewerCount">No. assigned</message> <message key="manager.statistics.statistics.reviewers">Reviewers</message> <message key="manager.statistics.statistics.reviewerScore">Editor score</message> <message key="manager.statistics.statistics.reviewsPerReviewer">No. of reviews</message> <message key="manager.statistics.statistics.selectSections">Select the sections for calculating this journal's peer-reviewed statistics.</message> <message key="manager.statistics.statistics.subscriptions">Subscriptions</message> <message key="manager.subscriptionPolicies">Subscription Policies</message> <message key="manager.subscriptionPolicies.authorSelfArchive">Author Self-Archiving Policy</message> <message key="manager.subscriptionPolicies.authorSelfArchiveDescription">The following Author Self-Archiving Policy will be included in About the Journal under Policies.</message> <message key="manager.subscriptionPolicies.delayedOpenAccess">Delayed Open Access</message> <message key="manager.subscriptionPolicies.delayedOpenAccessDescription">With delayed open access, editors are still able to designate specific articles within an issue for immediate open access.</message> <message key="manager.subscriptionPolicies.delayedOpenAccessDescription1">The back issues of this journal will be available in an open access format</message> <message key="manager.subscriptionPolicies.delayedOpenAccessDescription2">month(s) after an issue is published.</message> <message key="manager.subscriptionPolicies.delayedOpenAccessDurationValid">Please select a valid duration length.</message> <message key="manager.subscriptionPolicies.delayedOpenAccessPolicyDescription">The following Delayed Open Access Policy will be posted in About the Journal under Policies.</message> <message key="manager.subscriptionPolicies.expiry">Subscription Expiry</message> <message key="manager.subscriptionPolicies.expiryDescription">Upon subscription expiry, readers may be denied access to all subscription content or may continue to retain access to subscription content published prior to the subscription expiry date.</message> <message key="manager.subscriptionPolicies.expiryFull">Full expiry</message> <message key="manager.subscriptionPolicies.expiryFullDescription">Readers are denied access to all subscription content upon subscription expiry.</message> <message key="manager.subscriptionPolicies.expiryPartial">Partial expiry</message> <message key="manager.subscriptionPolicies.expiryPartialDescription">Readers are denied access to recently published subscription content, but retain access to subscription content published prior to the subscription expiry date.</message> <message key="manager.subscriptionPolicies.expiryReminderAfterWeeks1">Notify subscribers by email</message> <message key="manager.subscriptionPolicies.expiryReminderAfterWeeks2">week(s) after subscription expiry.</message> <message key="manager.subscriptionPolicies.expiryReminderBeforeWeeks1">Notify subscribers by email</message> <message key="manager.subscriptionPolicies.expiryReminderBeforeWeeks2">week(s) before subscription expiry.</message> <message key="manager.subscriptionPolicies.expiryReminders">Subscription Expiry Reminders</message> <message key="manager.subscriptionPolicies.expiryRemindersDescription">Automated email reminders (available for editing by Journal Managers in OJS's Prepared Emails) can be sent to subscribers both before and after a subscription has expired.</message> <message key="manager.subscriptionPolicies.expiryRemindersDisabled"><![CDATA[<strong>Note:</strong> To activate these options, the site administrator must enable the <tt>scheduled_tasks</tt> option in the OJS configuration file. Additional server configuration may be required to support this functionality (which may not be possible on all servers), as indicated in the OJS documentation.]]></message> <message key="manager.subscriptionPolicies.expirySelectOne">Select one of the following:</message> <message key="manager.subscriptionPolicies.htmlInstructions"><![CDATA[HTML can be used in textarea (for font size, color, etc.), with "returns" treated as <tt><br></tt>; HTML editor works with Firefox browsers.]]></message> <message key="manager.subscriptionPolicies.numMonthsAfterSubscriptionExpiryReminderValid">Please select a valid value for the number of months after subscription expiry.</message> <message key="manager.subscriptionPolicies.numMonthsBeforeSubscriptionExpiryReminderValid">Please select a valid value for the number of months before subscription expiry.</message> <message key="manager.subscriptionPolicies.numWeeksAfterSubscriptionExpiryReminderValid">Please select a valid value for the number of weeks after subscription expiry.</message> <message key="manager.subscriptionPolicies.numWeeksBeforeSubscriptionExpiryReminderValid">Please select a valid value for the number of weeks before subscription expiry.</message> <message key="manager.subscriptionPolicies.openAccessNotificationDescription">Registered readers will have the option of receiving the table of contents by email when an issue becomes open access.</message> <message key="manager.subscriptionPolicies.openAccessNotificationDisabled"><![CDATA[<strong>Note:</strong> To activate this option, the site administrator must enable the <tt>scheduled_tasks</tt> option in the OJS configuration file. Additional server configuration may be required to support this functionality (which may not be possible on all servers), as indicated in the OJS documentation.]]></message> <message key="manager.subscriptionPolicies.onlinePaymentNotifications">Online Payment Notifications</message> <message key="manager.subscriptionPolicies.onlinePaymentNotificationsDescription">Automated email notifications (available for editing by Journal Managers in OJS's Prepared Emails) can be sent to the Subscription Manager upon the completion of subscription online payments.</message> <message key="manager.subscriptionPolicies.enableSubscriptionOnlinePaymentNotificationPurchaseIndividual">Notify Subscription Manager by email upon online purchase of an Individual subscription.</message> <message key="manager.subscriptionPolicies.enableSubscriptionOnlinePaymentNotificationPurchaseInstitutional">Notify Subscription Manager by email upon online purchase of an Institutional subscription (recommended).</message> <message key="manager.subscriptionPolicies.enableSubscriptionOnlinePaymentNotificationRenewIndividual">Notify Subscription Manager by email upon online renewal of an Individual subscription.</message> <message key="manager.subscriptionPolicies.enableSubscriptionOnlinePaymentNotificationRenewInstitutional">Notify Subscription Manager by email upon online renewal of an Institutional subscription.</message> <message key="manager.subscriptionPolicies.onlinePaymentPurchaseInstitutionalDescription"><![CDATA[<strong>Note:</strong> Institutional subscriptions purchased online require approval of the provided domain and IP ranges and activation of the subscription by the Subscription Manager.]]></message> <message key="manager.subscriptionPolicies.onlinePaymentDisabled"><![CDATA[<strong>Note:</strong> To enable these options, the Journal Manager must enable the online payments module, including online payments for subscriptions, under Reader Fees.]]></message> <message key="manager.subscriptionPolicies.openAccessOptions">Open Access Options For Subscription Journals</message> <message key="manager.subscriptionPolicies.openAccessOptionsDescription">Subscription journals can provide "delayed open access" to their published content, as well as permit "author self-archiving" (both of which increase readership and citation of content).</message> <message key="manager.subscriptionPolicies.subscriptionAdditionalInformation">Subscription Information</message> <message key="manager.subscriptionPolicies.subscriptionAdditionalInformationDescription">The Subscription Types and fee structure will be automatically placed under Subscriptions on the About the Journal page, along with the name and contact information for the Subscription Manager. Additional information about subscriptions, such as methods of payment or support for subscribers in developing countries, can be added here.</message> <message key="manager.subscriptionPolicies.subscriptionContact">Subscription Manager</message> <message key="manager.subscriptionPolicies.subscriptionContactDescription">The contact listed under Subscriptions in About the Journal.</message> <message key="manager.subscriptionPolicies.subscriptionContactEmailValid">Please enter a valid email.</message> <message key="manager.subscriptionPolicies.subscriptionPoliciesSaved">Your subscription policy settings have been updated.</message> <message key="manager.subscriptions">Subscriptions</message> <message key="manager.individualSubscriptions">Individual Subscriptions</message> <message key="manager.institutionalSubscriptions">Institutional Subscriptions</message> <message key="manager.subscriptions.confirmDelete">Are you sure you want to delete this subscription?</message> <message key="manager.subscriptions.summary">Subscriptions Summary</message> <message key="manager.subscriptions.create">Create New Subscription</message> <message key="manager.subscriptions.createTitle">Create</message> <message key="manager.subscriptions.renew">Renew</message> <message key="manager.subscriptions.dateEnd">End</message> <message key="manager.subscriptions.dateEndSearch">End Date</message> <message key="manager.subscriptions.dateStart">Start</message> <message key="manager.subscriptions.dateStartSearch">Start Date</message> <message key="manager.subscriptions.domain">Domain</message> <message key="manager.subscriptions.edit">Edit Subscription</message> <message key="manager.subscriptions.editTitle">Edit</message> <message key="manager.subscriptions.withStatus">With Status</message> <message key="manager.subscriptions.allStatus">All</message> <message key="manager.subscriptions.form.status">Status</message> <message key="manager.subscriptions.form.statusRequired">A subscription status is required.</message> <message key="manager.subscriptions.form.statusValid">Please select a valid subscription status.</message> <message key="manager.subscriptions.form.typeId">Subscription type</message> <message key="manager.subscriptions.form.typeIdRequired">A subscription type is required.</message> <message key="manager.subscriptions.form.typeIdValid">Please select a valid subscription type.</message> <message key="manager.subscriptions.form.dateRemindedBefore">Pre-expiry Reminder Sent</message> <message key="manager.subscriptions.form.dateRemindedAfter">Post-expiry Reminder Sent</message> <message key="manager.subscriptions.form.dateStart">Start date</message> <message key="manager.subscriptions.form.dateStartRequired">A subscription start date is required.</message> <message key="manager.subscriptions.form.dateStartValid">Please select a valid subscription start date.</message> <message key="manager.subscriptions.form.dateEnd">End date</message> <message key="manager.subscriptions.form.dateEndRequired">A subscription end date is required.</message> <message key="manager.subscriptions.form.dateEndValid">Please select a valid subscription end date.</message> <message key="manager.subscriptions.form.userProfileInstructions">Note: All changes below are to user's system-wide profile.</message> <message key="manager.subscriptions.form.userId">User</message> <message key="manager.subscriptions.form.userContact">Contact</message> <message key="manager.subscriptions.form.userIdRequired">A user is required.</message> <message key="manager.subscriptions.form.userIdValid">Please select a valid user.</message> <message key="manager.subscriptions.form.userCountryValid">Please select a valid country.</message> <message key="manager.subscriptions.form.notifyEmail">Send the user an email with their username and subscription details.</message> <message key="manager.subscriptions.form.notifyEmailValid">Please use the checkbox provided.</message> <message key="manager.subscriptions.form.membership">Membership</message> <message key="manager.subscriptions.form.referenceNumber">Reference Number</message> <message key="manager.subscriptions.form.membershipInstructions">Enter membership information if the subscription type requires that subscribers belong to an association or organization.</message> <message key="manager.subscriptions.form.membershipRequired">The selected subscription type requires membership information.</message> <message key="manager.subscriptions.form.notes">Notes</message> <message key="manager.subscriptions.form.domain">Domain</message> <message key="manager.subscriptions.form.institutionName">Institution name</message> <message key="manager.subscriptions.form.institutionNameRequired">An institution name is required.</message> <message key="manager.subscriptions.form.institutionMailingAddress">Mailing address</message> <message key="manager.subscriptions.form.domainInstructions"><![CDATA[If a domain is entered here, IP ranges are optional.<br />Valid values are domain names (e.g. lib.sfu.ca).]]></message> <message key="manager.subscriptions.form.domainIPRangeRequired">The selected subscription type requires a domain and/or an IP range for subscription authentication.</message> <message key="manager.subscriptions.form.domainValid">Please enter a valid domain.</message> <message key="manager.subscriptions.form.ipRange">IP ranges</message> <message key="manager.subscriptions.form.ipRangeItem"><![CDATA[•]]></message> <message key="manager.subscriptions.form.ipRangeInstructions"><![CDATA[If IP ranges are entered here, the domain is optional.<br />Valid values include an IP address (e.g. 142.58.103.1), IP range (e.g. 142.58.103.1 - 142.58.103.4), IP range with wildcard '*' (e.g. 142.58.*.*), and an IP range with CIDR (e.g. 142.58.100.0/24).]]></message> <message key="manager.subscriptions.form.ipRangeValid">Please enter a valid IP range.</message> <message key="manager.subscriptions.form.deleteIpRange">Delete</message> <message key="manager.subscriptions.form.addIpRange">Add</message> <message key="manager.subscriptions.form.saveAndCreateAnother">Save and Create Another</message> <message key="manager.subscriptions.form.subscriptionContactRequired">In order to send the user a notification email, the subscription contact name and email address must be specified in the journal Setup.</message> <message key="manager.subscriptions.form.subscriptionExists">This user already has a subscription for this journal.</message> <message key="manager.subscriptions.form.typeRequired">A subscription type must be created before new subscriptions can be made.</message> <message key="manager.subscriptions.ipRange">IP Range</message> <message key="manager.subscriptions.membership">Membership</message> <message key="manager.subscriptions.referenceNumber">Reference Number</message> <message key="manager.subscriptions.notes">Notes</message> <message key="manager.subscriptions.noneCreated">No subscriptions</message> <message key="manager.subscriptions.selectContact">Select Subscription Contact</message> <message key="manager.subscriptions.selectUser">Select User</message> <message key="manager.subscriptions.selectSubscriber.desc">Subscription access privileges are automatically granted to the journal's Journal Managers, Editors, Section Editors, Layout Editors, Copyeditors, and Proofreaders.</message> <message key="manager.subscriptions.select">Select</message> <message key="manager.subscriptions.subscriptionCreatedSuccessfully">Subscription created successfully.</message> <message key="manager.subscriptions.subscriptionType">Subscription Type</message> <message key="manager.subscriptions.user">User</message> <message key="manager.subscriptions.contact">Contact Name</message> <message key="manager.subscriptions.institutionName">Institution Name</message> <message key="manager.subscriptionTypes">Subscription Types</message> <message key="manager.subscriptionTypes.confirmDelete">Warning! All subscriptions with this subscription type will also be deleted. Are you sure you want to continue and delete this subscription type?</message> <message key="manager.subscriptionTypes.cost">Cost</message> <message key="manager.subscriptionTypes.subscriptions">Subscriptions</message> <message key="manager.subscriptionTypes.individual">Individual</message> <message key="manager.subscriptionTypes.institutional">Institutional</message> <message key="manager.subscriptionTypes.create">Create New Subscription Type</message> <message key="manager.subscriptionTypes.createTitle">Create</message> <message key="manager.subscriptionTypes.duration">Duration</message> <message key="manager.subscriptionTypes.edit">Edit Subscription Type</message> <message key="manager.subscriptionTypes.editTitle">Edit</message> <message key="manager.subscriptionTypes.form.cost">Cost</message> <message key="manager.subscriptionTypes.form.costInstructions">Enter a numeric value (e.g. 40 or 40.00) without symbol (e.g., $).</message> <message key="manager.subscriptionTypes.form.costNumeric">The cost must be a positive, numeric value.</message> <message key="manager.subscriptionTypes.form.costRequired">A cost is required.</message> <message key="manager.subscriptionTypes.form.currency">Currency</message> <message key="manager.subscriptionTypes.form.currencyRequired">A currency is required.</message> <message key="manager.subscriptionTypes.form.currencyValid">Please select a valid currency.</message> <message key="manager.subscriptionTypes.form.description">Description</message> <message key="manager.subscriptionTypes.form.nonExpiring.expiresAfter">Expires after</message> <message key="manager.subscriptionTypes.form.nonExpiring.months">months (e.g. 12)</message> <message key="manager.subscriptionTypes.form.nonExpiring.neverExpires">Never expires</message> <message key="manager.subscriptionTypes.form.nonExpiringValid">Please use the provided options.</message> <message key="manager.subscriptionTypes.form.duration">Duration</message> <message key="manager.subscriptionTypes.form.durationInstructions">The number of months the subscription lasts (e.g. 12).</message> <message key="manager.subscriptionTypes.form.durationNumeric">The duration must be a positive, numeric value.</message> <message key="manager.subscriptionTypes.form.durationRequired">A duration is required.</message> <message key="manager.subscriptionTypes.form.format">Format</message> <message key="manager.subscriptionTypes.form.formatRequired">A subscription type format is required.</message> <message key="manager.subscriptionTypes.form.formatValid">Please select a valid subscription type format.</message> <message key="manager.subscriptionTypes.form.subscriptions">Subscriptions</message> <message key="manager.subscriptionTypes.form.individual">Individual (users are validated via login)</message> <message key="manager.subscriptionTypes.form.institutional">Institutional (users are validated via domain or IP address)</message> <message key="manager.subscriptionTypes.form.institutionalValid">Please use the provided options.</message> <message key="manager.subscriptionTypes.form.membership"><![CDATA[Subscriptions require membership information<br />(e.g. of an association, organization, consortium, etc.)]]></message> <message key="manager.subscriptionTypes.form.membershipValid">Please use the checkbox provided.</message> <message key="manager.subscriptionTypes.form.options">Options</message> <message key="manager.subscriptionTypes.form.public"><![CDATA[Do not make this subscription type publicly available or visible<br />(e.g. under Subscriptions in About the Journal).]]></message> <message key="manager.subscriptionTypes.form.publicValid">Please use the checkbox provided.</message> <message key="manager.subscriptionTypes.form.saveAndCreateAnotherType">Save and Create Another</message> <message key="manager.subscriptionTypes.form.typeName">Name of Type</message> <message key="manager.subscriptionTypes.form.typeNameExists">A subscription type with this name already exists.</message> <message key="manager.subscriptionTypes.form.typeNameRequired">A subscription type name is required.</message> <message key="manager.subscriptionTypes.name">Subscription type</message> <message key="manager.subscriptionTypes.noneCreated">No subscription types have been created.</message> <message key="manager.subscriptionTypes.subscriptionTypeCreatedSuccessfully">Subscription type created successfully.</message> <!-- Categories --> <message key="manager.setup.categories">Categories</message> <message key="manager.setup.categories.description">Choose the most appropriate categories from the set listed above. Readers will be able to browse by category from the complete journal set.</message> </locale>