From 744e0b7c95412e642725a1724f4b82dd47dff4ae Mon Sep 17 00:00:00 2001
From: ubc-tuehoang <86985864+ubc-tuehoang@users.noreply.github.com>
Date: Fri, 23 Feb 2024 15:02:24 -0800
Subject: [PATCH] modified to program and application (#4)
* update conference to program
* updated paper to application
* modified paper to application for json files
* updated message
* updated help log for paper
* updated more help content fixes
---------
Co-authored-by: ubc-tuehoang A review preference is a small integer that indicates how much you want to review a submission. Positive numbers mean you want to review, negative numbers mean you don’t, and −100 means you think you have a conflict. −20 to 20 is a typical range for real preferences; multiple submissions can have the same preference. The automatic assignment algorithm attempts to assign reviews in descending preference order. Different users’ preference values are not compared and need not use the same scale. Select a column heading to sort by that column. Enter preferences in the text boxes or on the paper pages. You may also upload preferences from a text file; see the “Download” and “Upload” links below the paper list. A review preference is a small integer that indicates how much you want to review a submission. Positive numbers mean you want to review, negative numbers mean you don’t, and −100 means you think you have a conflict. −20 to 20 is a typical range for real preferences; multiple submissions can have the same preference. The automatic assignment algorithm attempts to assign reviews in descending preference order, using topic scores to break ties. Different users’ preference values are not compared and need not use the same scale. The list shows all submissions and their topics (high interest topics, low interest topics). “Topic score” summarizes your interest in the submission’s topics. Select a column heading to sort by that column. Enter preferences in the text boxes or on the paper pages. You may also upload preferences from a text file; see the “Download” and “Upload” links below the paper list. A review preference is a small integer that indicates how much you want to review a submission. Positive numbers mean you want to review, negative numbers mean you don’t, and −100 means you think you have a conflict. −20 to 20 is a typical range for real preferences; multiple submissions can have the same preference. The automatic assignment algorithm attempts to assign reviews in descending preference order. Different users’ preference values are not compared and need not use the same scale. Select a column heading to sort by that column. Enter preferences in the text boxes or on the application pages. You may also upload preferences from a text file; see the “Download” and “Upload” links below the application list. A review preference is a small integer that indicates how much you want to review a submission. Positive numbers mean you want to review, negative numbers mean you don’t, and −100 means you think you have a conflict. −20 to 20 is a typical range for real preferences; multiple submissions can have the same preference. The automatic assignment algorithm attempts to assign reviews in descending preference order, using topic scores to break ties. Different users’ preference values are not compared and need not use the same scale. The list shows all submissions and their topics (high interest topics, low interest topics). “Topic score” summarizes your interest in the submission’s topics. Select a column heading to sort by that column. Enter preferences in the text boxes or on the application pages. You may also upload preferences from a text file; see the “Download” and “Upload” links below the application list. Kiosk mode is a discussion status page with no other site privileges. It’s safe to leave a browser in kiosk mode open in the hallway. Kiosk mode will sign your browser out of the site. Do not use kiosk mode on your main browser. These URLs access kiosk mode directly: Formulas, such as “sum(OveMer)”, are calculated from review statistics and paper information. Named formulas are shared with the PC and can be used in other formulas. To view an unnamed formula, use a search term like “show:(sum(OveMer))”. Formulas, such as “sum(OveMer)”, are calculated from review statistics and application information. Named formulas are shared with the PC and can be used in other formulas. To view an unnamed formula, use a search term like “show:(sum(OveMer))”.
');
if (show_papers)
diff --git a/scripts/script.js b/scripts/script.js
index deb93afe2..cbc3716c6 100644
--- a/scripts/script.js
+++ b/scripts/script.js
@@ -3439,7 +3439,7 @@ handle_ui.on("js-tracker", function (evt) {
hc.push('PC members without tag ' + vis.substring(1));
hc.push_pop('Named formulas
');
- hc.push(' ");
+ j.append("No recent activity in papers you’re following ");
}
handle_ui.on("js-open-activity", function (evt) {
diff --git a/src/checkformat.php b/src/checkformat.php
index c494da397..1dedd30d9 100644
--- a/src/checkformat.php
+++ b/src/checkformat.php
@@ -197,7 +197,7 @@ function banal_json() {
$limit = $doc->conf->opt("banalLimit") ?? 8;
if ($limit > 0) {
if ($n > $limit) {
- $this->error_at("error", "<0>Server too busy to check paper formats");
+ $this->error_at("error", "<0>Server too busy to check application formats");
$this->inform_at("error", "<0>This is a transient error; feel free to try again.");
return $this->complete_banal_json($bj, $flags | CheckFormat::RUN_ABANDONED);
}
@@ -507,7 +507,7 @@ private function check_papersize(CheckFormat $cf, $bj, FormatSpec $spec) {
}
}
if (!$ok) {
- $cf->problem_at("papersize", "<0>Paper size mismatch: expected " . commajoin(array_map(function ($d) { return FormatSpec::unparse_dimen($d, "paper"); }, $spec->papersize), "or") . ", got " . FormatSpec::unparse_dimen([$papersize[1], $papersize[0]], "paper"), 2);
+ $cf->problem_at("papersize", "<0>Application size mismatch: expected " . commajoin(array_map(function ($d) { return FormatSpec::unparse_dimen($d, "paper"); }, $spec->papersize), "or") . ", got " . FormatSpec::unparse_dimen([$papersize[1], $papersize[0]], "application"), 2);
}
}
diff --git a/src/help/h_bulkassign.php b/src/help/h_bulkassign.php
index 5bfa44aa6..56878215b 100644
--- a/src/help/h_bulkassign.php
+++ b/src/help/h_bulkassign.php
@@ -11,21 +11,21 @@ static function print(HelpRenderer $hth) {
file) to prepare an assignment. HotCRP will display the consequences of the
requested assignment for confirmation and approval.No recent activity in applications you’re following
Assignment CSVs contain paper
and action
fields,
-where paper
determines which submissions are affected and
+
Assignment CSVs contain application
and action
fields,
+where application
determines which submissions are affected and
action
determines what kind of assignment is performed. The
-paper
field can be a simple submission number, like “10”, or a
+application
field can be a simple submission number, like “10”, or a
search string, like “#manny OR #ramirez”. Other parameter fields depend on the
action. For instance, the tag
action adds the tag specified in
the tag
field. Actions requiring a user locate that user via the
email
, name
, first name
, last
name
, and/or user
fields.
This example file clears existing R1 review assignments for papers tagged +
This example file clears existing R1 review assignments for applications tagged #redo, then assigns two primary reviews for submission #1 and one secondary review for submission #2:
-paper,action,email,round +application,action,email,round #redo,clearreview,all,R1 1,primary,man@alice.org 2,secondary,slugger@manny.com @@ -33,7 +33,7 @@ static function print(HelpRenderer $hth) {Errors will be reported if
+with their assigned applications.man@alice.org
orslugger@manny.com
aren’t PC members, or if they have conflicts -with their assigned papers.Assignment files are parsed from top to bottom, but applied as a unit. For example, if a file clears and then recreates a existing review assignment, @@ -41,8 +41,8 @@ static function print(HelpRenderer $hth) { echo $hth->subhead("Action overview"); self::print_actions($hth->user, $hth); - echo '
Notes: The
paper
parameter -can be a paper number, like “1”, or a search, like + echo 'Notes: The
-application
parameter +can be a application number, like “1”, or a search, like “re:jhala #good”. Instead of auser
parameter, you can supplyname
,first_name
, and/orlast_name
.tag
@@ -69,29 +69,29 @@ static function print_action_review(HelpRenderer $hth) {drew@harvard.edu
in review round R2, or, if Drew already has a review assignment for submission #1, modify that review’s type and round:paper,action,email,reviewtype,round +application,action,email,reviewtype,round 1,review,drew@harvard.edu,primary,R2To avoid modifying an existing review, use this syntax, which means “ignore this assignment unless the current review type is ‘none’”:
-paper,action,email,reviewtype,round +application,action,email,reviewtype,round 1,review,drew@harvard.edu,none:primary,R2To modify an existing review (the “
-any
” review type only matches existing reviews):paper,action,email,reviewtype,round +application,action,email,reviewtype,round 1,review,drew@harvard.edu,any,R2To change an existing review from round R1 to round R2:
-paper,action,email,reviewtype,round +application,action,email,reviewtype,round 1,review,drew@harvard.edu,any,R1:R2To change all round-R1 primary reviews to round R2:
-paper,action,email,reviewtype,round +application,action,email,reviewtype,round all,review,all,primary,R1:R2The
-primary
,secondary
,pcreview
, @@ -111,14 +111,14 @@ static function print_action_tag($hth) {clear
. For example, this file clears all #p tags with value less than 10:paper,action,tag +application,action,tag #p#<10,cleartag,pTo add to a tag order, use action
+order #p that lists applications 4, 3, 2, 9, 10, and 6, in that order: -nexttag
; to add to a gapless tag order, useseqnexttag
. For example, this file creates a tag -order #p that lists papers 4, 3, 2, 9, 10, and 6, in that order:paper,action,tag +application,action,tag all,cleartag,p 4,nexttag,p 3,nexttag,p @@ -154,7 +154,7 @@ static function add_bulk_assignment_action(&$apx, $uf, $hth) { && ($hashid = $hth->hashid("bulkassignactions/{$uf->name}"))) { $n = "{$n}"; } - $t .= $n . 'paper
'; + $t .= $n . 'application
'; foreach ($uf->parameters ?? [] as $param) { $t .= ', '; if ($param[0] === "?") { diff --git a/src/help/h_chairsguide.php b/src/help/h_chairsguide.php index 8d660cb7e..b1b34b45d 100644 --- a/src/help/h_chairsguide.php +++ b/src/help/h_chairsguide.php @@ -116,10 +116,7 @@ static function print_assignments(HelpRenderer $hth, $gj) { } else if ($gj->itemid === 5) { echo "\n"; + " Tracks give chairs fine-grained control over PC members’ access rights for individual papers. Example situations calling for tracks include external review committees, PC-paper review committees, and multi-track programs.\n"; } else if ($gj->itemid === 6) { echo " ", $hth->setting_link("Prepare tracks (optional).", "track"), - " Tracks give chairs fine-grained control over PC - members’ access rights for individual papers. Example situations calling for - tracks include external review committees, PC-paper review committees, and - multi-track conferences.
", $hth->hotlink("Collect review preferences from the PC.", "reviewprefs"), " @@ -165,20 +162,12 @@ static function print_assignments(HelpRenderer $hth, $gj) { static function print_chair_conflicts(HelpRenderer $hth) { echo $hth->subhead("Chair conflicts"); - echo "
Chairs and system administrators can access any information stored in the -conference system, including reviewer identities for conflicted papers. -It is easiest to simply accept such conflicts as a fact of life. Chairs -who can’t handle conflicts fairly shouldn’t be chairs. However, HotCRP -does offer other mechanisms for conflicted reviews.
+ echo "Chairs and system administrators can access any information stored in the program system, including reviewer identities for conflicted papers. It is easiest to simply accept such conflicts as a fact of life. Chairs who can’t handle conflicts fairly shouldn’t be chairs. However, HotCRP does offer other mechanisms for conflicted reviews.
First, each paper can be assigned a paper administrator: a PC member who manages that paper’s reviewing and discussion. Use the left-hand side of a ", $hth->hotlink("submission’s assignment page", "assign"), " to enter its administrator. (You may need to -“Override conflicts” to access the assignment page.) -Paper administrators have full privilege to assign and view reviews for their -papers, and can, for example, use the autoassignment tool, but they cannot change -conference settings. When a paper -has an administrator, chair conflicts cannot be overridden.
+“Override conflicts” to access the assignment page.) Paper administrators have full privilege to assign and view reviews for their papers, and can, for example, use the autoassignment tool, but they cannot change program settings. When a paper has an administrator, chair conflicts cannot be overridden.Paper administrators make life easy for PC reviewers and greatly restrict conflicted chairs’ access. Usually this suffices. @@ -219,7 +208,7 @@ static function print_premeeting(HelpRenderer $hth, $gj) { echo "
\n"; } else if ($gj->itemid === 3) { @@ -291,9 +280,8 @@ static function print_atmeeting(HelpRenderer $hth, $gj) { " to expose decisions to PC members if desired.\n"; } else if ($gj->itemid === 4) { - echo " Set ", $hth->setting_link("PC can see review contents", "review_visibility_pc"), " to “Yes” (optional). This opens up the reviews to the program committee, allowing everyone to see scores and read reviews for non-conflicted papers. - (During most conferences’ review periods, a PC member can see a paper’s reviews + (During most programs’ review periods, a PC member can see a paper’s reviews only after completing their own review for that paper.)
\n"; + echo " Shepherding (optional). If your conference uses - shepherding for accepted papers, you can assign shepherds either ", - $hth->hotlink("paper by paper", "paper"), " or ", $hth->hotlink("automatically", "autoassign", "t=accepted"), ".
\n"; } } diff --git a/src/help/h_developer.php b/src/help/h_developer.php index 4407ed5ca..10753a1b7 100644 --- a/src/help/h_developer.php +++ b/src/help/h_developer.php @@ -60,8 +60,7 @@ function print_usage() { } function print_settings() { - echo " Shepherding (optional). If your program uses shepherding for accepted applications, you can assign shepherds either ", + $hth->hotlink("application by application", "paper"), " or ", $hth->hotlink("automatically", "autoassign", "t=accepted"), ".
The chair-only
api/settings
endpoint accesses -conference settings in ", + echo "The chair-only
@@ -91,8 +90,7 @@ function print_settings() { } function print_submissions() { - echo "api/settings
endpoint accesses program settings in ", $this->hth->hotlink("JSON format", "help", ["t" => "jsonsettings"]) . ". To modify settings, use the POST method and provide a JSON request body. Examples:The
api/paper
endpoint accesses conference -submissions. GET calls return paper information; use + echo "The
"; diff --git a/src/help/h_formulas.php b/src/help/h_formulas.php index 08176fd1d..4657a2cc8 100644 --- a/src/help/h_formulas.php +++ b/src/help/h_formulas.php @@ -5,17 +5,17 @@ class Formulas_HelpTopic { static function print(HelpRenderer $hth) { echo "api/paper
endpoint accesses program submissions. GET calls return paper information; useapi/PAPERID/paper
to return one paper, andapi/paper?q=SEARCH&t=SEARCHTYPE
to return all papers matchingSEARCH
.Program committee members and administrators can search and display formulas -that calculate properties of paper scores—for instance, the -standard deviation of papers’ Overall merit scores, or average Overall +that calculate properties of application scores—for instance, the +standard deviation of applications’ Overall merit scores, or average Overall merit among reviewers with high Reviewer expertise.
To display a formula, use a search term such as “", $hth->search_link("show:var(OveMer)"), "” (show -the variance in Overall merit scores, along with statistics for all papers). +the variance in Overall merit scores, along with statistics for all applications). You can also ", $hth->hotlink("graph formulas", "graph", "group=formula"), ". To search for a formula, use a search term such as “", $hth->search_link("formula:var(OveMer)>0.5"), "” -(select papers with variance in Overall merit greater than 0.5). +(select applications with variance in Overall merit greater than 0.5). Or save formulas using ", $hth->search_link("Search > View options", ["q" => "", "#" => "view"]), " > Edit formulas.
@@ -68,7 +68,7 @@ static function print(HelpRenderer $hth) { echo $hth->trow("log(e, b)", "Log to the base b"); echo $hth->trow("round(e[, m])", "Round to the nearest multiple of m"); echo $hth->tgroup("Submission properties"); - echo $hth->trow("pid", "Paper ID"); + echo $hth->trow("pid", "Application ID"); echo $hth->trow("au", "Number of authors"); echo $hth->trow("au:pc", "Number of PC authors"); echo $hth->trow("au:text", "Number of authors matching text"); @@ -77,8 +77,8 @@ static function print(HelpRenderer $hth) { echo $hth->trow("topics:text", "Number of topics matching text"); } echo $hth->tgroup("Tags"); - echo $hth->trow("#tagname", "True if this paper has tag tagname"); - echo $hth->trow("tagval:tagname", "The value of tag tagname, or null if this paper doesn’t have that tag"); + echo $hth->trow("#tagname", "True if this application has tag tagname"); + echo $hth->trow("tagval:tagname", "The value of tag tagname, or null if this application doesn’t have that tag"); echo $hth->tgroup("Scores"); echo $hth->trow("overall-merit", "This review’s Overall merit scoreOnly completed reviews are considered."); echo $hth->trow("OveMer", "Abbreviations also accepted"); @@ -103,9 +103,9 @@ static function print(HelpRenderer $hth) { echo $hth->subhead("Aggregate functions"); echo "Aggregate functions calculate a -value based on all of a paper’s reviews and/or review preferences. +value based on all of a application’s reviews and/or review preferences. For instance, “max(OveMer)” would return the maximum Overall merit score -assigned to a paper.
+assigned to a application.An aggregate function’s argument is calculated once per viewable review or preference. diff --git a/src/help/h_jsonsettings.php b/src/help/h_jsonsettings.php index ed960b455..fc2d3fcb5 100644 --- a/src/help/h_jsonsettings.php +++ b/src/help/h_jsonsettings.php @@ -19,10 +19,7 @@ function __construct(HelpRenderer $hth) { function print() { echo "
With ", $this->hth->setting_group_link("Settings > Advanced", "json"), - ", administrators can configure site operation by modifying a JSON -specification. Advanced users can copy settings from one conference to -another and configure aspects of the site not accessible via the normal -settings UI.
"; + ", administrators can configure site operation by modifying a JSON specification. Advanced users can copy settings from one program to another and configure aspects of the site not accessible via the normal settings UI."; echo $this->hth->subhead("View settings"); @@ -117,11 +114,9 @@ class=\"settings-jpath\">decision is an array with one entry per } -+ Copying settings between conferences. Beware of IDs -when copying settings between conferences. Unless you are careful, the IDs -used in one conference may differ from the IDs in another. Consider removing -the IDs from a conference’s JSON settings before uploading those settings to -another conference.
Copying settings between programs. Beware of IDs +when copying settings between programs. Unless you are careful, the IDs +used in one program may differ from the IDs in another. Consider removing the IDs from a program’s JSON settings before uploading those settings to another program.
Other common components in object lists include diff --git a/src/help/h_ranking.php b/src/help/h_ranking.php index 8140ab5dc..207b8930e 100644 --- a/src/help/h_ranking.php +++ b/src/help/h_ranking.php @@ -4,24 +4,24 @@ class Ranking_HelpTopic { static function print(HelpRenderer $hth) { - echo "
Paper ranking is a way to extract the PC’s preference order for -submitted papers. Each PC member ranks the submitted papers, and a voting + echo "
Application ranking is a way to extract the PC’s preference order for +submitted applications. Each PC member ranks the submitted applications, and a voting algorithm, the Schulze method by default, combines these rankings into a global preference order.
HotCRP supports ranking through ", $hth->help_link("tags", "tags"), ". The chair chooses a tag for ranking—“rank” is a good default—and enters it on ", $hth->setting_link("the settings page", "tag_rank"), ". -PC members then rank papers using their private versions of this tag, +PC members then rank applications using their private versions of this tag, tagging their first preference with “~rank#1”, their second preference with “~rank#2”, and so forth. To combine PC rankings into a global preference order, the PC -chair selects all papers on ", $hth->search_link("the search page", ""), +chair selects all applications on ", $hth->search_link("the search page", ""), " and chooses Tags > Calculate rank, entering “rank” for the tag. At that point, the global rank can be viewed by ", $hth->search_link("searching for “order:rank”", "order:rank"), ".
-PC members can enter rankings by reordering rows in a paper list. +
PC members can enter rankings by reordering rows in a application list. For example, for rank tag “rank”, PC members should ", $hth->search_link("search for “editsort:#~rank”", "editsort:#~rank"), ". Ranks can be entered directly in the text fields, or the rows can be dragged @@ -36,12 +36,12 @@ static function print(HelpRenderer $hth) { # Edit the rank order by rearranging this file's lines. # The first line has the highest rank. -# Lines that start with \"#\" are ignored. Unranked papers appear at the end +# Lines that start with \"#\" are ignored. Unranked applications appear at the end # in lines starting with \"X\", sorted by overall merit. Create a rank by # removing the \"X\"s and rearranging the lines. A line that starts with \"=\" -# marks a paper with the same rank as the preceding paper. A line that starts +# marks a application with the same rank as the preceding application. A line that starts # with \">>\", \">>>\", and so forth indicates a rank gap between the preceding -# paper and the current paper. When you are done, upload the file at +# application and the current application. When you are done, upload the file at # http://your.site.here.com/offline Tag: ~rank diff --git a/src/help/h_revrate.php b/src/help/h_revrate.php index dc44bb81f..d092036cf 100644 --- a/src/help/h_revrate.php +++ b/src/help/h_revrate.php @@ -26,7 +26,7 @@ static function print(HelpRenderer $hth) {
Too narrow: The review’s perspective seems limited; for instance, it might overly privilege the reviewer’s own work. Disrespectful: The review’s tone is unnecessarily aggressive or exhibits bias. -Not correct: The review misunderstands the paper. +Not correct: The review misunderstands the application. HotCRP reports aggregate ratings for each review. diff --git a/src/help/h_revround.php b/src/help/h_revround.php index f813e2fad..c0524a20b 100644 --- a/src/help/h_revround.php +++ b/src/help/h_revround.php @@ -4,11 +4,11 @@ class RevRound_HelpTopic { static function print(HelpRenderer $hth) { - echo "
Many conferences divide their review assignments into named rounds, + echo "
Many programs divide their review assignments into named rounds, such as “R1” or “lastround”. (We suggest very short names like “R1”.) Different review rounds can have different deadlines and can even have different fields on their review forms. -To search for any paper with a round “R2” review assignment, ", +To search for any application with a round “R2” review assignment, ", $hth->search_link("search for “re:R2”", "re:R2"), ". To list a PC member’s round “R1” review assignments, ", $hth->search_link("search for “re:membername:R1”", "re:membername:R1"), ".
diff --git a/src/help/h_scoresort.php b/src/help/h_scoresort.php index a5b75e88c..1c409e795 100644 --- a/src/help/h_scoresort.php +++ b/src/help/h_scoresort.php @@ -5,8 +5,8 @@ class ScoreSort_HelpTopic { static function print(HelpRenderer $hth) { echo " -Some paper search results include columns with score graphs. Click on a score -column heading to sort the paper list using that score. Search > View +
Some application search results include columns with score graphs. Click on a score +column heading to sort the application list using that score. Search > View options changes how scores are sorted. There are five choices:
@@ -14,9 +14,9 @@ static function print(HelpRenderer $hth) {
- Counts (default)
- Sort by the number of highest scores, then the number of second-highest -scores, then the number of third-highest scores, and so on. To sort a paper +scores, then the number of third-highest scores, and so on. To sort a application with fewer reviews than others, HotCRP adds phantom reviews with scores just -below the paper’s lowest real score. Also known as Minshall score.
+below the application’s lowest real score. Also known as Minshall score.- Average
- Sort by the average (mean) score.
diff --git a/src/help/h_search.php b/src/help/h_search.php index f323b7397..cdffce9cc 100644 --- a/src/help/h_search.php +++ b/src/help/h_search.php @@ -33,7 +33,7 @@ static function print(HelpRenderer $hth) { " and use “With any of the words” and “Without the words.”You can search several categories, depending on your role in the -conference. Options include:
+program. Options include:
- ", PaperSearch::limit_description($hth->conf, "s"), " — all submissions ready for review.
- ", PaperSearch::limit_description($hth->conf, "a"), " — submissions for which you’re a contact.
@@ -43,7 +43,7 @@ static function print(HelpRenderer $hth) {Search won’t show you information you aren’t supposed to see. For example, -authors can only search their own submissions, and if the conference used +authors can only search their own submissions, and if the program used anonymous submission, then only the PC chairs can search by author.
By default, search examines titles, abstracts, and authors. ", diff --git a/src/help/h_tags.php b/src/help/h_tags.php index 304f1d730..9ff22c771 100644 --- a/src/help/h_tags.php +++ b/src/help/h_tags.php @@ -22,10 +22,7 @@ function print_intro() { $conflictmsg = " and conflicted PC members"; } - echo "
PC members and administrators can attach tag names to papers. -It’s easy to change tags and to list all papers with a given tag, -and ordered tags preserve a particular paper order. -Tags also affect color highlighting in paper lists.
+ echo "PC members and administrators can attach tag names to applicaitons. It’s easy to change tags and to list all applications with a given tag, and ordered tags preserve a particular application order. Tags also affect color highlighting in application lists.
Tags are visible to the PC and hidden from authors$conflictmsg. Twiddle tags, with names like “#~tag”, are visible only to their creators. Tags @@ -36,7 +33,7 @@ function print_intro() { function print_finding() { $hth = $this->hth; echo $hth->subhead("Find tags", "find"); - echo "
A paper’s tags are shown like this on the paper page:
+ echo "A application’s tags are shown like this on the application page:
', "", @@ -51,18 +48,17 @@ function print_finding() { '
-To find all papers with tag “#discuss”:
+To find all applications with tag “#discuss”:
", $hth->search_form("#discuss"), "-You can also search with “", $hth->search_link("show:tags"), "” to see each -paper’s tags, or “", $hth->search_link("show:#tagname"), "” to see a particular tag +
You can also search with “", $hth->search_link("show:tags"), "” to see each application’s tags, or “", $hth->search_link("show:#tagname"), "” to see a particular tag as a column.
Tags are only shown to PC members and administrators. "; if ($this->user->isPC) { if ($this->conf->tag_seeall) { - echo "Currently PC members can see tags for any paper, including conflicts."; + echo "Currently PC members can see tags for any application, including conflicts."; } else { echo "They are hidden from conflicted PC members; for instance, if a PC member searches for a tag, the result will never include their conflicts."; } @@ -76,14 +72,14 @@ function print_changing() { echo $hth->subhead("Change tags", "change"); echo "
-
For one paper: Go to a paper page, click the +
- -
For one application: Go to a application page, click the “", expander(true), "Tags” expander, and enter tags separated by spaces.
For many papers: ", $hth->hotlink("Search", "search"), -" for papers, select them, and use the action area underneath the -search list. Add adds tags to the selected papers, Remove removes -tags from the selected papers, and Define adds the tag to the selected -papers and removes it from all others.
+- @@ -91,7 +87,7 @@ function print_changing() { $hth->search_link("edit:tag:tagname"), "” to add tags with checkboxes; search for “", $hth->search_link("edit:tagval:tagname"), "” to type in tag values; or search for “", $hth->search_link("edit:tags"), "” -to edit papers’ full tag lists. +to edit applications’ full tag lists.
For many applications: ", $hth->hotlink("Search", "search"), +" for applications, select them, and use the action area underneath the +search list. Add adds tags to the selected applications, Remove removes +tags from the selected applications, and Define adds the tag to the selected +applications and removes it from all others.
", Ht::img("extagssearch.png", "[Setting tags on the search page]", ["width" => 510, "height" => 94]), "
", Ht::img("extagseditkw.png", "[Tag editing search keywords]", ["width" => 543, "height" => 133]), "
@@ -114,31 +110,31 @@ function print_values() { specific values with search terms like “", $hth->search_link("#discuss#2"), "” or “", $hth->search_link("#discuss>1"), "”. A search like “", $hth->search_link("order:#tagname"), "” selects -papers with the named tag and displays them ordered by that tag’s values. +applications with the named tag and displays them ordered by that tag’s values. -It’s common to assign increasing tag values to a set of papers. Do this +
It’s common to assign increasing tag values to a set of applications. Do this using the ", $hth->hotlink("search screen", "search"), ". Search for the -papers you want, sort them into the right order, select their checkboxes, and +applications you want, sort them into the right order, select their checkboxes, and choose Define order in the tag action area. If no sort gives what -you want, search for the desired paper numbers in order—for instance, +you want, search for the desired application numbers in order—for instance, “", $hth->search_link("4 1 12 9"), "”—then Select all and Define order.
Define order might assign values “#tag#1”, “#tag#3”, “#tag#6”, and “#tag#7” -to adjacent papers. The gaps make it harder to infer -conflicted papers’ positions. (Any given gap might or might not hold a -conflicted paper.) The Define gapless order action assigns +to adjacent applications. The gaps make it harder to infer +conflicted applications positions. (Any given gap might or might not hold a +conflicted application.) The Define gapless order action assigns strictly sequential values, like “#tag#1”, “#tag#2”, “#tag#3”, “#tag#4”. Define order is better for most purposes.
-To add new papers at the end of an existing discussion order, use Add to +
To add new applications at the end of an existing discussion order, use Add to order. To create an order by entering explicit positions and/or dragging -papers into order, use a search like “", $hth->search_link("editsort:#tagname"), "”.
+applications into order, use a search like “", $hth->search_link("editsort:#tagname"), "”.The ", $hth->hotlink("autoassigner", "autoassign", "a=discorder"), " -has special support for creating discussion orders. It tries to group papers +has special support for creating discussion orders. It tries to group applications with similar PC conflicts, which can make the meeting run smoother.
"; } @@ -146,12 +142,12 @@ function print_colors() { $hth = $this->hth; echo $hth->subhead("Colors", "colors"); echo "Tags “red”, “orange”, “yellow”, “green”, “blue”, “purple”, “gray”, and -“white” act as highlight colors. For example, papers tagged with “#red” will -appear red in paper lists (for people -who can see that tag). Tag a paper “#~red” to make it red only on your display. +“white” act as highlight colors. For example, applications tagged with “#red” will +appear red in application lists (for people +who can see that tag). Tag a application “#~red” to make it red only on your display. Other styles are available; try “#bold”, “#italic”, “#big”, “#small”, and “#dim”. The ", $hth->setting_link("settings page", "tag_style"), " can associate other tags -with colors so that, for example, “" . $hth->search_link("#reject") . "” papers appear +with colors so that, for example, “" . $hth->search_link("#reject") . "” applications appear gray.
\n"; } @@ -165,53 +161,53 @@ function print_example_r1reject() { echo "Skip low-ranked submissions. Mark low-ranked submissions with tag “#r1reject”, then ask the PC to " . $this->hth->search_link("search for “#r1reject”", "#r1reject") . ". PC members -can check the list for papers they’d like to discuss anyway. They can email -the chairs about such papers, or remove the tag themselves. (You might make +can check the list for applications they’d like to discuss anyway. They can email +the chairs about such applications, or remove the tag themselves. (You might make the “#r1reject” tag chair-only so an evil PC member couldn’t add it to a -high-ranked paper, but it’s usually better to trust the PC.)
\n"; +high-ranked application, but it’s usually better to trust the PC.)\n"; } function print_example_controversial() { - echo "Mark controversial papers that would benefit from additional review. + echo "
Mark controversial applications that would benefit from additional review. PC members could add the “#controversial” tag when the current reviewers disagree. A ", $this->hth->hotlink("search", "search", ["q" => "#controversial"]), " shows where the PC thinks more review is needed.
\n"; } function print_example_pcpaper() { - echo "Mark PC-authored papers for extra scrutiny. + echo "
Mark PC-authored applications for extra scrutiny. First, ", $this->hth->hotlink("search for PC members’ last names in author fields", "search", "t=s&qt=au"), ". - Check for accidental matches and select the papers with PC members as authors, then use the action area below the search list to add the tag “#pcpaper”. - A ", $this->hth->hotlink("search", "search", "t=s&q=-%23pcpaper"), " shows papers without PC authors.
\n"; + Check for accidental matches and select the applications with PC members as authors, then use the action area below the search list to add the tag “#pcpaper”. + A ", $this->hth->hotlink("search", "search", "t=s&q=-%23pcpaper"), " shows applications without PC authors.\n"; } function print_example_allotment() { $vt = $this->hth->example_tag(TagInfo::TF_ALLOTMENT) ?? "vote"; - echo "Vote for papers. + echo "
Vote for applications. The chair can define tags used for allotment voting", $this->hth->tag_settings_having_note(TagInfo::TF_ALLOTMENT), ".", $this->hth->change_setting_link("tag_vote_allotment"), - " Each PC member is assigned an allotment of votes to distribute among papers. - For instance, if “#{$vt}” were a voting tag with an allotment of 10, then a PC member could assign 5 votes to a paper by adding the twiddle tag “#~{$vt}#5”. + " Each PC member is assigned an allotment of votes to distribute among applications. + For instance, if “#{$vt}” were a voting tag with an allotment of 10, then a PC member could assign 5 votes to a application by adding the twiddle tag “#~{$vt}#5”. The system automatically sums PC members’ votes into the public “#{$vt}” tag. - To search for papers by vote count, search for “", $this->hth->search_link("rorder:#$vt"), + To search for applications by vote count, search for “", $this->hth->search_link("rorder:#$vt"), "”. (", $this->hth->help_link("voting"), ")
\n"; } function print_example_rank() { - echo "Rank papers. - Each PC member can set tags indicating their preference ranking for papers. - For instance, a PC member’s favorite paper would get tag “#~rank#1”, the next favorite “#~rank#2”, and so forth. + echo "
Rank applications. + Each PC member can set tags indicating their preference ranking for applications. + For instance, a PC member’s favorite application would get tag “#~rank#1”, the next favorite “#~rank#2”, and so forth. The chair can then combine these rankings into a global preference order using a Condorcet method. (", $this->hth->help_link("ranking"), ")
\n"; } function print_example_discuss() { echo "Define a discussion order. -Publishing the order lets PC members prepare to discuss upcoming papers. +Publishing the order lets PC members prepare to discuss upcoming applications. Define an ordered tag such as “#discuss”, then ask the PC to ", $this->hth->search_link("search for “order:#discuss”", "order:#discuss"), ". -The PC can now see the order and use quick links to go from paper to paper."; +The PC can now see the order and use quick links to go from application to application."; if ($this->user->isPC && !$this->conf->tag_seeall) { - echo " However, since PC members can’t see tags for conflicted papers, each PC member might see a different list.", $this->hth->change_setting_link("tag_visibility_conflict"); + echo " However, since PC members can’t see tags for conflicted applications, each PC member might see a different list.", $this->hth->change_setting_link("tag_visibility_conflict"); } echo "
\n"; } diff --git a/src/help/h_votetags.php b/src/help/h_votetags.php index 1f3f965e1..f1ce52547 100644 --- a/src/help/h_votetags.php +++ b/src/help/h_votetags.php @@ -5,12 +5,12 @@ class VoteTags_HelpTopic { static function print(HelpRenderer $hth) { $votetag = $hth->example_tag(TagInfo::TF_ALLOTMENT) ?? "vote"; - echo "Some conferences have PC members vote for papers. In + echo "
Some programs have PC members vote for applications. In allotment voting, each PC member is assigned a vote allotment to -distribute among unconflicted papers; a PC member might assign one vote to one +distribute among unconflicted applications; a PC member might assign one vote to one submission and five to another. In approval voting, each PC member -can vote for as many papers as they like. The PC’s aggregated vote totals -might help determine which papers to discuss.
+can vote for as many applications as they like. The PC’s aggregated vote totals +might help determine which applications to discuss.HotCRP supports voting through ", $hth->help_link("tags", "tags"), ". The chair can ", $hth->setting_link("define a set of voting tags", "tag_vote_allotment"), @@ -27,9 +27,9 @@ static function print(HelpRenderer $hth) { updates the main “#vote” tag to reflect the total. (An error is reported when PC members exceed their allotment.)
-To see papers’ vote counts in a list, search for ", +
To see applications’ vote counts in a list, search for ", $hth->search_link("show:#{$votetag}"), -". To list the papers with votes, sorted by vote count (most votes first), +". To list the applications with votes, sorted by vote count (most votes first), search for ", $hth->search_link("rorder:#{$votetag}"), " or ", $hth->search_link("rorder:#{$votetag} show:#{$votetag}"), ".
diff --git a/src/multiconference.php b/src/multiconference.php index f6b8911ae..7f79f9d55 100644 --- a/src/multiconference.php +++ b/src/multiconference.php @@ -169,9 +169,9 @@ static private function make_qrequest() { /** @return string */ static private function nonexistence_error() { if (PHP_SAPI === "cli") { - return "Conference not specified. Use `-n CONFID` to specify a conference."; + return "Program not specified. Use `-n CONFID` to specify a program."; } else { - return "Conference not specified."; + return "Program not specified."; } } diff --git a/src/pages/p_adminhome.php b/src/pages/p_adminhome.php index 1e01c8380..9f89a1f1d 100644 --- a/src/pages/p_adminhome.php +++ b/src/pages/p_adminhome.php @@ -58,14 +58,14 @@ static function print(Contact $user) { } // Conference names if ($conf->opt("shortNameDefaulted")) { - $ml[] = new MessageItem(null, "<5>hoturl("settings", "group=basics") . "\">Set the conference abbreviation to a short name for your conference, such as “OSDI ’14”", MessageSet::WARNING_NOTE); + $ml[] = new MessageItem(null, "<5>hoturl("settings", "group=basics") . "\">Set the program abbreviation to a short name for your program, such as “OSDI ’14”", MessageSet::WARNING_NOTE); } else if (simplify_whitespace($conf->short_name) != $conf->short_name) { - $ml[] = new MessageItem(null, "<5>The hoturl("settings", "group=basics") . "\">conference abbreviation setting has a funny value. To fix it, remove leading and trailing spaces, use only space characters (no tabs or newlines), and make sure words are separated by single spaces (never two or more)", MessageSet::WARNING); + $ml[] = new MessageItem(null, "<5>The hoturl("settings", "group=basics") . "\">program abbreviation setting has a funny value. To fix it, remove leading and trailing spaces, use only space characters (no tabs or newlines), and make sure words are separated by single spaces (never two or more)", MessageSet::WARNING); } // Site contact $site_contact = $conf->site_contact(); if (!$site_contact->email || $site_contact->email == "you@example.com") { - $ml[] = new MessageItem(null, "<5>hoturl("settings", "group=basics") . "\">Set the conference contact’s name and email so submitters can reach someone if things go wrong", MessageSet::URGENT_NOTE); + $ml[] = new MessageItem(null, "<5>hoturl("settings", "group=basics") . "\">Set the program contact’s name and email so submitters can reach someone if things go wrong", MessageSet::URGENT_NOTE); } // Configuration updates if ($conf->opt("oAuthTypes")) { diff --git a/src/pages/p_autoassign.php b/src/pages/p_autoassign.php index a20824b34..63725f67b 100644 --- a/src/pages/p_autoassign.php +++ b/src/pages/p_autoassign.php @@ -201,9 +201,9 @@ private function print_review_actions() { ["size" => 3, "class" => $this->ms->control_class("review:count", "js-autosubmit")]), " additional ", Ht::select("review:rtype", ["primary" => "primary", "secondary" => "secondary", "optional" => "optional", "metareview" => "metareview"], $qreq["review:type"]), - " review(s) per selected paper\n"; + " review(s) per selected application\n"; - $this->print_radio_row("a", "review_ensure", "Ensure each selected paper has at least", ["open" => true]); + $this->print_radio_row("a", "review_ensure", "Ensure each selected application has at least", ["open" => true]); echo " ", Ht::entry("review_ensure:count", $qreq["review_ensure:count"] ?? 1, ["size" => 3, "class" => $this->ms->control_class("review_ensure:count", "js-autosubmit")]), " ", @@ -216,7 +216,7 @@ private function print_review_actions() { ["size" => 3, "class" => $this->ms->control_class("review_per_pc:count", "js-autosubmit")]), " additional ", Ht::select("review_per_pc:rtype", ["primary" => "primary", "secondary" => "secondary", "optional" => "optional", "metareview" => "metareview"], $qreq["review_per_pc:rtype"]), - " review(s) from this paper selection"; + " review(s) from this application selection"; // Review round $rev_rounds = $this->conf->round_selector_options(null); @@ -244,7 +244,7 @@ private function print_conflict_actions() { $this->print_radio_row("a", "prefconflict", "Assign conflicts when PC members have review preferences of −100 or less"); $this->print_radio_row("a", "clear", "Clear all ", ["open" => true]); echo Ht::select("clear:type", ["primary" => "primary", "secondary" => "secondary", "optional" => "optional", "metareview" => "metareview", "conflict" => "conflict", "lead" => "discussion lead", "shepherd" => "shepherd"], $this->qreq["clear:type"]), - " assignments for selected papers and PC members\n"; + " assignments for selected applications and PC members\n"; } private function print_lead_actions() { @@ -262,7 +262,7 @@ private function print_discussion_actions() { $this->print_radio_row("a", "discussion_order", "Create discussion order in tag #", ["open" => true]); echo Ht::entry("discussion_order:tag", $this->qreq["discussion_order:tag"] ?? "discuss", ["size" => 12, "class" => $this->ms->control_class("discussion_order:tag", "js-autosubmit")]), - ", grouping papers with similar PC conflicts"; + ", grouping applications with similar PC conflicts"; } private function bp_selector($i, $which) { @@ -285,7 +285,7 @@ private function print_bad_pairs() { echo '', $this->bp_selector($i, "a"), " and ", $this->bp_selector($i, "b"); if ($i == 1) { - echo ' to the same paper ( · )'; + echo ' to the same application ( · )'; } echo " \n"; } @@ -308,7 +308,7 @@ private function print() { Assignment methods:
For example, this file clears existing R1 review assignments for papers + echo "
For example, this file clears existing R1 review assignments for applications tagged #redo, then assigns two primary reviews for submission #1 and one secondary review for submission #2:
@@ -240,7 +240,7 @@ function print() { Assignment methods: @@ -266,7 +266,7 @@ function print() { '