SRMv2 Wiki - User contributions [en]

Upload your final version

2025-12-04T13:53:53Z

Sbehnke: /* Before uploading, please check: */

Before uploading, please check:
* all authors are listed in the correct order
* the orcids are correct and working, add orcid to your SRM profile
* the affiliations are correct
* the acknowledgements section is completed: All organizations that have made a contribution are named.

Uploading pdfs and other files has been simplified. There is now only one link:

[[File:upload_files.PNG]]

Please click on "Upload File":

Here you can upload all important files for your submission. Some uploads are locked and are only available once certain criteria is met. For example you must upload your paper before uploading additional media files.

[[File:Add_Files.PNG]]

1) If your paper is accepted, you should upload the final version of your paper choosing "CRC Paper (PDF)" from the drop-down menu, the final pdf will be shown with the suffix _CRC.

2) If you want to add videos or other multimedia material to your paper, so that they will be published together with the paper and go into the Digital Library, please choose CRC Media (ZIP). Multimedia files that were uploaded during submission will not be considered for publication.

3) From 2022, all new releases published by Eurographics will be licensed under Creative Commons. Please upload your completed and signed "License-to-Publish Form (EG-CC-BY)". There is a separate workflow for signing licenses for Computer Graphics Forum (regular issues, conference issue, special issues).

[[File:cc-by-license-upload.png]]

4) Please upload the LaTeX Sources (as zip file), this is required for the publication process.

----
Common mistakes and important hints:

-- please make sure you are using the current egpubl style file.

-- starting with 2024, page numbers should be local to each paper in the format i of n, with i the current page number and n the total number of pages of the respective paper.

-- Formatting of figure captions: "Figure <number>" should be bold and the caption should be set in italics. Please compare the template.
This is often caused by overwriting the default settings when using the figure, caption, or subfigure package.
(try using: \captionsetup{labelfont=bf,textfont=it})

-- Please add your ORCID id to your SRM profile. (https://srmv2.eg.org/COMFy/Account/EditProfile) For more information about ORCID, please visit https://orcid.org/.

Upload your final version

2025-12-04T13:53:09Z

Sbehnke: /* Before uploading, please check: */

== Before uploading, please check: ==
all authors are listed in the correct order
the orcids are correct and working, add orcid to your SRM profile
the affiliations are correct
the acknowledgements section is completed: All organizations that have made a contribution are named.

Uploading pdfs and other files has been simplified. There is now only one link:

[[File:upload_files.PNG]]

Please click on "Upload File":

Here you can upload all important files for your submission. Some uploads are locked and are only available once certain criteria is met. For example you must upload your paper before uploading additional media files.

[[File:Add_Files.PNG]]

1) If your paper is accepted, you should upload the final version of your paper choosing "CRC Paper (PDF)" from the drop-down menu, the final pdf will be shown with the suffix _CRC.

2) If you want to add videos or other multimedia material to your paper, so that they will be published together with the paper and go into the Digital Library, please choose CRC Media (ZIP). Multimedia files that were uploaded during submission will not be considered for publication.

3) From 2022, all new releases published by Eurographics will be licensed under Creative Commons. Please upload your completed and signed "License-to-Publish Form (EG-CC-BY)". There is a separate workflow for signing licenses for Computer Graphics Forum (regular issues, conference issue, special issues).

[[File:cc-by-license-upload.png]]

4) Please upload the LaTeX Sources (as zip file), this is required for the publication process.

----
Common mistakes and important hints:

-- please make sure you are using the current egpubl style file.

-- starting with 2024, page numbers should be local to each paper in the format i of n, with i the current page number and n the total number of pages of the respective paper.

-- Formatting of figure captions: "Figure <number>" should be bold and the caption should be set in italics. Please compare the template.
This is often caused by overwriting the default settings when using the figure, caption, or subfigure package.
(try using: \captionsetup{labelfont=bf,textfont=it})

-- Please add your ORCID id to your SRM profile. (https://srmv2.eg.org/COMFy/Account/EditProfile) For more information about ORCID, please visit https://orcid.org/.

Upload your final version

2025-12-04T13:49:33Z

Sbehnke:

==Before uploading, please check: ==

Uploading pdfs and other files has been simplified. There is now only one link:

[[File:upload_files.PNG]]

Please click on "Upload File":

Here you can upload all important files for your submission. Some uploads are locked and are only available once certain criteria is met. For example you must upload your paper before uploading additional media files.

[[File:Add_Files.PNG]]

1) If your paper is accepted, you should upload the final version of your paper choosing "CRC Paper (PDF)" from the drop-down menu, the final pdf will be shown with the suffix _CRC.

2) If you want to add videos or other multimedia material to your paper, so that they will be published together with the paper and go into the Digital Library, please choose CRC Media (ZIP). Multimedia files that were uploaded during submission will not be considered for publication.

3) From 2022, all new releases published by Eurographics will be licensed under Creative Commons. Please upload your completed and signed "License-to-Publish Form (EG-CC-BY)". There is a separate workflow for signing licenses for Computer Graphics Forum (regular issues, conference issue, special issues).

[[File:cc-by-license-upload.png]]

4) Please upload the LaTeX Sources (as zip file), this is required for the publication process.

----
Common mistakes and important hints:

-- please make sure you are using the current egpubl style file.

-- starting with 2024, page numbers should be local to each paper in the format i of n, with i the current page number and n the total number of pages of the respective paper.

-- Formatting of figure captions: "Figure <number>" should be bold and the caption should be set in italics. Please compare the template.
This is often caused by overwriting the default settings when using the figure, caption, or subfigure package.
(try using: \captionsetup{labelfont=bf,textfont=it})

-- Please add your ORCID id to your SRM profile. (https://srmv2.eg.org/COMFy/Account/EditProfile) For more information about ORCID, please visit https://orcid.org/.

SRMv2 - Documentation & Guidelines

2025-11-18T06:37:37Z

Sbehnke: /* SRMv2 Leaflet */

Please note: The SRMv2 is now running on https://srmv2.eg.org/COMFy.

If you need further help or assistance, please email to <SRMv2@eg.org> [mailto:SRMv2@eg.org].
== SRMv2 Leaflet ==
[[File:SRM-infosheet 2025-11-01.pdf]]

== General ==
* [[Login]]
* [[Register]]
* [[Forgot your password]]
* [[Change your Password]]
* [[Change your profile settings]]
* [[Your SRM home]]

== Authors ==
Please check your user profile: are your email address and affiliation correct? Please also add the ORCID ID. https://orcid.org/
* [[Create a submission]]
* [[Modify your submission]]
* [[Upload your final version]]
* [[Upload your revised version, if your paper is conditionally accepted]]

== Reviewer ==
* [[Accept Review Agreement]]
* [[Assign Reviewer]]
* [[Add Review]]

== IPC ==
* [[Bidding]]
* [[Assign Reviewer]]
* [[IPCUploader]]

== Chair ==
==== General ====
* [[Types of Reviewers]]
* [[Review Form]]
* [["Cooling off"]]

==== Submissions ====
* [[Submissions]]
* [[Change_Submission_Status | Change Submission Status]]
* [[Show Bidding]]

==== Reviews ====
* [[Current Review Status | Review Status]]

* [[Creating Assignments (assign IPC members to submissions)]]

==== Email ====
* [[Send Email | Send Email To IPCs / Reviewers / Authors]]

==== Discussions ====
* [[Discussion | Discussion]]
* [[Rebuttal Discussion | Rebuttal Discussion]]
* [[Reviewer Author Discussion | Reviewer Author Discussion]]
* [[IPC Discussion | IPC Discussion]]

==== further Setup ====
* [[edit Conference]]
* [[Manage IPC Member]]
* [[Set Areas of Expertise for IPC]]
* [[set Chair conflict | Chair's conflicts]]
* [[View Chairs]]
* [[Meeting Data]]
* [[set Contact Chairs]]



== Publication Editor ==
* [[Current CRC papers]]

== Additional Information ==
* [[Text Analysis Tool and IPC Uploader]]
* [[Provided Features in SRMv2]]
* [[Request Tracker]]
* [[FAQ]]
* [[Calculate Suggestion]]

== Admin ==


Only relevant for SRM admins from FHA: [https://wiki.eg.org/SRMv2Wiki/index.php/SRM_admin Guidelines for SRM admins]

SRMv2 - Documentation & Guidelines

2025-11-18T06:37:20Z

Sbehnke: /* SRMv2 Leaflet */

Please note: The SRMv2 is now running on https://srmv2.eg.org/COMFy.

If you need further help or assistance, please email to <SRMv2@eg.org> [mailto:SRMv2@eg.org].
== SRMv2 Leaflet ==
[File:SRM-infosheet 2025-11-01.pdf]]

== General ==
* [[Login]]
* [[Register]]
* [[Forgot your password]]
* [[Change your Password]]
* [[Change your profile settings]]
* [[Your SRM home]]

== Authors ==
Please check your user profile: are your email address and affiliation correct? Please also add the ORCID ID. https://orcid.org/
* [[Create a submission]]
* [[Modify your submission]]
* [[Upload your final version]]
* [[Upload your revised version, if your paper is conditionally accepted]]

== Reviewer ==
* [[Accept Review Agreement]]
* [[Assign Reviewer]]
* [[Add Review]]

== IPC ==
* [[Bidding]]
* [[Assign Reviewer]]
* [[IPCUploader]]

== Chair ==
==== General ====
* [[Types of Reviewers]]
* [[Review Form]]
* [["Cooling off"]]

==== Submissions ====
* [[Submissions]]
* [[Change_Submission_Status | Change Submission Status]]
* [[Show Bidding]]

==== Reviews ====
* [[Current Review Status | Review Status]]

* [[Creating Assignments (assign IPC members to submissions)]]

==== Email ====
* [[Send Email | Send Email To IPCs / Reviewers / Authors]]

==== Discussions ====
* [[Discussion | Discussion]]
* [[Rebuttal Discussion | Rebuttal Discussion]]
* [[Reviewer Author Discussion | Reviewer Author Discussion]]
* [[IPC Discussion | IPC Discussion]]

==== further Setup ====
* [[edit Conference]]
* [[Manage IPC Member]]
* [[Set Areas of Expertise for IPC]]
* [[set Chair conflict | Chair's conflicts]]
* [[View Chairs]]
* [[Meeting Data]]
* [[set Contact Chairs]]



== Publication Editor ==
* [[Current CRC papers]]

== Additional Information ==
* [[Text Analysis Tool and IPC Uploader]]
* [[Provided Features in SRMv2]]
* [[Request Tracker]]
* [[FAQ]]
* [[Calculate Suggestion]]

== Admin ==


Only relevant for SRM admins from FHA: [https://wiki.eg.org/SRMv2Wiki/index.php/SRM_admin Guidelines for SRM admins]

File:SRM-infosheet 2025-11-01.pdf

2025-11-18T06:36:43Z

Sbehnke:

SRMv2 - Documentation & Guidelines

2025-11-18T06:36:13Z

Sbehnke:

Please note: The SRMv2 is now running on https://srmv2.eg.org/COMFy.

If you need further help or assistance, please email to <SRMv2@eg.org> [mailto:SRMv2@eg.org].
== SRMv2 Leaflet ==
[[File: ]]
== General ==
* [[Login]]
* [[Register]]
* [[Forgot your password]]
* [[Change your Password]]
* [[Change your profile settings]]
* [[Your SRM home]]

== Authors ==
Please check your user profile: are your email address and affiliation correct? Please also add the ORCID ID. https://orcid.org/
* [[Create a submission]]
* [[Modify your submission]]
* [[Upload your final version]]
* [[Upload your revised version, if your paper is conditionally accepted]]

== Reviewer ==
* [[Accept Review Agreement]]
* [[Assign Reviewer]]
* [[Add Review]]

== IPC ==
* [[Bidding]]
* [[Assign Reviewer]]
* [[IPCUploader]]

== Chair ==
==== General ====
* [[Types of Reviewers]]
* [[Review Form]]
* [["Cooling off"]]

==== Submissions ====
* [[Submissions]]
* [[Change_Submission_Status | Change Submission Status]]
* [[Show Bidding]]

==== Reviews ====
* [[Current Review Status | Review Status]]

* [[Creating Assignments (assign IPC members to submissions)]]

==== Email ====
* [[Send Email | Send Email To IPCs / Reviewers / Authors]]

==== Discussions ====
* [[Discussion | Discussion]]
* [[Rebuttal Discussion | Rebuttal Discussion]]
* [[Reviewer Author Discussion | Reviewer Author Discussion]]
* [[IPC Discussion | IPC Discussion]]

==== further Setup ====
* [[edit Conference]]
* [[Manage IPC Member]]
* [[Set Areas of Expertise for IPC]]
* [[set Chair conflict | Chair's conflicts]]
* [[View Chairs]]
* [[Meeting Data]]
* [[set Contact Chairs]]



== Publication Editor ==
* [[Current CRC papers]]

== Additional Information ==
* [[Text Analysis Tool and IPC Uploader]]
* [[Provided Features in SRMv2]]
* [[Request Tracker]]
* [[FAQ]]
* [[Calculate Suggestion]]

== Admin ==


Only relevant for SRM admins from FHA: [https://wiki.eg.org/SRMv2Wiki/index.php/SRM_admin Guidelines for SRM admins]

Creating Assignments (assign IPC members to submissions)

2025-09-29T05:22:01Z

Sbehnke: /* External Script */

SRMV2 provides an automatic reviewer assignment process. There are two entry points:

(for the correct links, replace "event" by your event.)

https://srmv2.eg.org/COMFy/Conference/event/showSuggestionsForPaperAssignment
and
https://srmv2.eg.org/COMFy/Conference/event/showSuggestionsForPaperAssignmentBySubmission

At first the system shows a list of all IPC members with along with every review type which is currently assigned to the conference.
[[Image:ShowSuggestionBlank.png|thumb|350px|none|Show Suggestion for IPC without data]]

== Requirements and steps:==
# There are IPC members with status "accepted" (https://srmv2.eg.org/COMFy/Ipc/event/manageIPC). For clarity, pending or rejected IPC members should be removed.
# Different reviewer types exist (usually Primary, Secondary, Tertiary).
# IPCuploader and bidding are completed.
# SARA score calculation should be started.

As chair, you now have the option of either using the built-in solution or using an external script to create assignments. This script is owned and maintained by Prof. M. Wimmer. (https://gitlab.com/salzrat/eg-sig-sort)

=== Built-in ===
* Now a new suggestion can be created: https://srmv2.eg.org/COMFy/Conference/event/createNewSuggestionForIPC
::This suggestion can be edited, exported (and then edited offline if necessary) and imported again..
[[Image:CreatenewSuggestion.png]]

When you press create New Suggestion you set the preferences for the new matching. If you are interested how the matching is created: [[calculate Suggestion]]
==== Modify the matching ====
If you are not satisfied with the current mapping, you can start over to get a better mapping (the mapping is randomly shuffled) or adjust the system's mapping. To do this, click on the document you want to correct. You will be taken to the following page:
[[Image:EditSuggestion.png|thumb|350px|none|Edit Suggestion]]

There you can specify who is assigned as which review type. (One person cannot be in multiple review types in one submission!)
There you can access the submission, see every review type, who is currently assigned in this review type, a checkbox for every review type, the internally generated rating, the person's bid, his global expertise list. And how much expertise the person has that matches the paper.
In this table:
Score: value from IPCUploader (SARA TFIDF),
RatingOrg: value, generated through "Initialize Rating", calculated from SARA TFIDF combined with bidding. (*5 could review, *10 want review)

=== External Script===
* Initialize Ratings [[Image:InitializeRatings.png]]
*:Initializes Rating and RatingOrg for Sort. For this purpose, the score (=affinity score, from the IPCuploader) is combined with the bidding.
*:For “want review” the score is multiplied with 10, and for “could review” with 5.
* IPC members can help with sorting. Use "Manage Sorter" to invite them and assign them to submissions. Sorters are IPC members, they cannot see the authors.
[[Image:ManageSorter.png]]
:The goal is to set the ratings so that the order determined by the ratings corresponds to the preferences of a submission for IPC members.
:This type of sorting is not about assigning reviewers, but rather about whether the rating, which is formed from bidding and affinity scores, is in line with the wishes and preferences of the IPC members. The sorters can change the rating for this purpose (initially, rating = RatingORG). This new order can then be used to generate the assignment.
* After the sorting, export the ratings https://srmv2.eg.org/COMFy/Review/event/ExportSuggestions and use the external script, the result can then be imported: https://srmv2.eg.org/COMFy/Review/event/ImportSuggestions

=== Last step (for both alternatives)===
when everything is set: "take Suggestion Live": the assignments are now active, IPC member should be informed.
:Use this button only once.
:There is no way to change active assignments through this menu.

Parse Preferences

2025-08-15T10:18:27Z

Sbehnke:

Here the preferences can be parsed. They are used for the author during the submission phase to [https://wiki.eg.org/SRMv2Wiki/index.php/Modify_your_submission#Edit.2FAdd_Preferences categorize the submission]. Every line indicates a new preference, when the line starts with a star (*) it will be recognized as a Top level category.

<div style="border:1px solid #000000;padding:5px;">
<b style="color:#f00000;">! IMPORTANT NOTE !</b><br>
This list should not be modified after authors start to upload their papers.
</div>

[[Image:ParsePreferences.png|thumb|350px|none|ParsePreferences.png]]

It is possible to reuse the categories from the old SRM system as they use the same parsing or reuse them from another conference.

Parse Preferences

2025-08-15T10:18:13Z

Sbehnke:

Here the preferences can be parsed. They are used for the author during the submission phase to [https://wiki.eg.org/SRMv2Wiki/index.php/Modify_your_submission#Edit.2FAdd_Preferences categorize the submission]. Every line indicates a new preference, when the line starts with a star (*) it will be recognized as a Top level category.

<div style="border:1px solid #000000;padding:5px;">
<b style="color:#f00000;">! IMPORTANT NOTE !</b><br>
This list should not be modified after authors start to upload their papers.
</div>

[[Image:ParsePreferences.png|thumb|350px|none|Self Check]]

It is possible to reuse the categories from the old SRM system as they use the same parsing or reuse them from another conference.

Parse Preferences

2025-08-15T10:14:13Z

Sbehnke:

Here the preferences can be parsed. They are used for the author during the submission phase to [https://wiki.eg.org/SRMv2Wiki/index.php/Modify_your_submission#Edit.2FAdd_Preferences categorize the submission]. Every line indicates a new preference, when the line starts with a star (*) it will be recognized as a Top level category.

<div style="border:1px solid #000000;padding:5px;">
<b style="color:#f00000;">! IMPORTANT NOTE !</b><br>
This list should not be modified after authors start to upload their papers.
</div>

It is possible to reuse the categories from the old SRM system as they use the same parsing or reuse them from another conference.

Parse Preferences

2025-08-15T10:10:36Z

Sbehnke:

Here the preferences can be parsed. They are used for the author during the submission phase to [https://wiki.eg.org/SRMv2Wiki/index.php/Modify_your_submission#Edit.2FAdd_Preferences categorize the submission]. Every line indicates a new preference, when the line starts with a star (*) it will be recognized as a Top level category.

<div style="border:1px solid #000000;padding:5px;">
<b style="color:#f00000;">! IMPORTANT NOTE !</b><br>
This list should not be modified after authors start to upload their papers.
</div>

[[Image:parsePreferences.png|thumb|625px|none|parse Preferences]]

It is possible to reuse the categories from the old SRM system as they use the same parsing or reuse them from another conference.

Parse Preferences

2025-08-15T10:09:56Z

Sbehnke:

Here the preferences can be parsed. They are used for the author during the submission phase to [https://wiki.eg.org/SRMv2Wiki/index.php/Modify_your_submission#Edit.2FAdd_Preferences categorize the submission]. Every line indicates a new preference, when the line starts with a star (*) it will be recognized as a Top level category.

<div style="border:1px solid #000000;padding:5px;">
<b style="color:#f00000;">! IMPORTANT NOTE !</b><br>
This list should not be modified after authors start to upload their papers.
</div>

[[Image:parsePreferences.png|thumb|400px|none|parse Preferences]]

It is possible to reuse the categories from the old SRM system as they use the same parsing or reuse them from another conference.

File:ParsePreferences.png

2025-08-15T10:09:02Z

Sbehnke: Sbehnke uploaded a new version of File:ParsePreferences.png

SRM admin

2025-08-15T09:57:54Z

Sbehnke: /* Admin Conference Settings */

== Admin Settings ==
These guidelines are only relevant for SRM admins from FHA: (in progress)
* [[ Admin Main Screen ]]

== Admin Conference Settings ==
* [[Self Check]]
* [[Edit Conference]]
* [[Parse Preferences]]

* [[Manage Chairs]]
* [[Manage PublicationEditor]]
* [[Manage Additional Conference Fields]]
* [[Manage Additional Review Fields]]
* [[Manage ReviewerTypes]]
* [[Manage Additional Submission Files]] <-- todo
* [[Swap Phase]]
* [[Auto Swap Phase]]
* [[Create Backup]]

== Additional Info ==
* [[Review2CRC| HowTo: Review -> CRC]]

Todo:

File:SRMv2SelfCheck.png

2025-08-15T09:54:04Z

Sbehnke:

SRMv2 - Documentation & Guidelines

2025-08-15T09:15:11Z

Sbehnke: /* Authors */

Please note: The SRMv2 is now running on https://srmv2.eg.org/COMFy.

If you need further help or assistance, please email to <SRMv2@eg.org> [mailto:SRMv2@eg.org].

== General ==
* [[Login]]
* [[Register]]
* [[Forgot your password]]
* [[Change your Password]]
* [[Change your profile settings]]
* [[Your SRM home]]

== Authors ==
Please check your user profile: are your email address and affiliation correct? Please also add the ORCID ID. https://orcid.org/
* [[Create a submission]]
* [[Modify your submission]]
* [[Upload your final version]]
* [[Upload your revised version, if your paper is conditionally accepted]]

== Reviewer ==
* [[Accept Review Agreement]]
* [[Assign Reviewer]]
* [[Add Review]]

== IPC ==
* [[Bidding]]
* [[Assign Reviewer]]
* [[IPCUploader]]

== Chair ==
==== General ====
* [[Types of Reviewers]]
* [[Review Form]]
* [["Cooling off"]]

==== Submissions ====
* [[Submissions]]
* [[Change_Submission_Status | Change Submission Status]]
* [[Show Bidding]]

==== Reviews ====
* [[Current Review Status | Review Status]]

* [[Creating Assignments (assign IPC members to submissions)]]

==== Email ====
* [[Send Email | Send Email To IPCs / Reviewers / Authors]]

==== Discussions ====
* [[Discussion | Discussion]]
* [[Rebuttal Discussion | Rebuttal Discussion]]
* [[Reviewer Author Discussion | Reviewer Author Discussion]]
* [[IPC Discussion | IPC Discussion]]

==== further Setup ====
* [[edit Conference]]
* [[Manage IPC Member]]
* [[Set Areas of Expertise for IPC]]
* [[set Chair conflict | Chair's conflicts]]
* [[View Chairs]]
* [[Meeting Data]]
* [[set Contact Chairs]]



== Publication Editor ==
* [[Current CRC papers]]

== Additional Information ==
* [[Text Analysis Tool and IPC Uploader]]
* [[Provided Features in SRMv2]]
* [[Request Tracker]]
* [[FAQ]]
* [[Calculate Suggestion]]

== Admin ==


Only relevant for SRM admins from FHA: [https://wiki.eg.org/SRMv2Wiki/index.php/SRM_admin Guidelines for SRM admins]

Admin Main Screen

2025-07-01T15:53:19Z

Sbehnke: /* Edit Info */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 1000 words.

* Uses IPC Uploader: Sets the links for the IPCUploader are visible - otherwise they are hidden. Presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload their representative papers. 

* check Amount of Pages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* check Page Size: Sets if the Page Size should be checked. Enforces the check in CRC, gives a Warning in Submission Phase.

* check Embedded Fonts: Sets if the CRC PDF should be checked if the fonts are embedded. (Check it always!)

* check CMYK Color Space: Sets if the CRC PDF should be checked if the fonts color space is in CMYK.

* Image: Upload possibility for a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

https://srmv2.eg.org/COMFy/Account/ViewUserDb

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

https://srmv2.eg.org/COMFy/Account/AdminLogin

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

https://srmv2.eg.org/COMFy/Account/EditInfo

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

File:SRMv2EditInfo.png

2025-07-01T15:50:55Z

Sbehnke:

Admin Main Screen

2025-07-01T15:50:16Z

Sbehnke: /* Edit Info */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 1000 words.

* Uses IPC Uploader: Sets the links for the IPCUploader are visible - otherwise they are hidden. Presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload their representative papers. 

* check Amount of Pages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* check Page Size: Sets if the Page Size should be checked. Enforces the check in CRC, gives a Warning in Submission Phase.

* check Embedded Fonts: Sets if the CRC PDF should be checked if the fonts are embedded. (Check it always!)

* check CMYK Color Space: Sets if the CRC PDF should be checked if the fonts color space is in CMYK.

* Image: Upload possibility for a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

https://srmv2.eg.org/COMFy/Account/ViewUserDb

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

https://srmv2.eg.org/COMFy/Account/AdminLogin

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

https://srmv2.eg.org/COMFy/Account/EditInfo

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:49:49Z

Sbehnke: /* Login as other User */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 1000 words.

* Uses IPC Uploader: Sets the links for the IPCUploader are visible - otherwise they are hidden. Presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload their representative papers. 

* check Amount of Pages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* check Page Size: Sets if the Page Size should be checked. Enforces the check in CRC, gives a Warning in Submission Phase.

* check Embedded Fonts: Sets if the CRC PDF should be checked if the fonts are embedded. (Check it always!)

* check CMYK Color Space: Sets if the CRC PDF should be checked if the fonts color space is in CMYK.

* Image: Upload possibility for a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

https://srmv2.eg.org/COMFy/Account/ViewUserDb

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

https://srmv2.eg.org/COMFy/Account/AdminLogin

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:48:59Z

Sbehnke: /* Login as other User */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 1000 words.

* Uses IPC Uploader: Sets the links for the IPCUploader are visible - otherwise they are hidden. Presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload their representative papers. 

* check Amount of Pages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* check Page Size: Sets if the Page Size should be checked. Enforces the check in CRC, gives a Warning in Submission Phase.

* check Embedded Fonts: Sets if the CRC PDF should be checked if the fonts are embedded. (Check it always!)

* check CMYK Color Space: Sets if the CRC PDF should be checked if the fonts color space is in CMYK.

* Image: Upload possibility for a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

https://srmv2.eg.org/COMFy/Account/ViewUserDb

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

File:SRMv2AdminLogin.png

2025-07-01T15:48:44Z

Sbehnke:

Admin Main Screen

2025-07-01T15:47:34Z

Sbehnke: /* View User Database */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 1000 words.

* Uses IPC Uploader: Sets the links for the IPCUploader are visible - otherwise they are hidden. Presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload their representative papers. 

* check Amount of Pages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* check Page Size: Sets if the Page Size should be checked. Enforces the check in CRC, gives a Warning in Submission Phase.

* check Embedded Fonts: Sets if the CRC PDF should be checked if the fonts are embedded. (Check it always!)

* check CMYK Color Space: Sets if the CRC PDF should be checked if the fonts color space is in CMYK.

* Image: Upload possibility for a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

https://srmv2.eg.org/COMFy/Account/ViewUserDb

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

File:SRMv2MergeUser.png

2025-07-01T15:46:02Z

Sbehnke:

Admin Main Screen

2025-07-01T15:42:05Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 1000 words.

* Uses IPC Uploader: Sets the links for the IPCUploader are visible - otherwise they are hidden. Presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload their representative papers. 

* check Amount of Pages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* check Page Size: Sets if the Page Size should be checked. Enforces the check in CRC, gives a Warning in Submission Phase.

* check Embedded Fonts: Sets if the CRC PDF should be checked if the fonts are embedded. (Check it always!)

* check CMYK Color Space: Sets if the CRC PDF should be checked if the fonts color space is in CMYK.

* Image: Upload possibility for a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:33:15Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.


Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* Has Submission Images: Adds the possibility for a submission to add a representative image to the submission.

* Elevated IPCs: Sets the IPCs to have near chair able power within the system (access all non conflicted submissions, see authors, see reviews).

* Reviewer Author Discussion: Activates the anonymous discussion forum for authors and reviewers. Typically used in the 2nd review cycle.

* Activated Bidding: Sets the links for bidding visible - otherwise they are hidden. When activated the IPC member can set conflicts, edit the area of preferences, and bid on the papers.

* Activated Rebuttal: Sets the links for rebuttal for authors / rebuttal forums for reviewer visible - otherwise they are hidden. When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:27:47Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.



Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Hidden in Userhome: Hides the conference from the User home. When a conference is done, then it is still in "MySubmissions" or "My Chairings". If this option is enabled all the conference disappears in every userhome (except Elevated chairs).

* New Submissions Allowed: If author may submit new Submissions into the system. After the first review cycle the submission deadline gets extended, so users may update their submission but no new once are accepted. Do not check it when switching to 2nd cycle or CRC phase.

* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:20:42Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default submission description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.



* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:20:05Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.



* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:19:35Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* "Shortname:" The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.



* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:18:48Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in and watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.



* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:18:03Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in an watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries. Wildcards are possible.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Page Size: the entry for the Page size: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.



* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:13:10Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in an watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. '0' means 'not visible', '1' means 'first review cycle visible' and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true' are visible.

* Chair Cycle Visible
* Senior Recommendation Cycle Visible
* Author Summary Cycle Visible

* SRM Email (a SRM email for help-> SRM admin), Chair Email (a mailman list with the Program Chairs): The technical support team will setup the SRM email on request.

* Accept Decline Dropdown: used for the senior recommendation and the chair decision. Can be changed when switching the phases.

* Assign Email Text: template, used when IPC members assign tertiaries.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Submission Deadline: The submission deadline is the date when no further submissions/content can be uploaded. Submissions in CRC phase, chairs and admins can overrule this exception. When a submission enters the review phase the submission is locked for the user, so he can't modify/delete it. Then if the chair wants a second/third submission phase the deadline must be extended, so the author can upload another submission. (Time to enter is local time (Austria/ Germany), time shown is UTC.)

* Instruction: The instruction is the longer description. It can be accessed from /COMFy/Conference/<ConferenceShortName>/Instruction. Here is like in Description [[SRM2v2Javascript | HTML & Javascript]] enabled!

* AbstractDeadline: The abstract deadline, after this date it is not allowed for authors to change the abstract or the title.

* IsAbstractDeadlineStrict: If this checkbox is set, the abstract deadline is enforced. Otherwise the abstract deadline is ignored.

* SRM Email: The email where the user can get SRMv2 Help.

* chair Email: The email for chairs. One Email! most of the time for a mailinglist entry for chairs.

* Assign Email Text: The text the user gets presented when he assigns other users. Wildcards are possible.

* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:03:08Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in an watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are tied to the prefix. However, it is possible.

* Additional Material File Size: 700 is a good value.

* Review Cycle Visible: sets the reviews visible for the author. 0 means not visible, 1 means first review cycle visible and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true'.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Submission Deadline: The submission deadline is the date when no further submissions/content can be uploaded. Submissions in CRC phase, chairs and admins can overrule this exception. When a submission enters the review phase the submission is locked for the user, so he can't modify/delete it. Then if the chair wants a second/third submission phase the deadline must be extended, so the author can upload another submission. (Time to enter is local time (Austria/ Germany), time shown is UTC.)

* Instruction: The instruction is the longer description. It can be accessed from /COMFy/Conference/<ConferenceShortName>/Instruction. Here is like in Description [[SRM2v2Javascript | HTML & Javascript]] enabled!

* AbstractDeadline: The abstract deadline, after this date it is not allowed for authors to change the abstract or the title.

* IsAbstractDeadlineStrict: If this checkbox is set, the abstract deadline is enforced. Otherwise the abstract deadline is ignored.

* SRM Email: The email where the user can get SRMv2 Help.

* chair Email: The email for chairs. One Email! most of the time for a mailinglist entry for chairs.

* Assign Email Text: The text the user gets presented when he assigns other users. Wildcards are possible.

* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T15:01:23Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in an watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. 

* Conference Instruction: Provide LaTeX templates etc.

* New Submission Description: Overwrites the default description.

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are bound to the prefix. It is possible though.

* Additional Material File Size: 700 is a good value

* Review Cycle Visible: sets the reviews visible for the author. 0 means not visible, 1 means first review cycle visible and so on. Only the fields (and comments) of the review fields which have 'Visible for Author = true'.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Submission Deadline: The submission deadline is the date when no further submissions/content can be uploaded. Submissions in CRC phase, chairs and admins can overrule this exception. When a submission enters the review phase the submission is locked for the user, so he can't modify/delete it. Then if the chair wants a second/third submission phase the deadline must be extended, so the author can upload another submission. (Time to enter is local time (Austria/ Germany), time shown is UTC.)

* Instruction: The instruction is the longer description. It can be accessed from /COMFy/Conference/<ConferenceShortName>/Instruction. Here is like in Description [[SRM2v2Javascript | HTML & Javascript]] enabled!

* AbstractDeadline: The abstract deadline, after this date it is not allowed for authors to change the abstract or the title.

* IsAbstractDeadlineStrict: If this checkbox is set, the abstract deadline is enforced. Otherwise the abstract deadline is ignored.

* SRM Email: The email where the user can get SRMv2 Help.

* chair Email: The email for chairs. One Email! most of the time for a mailinglist entry for chairs.

* Assign Email Text: The text the user gets presented when he assigns other users. Wildcards are possible.

* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T14:55:01Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in an watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Conference Name: The long name of the conference. Will be seen in the overview of the conference.

* Conference Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. [[SRM2v2Javascript | HTML & Javascript]] enabled!

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are bound to the prefix. It is possible though.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Submission Deadline: The submission deadline is the date when no further submissions/content can be uploaded. Submissions in CRC phase, chairs and admins can overrule this exception. When a submission enters the review phase the submission is locked for the user, so he can't modify/delete it. Then if the chair wants a second/third submission phase the deadline must be extended, so the author can upload another submission. (Time to enter is local time (Austria/ Germany), time shown is UTC.)

* Instruction: The instruction is the longer description. It can be accessed from /COMFy/Conference/<ConferenceShortName>/Instruction. Here is like in Description [[SRM2v2Javascript | HTML & Javascript]] enabled!

* is Review Visible: sets the reviews visible for the author. When this field is checked, the author can see the reviews in his submission. Only the fields (and comments) of the review fields which have Visible for Author = true.

* AbstractDeadline: The abstract deadline, after this date it is not allowed for authors to change the abstract or the title.

* IsAbstractDeadlineStrict: If this checkbox is set, the abstract deadline is enforced. Otherwise the abstract deadline is ignored.

* SRM Email: The email where the user can get SRMv2 Help.

* chair Email: The email for chairs. One Email! most of the time for a mailinglist entry for chairs.

* Assign Email Text: The text the user gets presented when he assigns other users. Wildcards are possible.

* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

Check Boxes:

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

Admin Main Screen

2025-07-01T14:50:04Z

Sbehnke: /* Create Conference */

Opposed to the normal Home Screen of the users the admins main Screen is the Event page. There he can see all current, previous and hidden conferences and access them.

[[Image:SRMv2AdminMainScreen.png|thumb|350px|none|Admin Main Screen]]

=== Create Conference ===
With Create Conference https://srmv2.eg.org/COMFy/Conference/addNewConference the admin can create a new Conference. All settings can be modified by the admin later. Although some should NOT be modified (only in certain cases) once the conference runs.

* Shortname: The shortname is the unique! identifier for the conference. This identifier will be used for the URL generation, short links in the system and internal for the access management. It is suggested not to change this value once the conference runs. As users who are logged in an watch the current conference will get broken links (until they refreshed), the access rights will be modified and the sent emails from the system will not work.

* Hide Conference: Hide conference hides the conference from all non admin users. This means you can setup the conference, check if everything is working. It is even possible to give eg. chairs the link to the conference to see if everything is fine, as it is only hidden not locked.

* Name: The long name of the conference. Will be seen in the overview of the conference.

* Description: Here you can enter a short description about the conference. This info will be seen on the conference info page. [[SRM2v2Javascript | HTML & Javascript]] enabled!

* Prefix: The prefix is the prefix for the submission. Standardprefix is paper, so the submission will be named paper1000, paper1001 and so on. Do not use digits in prefix: For example use "FP-first" and "FP-second" instead of "FP1" and "FP2". Here like with the conference shortname it is not recommended to change the settings as again the URLs and internal rights are bound to the prefix. It is possible though.

* Submission Publication Length: The maximum amount of pages a paper may have. During the submission phase the user gets a warning when the publication length is not met. During the CRC Phase the publication length is enforced when checkAmountPages is checked.

* Submission Deadline: The submission deadline is the date when no further submissions/content can be uploaded. Submissions in CRC phase, chairs and admins can overrule this exception. When a submission enters the review phase the submission is locked for the user, so he can't modify/delete it. Then if the chair wants a second/third submission phase the deadline must be extended, so the author can upload another submission. (Time to enter is local time (Austria/ Germany), time shown is UTC.)

* Instruction: The instruction is the longer description. It can be accessed from /COMFy/Conference/<ConferenceShortName>/Instruction. Here is like in Description [[SRM2v2Javascript | HTML & Javascript]] enabled!

* is Review Visible: sets the reviews visible for the author. When this field is checked, the author can see the reviews in his submission. Only the fields (and comments) of the review fields which have Visible for Author = true.

* AbstractDeadline: The abstract deadline, after this date it is not allowed for authors to change the abstract or the title.

* IsAbstractDeadlineStrict: If this checkbox is set, the abstract deadline is enforced. Otherwise the abstract deadline is ignored.

* SRM Email: The email where the user can get SRMv2 Help.

* chair Email: The email for chairs. One Email! most of the time for a mailinglist entry for chairs.

* Assign Email Text: The text the user gets presented when he assigns other users. Wildcards are possible.

* activated Bidding: sets the bidding active. When activated the IPC member can set conflicts edit the area of preferences and bid on the papers.

* activated Rebuttal: When activated the user gets presented a link in his submission, where he can enter a one time complaint. This complaint may not have more than 100 words.

* Uses IPC Uploader: presents the IPC member with a link in their IPC home where they can access the IPC uploader. There they can upload there their paper. They must be imported with "get IPCs from Comfy" in the IPC uploader to activate their account.

* checkAmountPages: sets if the amount of pages should be checked or not in the CRC phase. (they will get notified in the submission phase regardless). Its not possible for the author to upload then a paper in the CRC phase with a larger amount of pages.

* checkPagesize: sets if the Pagesize should be checked on the CRC upload. If there then there are no fonts embedded the paper gets refused.

* pageSize: the entry for the Pagesize: "612 x 792" for letter, "595 x 841" for A4 or "(no_check)" for ignoring the Size.

* checkEmbeddedFonts: sets if the fonts should be embedded in the CRC upload. If there then there are no fonts embedded the paper gets refused.

* checkCMYKColorSpace: sets if the paper should be in the CMYK color space. If there then there are no fonts embedded the paper gets refused.

* Image: sets a small image for the conference. Otherwise a standard image will be presented.

=== View User Database ===

This shows all current users. It is the implementation of the [[https://wiki.eg.org/SRMv2Wiki/index.php/AddUser Add User ]] implementation. With the exception that the admin can see on this page also other admins. Other users (chair, authors, ...) wont see admins there. It is possible to search and sort for each of the entries. There are three different functions:
* Edit: Can edit the userprofile of a user, (inclusive the admin can reject the accepted review agreement).

* Delete user: a user is deleted and all his dependencies too. (check to confirm).

* Login as other user. The admin will be logged into the user. (and see everything this user sees, and access everywhere the user has access to).

==== mergeUser ====
It is further possible to merge two users together. If one has two accounts. The user on the top, will get his rights removed, the user on the bottom will get all additional access rights. The user will currently NOT be deleted after the merge.

[[Image:SRMv2MergeUser.png|thumb|350px|none|Merge User]]

=== Login as other User ===

Here the admin can login as a other user. It is possible to enter the username or the email.

[[Image:SRMv2AdminLogin.png|thumb|350px|none|SRMv2 Admin Login]]

=== Edit Info ===

Edit Info modifies the message of the day, the user can see. For example a testentry and two scripts:

[[Image:SRMv2EditInfo.png|thumb|350px|none|SRMv2 Edit Info]]

Example: [[Image:SRMv2EditInfoExample.png|thumb|350px|none|SRMv2 Edit Info example]]

Here again is [[SRM2v2Javascript | HTML & Javascript]] enabled

File:SRMv2AdminMainScreen.png

2025-07-01T14:48:08Z

Sbehnke:

IPC Discussion

2025-06-24T11:01:59Z

Sbehnke: Created page with "Will be enabled with Edit conference -> Elevated IPCs. This will be used during Conference IPC meeting to discuss results of the submissions."

Will be enabled with Edit conference -> Elevated IPCs. This will be used during Conference IPC meeting to discuss results of the submissions.

Rebuttal Discussion

2025-06-24T10:50:43Z

Sbehnke:

The Rebuttal can be activated in Edit Conference. (with admin or chair admin rights.)

[[file:ActivateRebuttal.png]]

Set the deadline in Deadline Mangement: [[file:SetRebuttalDeadline.png]]

After the rebuttal deadline, activate the rebuttal discussion under [[Types_of_Reviewers]].

Rebuttal Discussion

2025-06-24T10:49:47Z

Sbehnke:

The Rebuttal can be activated in Edit Conference. (with admin or chair admin rights.)

[[file:ActivateRebuttal.png]]

Set the deadline in: [[file:SetRebuttalDeadline.png]]

After the rebuttal deadline, activate the rebuttal discussion under [[Types_of_Reviewers]].

Rebuttal Discussion

2025-06-24T10:48:50Z

Sbehnke:

File:SetRebuttalDeadline.png

2025-06-24T10:47:51Z

Sbehnke:

Rebuttal Discussion

2025-06-24T10:44:23Z

Sbehnke:

The Rebuttal can be activated in Edit Conference.

[[file:ActivateRebuttal.png]]

Rebuttal Discussion

2025-06-24T10:44:17Z

Sbehnke:

The Rebuttal can be activated in Edit Conference.
[[file:ActivateRebuttal.png]]

Rebuttal Discussion

2025-06-24T10:44:05Z

Sbehnke:

The Rebuttal can be activated in Edit Conference. [[file:ActivateRebuttal.png]]

File:ActivateRebuttal.png

2025-06-24T10:43:20Z

Sbehnke:

Rebuttal Discussion

2025-06-24T10:42:14Z

Sbehnke: Created page with "The Rebuttal can be activated in Edit Conference."

The Rebuttal can be activated in Edit Conference.

Discussion

2025-06-24T10:38:46Z

Sbehnke:

Discussions between all reviewer types of a submission are possible and can be configured in [[Types of Reviewers]]. If the event uses rebuttal, the [[Rebuttal Discussion]] should be enabled.