{% extends "form.html" %} {% from "macros.html" import render_field, form_tag %} {% block content %} {{ super() }} {% if request.endpoint == "load_researcher_affiliations" %}

Format your affiliation data as either a comma-separated or tab-separated text file. The first row of the file must contain valid field headers from the following:

Where a field's header or value is not provided, the value from your organisation will be used if available, e.g., Organisation, City, Country, Disambiguation ID, and Disambiguation Source can be omitted where redundant for the item(s).
On successful completion, the user's ORCID iD and item's put-code and visibility will be returned for each affiliation item written. The Hub attempts to identify when information
is an update rather than a new item; however, to explicitly update an item include a field with the item's put-code to specify which item is to be overwritten.
For more information on the affiliation tasks, including definitions and behaviour see the Hub's documentation for affiliations.

{% endif %} {% if request.endpoint == "load_researcher_funding" %}

Format your funding data as either a json or yaml file. Multiple items can be specified but each must contain an invitees list together with the
ORCID message schema compliant-data that is to be written to each invitee's ORCID record:

On successful completion, the user's ORCID iD and item's put-code and visibility will be returned for each funding item written. The Hub attempts to identify when information
is an update rather than a new item; however, to explicitly update an item include a field with the item's put-code to specify which item is to be overwritten.
For more information on the funding tasks, including definitions and behaviour see the Hub's documentation for funding.

{% endif %} {% if request.endpoint == "load_researcher_work" %}

Format your works data as either a json or yaml file. Multiple items can be specified but each must contain an invitees list together with the
ORCID message schema compliant-data that is to be written to each invitee's ORCID record:

On successful completion, the user's ORCID iD and item's put-code and visibility will be returned for each work item written. The Hub attempts to identify when information
is an update rather than a new item; however, to explicitly update an item include a field with the item's put-code to specify which item is to be overwritten.
For more information on the work tasks, including definitions and behaviour see the Hub's documentation for works.

{% endif %} {% if request.endpoint == "load_researcher_peer_review" %}

Format your peer review data as either a json or yaml file. Multiple items can be specified but each must contain an invitees list together with the
ORCID message schema compliant-data that is to be written to each invitee's ORCID record:

A valid review-group-id must be specified. NB: Review Group IDs may be created in the Hub here.
On successful completion, the user's ORCID iD and item's put-code and visibility will be returned for each peer review item written. The Hub attempts to identify when information
is an update rather than a new item; however, to explicitly update an item include a field with the item's put-code to specify which item is to be overwritten.
For more information on the peer review tasks, including definitions and behaviour see the Hub's peer review documentation.

{% endif %} {% endblock %}