[WG] Discovery Improvements - Results page improvements

[lawrence]

1. Results page should identify all the search criteria (spatial/temporal etc)
2. The headings should be investigated for top justification, and
3. the "location" keyword should possibly include the +/- definitions underneath
4. Refine Search should be a link from after the results to a "populated" advanced page ...
5. Check the size of the dataset column for (no abstract) datasets

[lawrence]

Changeset:2528 addresses 2,3 and 5 as well as ticket:730. The others will have to wait on ticket:731.

[lawrence]

changeset:2533 addresses point 1

[lawrence]

Refine search may have to wait on some underlying architecture changes. I could do it now, but think it would be easier after we move to Pylons. Can we live without it for now? (I do need to add an advanced search button back though).

[selatham]

Should this 'populated refine search' go into #729 - future improvements where we have put the things that require ajax/cookies.

[selatham]

Comment on interface navigation(as at 11:00am Friday 1st June). When you get a results page, then try using the 'New search' and choose a target - there is no obvious way to 'submit' the query.

[lawrence]

Apart from hitting a carriage return. Doesn't that work? Isn't that folks expectation of the default? There isn't a lot of real estate on the page for putting a massive button.

[lawrence]

Ok, I see, if you type, then choose, a carriage return doesn't work. Maybe I'll have to fit one in ...