Besides the two editors assigned to review the article, a third editor (demo editor) will be appointed to create the online demo. Ideally, the demo editor should be one of the authors of the article, but if the author is unable to create the demo, the editors shall assign someone to the task. A good choice could be the editor in charge of reviewing the code.

The tasks of the demo editor are:

• Help authors with any technical issues they might have. The editors are their gateway to IPOL and they need to be guided.
• Check that the title of the demo matches exactly the title of the article (including capitalization).
• When the article becomes a pre-print, make sure that the demo is downloading the source code from the article's page, not from any other location (say, dev.ipol.im, external servers, etc.)
• Once the demo is published, the system will keep monitoring that it works correctly. If the system sends an email about compilation or execution errors it is the responsibility of the editor to check it out. This is specially important in the case of published articles.
• When a workshop eventually turns into a pre-print, remember to update the ID of the demo and change its state to "preprint".
• Ask for the creation of the pre-print page (which includes the demo) as soon as you decide that the article is suitable for IPOL. This allows to discover and fix eventual bugs way before the publication.
• Discuss with the author about the libraries they use in their source code. In case a library is not accepted in IPOL, we can do it after a quick discussion. Also, the author can include the whole library (or parts of it) as non-reviewed material within their own sources.
• In the case of a Python program the authors can use any library found at the Python Package Index (PPI). It is mandatory to use a virtual environment to that purpose. The demo system supports the specification and installation of Python virtual environments automatically.
• You can create as many tests you want in the demo system (just use the 55555 prefix and set the state to 'test'). But remember to remove them when you no longer need them. If you maintain a test demo for a long time probably it means that it is not a quick test, but a demo that should be turned into a workshop with a permanent URL.
• The demo system allows to reconstruct experiments from the archive's page. This is not done automatically because the system needs the editors to first ensure that they have added all the necessary information (visible or not) in the archive. The editor should activate the reconstruction option as soon as possible since it will not be possible to reconstruct experiments performed before the date of the activation.
• As a minimal test before the publication of the demo, upload some data and test the algorithm with different parameters. Finally, check that the archive shows the results of the performed experiments and that the reconstruction works correctly (i.e. no missing blobs).