Old to-do list from projects preceding COOL - partially cleaned up

(Comments added by Caoimhín Ó Donnaíle are written in green like this)

Things to do

Bigger and more technical things to do

Requests from Kent 2012-2013

Suggestions and priorities from TOOLS team discussion in Gothenburg, 2012-08

The evaluation form for training workshops should be available as an online form, and the results should be stored online.

We need to use language names, not just codes, in the forms for authoring and filtering Clilstore units.
 The kind of square box used for language selection in Google Translate would be great (especially with the memory of recently used languages). (But it requires more programming (perhaps in Javascript) than the current system.)
 Native names for languages are fine, but it would be good if the list also included a Latin script translation in alphabetic order, as well as the current local script (Arabic, Greek Cyrillic or whatever) version as at present.
 This should continue to be possible to compose and store units with any valid language code. i.e. It should not be restricted to languages for which Multidict currently has dictionaries.

In the form for authoring a new unit, where it currently says "Embed code", this should be changed to a dropdown with "Embed code" as the default, but listing other possibilities: Youtube URL; Flickr URL; TED URL, Ipadio URL, etc. The program would then attempt to make sense of these URLs, extract the relevant information, and turn this into the appropriate embed code.

User management:
 E-mail address verification should be compulsory before registration is confirmed.
 If a user forgets his or her password, it should be possible to request an e-mail containing a link valid for an hour which will allow the password to be reset. (But a password hints facility is not needed.) Done
 There should be a "profile" page for each user. The user's "real name" should be visible to everyone, but the e-mail address should only be visible to Admin (except perhaps if the user themselves asks for it to be made visible).
 It would be nice to allow the user to upload a profile picture, and specify a university or college affiliation, and perhaps homepage and Facebook links.
 Registered users would have the facility to specify the additional fields to be included when the "Include optional columns" box is ticked. Some of the possible optional fields would be: number of hits; length of text in words (or characters); length of vidio; whether the unit includes exercises.

A red "Report abuse" button is required. This should be at the end of unit, and the user should be required to fill in a form with a capcha, giving details of the problem. This would e-mail Kent and Caoimhín (Skye) directly. Done

It would be nice to possibly add a new bar at the top of the page where the links to "Clilstore", "Unit info", "Email the author" would reside, leaving room for possibly more author-generated link buttons on the existing bar. However, this might move the video and scrolling text area too far down the screen, especially if the user was on a device with a small screen.

The possibility of automatically resizing the video to suit the screen width should be investigated.

It is important to get Google Translate working again with Multidict Done. (And efforts should continue to improve the repertoire of dictionaries in general.)

Wysiwyg editing of the text should be implemented, if reasonably possible. Done

A student interface, beginning with Kent's suggested design, should be implemented and discussed and improved as a separate page at first, with the idea of possibly making it the Clilstore "top" page.

There should be a facility for authors to create menu page of Clilstore units on a particular topic or for a particular class. These would be simple, with just a title, summary, author, and list of units which the author would specify by inputing their numbers. The address of the menu would be something like "../menu/42".

The team could also create some fancier webpages showcasing units on particular topics, but these would be produced as separate "one-offs".

Clilstore should have an "About" page and a `"Help" page in the title bar (as Multidict and Wordlink already have). The Help page would have help for students and (a lot more) help for authors. The help for authors would include links to good sites for videos (e.g. Youtube) and especially to good sites for videos with transcripts (e.g. TED).

We decided there was no urgency and possibily no need for keywords and subject classification of units, but this should be kept under review.

We decided that an acknowledgements frame at the bottom might be an unnecessary complication, as acknowledgements could be included if need be in small print at the bottom of the text, but this should be kept under review.

2013-01-31 CPD