{% extends "admin/core/base.html" %} {% load foundation %} {% load i18n %} {% block title %}Projected Issue {{ article.title }}{% endblock %} {% block title-section %}Projected Issue{% endblock %} {% block title-sub %}#{{ article.pk }} / {{ article.correspondence_author.last_name }} / {{ article.safe_title }}{% endblock %} {% block breadcrumbs %} {{ block.super }} {% include "elements/breadcrumbs/unassigned_base.html" %}
  • {{ article.safe_title }}
  • Assign Projected Issue
  • {% endblock breadcrumbs %} {% block body %}

    Form

    {% csrf_token %} {{ form|foundation }}

    Help

    {% trans "What is this for?" %}

    {% trans "The projected issue field can be used internally to keep track of plans and communicate with typesetters, without affecting issue assignment or displaying anything publicly. It is helpful for journals that add articles to issues on a rolling basis and publish them individually." %}

    {% trans "You can assign articles directly to issues in the prepublication stage or through " %}{% trans "issue management" %}.

    {% trans "How does it work?" %}

    {% trans "Select an issue from the drop down on the left and press save. This article's projected issue will now be set." %}

    {% trans "Can I unset a projected issue?" %}

    {% trans "Yes, you can select the blank option (-------) from the dropdown." %}

    {% endblock body %}