From 50b7dd85799252b55a6e61ad0dcfc86ca53c1f6e Mon Sep 17 00:00:00 2001
From: Jean-Sebastien Caux <jscaux@ABACUS.local>
Date: Sun, 17 Apr 2016 10:00:07 +0200
Subject: [PATCH] Change presentation overall (remove separate page for PWR
refereeing)
---
scipost/models.py | 2 +-
scipost/templates/scipost/FAQ.html | 16 +++++++++--
scipost/templates/scipost/graph.html | 8 ++++++
scipost/templates/scipost/index.html | 3 +-
.../scipost/peer_witnessed_refereeing.html | 27 ------------------
scipost/urls.py | 2 --
scipost/views.py | 5 ----
.../submissions/sub_and_ref_procedure.html | 28 ++++++++++++-------
.../templates/submissions/submissions.html | 1 -
9 files changed, 42 insertions(+), 50 deletions(-)
delete mode 100644 scipost/templates/scipost/peer_witnessed_refereeing.html
diff --git a/scipost/models.py b/scipost/models.py
index 74a5071b1..29b8e09ab 100644
--- a/scipost/models.py
+++ b/scipost/models.py
@@ -344,7 +344,7 @@ class Team(models.Model):
"""
leader = models.ForeignKey(Contributor)
members = models.ManyToManyField (Contributor, blank=True, related_name='team_members')
- name = models.CharField(max_length=20)
+ name = models.CharField(max_length=100)
established = models.DateField(default=timezone.now)
def __str__(self):
diff --git a/scipost/templates/scipost/FAQ.html b/scipost/templates/scipost/FAQ.html
index fa6dbfe9d..4c3d2d4eb 100644
--- a/scipost/templates/scipost/FAQ.html
+++ b/scipost/templates/scipost/FAQ.html
@@ -21,13 +21,13 @@
</div>
<h3>What are the distinguishing features of SciPost Journals?</h3>
<p>All SciPost Journals are subscription-free, two-way open access (free for readers, free for authors) online journals.</p>
- <p>Manuscripts submitted to SciPost undergo the extremely stringent <a href="{% url 'scipost:peer_witnessed_refereeing' %}">peer-witnessed refereeing</a> process, guaranteeing that papers published in SciPost Journals meet the highest possible academic standards.</p>
+ <p>Manuscripts submitted to SciPost undergo the extremely stringent <a href="/scipost/FAQ/#pwr">peer-witnessed refereeing</a> process, guaranteeing that papers published in SciPost Journals meet the highest possible academic standards.</p>
<br/>
<hr class="hr6">
<h3>Why should I submit my manuscripts to SciPost?</h3>
<p>Because:</p>
<ul>
- <li>you think your work can withstand the stringest form of pre-publication scrutiny: <a href="{% url 'scipost:peer_witnessed_refereeing' %}">peer-witnessed refereeing</a></li>
+ <li>you think your work can withstand the stringest form of pre-publication scrutiny: <a href="/scipost/FAQ/#pwr">peer-witnessed refereeing</a></li>
<li>you want your referees to have to adhere to the same standards of professionalism which are expected of you as an author</li>
<li>you want all steps of the editorial process to be handled by professional scientists, not non-specialist journal staff editors</li>
<li>you want your published work to be openly accessible and not hidden behind a paywall</li>
@@ -39,6 +39,18 @@
<h3>How do I submit my manuscript to SciPost?</h3>
<p>After registering as a Contributor, simply follow the <a href="{% url 'submissions:sub_and_ref_procedure' %}">submission procedure</a>.</p>
<br/>
+ <br/>
+ <hr class="hr6">
+ <h3 id="pwr">How does peer-witnessed refereeing work?</h3>
+ <p>This is a short summary; for a more detailed description, see our <a href="{% url 'submissions:sub_and_ref_procedure' %}">submission and refereeing procedure</a>.</p>
+ <ul>
+ <li>Reports are gathered from editorially-invited referees, but can also be volunteered by registered SciPost Contributors during refereeing rounds.</li>
+ <li>Reports are posted online (after rapid editorial vetting) on the Submission's Page, and can be replied to (privilege of Authors only) or commented on by all Contributors.</li>
+ <li>Anonymity can be preserved at all meaningful stages if desired (as a referee, you can choose to remain anonymous on a particular Report, but named on another).</li>
+ </ul>
+ <p>Contributors thus have additional incentives to actively participate and provide not only high-quality Submissions,
+ but also Reports and Comments of the highest achievable professional caliber.
+ Quality is moreover promoted by Editorial vetting of all Reports, Replies and Comments before public posting.</p>
<hr class="hr6">
<h3>Will my SciPost publications be citable?</h3>
<p>All SciPost publications will obtain a unique DOI, enabling citations and metrics as per other journals.</p>
diff --git a/scipost/templates/scipost/graph.html b/scipost/templates/scipost/graph.html
index 60406c2e9..511b067d7 100644
--- a/scipost/templates/scipost/graph.html
+++ b/scipost/templates/scipost/graph.html
@@ -162,6 +162,14 @@ function transform(d) {
<section>
<h1>Graph</h1>
{{ graph }}
+ {% if graph.private }}
+ <h3>Teams with access:</h3>
+ <ul>
+ {% for team in graph.teams_with_access %}
+ {{ team.header_as_li }}
+ {% endfor %}
+ </ul>
+ {% endif %}
<div class="row">
<div class="col-3">
diff --git a/scipost/templates/scipost/index.html b/scipost/templates/scipost/index.html
index cce12c3bd..5094b88ea 100644
--- a/scipost/templates/scipost/index.html
+++ b/scipost/templates/scipost/index.html
@@ -22,9 +22,8 @@
<h1><a href="{% url 'journals:journals' %}">Journals</a></h1>
<p id="journalsannouncesmall">OPEN FOR SUBMISSION FROM JUNE 2016</p>
<p>SciPost publishes a portfolio of high-quality two-way open access scientific journals.</p>
- <p>All SciPost Journals implement the stringent <a href="{% url 'scipost:peer_witnessed_refereeing' %}">peer-witnessed refereeing</a> principle.</p>
+ <p>All SciPost Journals implement the stringent <a href="/scipost/FAQ/#pwr">peer-witnessed refereeing</a> principle.</p>
<p>All Journals are fully managed by professional scientists.</p>
- <h3><a href="{% url 'scipost:peer_witnessed_refereeing' %}">About peer-witnessed refereeing</a></h3>
<h3><a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and refereeing procedure</a></h3>
</div>
</div>
diff --git a/scipost/templates/scipost/peer_witnessed_refereeing.html b/scipost/templates/scipost/peer_witnessed_refereeing.html
deleted file mode 100644
index 4e1366ae6..000000000
--- a/scipost/templates/scipost/peer_witnessed_refereeing.html
+++ /dev/null
@@ -1,27 +0,0 @@
-{% extends 'scipost/base.html' %}
-
-{% block pagetitle %}: peer-witnessed refereeing{% endblock pagetitle %}
-
-{% block bodysup %}
-
-<section>
- <div class="flex-greybox">
- <h1>SciPost's Peer Review Method: Peer-Witnessed Refereeing.</h1>
- </div>
- <h3>Reporting</h3>
- <ul>
- <li>Reports are gathered from editorially-invited referees, but can also be volunteered by registered SciPost Contributors during refereeing rounds.</li>
- <li>Reports are posted online (after rapid editorial vetting) on the Submission's Page, and can be replied to (Authors only) or commented on by all Contributors.</li>
- <li>Anonymity can be preserved at all meaningful stages if desired (you can e.g. elect to remain anonymous on a given Report, but named on another).</li>
- </ul>
-
- <p>Contributors thus have additional incentives to actively participate and provide not only high-quality Submissions, but also Reports and Comments of the highest achievable professional caliber.</p>
- <p>Abusive behaviour is prevented by Editorial vetting of all Reports, Replies and Comments before public posting.</p>
-
- <br />
- <h1><a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and Refereeing procedure</a></h1>
-
-
-</section>
-
-{% endblock bodysup %}
diff --git a/scipost/urls.py b/scipost/urls.py
index 50ed36f30..5a49b1364 100644
--- a/scipost/urls.py
+++ b/scipost/urls.py
@@ -14,8 +14,6 @@ urlpatterns = [
url(r'^FAQ$', TemplateView.as_view(template_name='scipost/FAQ.html'), name='FAQ'),
url(r'^terms_and_conditions$', TemplateView.as_view(template_name='scipost/terms_and_conditions.html'), name='terms_and_conditions'),
url(r'^privacy_policy$', TemplateView.as_view(template_name='scipost/privacy_policy.html'), name='privacy_policy'),
- #url(r'^description$', views.description, name='description'),
- url(r'^peer_witnessed_refereeing$', TemplateView.as_view(template_name='scipost/peer_witnessed_refereeing.html'), name='peer_witnessed_refereeing'),
# Search
url(r'^search$', views.search, name='search'),
diff --git a/scipost/views.py b/scipost/views.py
index b0701f440..8f92b40f8 100644
--- a/scipost/views.py
+++ b/scipost/views.py
@@ -130,11 +130,6 @@ def index(request):
def base(request):
return render(request, 'scipost/base.html')
-def description(request):
- response = HttpResponse(content_type='application/pdf')
- response['Content-Disposition'] = 'filename="SciPost_Description.pdf"'
- return response
-
################
# Contributors:
diff --git a/submissions/templates/submissions/sub_and_ref_procedure.html b/submissions/templates/submissions/sub_and_ref_procedure.html
index 92fca584b..be682cb11 100644
--- a/submissions/templates/submissions/sub_and_ref_procedure.html
+++ b/submissions/templates/submissions/sub_and_ref_procedure.html
@@ -27,18 +27,26 @@
<br/>
<hr class="hr6"/>
- <h3>Refereeing procedure</h3>
- <p>All incoming Submissions to SciPost Journals are peer-reviewed using SciPost's <a href="{% url 'scipost:peer_witnessed_refereeing' %}">peer-witnessed refereeing</a> process, implementing the highest standard of refereeing available. The precise procedure follows this pattern (the various types of Editors are described in the next section):</p>
- <ul>
- <li>A member of the Editorial College is internally selected and becomes Editor-in-charge of the manuscript. A Submission Page is activated (this is similar to a Commentary Page, but with Reports also enabled), and is immediately open to Contributor Comments and Author Replies, all of which are vetted by the Editor-in-charge of the submission.</li>
- <li>The Editor-in-charge starts a Refereeing round (whose duration depends on the Journal, see below), inviting specific Contributors to provide an Invited Report.</li>
+ <h3 id="pwr">Refereeing procedure</h3>
+ <p>All incoming Submissions to SciPost Journals are peer-reviewed using SciPost's <a href="/scipost/FAQ/#pwr">peer-witnessed refereeing</a> process, implementing the highest standard of refereeing available. The precise procedure follows this pattern:</p>
+ <ol>
+ <li>A member of the Editorial College is internally selected and becomes Editor-in-charge of the manuscript.</li>
+ <li>A Submission Page is activated (this is similar to a Commentary Page, but with Reports also enabled).</li>
+ <li>The Submission is immediately opened to Contributor Comments and Author Replies, all of which are vetted by an Editorial Fellow before eventually appearing online.</li>
+ <li>The Editor-in-charge starts a refereeing round (whose duration depends on the Journal, see below), inviting specific Contributors to provide an Invited Report.</li>
<li>During a refereeing round, registered Contributors to SciPost can volunteer a Contributed Report.</li>
<li>During the refereeing round, authors can continuously provide Replies to Reports and Comments.</li>
- <li>At the end of the refereeing round, Reports, Replies and Comments are assessed by the Editor-in-charge, who formulates an editorial recommendation and forwards it to the
-Editorial College, which takes the editorial decision by majority vote of the relevant specialty’s Editorial Fellows.</li>
- <li>The Editorial decision is communicated to the Authors. This consists in either a publication offer, request for resubmission (with minor revisions, or major revisions (leading to another refereeing round)), or rejection.</li>
- <li>The Authors can respond to the Editorial decision by accepting an eventual publication offer (in which case the Submission Page and its contents are moved to a SciPost Publication Page), by revising their manuscript and resubmitting to SciPost (in which case a new Submission Page is opened, retaining a link to the previous version's Submission Page), or by withdrawing their Submission (in which case the Submission Page is deactivated and all its contents removed from public view).</li>
- </ul>
+ <li>At the end of the refereeing round, Reports, Replies and Comments are 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.</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>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 all its contents removed from public view.</li>
+ </ol>
+ </ol>
<p>The duration of refereeing rounds depends on the Journal: 4 weeks for traditional articles, and 8 weeks for Lecture Notes.</p>
</section>
diff --git a/submissions/templates/submissions/submissions.html b/submissions/templates/submissions/submissions.html
index c6ee4f481..96a75f8df 100644
--- a/submissions/templates/submissions/submissions.html
+++ b/submissions/templates/submissions/submissions.html
@@ -13,7 +13,6 @@
<div class="flex-container">
<div class="flex-greybox320">
<h1>SciPost Submissions</h1>
- <h3><a href="{% url 'scipost:peer_witnessed_refereeing' %}">About peer-witnessed refereeing</a></h3>
<h3><a href="{% url 'submissions:sub_and_ref_procedure' %}">Submission and refereeing procedure</a></h3>
<h3><a href="{% url 'submissions:submit_manuscript' %}">Submit a manuscript to SciPost</a></h3>
</div>
--
GitLab