WilliamWDTK
WilliamWDTK
For example, entering a user ID in the user search box in the admin interface should bring up a user exact matching that ID. Same for requests, bodies etc.
Searching for `urn:` returns `blackburn_with_darwen`. I did not expect this. [https://www.whatdotheyknow.com/admin/tags?utf8=%E2%9C%93&query=urn%3A&model_type=PublicBody&commit=Search+tags](https://www.whatdotheyknow.com/admin/tags?utf8=%E2%9C%93&query=urn%3A&model_type=PublicBody&commit=Search+tags): 
\>5 characters of text on requests and messages (but not annotations) which are reduced prominence, perhaps excluding back-paged requests.
This ensures that requesters still have access to at least know the existence of their request. Individual messages can still be hidden from the requester as needed.
On [WDTK batch 1031](https://www.whatdotheyknow.com/info_request_batch/1031), the first two requests as currently listed ([`finances_92`](https://www.whatdotheyknow.com/request/finances_92) and [`finances_198`](https://www.whatdotheyknow.com/request/finances_198)) currently only display the title and status, not the user, date or authority.  [batcherror.zip](https://github.com/mysociety/alaveteli/files/9275732/batcherror.zip)
See the history of https://www.whatdotheyknow.com/admin/bodies/1001 An invalid URL (`banana`) for disclosure log was accepted, and led to `https://www.whatdotheyknow.com/body/banana`. I perhaps should not have tested it on a live, body, but...
> * Should the link be the normal link to the request, or a better, less intimidating, link? I think a less intimidating link would be better. The ideal, for...
It has been noted (on WDTK Slack) that the fact (according to @RichardTaylor) that redactions also apply to attachment filenames is: - non-obvious and perhaps unexpected, and - not documented...
On on-site help pages, and explicitly stating so in the footer of emails from requests concerned.
Focus on the search box, such that one can start typing and hit enter, on loading (or a subsidiary page): - `/admin/bodies` - `/admin/requests` - `/admin/tags` - `/admin/comments` - `/admin/users`...