Reviewers (Reviewers, Area Chairs, and Senior Area Chairs) may or may not attend the conference and may not have a profile in the system. They get imported to the reviewers table in the database.
From the Admin menu, choose Import → Reviewer and Area Chair Import. to import reviewers from a spreadsheet. Instructions are provided on the page.
The deadline to accept the comp is set dates table as ReviewerCompTransferDeadline
Check the wording in core/templates/EmailTemplateCompedReviewerAreaChairReg.html to make sure the wording is still correct
Visit the reviewers table (/admin/core/reviewers/) in the Django admin and filter for the current year. In the filter list on the right there is a way to filter by kind. Kind distinguishes between e.g. Reviewers and Area Chairs. You can also filter by category. Category distinguishes between, e.g. Senior Area Chairs vs. Area Chairs and for reviewers, category can distinguish between top reviewers and not-top reviewers. Using these filters, use the Action: “Set gets_complimentary_registration=True” to set who gets a complimentary registration. Usually, the top 10% of reviewers plus Area Chairs plus Senior Area Chairs get a complimentary registration.
Sometimes, we allow subsets of reviewers to transfer their free registration to someone else. We've done this in the past for Senior Area Chairs. Filter for the correct group, then use the Action: “Set Transferrable.” One consideration is that when ticket is donated, it still appears in some reports as if the original AC is attending. This complicates finding moderators.
Set the correct filter and use the Action: “Invite to Accept, Decline, or Transfer Comp" to email an invitation to claim the registration. The outbound email will reference a deadline set by the date “ReviewerCompTransferDeadline”. The comp will not be created until the chair claims it.
At a multi-location conference the claim page asks which city the reviewer will attend. In the Locations admin (/admin/core/locations/), Reviewer comp limit caps the reviewer comps claimed at each location: blank means no limit, 0 offers none. Once a city reaches its limit it is no longer offered on the claim page, and the Comps claimed column shows the count. Only comps with the Reviewer justification count.
Some reviewer comps never count, and the city stays offered to those reviewers once it is full:
The claim records this on the seat as Exempt from reviewer comp limit; unticking it makes the seat count again. A comp never takes a paper's author reserve place. A presenter's comp does give them a seat, which releases the place the author reserve keeps for them (see Author Reserve).
A reviewer can only transfer a comp for a city offered on their own claim page, so a reviewer with no exemption cannot transfer a full city's comp, even to that paper's presenter.
After ticking Enforce site survey presenter at a location that already has exempt comps, re-test them with ./manage.py nips26-retest-reviewer-comp-exemptions.
--apply, which can put a location over its limit (shown as OVER LIMIT). Review the dry run first.Step 2: “Give complimentary registrations to classes of reviewers and area chairs, including creating missing local accounts” allows you to select a category of reviewer, e.g. Top Reviewers or Area Chairs and give then an immediate full, physical complimentary registration. If the reviewer doesn't have an account, one is created. If they've already registered, a refund is issued. This method of comping reviewers is consider legacy, because a comp is given regardless of whether the reviewer will use it or not.