SciPost Code Repository

Skip to content
Snippets Groups Projects
Commit b298f3cf authored by Jean-Sébastien Caux's avatar Jean-Sébastien Caux
Browse files

Add .docx template file field to Journal; specialize authoring ins.

parent 3680bf53
No related branches found
No related tags found
No related merge requests found
# Generated by Django 2.2.16 on 2021-04-21 20:11
from django.db import migrations, models
class Migration(migrations.Migration):
dependencies = [
('journals', '0106_journal_cf_metrics'),
]
operations = [
migrations.AddField(
model_name='journal',
name='template_docx',
field=models.FileField(blank=True, help_text='.docx template', max_length=256, upload_to='UPLOADS/TEMPLATES/docx/%Y/', verbose_name='Template (.docx)'),
),
]
...@@ -85,13 +85,17 @@ class Journal(models.Model): ...@@ -85,13 +85,17 @@ class Journal(models.Model):
verbose_name='Template (LaTeX, gzipped tarball)', verbose_name='Template (LaTeX, gzipped tarball)',
help_text='Gzipped tarball of the LaTeX template package', help_text='Gzipped tarball of the LaTeX template package',
upload_to='UPLOADS/TEMPLATES/latex/%Y/', max_length=256, blank=True) upload_to='UPLOADS/TEMPLATES/latex/%Y/', max_length=256, blank=True)
template_docx = models.FileField(
verbose_name='Template (.docx)',
help_text='.docx template',
upload_to='UPLOADS/TEMPLATES/docx/%Y/', max_length=256, blank=True)
# Cost per publication information # Cost per publication information
cost_info = JSONField(default=cost_default_value) cost_info = JSONField(default=cost_default_value)
# Calculated fields (to save CPU; field name always starts with cf_) # Calculated fields (to save CPU; field name always starts with cf_)
cf_metrics = JSONField(default=dict) cf_metrics = JSONField(default=dict)
objects = JournalQuerySet.as_manager() objects = JournalQuerySet.as_manager()
class Meta: class Meta:
...@@ -192,7 +196,7 @@ class Journal(models.Model): ...@@ -192,7 +196,7 @@ class Journal(models.Model):
if citation['year'] == str(year): if citation['year'] == str(year):
ncites += 1 ncites += 1
return ncites return ncites
def citedby_impact_factor(self, year, specialty=None): def citedby_impact_factor(self, year, specialty=None):
"""Compute the impact factor for a given year YYYY, from Crossref cited-by data. """Compute the impact factor for a given year YYYY, from Crossref cited-by data.
...@@ -238,7 +242,7 @@ class Journal(models.Model): ...@@ -238,7 +242,7 @@ class Journal(models.Model):
if int(citation['year']) <= year and int(citation['year']) >= year - 3: if int(citation['year']) <= year and int(citation['year']) >= year - 3:
ncites += 1 ncites += 1
return ncites / nrpub return ncites / nrpub
def cost_per_publication(self, year): def cost_per_publication(self, year):
try: try:
return int(self.cost_info[str(year)]) return int(self.cost_info[str(year)])
...@@ -252,7 +256,7 @@ class Journal(models.Model): ...@@ -252,7 +256,7 @@ class Journal(models.Model):
publications = self.get_publications() publications = self.get_publications()
from submissions.models import Submission from submissions.models import Submission
if publications: if publications:
pubyears = [year for year in range(publications.last().publication_date.year, pubyears = [year for year in range(publications.last().publication_date.year,
timezone.now().year)] timezone.now().year)]
else: else:
pubyears = [timezone.now().year] pubyears = [timezone.now().year]
......
...@@ -27,15 +27,28 @@ ...@@ -27,15 +27,28 @@
<div class="row"> <div class="row">
<div class="col-12"> <div class="col-12">
<hr> <hr>
<h2 class="highlight" id="manuprep">Manuscript preparation</h2> <h2 class="highlight" id="manuprep">Manuscript preparation</h2>
<p>We prefer authors to prepare their manuscript using the SciPost LaTeX2e style, which you can download {% if journal.doi_label == 'MigPol' %}
as a <a href="{% static 'submissions/latex/SciPost_LaTeX_Style_v1e.tar.gz' %}">gzipped tarball</a>, <p>Authors can prepare their manuscript in Word or LaTeX.</p>
composed of the following individual files: <p>
<ul> For Word, please use this <a href="{{ journal.template_docx.url }}">template</a>.
<li><a href="{% static 'submissions/latex/SciPost_LaTeX_Template.tex' %}">LaTeX2e template (.tex)</a></li> Manuscripts should be <strong>submitted as pdf files.</strong>
</p>
<p>For LaTeX, we prefer authors to prepare their manuscript using the SciPost LaTeX2e style, which you can download
as a <a href="{% static 'submissions/latex/SciPost_LaTeX_Style_v1e.tar.gz' %}">gzipped tarball</a>,
composed of the following individual files:
</p>
{% else %}
<p>We prefer authors to prepare their manuscript using the SciPost LaTeX2e style, which you can download
as a <a href="{% static 'submissions/latex/SciPost_LaTeX_Style_v1e.tar.gz' %}">gzipped tarball</a>,
composed of the following individual files:
</p>
{% endif %}
<ul>
<li><a href="{% static 'submissions/latex/SciPost_LaTeX_Template.tex' %}">LaTeX2e template (.tex)</a></li>
<li><a href="{% static 'submissions/latex/SciPost_LaTeX_Template.pdf' %}">LaTeX2e template (.pdf)</a></li> <li><a href="{% static 'submissions/latex/SciPost_LaTeX_Template.pdf' %}">LaTeX2e template (.pdf)</a></li>
<li><a href="{% static 'submissions/latex/SciPost.cls' %}">class file (.cls)</a></li> <li><a href="{% static 'submissions/latex/SciPost.cls' %}">class file (.cls)</a></li>
<li><a href="{% static 'submissions/latex/SciPost_bibstyle.bst' %}">BiBTeX style file (.bst)</a></li> <li><a href="{% static 'submissions/latex/SciPost_bibstyle.bst' %}">BiBTeX style file (.bst)</a></li>
...@@ -100,8 +113,12 @@ ...@@ -100,8 +113,12 @@
<p>All elements in your paper (equations, references, tables, figures etc) <p>All elements in your paper (equations, references, tables, figures etc)
should be hyperlinked to ensure ease of navigation.</p> should be hyperlinked to ensure ease of navigation.</p>
<p>There is no strict length limitation, but the authors are strongly encouraged to keep contents to the {% if journal.doi_label == 'MigPol' %}
strict minimum necessary for peers to reproduce the research described in the paper.</p> <p>Articles should be 6000 to 12000 words in length.</p>
{% else %}
<p>There is no strict length limitation, but the authors are strongly encouraged to keep contents to the
strict minimum necessary for peers to reproduce the research described in the paper.</p>
{% endif %}
<hr> <hr>
<h2 class="highlight" id="manusub">Manuscript submission</h2> <h2 class="highlight" id="manusub">Manuscript submission</h2>
...@@ -157,7 +174,9 @@ ...@@ -157,7 +174,9 @@
<hr> <hr>
<h2 class="highlight" id="resub">Resubmission</h2> <h2 class="highlight" id="resub">Resubmission</h2>
<p> <p>
To resubmit your manuscript, simply upload your new version to the arXiv. When this has appeared, you can then re-fill our <a href="{% url 'submissions:submit_manuscript' %}">Submission</a> form. Our system will automatically recognize your new version as a resubmission of your earlier manuscript. To resubmit your manuscript, please follow the resubmission link (from your personal page,
as corresponding author). Our system will then automatically recognize your new version
as a resubmission of your earlier manuscript.
</p> </p>
<hr> <hr>
...@@ -217,12 +236,16 @@ ...@@ -217,12 +236,16 @@
</p> </p>
</li> </li>
<li> <li>
<h4>Do I need to re-upload to the arXiv for each resubmission?</h4> <h4>Do I need to re-upload to a preprint server for each resubmission?</h4>
<p> <p>
Yes. We require your manuscript to be accessible to and seen by all interested parties worldwide, and the arXiv is the best channel for ensuring this. Ideally, yes, but we actually do not enforce this.
We prefer your manuscript to be accessible to and seen by all interested parties worldwide,
and the relevant preprint server is the best channel for ensuring this.
</p> </p>
<p> <p>
The only case in which you don't need to re-upload to the arXiv is when your manuscript has been accepted, and the (hopefully very minor) last modifications can be implemented by our production team during the proofs stage. The only case in which you don't need to re-upload to the relevant preprint server
is when your manuscript has been accepted, and the (hopefully very minor) last modifications
can be implemented by our production team during the proofs stage.
</p> </p>
</li> </li>
<li> <li>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment