Last changed
19 Sep 2002 ............... Length about 900 words (6000 bytes).
This is a WWW document maintained by
Steve Draper, installed at http://www.psy.gla.ac.uk/~steve/hci02/30wordsidea.html.
Web site logical path:
[www.psy.gla.ac.uk]
[~steve]
[hci02]
[this page]
30 word descriptions for conference items
These are notes on a scheme that was piloted at HCI 2002: having 30 word
descriptions of every item in the conference as an aid to selecting them. The
aim, not achieved this time, would be to allow delegates to review the whole
conference before they arrive and select what they would like to see, and even
whether they wish to attend. It shoudl be particularly good at showing all
the items related to a particular topic, regardelss of their type (poster,
paper, doctoral consortium paper, tutorial, ...).
- To help the organisers select referees for each item.
- To help group items into sessions, and to generate titles for sessions.
- To help delegates see what items there are to suit their interests, even if
these appear in diverse places.
- To produce an integrated view of the conference (instead of the proceedings
which group by type e.g. all papers together, all workshops somewhere else; or
the programme which groups by time and type). Thus a postgrad abstract from
the doctoral consortium, a poster, and a keynote could all appear together if
their content is related.
- In the call, require authors to produce a 30 word description for
each item (including posters, workshops, keynotes, etc.). Warn them that,
unlike the rest of their contribution, this description may be edited, and will
eventually be used as the committee's description of the item to the delegates.
A "call" wording is available.
- Have referees suggest edits to the 30 words. Have chairs modify them as
they go.
- Have one or more people carefully go over them all, with the papers to
hand, and edit them where required. Some features such as the label
"controversial" or "contains empirical work" may have to be added manually.
- Have them (accepted items) in the central spreadsheet/database used,
together with authors, titles, type, time, place. I.e. make sure such a single
centralised record is created, not many separate ones for papers, posters
etc., and yet another for the timetable.
- Go over the record, manually sorting it into an order that clusters things
of similar content area. Assign an ID number to each item using this order.
Of course there are many different orders you might use: judgement and
arbitrary choice play a big part here. But the idea is, that if someone looks
up an item in this list using say author, its neighbours might be interesting
because of their content.
- Print the master index in this order (each item shows author, title, index
number, type (paper, tutorial, etc.), time, place, 30 word description).
- Produce other indexes: by author, by type, by time, by place; AND by
keyword. These indexes refer by ID number to the main one. Keyword index is
produced using every word in both titles and 30-words; and deleting those
keywords with no discriminatory power ("and", "the", "HCI", etc.). In my demo,
these extra indexes would each fit on one page (several columns).
- Publish these in advance of the conference: on the web, in "Interfaces",
possibly in circulated programmes. The keyword index also tends to show at
once what themes are popular or not this year.
The idea was partly applied for the HCI 2002 conference. The 30 word
descriptions were collected, and they were used in a conference guide,
organised by the time and place of each item's presentation, in
Interfaces no.52 which was also distributed in the conference packs.
This version is imperfect because:
- The times and places were never put in the same digital place as the other
information (and I was too lazy to retype them). All the alternative
indices should have all the types of information.
-
In these online indices, items are referred to by an apparently arbitrary
ID number. Three indices are given here online:
Web site logical path:
[www.psy.gla.ac.uk]
[~steve]
[hci02]
[this page]
[Top of this page]