Maintaining the CSE webserver's PLSE webpages

The departmental webpages are maintained at http://www.cs.washington.edu/. Log in by clicking the "Log in" text at the lower right corner of the webpage Documentation regarding how to use the Drupal website used to appear at https://www.cs.washington.edu/lab/web/drupal/. That documentation is lacking in places, but is improving. Hopefully most of this webpage can be eliminated once the CSE Drupal documentation is better. If you have questions, send them to Dan Boren so that he can improve the documentation.

People

Tag yourself with "plse" and with your advisor's CSEnetID.

Research projects

The PLSE webpages list projects that group members are working on or have worked on in the past.

The projects are divided into “research areas”, such as “Design & architecture”, “Parallelism & concurrency”, etc. A single project may be listed under multiple research areas. There are a relatively small number of research areas, so that they are manageable and so that visitors will actually read and understand them. Talk with the faculty before adding a new research area.

Likewise, our preference is to have fewer rather than more projects. In general, each project should span multiple publications (even ones by different authors). We don't want to list a zillion micro-projects on our webpages, which will confuse readers and turn them off, rather than giving a flavor of our accomplishments.

You will write either one or two blurbs about your project. A one-paragraph blurb (max 600 characters) will appear in the PLSE list of projects. A slightly longer blurb (or the same one) will appear on the project's own homepage in the CSE website. The project is allowed to have its "main" webpage elsewhere, but even in that case there should at least be a stub on the CSE Drupal site that gives basic information and links to that one.

The blurb should clearly state:

The short blurb should be brief and punchy — 600 characters is a firm limit, but shorter is OK. Remember that it's going to appear in a list of a dozen other projects, so we can't have them be too long. The longer blurb can contain additional information.

Tagging:

Set the weight of the project to the negative of the year of the latest publication, software release, or other activity (example: -2012 or -1999. For a new project that has not yet had publicly-visible activity, use the negative of the current year.

Undergrads: You have to manually add undergraduates to the CSE Drupal website. (By contrast, faculty, grad students, and staff automatically appear.) Log in, click on “Content” in the upper left menu bar, and then click on “People”. Alternately, go straight to https://www.cs.washington.edu/#overlay=node/add/people.

Publications: If a publication entry is being populated by uploading a BibTeX file, then you shouldn't edit the publication directly from the web, because the next time the BibTeX file is reloaded, it will overwrite your changes. Rather, you should change the BibTeX file and then reload it. Currently, reloading the BibTeX file must be done manually by Dan Boren — send him email with your request. :-(

If you notice a duplicated publication, then you should coordinate with the person who created the duplicate. Many publications are automatically created by file upload. Just removing the duplicates manually will result in the duplicate being re-created the next time the file is uploaded. In general, you should make sure the BibTeX file has all desired information, then remove the manually-created version.

This file is /projects/swlab1/www/Internal/plse-webpages.html

[Some of this documentation should be merged into the official department documentation, since it applies to the site generally, but is (as of the time of writing) clearer than the official department documentation.]