diff --git a/journals/constants.py b/journals/constants.py
index d8d394a5c1c70eaba9b0dd14311e18d26a40f07a..0238bb1b1d0bd44d3940b27fa6e17048d5c75edf 100644
--- a/journals/constants.py
+++ b/journals/constants.py
@@ -5,14 +5,18 @@ __license__ = "AGPL v3"
# These are DOI's of the Journals, they are used as keys for the choicefield in `models.Journal`!
SCIPOST_JOURNAL_PHYSICS = 'SciPostPhys'
SCIPOST_JOURNAL_PHYSICS_SELECT = 'SciPostPhysSel'
+SCIPOST_JOURNAL_PHYSICS_COMMONS = 'SciPostPhysComm'
SCIPOST_JOURNAL_PHYSICS_LECTURE_NOTES = 'SciPostPhysLectNotes'
SCIPOST_JOURNAL_PHYSICS_PROC = 'SciPostPhysProc'
+SCIPOST_JOURNAL_PHYSICS_CODEBASES = 'SciPostPhysCodeb'
# Journal open for submission
SCIPOST_JOURNALS_SUBMIT = (
(SCIPOST_JOURNAL_PHYSICS, 'SciPost Physics'),
+ (SCIPOST_JOURNAL_PHYSICS_COMMONS, 'SciPost Physics Commons'),
(SCIPOST_JOURNAL_PHYSICS_LECTURE_NOTES, 'SciPost Physics Lecture Notes'),
- (SCIPOST_JOURNAL_PHYSICS_PROC, 'SciPost Physics Proceedings')
+ (SCIPOST_JOURNAL_PHYSICS_PROC, 'SciPost Physics Proceedings'),
+ (SCIPOST_JOURNAL_PHYSICS_CODEBASES, 'SciPost Physics Codebases'),
)
# Journal closed for submission
@@ -27,6 +31,8 @@ REGEX_CHOICES = '|'.join([
SCIPOST_JOURNAL_PHYSICS_PROC,
SCIPOST_JOURNAL_PHYSICS_SELECT,
SCIPOST_JOURNAL_PHYSICS_LECTURE_NOTES,
+ SCIPOST_JOURNAL_PHYSICS_CODEBASES,
+ SCIPOST_JOURNAL_PHYSICS_COMMONS,
SCIPOST_JOURNAL_PHYSICS
])
diff --git a/journals/migrations/0047_auto_20181023_0829.py b/journals/migrations/0047_auto_20181023_0829.py
new file mode 100644
index 0000000000000000000000000000000000000000..8ed6780e37b06ac4f54bdd9b7a68ec627233d125
--- /dev/null
+++ b/journals/migrations/0047_auto_20181023_0829.py
@@ -0,0 +1,20 @@
+# -*- coding: utf-8 -*-
+# Generated by Django 1.11.4 on 2018-10-23 06:29
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+
+ dependencies = [
+ ('journals', '0046_auto_20181020_2008'),
+ ]
+
+ operations = [
+ migrations.AlterField(
+ model_name='journal',
+ name='name',
+ field=models.CharField(choices=[('SciPostPhys', 'SciPost Physics'), ('SciPostPhysComm', 'SciPost Physics Commons'), ('SciPostPhysLectNotes', 'SciPost Physics Lecture Notes'), ('SciPostPhysProc', 'SciPost Physics Proceedings'), ('SciPostPhysCodeb', 'SciPost Physics Codebases'), ('SciPostPhysSel', 'SciPost Physics Select')], max_length=100, unique=True),
+ ),
+ ]
diff --git a/journals/templates/journals/SciPostPhysCodeb_about.html b/journals/templates/journals/SciPostPhysCodeb_about.html
new file mode 100644
index 0000000000000000000000000000000000000000..22c57d4f2e35b90a5a9d40804e29f08c9748a8e3
--- /dev/null
+++ b/journals/templates/journals/SciPostPhysCodeb_about.html
@@ -0,0 +1,109 @@
+
+{% extends 'journals/_base.html' %}
+
+{% block pagetitle %}{{block.super}}: About{% endblock pagetitle %}
+
+{% block link_class_physics_about %}active{% endblock %}
+
+{% block breadcrumb_items %}
+ {{block.super}}
+ <a href="{% url 'journal:issues' journal.doi_label %}" class="breadcrumb-item">SciPost Physics Codebases</a>
+ <span class="breadcrumb-item active">About</span>
+{% endblock %}
+
+{% block content %}
+
+ {% with header_text='About SciPost Physics Codebases' %}
+ {{block.super}}
+ {% endwith %}
+
+
+{% if perms.scipost.can_view_pool %}
+<div class="container border border-danger">
+ <span class="text-danger">DRAFT (POOLVIEW ONLY) - <a href="mailto:admin@scipost.org">COMMENTS WELCOME</a></span>
+
+
+
+ <div class="row">
+ <div class="col-md-6">
+ <h2>Aims</h2>
+ <p>SciPost Physics Codebases is a new-generation publication venue for computer codes and algorithms of relevance to research in Physics.</p>
+ <p>It aims to offer a high-profile venue in which top-level numerical algorithms, protocols and software packages can be disseminated as fully-featured publication objects benefitting from all things expected of top-quality papers.</p>
+ <p>Contributors to research-level software development can thus obtain proper recognition and find their rightful place within modern scientific literature.</p>
+ <p>As per other SciPost Journals, SciPost Physics Codebases is two-way open access, peer-witnessed refereed. Publications in SciPost Physics Codebases benefit from the same professional treatment given to our other Journals, including metadata handling, citable DOI, citations listing, funding information handling, and permanent archiving.</p>
+ </div>
+ <div class="col-md-6">
+ <h2>Scope</h2>
+ <p>SciPost Physics Codebases publishes outstanding-quality Codebases relevant to all specializations in Computational, Experimental and Theoretical Physics.</p>
+ <p>Examples of publishable Codebases include:</p>
+ <ul>
+ <li>Novel algorithms</li>
+ <li>Significant and original reimplementations of well-known algorithms</li>
+ <li>Ports of existing codebases to new languages and platforms</li>
+ </ul>
+ </div>
+ </div>
+
+ <div class="row">
+ <div class="col-md-6">
+ <h2>Content</h2>
+ <p>A Codebase by definition consists of the following elements:</p>
+ <ul>
+ <li>A detailed userguide consisting of:
+ <ul>
+ <li>An introduction with background information on the field of applicability of the software</li>
+ <li>A description of the generic workings of the algorithm, its novelty and added value</li>
+ <li>Installation instructions including listing of dependencies and requirements</li>
+
+ <li>A guide to using the software</li>
+ <li>Worked-out examples and tests for benchmarking</li>
+ </ul>
+ </li>
+ <li>The source code</li>
+ </ul>
+ <p>The source code itself is expected to be self-contained and to include installation instructions and benchmarking tests.</p>
+ </div>
+
+ <div class="col-md-6">
+ <h2>Submission and Editorial Process</h2>
+ <p>Authors should follow the <a href="{% url 'submissions:author_guidelines' %}">submission guidelines</a> to ensure seamless processing of their manuscript. The <a href="{% url 'journals:journals_terms_and_conditions' %}">SciPost Journals Terms and Conditions</a> apply to all Submissions to SciPost Physics Codebases.</p>
+ <p>All incoming Submissions are checked for plagiarism and follow the peer-witnessed refereeing procedures outlined in <a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and Refereeing procedure</a>.</p>
+ <p>All publication decisions are taken by the <a href="{% url 'scipost:about' %}#editorial_college_physics">Editorial College (Physics)</a>, following the rules set out in the <a href="{% url 'scipost:EdCol_by-laws' %}">Editorial College by-laws</a>.</p>
+ </div>
+ </div>
+
+ <div class="row">
+ <div class="col-md-6">
+ <h2>Licensing</h2>
+ <p>The submitted software must be released under a license which is compliant with the <a href="https://opensource.org/osd">Open Source Definition</a> of the <a href="https://opensource.org">Open Source Initiative</a>. There are many <a href="https://opensource.org/licenses">acceptable licenses</a>, among which:</p>
+ <ul>
+ <li>Apache License 2.0 (Apache-2.0)</li>
+ <li>BSD 3-Clause "New" or "Revised" license (BSD-3-Clause)</li>
+ <li>BSD 2-Clause "Simplified" or "FreeBSD" license (BSD-2-Clause)</li>
+ <li>GNU General Public License (GPL)</li>
+ <li>GNU Library or "Lesser" General Public License (LGPL)</li>
+ <li>MIT license (MIT)</li>
+ <li>Mozilla Public License 2.0 (MPL-2.0)</li>
+ <li>Common Development and Distribution License (CDDL-1.0)</li>
+ <li>Eclipse Public License (EPL-1.0)</li>
+ </ul>
+ <p>We also accept</p>
+ <ul>
+ <li><a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International (CC BY 4.0) License</a></li>
+ <li><a href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International (CC BY-NC 4.0) License</a></li>
+ <li><a href="http://creativecommons.org/licenses/by-nc/4.0/">Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) License</a></li>
+ <li><a href="https://creativecommons.org/share-your-work/public-domain/cc0/">Creative Commons CC0 Public Domain Dedication "No Rights Reserved"</a></li>
+ </ul>
+ <p>Other licenses can be considered upon request (please contact our <a href="mailto:edadmin@scipost.org">Editorial Administration</a>).</p>
+ <p>Upon acceptance of the codebase for publication, the detailed userguide will be published in SciPost Physics Codebases with a CC BY 4.0 license, allowing freedom to use, reproduce and distribute the articles and related content (unless otherwise noted), for commercial and noncommercial purposes, subject to the citation of the original source.</p>
+ <p>The publication will be citable (DOI registration via Crossref), and will benefit from full handling as per all other SciPost Journals. The source code will be hosted by SciPost and directly linked from the publication's page.</p>
+ </div>
+
+ </div>
+
+
+</div>
+{% endif %}
+
+
+{% endblock %}
diff --git a/journals/templates/journals/SciPostPhysCodeb_info_for_authors.html b/journals/templates/journals/SciPostPhysCodeb_info_for_authors.html
new file mode 100644
index 0000000000000000000000000000000000000000..400b145a2d1152d8922d972065c5e246f2b4f417
--- /dev/null
+++ b/journals/templates/journals/SciPostPhysCodeb_info_for_authors.html
@@ -0,0 +1,42 @@
+
+{% extends 'journals/_base.html' %}
+
+{% block pagetitle %}{{block.super}}: Info for Authors{% endblock pagetitle %}
+
+{% block link_class_physics_info %}active{% endblock %}
+
+{% block breadcrumb_items %}
+ {{block.super}}
+ <a href="{% url 'journal:issues' journal.doi_label %}" class="breadcrumb-item">SciPost Physics Codebases and Datasets</a>
+ <span class="breadcrumb-item active">Info for Authors</span>
+{% endblock %}
+
+{% block content %}
+
+ {% with header_text='Information for Authors' %}
+ {{block.super}}
+ {% endwith %}
+
+ <div class="row">
+ <div class="col-12">
+ <h3>Manuscript preparation</h3>
+ <ul>
+ <li>Please follow the <a href="{% url 'submissions:author_guidelines' %}">Author guidelines</a> to ensure seamless processing of your manuscript.</li>
+ </ul>
+
+ <h3>Submission and Refereeing</h3>
+ <ul>
+ <li>Make sure you have read and agree with the <a href="{% url 'journals:journals_terms_and_conditions' %}">SciPost Journals Terms and Conditions.</a></li>
+ <li>All Submissions to SciPost Physics Codebases and Datasets follow the peer-witnessed refereeing procedures outlined in
+ <a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and Refereeing procedure</a>.
+ </li>
+ </ul>
+
+ <h3>Decision</h3>
+ <ul>
+ <li>All publication decisions are taken by the <a href="{% url 'scipost:about' %}#editorial_college_physics">Editorial College (Physics)</a>, following the rules set out in the <a href="{% url 'scipost:EdCol_by-laws' %}">Editorial College by-laws</a>.</li>
+ </ul>
+ </div>
+ </div>
+
+{% endblock %}
diff --git a/journals/templates/journals/SciPostPhysComm_about.html b/journals/templates/journals/SciPostPhysComm_about.html
new file mode 100644
index 0000000000000000000000000000000000000000..3091dae58d286b472cb5d508bfea089d2fc53d88
--- /dev/null
+++ b/journals/templates/journals/SciPostPhysComm_about.html
@@ -0,0 +1,77 @@
+
+{% extends 'journals/_base.html' %}
+
+{% block pagetitle %}{{block.super}}: About{% endblock pagetitle %}
+
+{% block link_class_physics_about %}active{% endblock %}
+
+{% block breadcrumb_items %}
+ {{block.super}}
+ <a href="{% url 'journal:issues' journal.doi_label %}" class="breadcrumb-item">SciPost Physics Commons</a>
+ <span class="breadcrumb-item active">About</span>
+{% endblock %}
+
+{% block content %}
+
+ {% with header_text='About SciPost Physics Commons' %}
+ {{block.super}}
+ {% endwith %}
+
+
+{% if perms.scipost.can_view_pool %}
+<div class="container border border-danger">
+ <span class="text-danger">DRAFT (POOLVIEW ONLY) - <a href="mailto:admin@scipost.org">COMMENTS WELCOME</a></span>
+
+
+ <div class="row">
+ <div class="col-md-6">
+ <h2>Aims</h2>
+ <p>SciPost Physics Commons is a premium-quality, two-way open access, peer-witnessed refereed Journal for the general field of Physics.</p>
+ <p>Implementing <a href="{% url 'scipost:about' %}#GOA">Genuine Open Access</a>, SciPost Physics is a publishing venue in which uncompromising scientific quality meets the highest achievable standards of open accessibility.</p>
+ </div>
+ <div class="col-md-6">
+ <h2>Scope</h2>
+ <p>SciPost Physics Commons publishes outstanding-quality research articles in the domains of Experimental, Theoretical and Computational physics, including but not limited to:</p>
+ <ul>
+ {% for discipline in subject_areas %}
+ {% if discipline.0 == 'Physics' %}
+ {% for area in discipline.1 %}
+ <li>{{ area.1 }}</li>
+ {% endfor %}
+ {% endif %}
+ {% endfor %}
+ </ul>
+ </div>
+ </div>
+
+ <div class="row">
+ <div class="col-md-6">
+ <h2>Content</h2>
+ <p>The journal accepts three types of content: <strong>Letters</strong>, <strong>Articles</strong> and <strong>Reviews</strong>.</p>
+ <ul>
+ <li><strong>Letters</strong> report broad-interest, significant breakthroughs in Physics, of interest and importance to researchers in multiple subject areas.</li>
+ <li><strong>Articles</strong> provide in-depth, detailed reports of groundbreaking research within one or more subject areas.</li>
+ <li><strong>Reviews</strong> are short pieces taking a snapshot of a research area, written by recognized leaders in the field, providing a critical assessment of current frontline research and providing pointers towards future opportunities.</li>
+ </ul>
+ </div>
+ <div class="col-md-6">
+ <h2>Submission and Editorial Process</h2>
+ <p>Authors should follow the <a href="{% url 'submissions:author_guidelines' %}">submission guidelines</a> to ensure seamless processing of their manuscript. The <a href="{% url 'journals:journals_terms_and_conditions' %}">SciPost Journals Terms and Conditions</a> apply to all Submissions to SciPost Physics.</p>
+ <p>All incoming Submissions are checked for plagiarism and follow the peer-witnessed refereeing procedures outlined in <a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and Refereeing procedure</a>. Guest Fellows from the community can be called upon to act as Editor-in-charge.</p>
+ <p>All publication decisions are taken by the <a href="{% url 'scipost:about' %}#editorial_college_physics">Editorial College (Physics)</a>, following the rules set out in the <a href="{% url 'scipost:EdCol_by-laws' %}">Editorial College by-laws</a>.</p>
+ </div>
+ </div>
+
+ <div class="row">
+ <div class="col-12">
+ <h2>Publication: Open Access</h2>
+ <p>Publications in SciPost Physics Commons are published under the terms of the <a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International (CC BY 4.0) License</a>, allowing freedom to use, reproduce and distribute the articles and related content (unless otherwise noted), for commercial and noncommercial purposes, subject to the citation of the original source.</p>
+ </div>
+ </div>
+
+
+</div>
+{% endif %}
+
+
+{% endblock %}
diff --git a/journals/templates/journals/SciPostPhysComm_info_for_authors.html b/journals/templates/journals/SciPostPhysComm_info_for_authors.html
new file mode 100644
index 0000000000000000000000000000000000000000..497b4e1a908073c8611ead0dea513b934adf1bef
--- /dev/null
+++ b/journals/templates/journals/SciPostPhysComm_info_for_authors.html
@@ -0,0 +1,44 @@
+
+{% extends 'journals/_base.html' %}
+
+{% block pagetitle %}{{block.super}}: Info for Authors{% endblock pagetitle %}
+
+{% block link_class_physics_info %}active{% endblock %}
+
+{% block breadcrumb_items %}
+ {{block.super}}
+ <a href="{% url 'journal:issues' journal.doi_label %}" class="breadcrumb-item">SciPost Physics Commons</a>
+ <span class="breadcrumb-item active">Info for Authors</span>
+{% endblock %}
+
+{% block content %}
+
+ {% with header_text='Information for Authors' %}
+ {{block.super}}
+ {% endwith %}
+
+
+ <div class="row">
+ <div class="col-12">
+ <h3>Manuscript preparation</h3>
+ <ul>
+ <li>Please follow the <a href="{% url 'submissions:author_guidelines' %}">Author guidelines</a> to ensure seamless processing of your manuscript.</li>
+ </ul>
+
+ <h3>Submission and Refereeing</h3>
+ <ul>
+ <li>Make sure you have read and agree with the <a href="{% url 'journals:journals_terms_and_conditions' %}">SciPost Journals Terms and Conditions.</a></li>
+ <li>All Submissions to SciPost Physics Commons follow the peer-witnessed refereeing procedures outlined in
+ <a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and Refereeing procedure</a>. Guest Fellows from the community can be called upon to act as Editor-in-charge.
+ </li>
+ </ul>
+
+ <h3>Decision</h3>
+ <ul>
+ <li>All publication decisions are taken by the <a href="{% url 'scipost:about' %}#editorial_college_physics">Editorial College (Physics)</a>, following the rules set out in the <a href="{% url 'scipost:EdCol_by-laws' %}">Editorial College by-laws</a>.</li>
+ </ul>
+ </div>
+ </div>
+
+
+{% endblock %}
diff --git a/journals/templates/journals/SciPostPhys_about.html b/journals/templates/journals/SciPostPhys_about.html
index 55a7b01dc6793e5fd0a0db22dde3e9b84d9b5261..6952cb350a730f1489cb75d268c22c996801381a 100644
--- a/journals/templates/journals/SciPostPhys_about.html
+++ b/journals/templates/journals/SciPostPhys_about.html
@@ -50,7 +50,7 @@
<div class="row">
<div class="col-md-6">
<h2>Content</h2>
- <p>The content format for SciPost Physics is flexible: articles can be short letter-style communications of breakthroughs or in-depth reports of groundbreaking research. There is no minimum or maximum length: the article should however represent a complete, self-contained unit. The target audience can be researchers in many different subject areas, or specialists in one.</p>
+ <p>The content format for SciPost Physics is flexible: articles can be short letter-style communications of breakthroughs or in-depth reports of groundbreaking research. There is no minimum or maximum length: the article should however constitute a complete, self-contained unit. The target audience can be researchers in many different subject areas, or specialists in one.</p>
<p>The submission format is more demanding than in our other Journals: in addition to the main manuscript, authors must provide a two-page extended abstract detailing:
<ul>
<li>the context to the problem</li>
diff --git a/journals/templates/journals/journals.html b/journals/templates/journals/journals.html
index 34e0c431ee49bcb14f0c4740d319f15344681aa7..958c8d60e46b3c0bb254e5f6958f9c9a73abe428 100644
--- a/journals/templates/journals/journals.html
+++ b/journals/templates/journals/journals.html
@@ -20,7 +20,7 @@
<li class="nav-item">
{% if journal.active %}
<a href="{{journal.get_absolute_url}}" class="nav-link">{{journal}}</a>
- {% else %}
+ {% elif perms.scipost.can_view_pool %}
<a href="{% url 'journal:about' journal.name %}" class="nav-link">{{journal}}</a>
{% endif %}
</li>
@@ -57,21 +57,21 @@
</div>
<br/>
<h1 class="highlight" id="physics">Physics Journals</h1>
- <p>If you are a professional researcher in Physics, irrespective of your area of specialization, then our family of Physics Journals is designed to cover all your professional publishing requirements.</p>
+ <p>If you are a professional researcher in Physics, irrespective of your area of specialization, then our family of Physics Journals is designed to cover all your publishing requirements.</p>
<p>We offer different venues for different types of material; for research results, we also offer a gradation in terms of significance and editorial requirements.</p>
<p>Of course, publishing in any of our Journals automatically fulfils all your Open Access mandates, even the most demanding ones.</p>
<h2><button class="btn btn-danger text-white mb-2 p-2" type="button" data-toggle="collapse" data-target="#WhereToSubmit" aria-expanded="false" aria-controls="WhereToSubmit"><strong>Help!</strong> Where should I submit?</button></h2>
<div class="collapse" id="WhereToSubmit">
<div class="card card-body">
- <p>For <strong>Lecture Notes</strong>, <strong>Proceedings</strong> or <strong>Codebases/Datasets</strong>, the names say it all without ambiguity.</p>
+ <p>For <strong>Lecture Notes</strong>, <strong>Proceedings</strong> or <strong>Codebases</strong>, the names say it all without ambiguity.</p>
<p>But what about your <strong>research results</strong>? Ask yourself these two questions:</p>
<ul>
<li><em>Are these results exceptional in nature, in the sense that they represent a breakthrough or an achievement which clearly stands out?</em></li>
<li><em>Are you willing to make a special effort in conveying these results, in meeting the highest submission standards which we require, and in responding/reacting to any points raised under our toughest refereeing protocol?</em></li>
</ul>
<p>If you answered both questions in the affirmative, then consider submitting to <a href="{% url 'scipost:landing_page' 'SciPostPhys' %}">SciPost Physics</a>.</p>
- <p>On the other hand, if your results represent a significant advance but you desire a simpler submission and refereeing process, then <a href="{% url 'scipost:landing_page' 'SciPostPhysAdv' %}">SciPost Physics Advances</a> will provide you with a more streamlined experience.</p>
+ <p>On the other hand, if your results represent a significant advance but you desire a simpler submission and refereeing process, then <a href="{% url 'scipost:landing_page' 'SciPostPhysComm' %}">SciPost Physics Commons</a> will provide you with a more streamlined experience.</p>
</div>
</div>
<div class="card-deck">
@@ -89,13 +89,13 @@
</div>
<div class="card">
<div class="card-header banner">
- <h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysAdv' %}">SciPost Physics Advances</a> <em><small style="color: red;">New!</small></em></h1>
+ <h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysComm' %}">SciPost Physics Commons</a> <em><small style="color: red;">New!</small></em></h1>
</div>
<div class="card-body">
- <p>SciPost Physics Advances is a premium-quality refereed Journal for the general field of Physics.</p>
+ <p>SciPost Physics Commons is a premium-quality refereed Journal for the general field of Physics.</p>
<p>All submissions undergo our peer-witnessed refereeing protocol, led by community professionals under the guidance of our Editorial College (Physics).</p>
- <p>Publications in SciPost Physics Advances meet all Open Access requirements set by your institution and funding agency (even the most exacting), while remaining entirely free of author-facing charges.</p>
- <p>SciPos Physics Advances is the Genuine Open Access, by-and-for professional scientists publishing venue for all your significant research advances.</p>
+ <p>Publications in SciPost Physics Commons meet all Open Access requirements set by your institution and funding agency (even the most exacting), while remaining entirely free of author-facing charges.</p>
+ <p>SciPos Physics Commons is the Genuine Open Access, by-and-for professional scientists publishing venue for all your significant research advances.</p>
</div>
</div>
</div>
@@ -122,15 +122,12 @@
</div>
<div class="card">
<div class="card-header banner">
- <h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysCoDat' %}">SciPost Physics Codebases and Datasets</a> <em><small style="color: red;">New!</small></em></h1>
+ <h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysCodeb' %}">SciPost Physics Codebases</a> <em><small style="color: red;">New!</small></em></h1>
</div>
<div class="card-body">
- <p>SciPost Phys. CoDat. is an innovative peer-reviewed publication venue for modern forms of scientific contributions:</p>
- <ul>
- <li>reuseable codebases</li>
- <li>structured datasets</li>
- </ul>
- <p>Submissions undergo stringent peer-witnessed refereeing, with criteria tailored for this type of content; accepted manuscripts become full-fledged publications.</p>
+ <p>SciPost Physics Codebases is an innovative peer-reviewed publication venue for modern forms of scientific contributions which too often remains unrecognized: codes and algorithms at the heart of contemporary research.</p>
+ <p>This Journal offers proper recognition for code authors, in the form of fully-fledged citable publications.</p>
+ <p>Submissions undergo stringent peer-witnessed refereeing, with criteria tailored for this type of content.</p>
</div>
</div>
</div>
diff --git a/scipost/static/scipost/2018_10_SciPost_Journals_plan.png b/scipost/static/scipost/2018_10_SciPost_Journals_plan.png
index a5a889e559623900517b3981560920a726451799..15b6b88d0edfcea5a765423dec530ada708f8b4c 100644
Binary files a/scipost/static/scipost/2018_10_SciPost_Journals_plan.png and b/scipost/static/scipost/2018_10_SciPost_Journals_plan.png differ
diff --git a/scipost/templates/scipost/EdCol_by-laws.html b/scipost/templates/scipost/EdCol_by-laws.html
index e3a4b4b2f1e743b303084a2283fa0680b632d39e..be86e01c261f07762dd2ce385a917fc439b5bd17 100644
--- a/scipost/templates/scipost/EdCol_by-laws.html
+++ b/scipost/templates/scipost/EdCol_by-laws.html
@@ -17,6 +17,493 @@
{% load scipost_extras %}
+
+
+{% if perms.scipost.can_view_pool %}
+<div class="container border border-danger">
+ <span class="text-danger">DRAFT (POOLVIEW ONLY) - <a href="mailto:admin@scipost.org">COMMENTS WELCOME</a></span>
+
+
+<div class="row">
+ <div class="col-12">
+ <h1 class="highlight">SciPost Editorial Colleges By-laws</h1>
+
+ <p>
+ Functioning of the SciPost Editorial Colleges is governed by the following set of by-laws.
+ </p>
+ <p>
+ These complement and are subsidiary to the legal statutes of Stichting SciPost
+ (hereafter: the Foundation).
+ </p>
+
+ <ol>
+ <hr>
+ <li><strong>Editorial Colleges and their Composition</strong><a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#Composition">view/hide</a>
+ <div id="Composition" class="py-2" style="display: none;">
+ <ol>
+ <li><strong>The Colleges</strong>
+ <p>
+ An Editorial College is formed for each field of the sciences in which SciPost
+ carries out publishing activities. The Editorial College of a certain field takes
+ responsibility for editorial matters for all Journals operating in that field.
+ For interdisciplinary submissions, Fellows from distinct Colleges can be called
+ upon during the evaluation process.
+ </p>
+ </li>
+ <li><strong>Eligibility</strong>
+ <p>
+ Fellows of an Editorial College must be professionally active academics
+ with a position of at least associate professor level or equivalent
+ at a recognized university or research institute. They must possess an extensive
+ publication record demonstrating world-leading research capabilities in at least one
+ stated subject area covered by SciPost Journals. There is no age limitation.
+ </p>
+ </li>
+ <li><strong>Number of Fellows</strong>
+ <p>
+ The size of an Editorial College will be such that each stated subject area
+ will be represented by at least 8 Fellows. There is no maximum.
+ The number of Fellows
+ caring for a stated subject area shall be adjusted to ensure a workload per Fellow
+ limited to approximately one half-day per month on average.
+ </p>
+ </li>
+ <li><strong>Appointment by the Foundation</strong>
+ <p>
+ If the number of Fellows in a stated specialty is below the required minimum number,
+ or if the number of currently available Fellows in a stated specialty
+ has diminished to a level where processing of Submissions becomes delayed,
+ the Foundation has the right to directly nominate and immediately appoint
+ individuals deemed to fulfil the eligibility criteria.
+ </p>
+ </li>
+ <li><strong>Appointment by election</strong>
+ <p>
+ Foundation board members, members of the Advisory Board as well as current and past
+ Fellows of an Editorial College can nominate candidates for an Editorial Fellowship.
+ Candidates must fulfil the eligiblity criteria.
+ These nominations shall be forwarded to the relevant Editorial College
+ for voting, at the latest at the next Virtual General Meeting.
+ If a candidate secures a positive vote from at least three quarters
+ of the Fellows currently
+ caring for the candidate's stated main expertise, and if no veto is received from
+ Fellows in other subject areas, from the Advisory Board or from the Foundation's
+ Board, then the candidate is deemed elected, and is invited to join by the
+ Foundation. Appointment to an Editorial College starts immediately upon receipt
+ of a positive answer from the candidate.
+ </p>
+ </li>
+ <li><strong>Duration</strong>
+ <p>
+ An appointment as Fellow of an Editorial College is for a duration of 2 years.
+ </p>
+ </li>
+ <li><strong>Visibility</strong>
+ <p>
+ The composition of an Editorial College is publicly known. The list of Editorial
+ Fellows and their stated expertises is published on the website.
+ </p>
+ </li>
+ <li><strong>Renewal</strong>
+ <p>
+ An appointment is renewable without limitation. A Fellow coming to the end of
+ an appointment is automatically put up for re-election, unless
+ the said Fellow has informed the Foundation of his/her desire not to renew,
+ or if the Foundation or the Advisory Board vetoes the renewal.
+ </p>
+ </li>
+ <li><strong>End of appointment</strong>
+ <p>
+ Appointment as an Editorial Fellow immediately ends upon:
+ <ul>
+ <li>the Fellow informing the Foundation of his/her wish to cease
+ his/her Fellowship</li>
+ <li>the Fellow ceasing to fulfil the eligibility criteria</li>
+ <li>the Foundation terminating the appointment due to
+ conduct which it deems to be improper or in
+ conflict with the general aims and guiding principles of the Foundation.</li>
+ </ul>
+ </p>
+ </li>
+ </ol>
+ </div>
+ </li>
+
+ <hr>
+ <li><strong>Meetings</strong> <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#Meetings">view/hide</a>
+ <div id="Meetings" class="py-2" style="display: none;">
+ <p>
+ Editorial Colleges, consisting of internationally-renowned scientists with a broad
+ geographic distribution, do not physically meet. Meetings are instead organized
+ using online facilities.
+ </p>
+ <ol>
+ <li><strong>Virtual General Meetings</strong>
+ <p>Once per year, Fellows of the Editorial Colleges are asked to participate in a
+ virtual general meeting. The meeting is organized by the Foundation and takes
+ place over the course of one week during the month of January.</p>
+ <p>For the VGM, a special web page is activated, which is accessible only to
+ Fellows, members of the Advisory Board and Foundation Board members.
+ This page contains items and points of discussion put forward by
+ the Foundation, Advisory Board and Editorial Fellows,
+ and can be consulted and acted upon by Board members and Fellows at
+ their own leisure during the week of the meeting.
+ The meeting is chaired by the Foundation's chairman.
+ During the week of the meeting, Fellows are able to comment on individual items and
+ bring forth motions for voting.
+ Re-elections, new nominations to the College and suggested amendments
+ to the By-laws must appear among the items at the meeting.</p>
+ <p>At the end of the week, the meeting is closed, and motions are put forward
+ for voting, which is open online for one week after the end of the VGM.</p>
+ <p>Within one week following the end of voting, the Foundation sets to work
+ implementing the decisions taken
+ and releases the minutes of the VGM to the Advisory Board and Editorial College.</p>
+ </li>
+ <li><strong>Extraordinary Virtual Meetings</strong>
+ <p>At any time, the Foundation can call an Extraordinary Virtual Meeting, to
+ discuss pressing issues. This meeting must be
+ announced at least one week before its scheduled start.
+ An EVM otherwise follows the same procedures as a VGM.
+ </p>
+ </li>
+ </ol>
+ </div>
+ </li>
+
+ <hr>
+ <li><strong>Submissions processing</strong> <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#SubmissionsProcessing">view/hide</a>
+ <div id="SubmissionsProcessing" class="py-2" style="display: none;">
+ <p>The primary responsibility of the Editorial Colleges is to run the editorial process
+ for all SciPost Journals. The Colleges shall strive for the very highest standards of
+ professionalism achievable in the refereeing process.</p>
+ <ol>
+ <li><strong>Submissions pool</strong>
+ <p>
+ Incoming Submissions are added to the field-specific pool of manuscripts
+ under consideration for publication.
+ This pool is visible to all members of the relevant Editorial College (with the
+ exception of Fellows flagged for potential conflict of interest with the authors
+ or the contents of the incoming Submission),
+ as well as to the Advisory Board and Foundation.
+ Each item in the pool represents a single Submission's whole history, including
+ possible earlier (pre-resubmission) versions.</p>
+ <p>
+ Submissions in the pool can be in any of the following stages:
+ <ul>
+ <li>Pre-screening</li>
+ <li>Screening</li>
+ <li>Editor-in-charge appointed</li>
+ <li>Refereeing round open</li>
+ <li>Refereeing round closed</li>
+ <li>Editorial Recommendation formulated</li>
+ <li>Awaiting resubmission</li>
+ <li>Editorial College decision pending</li>
+ <li>Rejected</li>
+ <li>Accepted and in production</li>
+ <li>Published</li>
+ </ul>
+ </p>
+ </li>
+ <li><strong>Pre-screening</strong>
+ <p>
+ For each Submission added to the pool, a thorough plagiarism check is performed
+ by SciPost's Editorial Administration. Appropriate action (immediate rejection;
+ request to authors for modified version) is taken if necessary. A thorough scan
+ is performed to flag potential conflicts of interest of authors with Fellows,
+ and a list of potential Editors-in-charge is preselected based on expertise and
+ availability.
+ </p>
+ <p>
+ Special provisions exist for certain classes of Journals:
+ <ul>
+ <li>for <em>Commons</em>-class Journals, Editors-in-charge can
+ be preselected not only from current Fellows, but from well-respected members of the
+ community at large (in which case they become guest Fellows).</li>
+ <li>for <em>Proceedings</em>-class Journals, Editoris-in-charge are normally
+ preselected from the guest Fellows selected by the proceedings convenors
+ (in normal circumstances the conference/workshop organizers).</li>
+ </ul>
+ </p>
+ </li>
+ <li><strong>Screening</strong>
+ <p>
+ The preselected Fellows are sent an assignment request to become Editor-in-charge.
+ Other Fellows within the Editorial College do not receive an assignment request but
+ can still view a Submission's details and volunteer to become Editor-in-charge
+ through their visibility rights on the Submissions pool.
+ </p>
+ <p>
+ Each assigned Fellow can explicitly decline the assignment, stating a reason among:
+ <em>too busy</em>, <em>conflict of interest</em>, <em>insufficiently qualified</em>
+ or <em>not interested</em>.
+ If the preselected list of Fellows empties and the submission has still not been
+ taken charge of, the preselection list is extended and new assignment requests
+ are sent to different Fellow.
+ If 5 assignments are declined citing <em>lack of interest</em>, the Submission is returned
+ to the authors and not considered for further processing towards publication.
+ </p>
+ <p>
+ The Editorial College must make all reasonable efforts to ensure that the pre-screening process
+ be completed within 5 working days starting from the moment of submission.
+ If this proves impossible (for example due to a large influx of Submissions and current
+ unavailability of specialist Fellows), the authors are informed of the delay and
+ given the option of either withdrawing their Submission,
+ or of accepting an open extension to the duration of their Submission's pre-screening process.
+ </p>
+ </li>
+ <li><strong>Appointment of Editor-in-charge</strong>
+ <p>The first Fellow of the Editorial College
+ (or, for <em>Commons</em>- or <em>Proceedings</em>-class Journals, guest Fellow)
+ who accepts an assignment,
+ or who volunteers while perusing the pool, becomes Editor-in-charge of the Submission,
+ under the conditions that:
+ <ol>
+ <li>the Submission's main specialty matches one of the Fellow's stated specialties</li>
+ <li>there is no conflict of interest of any form between the Fellow and any of the Submission's authors</li>
+ <li>there is no personal or hierarchical relationship between the Fellow and any of the Submission's authors</li>
+ <li>the Fellow has not co-authored a paper with any of the Submission's authors in the last 5 years.</li>
+ </ol>
+ It is the responsibility of the Fellow to ensure that these conditions are met.</p>
+ <p>Upon appointment of the Editor-in-charge, the online Submission Page is automatically
+ created and opened for contributed Reports and Comments, and the Editor-in-charge is required to
+ immediately open a refereeing round.
+ </p>
+ </li>
+ <li><strong>Refereeing rounds</strong>
+ <ol>
+ <li>Opening
+ <p>Upon appointment of the Editor-in-charge, or resubmission after a major revision,
+ a refereeing round must be opened.
+ At least 3 referees must be invited to provide a Report.
+ Referees can accept or decline the invitation; if a referee declines or fails to commit
+ within 5 working days, the Editor-in-charge must seek an alternative referee.
+ </p>
+ </li>
+ <li>Duration
+ <p>The indicated duration of a refereeing round is 4 weeks for normal papers and 8 weeks for Lecture Notes,
+ counted from the moment one of the invited referees first accepts to provide a report.
+ Referees will automatically be sent reminders of impending deadlines.
+ </p>
+ </li>
+ <li>Access to identities
+ <p>Besides the invited Reports, contributed Reports and Comments can also be provided by
+ registered Contributors. Although anonymity can be requested by the Contributor upon
+ submission of a contributed Report, this implements anonymity on the public interface only: the
+ identity of the authors of all contributed Reports are accessible to the Editor-in-charge of
+ the Submission. It is forbidden for the Editor-in-charge to reveal those identities in any
+ way, except to non-conflicted members of the Editorial College or of the Advisory Board if it is deemed
+ necessary.</p>
+ </li>
+ <li>Admissibility of Reports and Comments
+ <p>The Editor-in-charge must ensure that referees he/she invites to report on a given manuscript
+ are in particular not in conflict of interest, personal or hierarchical relationship with any of the authors
+ and more generally fulfil the conditions stated in the
+ <a href="{% url 'journals:journals_terms_and_conditions' %}#referee_obligations">referee obligations</a>.
+ Similarly, the Editor-in-charge must verify that the authors of contributed Reports and Comments
+ also fulfil these conditions (this occurring during vetting of the Report). If in doubt, the Editor-in-charge
+ must disregard the Reports and Comments in question when formulating the Editorial Recommendation.</p>
+ </li>
+ <li>Closing and author reponse
+ <p>At the end of the stated duration, submission of Reports on the Submission Page is deactivated.
+ The Editor-in-charge invites the authors to finalize their responses to any submitted Reports
+ and Comments before the Editorial Recommendation is formulated.</p>
+ </li>
+ <li>Minimal number of Reports
+ <p>
+ Two types of Reports are considered: <em>invited</em> and <em>contributed</em>,
+ respectively from Editor-in-charge-invited or from volunteer referees.
+ Moreover, upon vetting, the Editor-in-charge determines whether a Report is
+ <em>substantial</em> (if it reviews the Submission
+ in a thorough and complete manner) or <em>fractional</em> (if it covers only
+ some aspects).
+ The minimal number of Reports required for the Editor-in-charge to make a
+ recommendation depends on the Journal which is submitted to:
+ </p>
+ <ul>
+ <li>for field-leading titles: at least two substantial Reports,
+ at least one of which is an invited one</li>
+ <li>for <em>Commons</em> and other field-specific titles: at least two Reports,
+ at least one of which is an invited one</li>
+ <li>for <em>Proceedings</em>: at least one Report.</li>
+ </ul>
+ <br/>
+ <p>
+ If none of the invited referees have responded within the first round,
+ the Editor-in-charge must start a second round and invite three new referees.
+ If no invited or contributed Report has been obtained at the end of the second round,
+ the Editor-in-charge can elect to put forth a motion of rejection due to lack
+ of interest, or to extend the refereeing round.</p>
+ </li>
+ </ol>
+ </li>
+ <li><strong>Editorial Recommendation</strong>
+ <p>An Editorial Recommendation is formulated by the Editor-in-charge at the end of a
+ refereeing round. The recommendation is based on the invited Reports, eventual contributed
+ Reports, eventual Comments together with the Editor-in-charge's own assessment of the Submission.
+ Such a recommendation is not made publicly visible. The recommendation can be for:
+ <ul>
+ <li>Publication as Select (reserved for the top 10% of papers submitted to a field-leading title)</li>
+ <li>Publication (in the targeted Journal)</li>
+ <li>Publication (promotion to field-leading Journal)</li>
+ <li>Publication (transfer to other Journal)</li>
+ <li>Minor revision</li>
+ <li>Major revision</li>
+ <li>Rejection.</li>
+ </ul>
+ </p>
+ <ol>
+ <li>
+ <p>A recommendation to Publish as Select, Publish or Reject is immediately forwarded to the
+ Editorial College for decision. It is at this stage not communicated to the authors.</p>
+ </li>
+ <li>
+ <p>If the Editorial Recommendation is for a minor or major revision, it is communicated
+ directly to the authors, who must then resubmit. Upon resubmission, the Editor-in-charge
+ can either start a new refereeing round or directly formulate a new editorial recommendation.</p>
+ </li>
+ </ol>
+ </li>
+ <li><strong>Editorial College Vote</strong>
+ <p>
+ The decision to publish or reject a paper is formally taken by the relevant
+ Editorial College.
+ After being formulated by the Editor-in-charge, the Editorial Recommendation
+ is made visible to all non-conflicted Fellows.
+ At this point, the recommendation can be one of these possibilities:
+ </p>
+ <ul>
+ <li>(for submissions to field-leading titles only) Publication as Select</li>
+ <li>Publication</li>
+ <li>Transfer to other Journal for Publication</li>
+ <li>Rejection.</li>
+ </ul>
+ <br/>
+ <ol>
+ <li><strong>Publication as Select</strong>
+ <p>
+ Submissions to a field-leading title which are deemed to be of superlative
+ quality (top 10% of the manuscripts published in that title) by the
+ Editor-in-charge can be put forward for potential publication
+ as Select. In this case, all Fellows of the Editorial College in the relevant
+ discipline can participate in the decision,
+ except for those in conflict of interest, personal or hierarchical relationship
+ with any of the authors. The Editor-in-charge by definition supports this promotion
+ to Select and does not need to vote;
+ other Fellows are asked to agree, abstain or disagree with the recommendation
+ to publish as Select. The Submission is promoted to Select if either:
+ </p>
+ <ul>
+ <li>specialist Fellows unanimously agree</li>
+ <li>a majority of specialist Fellows agrees, and no Fellow disagrees.</li>
+ </ul>
+ <br/>
+ <p>
+ If the Submission is not promoted to Select, the rules for normal Publication apply.
+ </p>
+ <p>
+ If the Submission is promoted to Select, then the main paper is prepared
+ for publication in the field-leading title, and the extended abstract is separately
+ prepared for publication in SciPost Selections.
+ </p>
+ </li>
+ <li><strong>Publication</strong>
+ <p>
+ If the editorial recommendation is to publish the paper, Fellows with expertises
+ corresponding to those of the Submission can vote to agree, abstain or disagree with
+ publication. The Submission is accepted if:
+ </p>
+ <ol>
+ <li>at least 4 specialist Fellows agree and none disagree</li>
+ <li>a majority of all specialist Fellows agrees.</li>
+ </ol>
+ <p>
+ Upon acceptance, the authors are informed and the paper is immediately
+ forwarded to Production.
+ </p>
+ <p>
+ If the editorial recommendation was to accept the paper, but the voting
+ conditions for acceptance given above are not met, then the Editor-in-charge
+ must reformulate the recommendation to either:
+ <ul>
+ <li>a request for revision, which is then forwarded to the authors, further
+ consideration of the manuscript then following the rules for resubmission</li>
+ <li>publication in another Journal</li>
+ </ul>
+ <br/>
+ For example, a submission failing to meet the requirements to be published
+ in a field-leading title can be put forward for publication in the field's
+ <em>Commons</em> title.
+ </p>
+ </li>
+ <li><strong>Rejection</strong>
+ <p>
+ If the editorial recommendation is to reject the paper, specialist Fellows are asked
+ to agree, abstain, or veto the recommendation.
+ </p>
+ <p>
+ If a majority of specialist
+ Fellows agrees to reject, the paper is rejected.
+ </p>
+ <p>
+ If a majority is not reached and
+ a Fellow disagrees with the recommendation to reject the paper,
+ that Fellow is invited to
+ take over as Editor-in-charge of the Submission and to start a
+ new refereeing round. If none of the disagreeing Fellows accept to take charge,
+ the paper is rejected.
+ </p>
+ <p>
+ Otherwise, if a majority is not reached but no Fellow has vetoed the
+ rejection recommendation, the paper is rejected.
+ </p>
+ <p>
+ Upon rejection, the authors are informed, the Submission Page
+ is deactivated and its contents removed from public view, unless the
+ authors explicitly request otherwise.
+ </p>
+ </li>
+ <li><strong>Special provision for <em>Proceedings</em></strong>
+ <p>For <em>Proceedings</em>-class Journals, the publication decision process is
+ delegated to the set of guest Fellows associated to the Proceedings Issue concerned.
+ To maintain high quality standards, the field's Editorial College retains rights
+ of regard and veto on any decisions taken by guest Fellows.
+ </p>
+ </li>
+ </ol>
+ </li>
+ <li><strong>Production</strong>
+ <p>Post-acceptance, the paper is handled by the production team, who produce the final version
+ of the manuscript and ensure compliance with publication requirements (including outbound
+ references linking). The final version is assigned a DOI and published online in the appropriate SciPost Journal.</p>
+ </li>
+ </ol>
+ </div>
+ </li>
+
+ <hr>
+ <li><strong>Amendments</strong> <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#Amendments">view/hide</a>
+ <div id="Amendments" class="py-2" style="display: none;">
+ <p>The present By-laws can be amended by:
+ <ul>
+ <li>the Foundation, with veto right (by majority vote) from the Advisory Board</li>
+ <li>by motion at a VGM, the motion being supported by a three-quarters majority vote of
+ all the Editorial Fellows, with veto right from the Foundation and (by majority vote) from the Advisory Board.</li>
+ </ul>
+ </p>
+ </div>
+ </li>
+ </ol>
+
+ </div>
+</div>
+
+
+
+</div>
+{% endif %}
+
+
+
<div class="row">
<div class="col-12">
<h1 class="highlight">SciPost Editorial College By-laws</h1>
@@ -25,8 +512,8 @@
<p>These complement and are subsidiary to the legal statutes of Stichting SciPost (hereafter: the Foundation).</p>
<ol>
<hr>
- <li>Composition of the Editorial College <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#Composition">view/hide</a>
- <div id="Composition" class="py-2" style="display: none;">
+ <li>Composition of the Editorial College <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#CompositionOld">view/hide</a>
+ <div id="CompositionOld" class="py-2" style="display: none;">
<ol>
<li>Eligibility
<p>Fellows of the Editorial College must be professionally active academics
@@ -93,8 +580,8 @@
</li>
<hr>
- <li>Meetings <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#Meetings">view/hide</a>
- <div id="Meetings" class="py-2" style="display: none;">
+ <li>Meetings <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#MeetingsOld">view/hide</a>
+ <div id="MeetingsOld" class="py-2" style="display: none;">
<p>The Editorial College, consisting of internationally-renowned scientists with a broad
geographic distribution, does not physically meet. Meetings are instead organized
using online facilities.</p>
@@ -129,8 +616,8 @@
</li>
<hr>
- <li>Submissions processing <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#SubmissionsProcessing">view/hide</a>
- <div id="SubmissionsProcessing" class="py-2" style="display: none;">
+ <li>Submissions processing <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#SubmissionsProcessingOld">view/hide</a>
+ <div id="SubmissionsProcessingOld" class="py-2" style="display: none;">
<p>The primary responsibility of the Editorial College is to run the editorial process
for all SciPost Journals. The College shall strive for the very highest standards of
professionalism achievable in the refereeing process.</p>
@@ -337,8 +824,8 @@
</li>
<hr>
- <li>Amendments <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#Amendments">view/hide</a>
- <div id="Amendments" class="py-2" style="display: none;">
+ <li>Amendments <a href="javascript:;" class="btn btn-default" data-toggle="toggle" data-target="#AmendmentsOld">view/hide</a>
+ <div id="AmendmentsOld" class="py-2" style="display: none;">
<p>The present By-laws can be amended by:
<ul>
<li>the Foundation, with veto right (by majority vote) from the Advisory Board</li>
diff --git a/scipost/templates/scipost/PlanSciPost.html b/scipost/templates/scipost/PlanSciPost.html
index 58e5833e2f8976754fe37bbcd8f1772be7e50889..f48e270d885c0a0d0d89d83b3ebb64cdeab9c0e0 100644
--- a/scipost/templates/scipost/PlanSciPost.html
+++ b/scipost/templates/scipost/PlanSciPost.html
@@ -25,17 +25,17 @@
<p class="ml-2 mr-2">We propose a simple hierarchy:</p>
<ul class="ml-3 mr-3">
<li><strong>A family of Journals for each field of science, headed by a field-leading title, and managed by a field-specific Editorial College</strong></li>
- <li><strong>A central Journal for top-level breakthroughs selected from field-leading titles</strong></li>
+ <li><strong>A central multidisciplinary Journal presenting extended abstracts of top-level breakthroughs, editorially selected from field-leading titles</strong></li>
</ul>
<p class="ml-2 mr-2">The general architecture is illustrated as follows:</p>
- <img style="max-width: 600px;" src="{% static 'scipost/2018_10_SciPost_Journals_plan.png' %}"></img>
+ <p><img style="max-width: 600px;" src="{% static 'scipost/2018_10_SciPost_Journals_plan.png' %}"></img></p>
- <p class="ml-2 mr-2">Within a given field, the set of journal titles is designed to respond to and serve field-specific needs (see the example of our family of <a href="{% url 'journals:journals' %}#physics">Physics Journals</a>). Each Journal must however follow our peer-witnessed refereeing workflow and general Editorial College-based procedures. Moreover, each field is to feature a field-leading title mirroring our pioneering Journal <a href="{% url 'journal:about' 'SciPostPhys' %}">SciPost Physics</a> (and in particular implementing promotion of selected extended abstracts for publication in <a href="{% url 'journals:journals' %}#selections">SciPost Selections</a>).</p>
+ <p class="ml-2 mr-2">Within a given field, the set of journal titles is designed to respond to and serve field-specific needs (see the example of our family of <a href="{% url 'journals:journals' %}#physics">Physics Journals</a>). Each Journal must however follow our open peer-witnessed refereeing workflow and general Editorial College-based procedures. Moreover, each field is to feature a field-leading title mirroring our pioneering Journal <a href="{% url 'journal:about' 'SciPostPhys' %}">SciPost Physics</a> (and in particular implementing promotion of selected extended abstracts for publication in <a href="{% url 'journals:journals' %}#selections">SciPost Selections</a>).</p>
<h3>Current situation and triggers for expansion</h3>
<p class="ml-2 mr-2 mt-2">
The Physics side of our operations is by now established, with our <a href="{% url 'journals:journals' %}#physics">Physics Journals</a> published under the auspices of the <a href="{% url 'scipost:about' %}#editorial_college_physics">Editorial College (Physics)</a>. We will continue expanding this side of our operations according to the increase in the number of submissions we receive.</p>
- <p class="ml-2 mr-2">On the infrastructure side, we have made great strides. Our platform is not just a simple website: we have conceived, designed and implemented a fully-featured system to handle all aspects of the publication business, from manuscript submission all the way to professional metadata curation. Since our systems were implemented from the start in a field-agnostic way, we are now in perfect position to enable other fields to profit from our development work.
+ <p class="ml-2 mr-2">On the infrastructure side, we have made great strides. Our platform is not just a website: we have conceived, designed and implemented a fully-featured system to handle all aspects of the publication business, from manuscript submission all the way to professional metadata curation. Since our systems were implemented from the start in a field-agnostic way, we are now in perfect position to enable other fields to profit from our development work.
</p>
<p class="ml-2 mr-2">
We are ready to launch operations in other fields; for any given field, we require that two simple preconditions (triggers) be met:
@@ -54,7 +54,7 @@
<div class="card-header"><strong>Support</strong></div>
<div class="card-body">
<ul>
- <li>Sufficient <a href="{% url 'sponsors:sponsors' %}">Sponsorships</a> to cover the equivalent of one more full-time editorial staff in our team</li>
+ <li>Sufficient <a href="{% url 'sponsors:sponsors' %}">Sponsorships</a> to cover the expected workflow (minimum of one more full-time editorial staff per new field)</li>
</ul>
</div>
</div>
diff --git a/scipost/templates/scipost/index.html b/scipost/templates/scipost/index.html
index a47a00d6dc11067f0ff14b190e356a315e9d8d4e..9f78caf59e23dbdd732cc4b3e8c8b768143f6818 100644
--- a/scipost/templates/scipost/index.html
+++ b/scipost/templates/scipost/index.html
@@ -15,7 +15,7 @@
<li class="nav-item">
{% if journal.active %}
<a href="{{journal.get_absolute_url}}" class="nav-link">{{journal}}</a>
- {% else %}
+ {% elif perms.scipost.can_view_pool %}
<a href="{% url 'journal:about' journal.name %}" class="nav-link">{{journal}}</a>
{% endif %}
</li>
diff --git a/submissions/migrations/0037_auto_20181023_0829.py b/submissions/migrations/0037_auto_20181023_0829.py
new file mode 100644
index 0000000000000000000000000000000000000000..64dd8dcb10fda999c084c018d644c0109819d59a
--- /dev/null
+++ b/submissions/migrations/0037_auto_20181023_0829.py
@@ -0,0 +1,20 @@
+# -*- coding: utf-8 -*-
+# Generated by Django 1.11.4 on 2018-10-23 06:29
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+
+ dependencies = [
+ ('submissions', '0036_merge_20181002_1358'),
+ ]
+
+ operations = [
+ migrations.AlterField(
+ model_name='submission',
+ name='submitted_to_journal',
+ field=models.CharField(choices=[('SciPostPhys', 'SciPost Physics'), ('SciPostPhysComm', 'SciPost Physics Commons'), ('SciPostPhysLectNotes', 'SciPost Physics Lecture Notes'), ('SciPostPhysProc', 'SciPost Physics Proceedings'), ('SciPostPhysCodeb', 'SciPost Physics Codebases')], max_length=30, verbose_name='Journal to be submitted to'),
+ ),
+ ]
diff --git a/submissions/templates/submissions/sub_and_ref_procedure.html b/submissions/templates/submissions/sub_and_ref_procedure.html
index 4e035d41f7f5a3d3b8c3f0716ed6322b928d6290..5e5c1833b688ad9076c6782a98b60866a939ffb0 100644
--- a/submissions/templates/submissions/sub_and_ref_procedure.html
+++ b/submissions/templates/submissions/sub_and_ref_procedure.html
@@ -21,6 +21,76 @@
</div>
</div>
+{% if perms.scipost.can_view_pool %}
+<div class="container border border-danger">
+ <span class="text-danger">DRAFT (POOLVIEW ONLY) - <a href="mailto:admin@scipost.org">COMMENTS WELCOME</a></span>
+
+<div class="row">
+ <div class="col-12">
+ <h2>Submission</h2>
+ <p>This is a quick summary. For more details, see the <a href="{% url 'journals:journals_terms_and_conditions' %}">SciPost Journals Terms and Conditions</a>
+ and the <a href="{% url 'submissions:author_guidelines' %}">author guidelines</a>.</p>
+ <h3>To submit an article for publication in a SciPost Journal, authors must:</h3>
+ <ol>
+ <li>Prepare their manuscript following the <a href="{% url 'submissions:author_guidelines' %}">author guidelines</a></li>
+ <li>Make your preprint publicly available on an appropriate preprint server:
+ <ul>
+ <li>Physics, Mathematics, Computer Science: <a href="http://arxiv.org">arXiv.org</a></li>
+ </ul>
+ </li>
+ <li>After appearance on the preprint server, fill the SciPost <a href="{% url 'submissions:submit_manuscript' %}">Submission</a> form, selecting which SciPost Journal to submit to and providing domain and speciality specifications.</li>
+ </ol>
+ </div>
+</div>
+
+
+<hr>
+<div class="row">
+ <div class="col-12">
+ <h2 id="pwr">Refereeing procedure</h2>
+ <p>All incoming Submissions to SciPost Journals are peer-reviewed using SciPost's <a href="/FAQ#pwr">peer-witnessed refereeing</a> process, implementing the highest standard of refereeing available. The procedure follows this pattern (this is a summary; the official rules are set out in the <a href="{% url 'scipost:EdCol_by-laws' %}">Editorial College by-laws</a> under section <em>Submissions processing</em>):</p>
+ <ol>
+ <li>
+ <strong>Pre-screening: plagiarism and conflicts of interest</strong>
+ <br/>The Submission is checked for plagiarism, and appropriate action (immediate rejection; request to authors for modified version) is taken if necessary. A thorough scan is performed to flag potential conflicts of interest of authors with Fellows.
+ </li>
+ <li>
+ <strong>Screening: finding an Editor-in-charge</strong>
+ <br/>The Submission is internally forwarded to Fellows of the relevant Editorial College, for them to consider becoming Editor-in-charge. For our Commons journals, members of the community can also be approached (in which case they become guest Fellows). If a (guest) Fellow expresses interest in the submission, he/she becomes Editor-in-charge. This screening process should occur on a timescale of 5 working days. Authors are contacted by our editorial administration in case of problems, in particular if extensions to the screening period prove necessary.</li>
+ <li>
+ <strong>Activation of the Submission page</strong>
+ <br/>Following successful screening, a Submission Page is activated. The Submission is immediately opened to Contributor Reports, Comments and Author Replies, all of which are vetted by an Editorial Fellow before eventually appearing online.</li>
+ <li>
+ <strong>Refereeing round</strong>
+ <br/>The Editor-in-charge starts a refereeing round (whose duration depends on the Journal, see below), inviting specific Contributors to provide an Invited Report.
+ During a refereeing round, registered Contributors to SciPost can volunteer a Contributed Report, and authors can continuously provide Replies to Reports and Comments.
+ The contents of Reports are publicly viewable, but the author of the Report can choose public anonymity (which is then known to Editors only). Authors are informed by email if a Report or a Comment on their paper is vetted through and published online (authors are welcome to respond, but should not feel obliged to do so before the refereeing round is closed).</li>
+ <li>
+ <strong>Closing of the refereeing round</strong>
+ <br/>At the end of the refereeing round, submission of Contributed Reports on the Submission Page is deactivated (reports from invited referees can still be considered, at the discretion of the Editor-in-charge). The Editor-in-charge invites the authors to finalize their responses to any submitted Reports and Comments before the Editorial Recommendation is formulated.</li>
+ <li>
+ <strong>Editorial recommendation</strong>
+ <br/>Reports, Replies and Comments are then assessed by the Editor-in-charge, who formulates an editorial recommendation.
+ <ol>
+ <li>If the editorial recommendation is for publication or rejection, it is forwarded to the Editorial College, which takes the binding editorial decision by consultation of the relevant specialty's Editorial Fellows (voting rights are given to at least 9 Fellows). If the recommendation is to publish the paper as Tier I (targeting approximately the top 10% of articles considered), a selection of Editorial Fellows from all specialties are given voting rights and can thus support or object to this promotion.</li>
+ <li>If the Editorial Recommendation is for a minor or major revision, it is communicated directly to the authors, who must then resubmit. Upon resubmission, the Editor-in-charge can either start a new refereeing round or directly formulate a new editorial recommendation.</li>
+ </ol></li>
+ <li>
+ <strong>Decision</strong>
+ <br/>After being taken by the Editorial College, the editorial decision (consisting in either a publication offer, or rejection) is communicated to the Authors.</li>
+ <ol>
+ <li>If the authors accept an eventual publication offer, the manuscript is sent to the production team. The final version is published online in the relevant SciPost Journal. The publication page links back to the original Submission Page and its contents.</li>
+ <li>If the manuscript is rejected or authors withdraw their Submission, the Submission Page is deactivated and removed from public view, unless the authors request it to remain available.</li>
+ </ol>
+ </ol>
+ <p>The duration of refereeing rounds depends on the Journal, but is normally 4 weeks for article-class material and 8 weeks for Lecture Notes-class material.</p>
+ </div>
+</div>
+
+
+</div>
+{% endif %}
+
<div class="row">
<div class="col-12">
<h2>Submission</h2>