What ORCID iDs and affiliations are
An ORCID iD is a free, permanent identification number for researchers, written as four groups of four digits, for example 0000-0002-1825-0097. Journals, funders and congresses use it to tell apart authors with the same name. Two cardiologists called Anna Müller have two different ORCID iDs.
An affiliation is the institution an author works for, such as a university hospital, a research institute or a company. On a scientific congress, the affiliations of the authors are printed with every abstract, and they matter for the review: a reviewer should not rate an abstract written by colleagues from their own institution.
Off until you switch them on
ORCID iDs and affiliations are useful on a scientific congress and a nuisance almost everywhere else. At a company's own conference, every speaker works for the same company, so every reviewer would be in conflict with every colleague's submission. That is why run.events keeps both off on every event, new and existing, until you switch them on.
The three switches are in Call for Content Settings, on the tab Speakers and messages:
- Collect ORCID iDs: speakers and authors are asked for their ORCID iD when they submit and in their speaker profile, and the ORCID iD is printed in the publications, such as the Book of Abstracts.
- Use affiliations: speakers and authors are asked for their institution, and the institution is shown on the programme and in the publications.
- Raise conflicts of interest from affiliations: a reviewer and an author from the same institution are treated as having a conflict of interest, so the reviewer is not offered that abstract. This switch appears only while Use affiliations is on.
Good to know: while a switch is off, its field appears nowhere: not in the submission, not in the speaker profile, not on your screens as organizer, not on the event portal and not in the publications. Values that were already stored are kept. If you switch it on again, they come back.
What speakers and authors enter
With Collect ORCID iDs on, the speaker profile and the people of a submission take an ORCID iD. run.events checks that it has the right form, four groups of four characters separated by hyphens, so a mistyped number with a missing digit is refused.
With Use affiliations on, each person on a session can carry one or more institutions. The author types an institution and presses Enter, or separates several institutions with a semicolon. Affiliations are free text: run.events does not choose from a list of institutions, so the same hospital can be written in several ways. Ask your authors in the call's instructions to write their institution in full, in the way it should appear in print.
Who is asked for an affiliation
Not everyone on a session needs an affiliation. Each session role decides it with its setting Affiliations: Not asked, Optional or Required. You find it on the card Session roles on the Content And Speakers page. A medical congress usually sets Required on presenting authors and co-authors, because the Book of Abstracts prints an institution for every author, and Optional on chairs. While Use affiliations is off, the setting on the role says so and cannot be changed.
See Session Roles: Presenting Author, Co-Authors and Chairs for the other settings of a session role.
Affiliations and conflicts of interest
When Raise conflicts of interest from affiliations is on, run.events compares the institutions of each reviewer with the institutions of the people of each abstract. When they share one, the reviewer has a conflict of interest of the kind Same affiliation, and the abstract is not offered to that reviewer.
run.events compares the affiliations given on the session and, in addition, the company in each person's profile. For your reviewers, give each one their institutions on the card Content Team on the Content And Speakers page: choose a reviewer, fill in Affiliations, and choose Apply. A reviewer without affiliations is compared by the company in their profile, which is often empty or out of date, so entering the institutions yourself is the safer way.
Before comparing, run.events tidies the names: it ignores upper and lower case, accents, punctuation and a legal form at the end, such as GmbH or Ltd. It does not expand abbreviations, so "Univ. Hospital Nordstadt" and "University Hospital Nordstadt" still do not match. On the card Conflicts of interest, Check with Amal asks Amal, the AI assistant of run.events, to compare institution names that are written in different ways. Each match it finds becomes a conflict of the kind Same organisation (AI check), with a sentence that explains why. If Amal matched two institutions that are in fact different, Not the same organisation removes the match for good.
The article Conflicts of Interest explains all kinds of conflicts and how to correct them.
When to switch them on
| Your event | Collect ORCID iDs | Use affiliations | Raise conflicts from affiliations |
|---|---|---|---|
| A scientific or medical congress with an abstract review | On | On | On |
| A professional conference with speakers from many organisations, without a review of abstracts | Off | On, if you want institutions on the programme | Off |
| A company's own conference, where all speakers share one employer | Off | Off | Off |
Decide before the call opens. If you switch on Use affiliations after many authors have submitted, their sessions have no affiliations, and you or the authors must add them afterwards.
Two common mistakes
- The submission asks for no institution, and no conflict of interest comes from a shared institution. Tick Use affiliations, and for conflicts of interest also Raise conflicts of interest from affiliations, in Call for Content Settings on the tab Speakers and messages. Then check the setting Affiliations on your session roles.
- Reviewers are offered abstracts from their own hospital. Your reviewers have no affiliations, or their institution is written differently from the authors' institution. Fill in each reviewer's Affiliations on the card Content Team, and run Check with Amal on the card Conflicts of interest.
Related articles