A distilled analysis of the full-text answers

We will read all the full-text answers attached to PollResults to "distill" remarkable comments, common praise, recurrent complains. We will then put all this together into a short paper which takes stakes of the trends in the user requirements in HEP information systems. Rather than real user requirements (see below) this is more intended to be a document which gives a flavour of what's on a user mind. The focus of this paper is to discuss the specificity of the needs of the community and be used with potential sponsors to clarify the bases on which our vision is built.

This is the page to define guidelines for the "distillers" to read the answers, assign them to classes, and weight comments.

-- SalvatoreMele - 10 Jul 2007

Guidelines

Read through the poll results trying to extract broad wishes from the user comments

Feature

The feature wished for. Rephase in your own words distill to a useful user-type wish. Should not be system specific, but rather phrased in user language. (I.e. don't try to rephrase the feature in terms of some current or future system, just phrase it as functionality that the user sees)

Type

Divide your wishes into 4 broad categories

• User Interface
• Content/Coverage
• Features
• Other

Strength

A relative measure (subjective) 1-10 1 being least strong, 10 being the strongest desire for this feature from the survey. A high strength could either be from many weak requests of a few strong requests.

Comments

Right...

References

Reference any particular response via the line number in the original document (note that I am creating a new column in the spreadsheet (without sorting) and adding unique IDs in this column that match the row numbers in Salavatore's original. That way I can sort if I want and preserve the IDs. #2 is the first real response, someone who prefers Google)

Don't feel the need to reference every response that bears on this, just if there is a particular response that is especially relevant or interesting.

Template

This is the template that I'll be using: