Introduction to Profiles
Last updated
Was this helpful?
Last updated
Was this helpful?
Profiles in OpenReview represent the identity of users on the platform—such as authors, reviewers, and area chairs. Each profile serves as a record user's publications, affiliations, and roles within the OpenReview system.
A profile typically includes:
Profile ID: This is the unique identifier in the system, in the format ~First_Last1
This is also sometimes referred to as a "tilde id". While each tilde ID points to a single profile, a profile may have multiple tilde IDs associated with it as a result of adding an alternate name or merging profiles.
Name(s): Full name and any alternate names (e.g., name changes, nicknames).
Email(s): Verified email addresses associated with the user. Only the email domains are publicly displayed- even PCs will not see the full emails for users submitting to their venue. Note, if you need to get the full author emails, refer to the instructions .
Affiliations: Work history or institutional associations.
Publications: Papers the user has authored or co-authored.
You can get one or more profiles using the Python API using the function openreview.tools.get_profiles()
. This function takes a list of profiles or emails, and for each item in the list, returns one of the following: It is possible to query a profile either using the profile's tilde id, or using any confirmed email to the profile
To get multiple profiles, you would use the function openreview.tools.get_profiles()
. This function takes a list of profiles or emails, and for each item in the list, returns a dictionary with the following:
Other arguments that can be used to get additional informations along with the profiles are:
with_publications
with_relations
with_preferred_emails
To get a tabular format, it is necessary to flatten the profile. After flattening (sample code below) a profile would look like this:
0
name@university.edu
https://test.com
name@university.edu
True
First Last
~First_Last2
PhD Student
2017
None
US
university.edu
name@university.edu
~First_Last2
There will be multiple columns for some profile fields recording each of the entries, for example: names_0_preferred, names_0_fullname
. Because profiles have different numbers of affiliations in their profile, some of these columns will be null for some profiles.
The code below takes a list of profile IDs or emails, and returns a DataFrame with all of the profile information in it in a tabular format.
Profiles are an OpenReview object that contains properties. The main three properties that you can expect to interact with are: id
, state
, and content
. For more details about each of these fields, see . Several of the fields of content
include lists or lists of dictionaries, which means that it is necessary to understand the structure of the profile in order to get the profile information.in order to access this data, it is Because you need to flatten the dictionary to create the fields, then extract the content, similarly to how the submission content was extracted. The original profile information looks something like this:
Once the DataFrame is created, it is possible to create a CSV with this data, or merge it with other OpenReview data. See for examples on how to combine profile with submission data.