36 lines
1.6 KiB
HTML
36 lines
1.6 KiB
HTML
{% extends "nomcom/nomcom_private_base.html" %}
|
|
{# Copyright The IETF Trust 2015, All Rights Reserved #}
|
|
{% load origin %}
|
|
{% load static %}
|
|
{% load django_bootstrap5 %}
|
|
{% block pagehead %}{{ form.media.css }}{% endblock %}
|
|
{% block subtitle %}- Merge Nominee Records{% endblock %}
|
|
{% block nomcom_content %}
|
|
{% origin %}
|
|
<h2>Merge Nominee Records</h2>
|
|
<p class="mt-3">
|
|
The nomination system encourages the community to nominate people by selecting
|
|
their email address from the set of addresses the tracker already knows. In order
|
|
to allow a person who does not yet have a datatracker account to be nominated, the
|
|
system also provides a way for the community to nominate people with a new,
|
|
previously unknown email address.
|
|
</p>
|
|
<p>
|
|
Occasionally, this results in multiple Nominee records which are associated with
|
|
the same person, but using different email addresses. In this case, the form to
|
|
<a href="{% url 'ietf.nomcom.views.private_merge_person' year=year %}">Request Merge of Person Records</a>
|
|
cannot be use, since it is the nominee records, not the person records which needs
|
|
to be merged. When this happens, you can use this form to merge the Nominee records.
|
|
</p>
|
|
{% if form %}
|
|
<form id="mergeform" method="post" class="my-3">
|
|
{% csrf_token %}
|
|
{% bootstrap_form form %}
|
|
<input class="btn btn-warning"
|
|
type="submit"
|
|
value="Request merge"
|
|
name="save">
|
|
</form>
|
|
{% endif %}
|
|
{% endblock %}
|
|
{% block js %}{{ form.media.js }}{% endblock %} |