Wireframes developed by Marion 11/07/06 for discussion with PIs
1. Phoebe home page
Displays introductory information plus thumbnails of the three ways in which users can access Phoebe's material: as a mind map, hierarchical list of topics and tag cloud.
Users can browse Phoebe without logging in; however, they will have to create an account and log in if they want to write a set of notes.
Clicking a thumbnail (or one of the links at the top of this or any other screen) enlarges that access route...
2. Forms of access to material in Phoebe
Clicking a node/list item/tag will take the user to the guidance, case studies etc. relating to that item (see 3.).
a) Mind map
Nodes in the mind map can be expanded and collapsed. http://phoebe.conted.ox.ac.uk/cgi-bin/trac.cgi/attachment/wiki/UploadedFiles/concept.gif?format=raw
b) Hierarchical list
Lists within in the hierarchy can be expanded and collapsed.
c) Tag cloud
Criteria for determining size of tags are TBD. Similarly themed items in Phoebe will have the same tag; also each item will have multiple tags, which will be categorised so that the same information can be access (appear?) in multiple contexts (everything will be illuminated... :-) ).
3. "Wise counsel, thoughtful replies and snappy answers"
...can be found here, in the left-hand part of the window. Links to case studies, exemplars etc. will appear in a pop-up window [Q: Accessed by a link/icon in the advice window?].
The right-hand side of the window is where the user will make their own notes, either as a commentary to personalise the material supplied by Phoebe, or to jot down ideas for the lesson plan.
- Title is by default the title of the left-hand pane but can be changed.
- Notes should be self-explanatory
- Tags allows the user to add their own tags (by default, this notes "page" will also have the tags displayed in the left-hand pane)
Note that, in order to write anything, the user must log in to Phoebe.
- Save As/Save? should be self-explanatory! Next time the user opens this set of notes, the notes they have typed previously will appear in the Notes box associated with this page of Phoebe.
- Share allows the user to make this set of notes available to others. Initially, this will allow any other Phoebe user to open and read the set of notes (provided that they have an account), but in future versions we would envisage controlling access to, say, a named list of users or to users within a particular institution only.
- Export allows the user to export the set of notes as a text file, e.g. for re-working into a complete plan within a word processor. [Q: This won't cause the notes to be deleted, will it?]
4. My Phoebe
This is the area where the user can manage their designs. Tasks that the user needs to be able to perform are:
- Open an existing design. [Q: Will this open the design and display the saved info alongside the relevant Phoebe pages?]
- View a design
[Q: Will this open the summary/snapshot view (as in file designplan.gif)?]
- Print a design
- Delete a design that is no longer wanted
[Q: Not clear what the purpose of the tag cloud is: is it just the user's tags, or all tags? And does it provide access to the resource materials?]
This is the summary/snapshot set of notes that should be displayed from the currently non-existent "View" option in My Phoebe:
Note that this screen will only display information relating to the components for which the user has made notes on one of the "node" screens. This means that if, for example, the user hasn't entered any notes relating to "post-session reflections" then nothing will appear for that component in this display.
[Q: Is this for display only, or can the user edit the plan? Can they edit it without compromising the integrity of the relationships to the individual Phoebe pages?]
[Q: TBD whether activities are listed individually or not...]
5. Sharing notes
This screen allows users to see plans/sets of notes created by other users. Initially, it will probably be notes created by all users.
[Q: How will users navigate to this screen?]
[Q: Need to rename some screen elements, e.g. "designs"; also "institution" if not supporting this level of user management in first version.]
6. Designing tags
[Q: What is the function of this screen, and how does the user navigate to it?]
A report listing user notes, grouped by any tags attatched. Probably not a high priority.