Fall 2007

Html Cleaner: clean up all the invalid html tags and attributes. Ensure html is well-formed.

Implement a system to add video tags.

User Interface Team

Video Tagging

Make image tagging use AJAX so that it becomes more intuitive to use.

The goal is to get rid of the "Tag" tab and allow a logged in author to tag his/her content from the content viewing page, but display none of these items to a regular user.

Fix Tagging Bugs

Make sure all XSS bugs and other kinds of bugs don't exist in tagging/image tagging.

Error management for Text Creation

Go over all your code for text editing and make sure that any errors are handled gracefully.
Make sure to comment your error-handling code.

Improve the Embed Content interface

Right now the pop-up to embed content isn't the best-looking page and it doesn't follow the current theme at all.
Talk to Sohum about using his themes/UI ideas to improve on this pop-up. He may even volunteer to improve it himself, but he'd definitely need your help.

Enable user to edit content. Save the changes to database.
Put the editor in its own control
Put the editor control in content page under Edit tab.

Finding images/content on the site without needing the GUID
Saving with AJAX to the backend
Some sort of frames around added content

Modify the User Profile page to have an area for a character-limited!! blurb.

Eventually will require backend to support extra metadata properties.

Show metadata in content views.

Create DTD of final markup specification so it can be parsed into a DOM. The DTD should be an extension of XHTML 1.0 Transitional.

Requires Backend Support

Implement Image Tag Viewing. Presumably these will show beneath the image as links (if applicable), and as mouse hovers.

Consult and implement the consensus design for groups of users and content.

Add properties dictionary support to Tag, Entity, and Content classes, and create a datastore for properties from the dictionaries.

Implement a system to model user suggestions for improvement/fixes to the application. Provide access to the front end for creating suggestions and retrieving suggestions. This system supports the "Suggestion Box" in the front end.

Overview the interfaces of the entire system, given the system architecture diagram. Identify missing or underdeveloped interfaces, and task personnel to stub code them ASAP. Obtain verified measurable progress on these taskings.
Deliverable:

• Document listing each interface, and the capabilities and information required by both sides (not method signatures, just specific English statements of functionality)
• Document showing taskings and specific deliverables expected from tasked personnel
• Annotate above document with progress reports

Ensure that the UI teams (UI and Content) have the resources necessary to complete their work.

Measurement:

Get commenting, rating, and comment ratings working.

Work out sorting of comments by usefulness, etc.

Finish a specification for algorithms traversing the relationship model for valuation.

In particular, I'd like this specification to detail how we'll be able to answer the various use case questions the customer is raising. I'm not particularly looking for specific algorithms (although you can begin working on these), but rather the abstract "hook" that enables us to use the data structures for algorithmic processing in a general way. Perhaps some sort of visitor?

Category backend objects.

Currently sorting in OR nodes creates two separately sorted lists. Merge the sorted lists into a single sorted list.
Add support in the relationship model for Categories.

Demonstrate working search sorting based on trust/authority levels.

View (Advanced search options working), Search(properly create trees), Relationship group (properly parse tree), and Backend (properly retrieve results) and all comes back through the pipeline back up to the view.

Ensure that search is working. Communicate with Jeeyun, Corey, and Aaron to ensure this is ready for the big day!

Debug odd/no words search. This includes the< href="http://www.skynet2.cs.rice.edu:8998/atelier/ticket/47"> a bug and the odd number of words bug. They are related to the balancing of automated tree creation and leaving one side null, I believe. Also need to check for no words being included in the search query-after the string parser has broken it up. (As this removes words such as "the", "a", etc.

Begin testing the design with actual users. For now your sample set can be other students (preferably non CS majors). Please conduct your tests in the fairest way possible: simply direct them to the site and let them do what they will. Don't interfere but only observe their stumbles, foibles, and questions. You may also suggest some tasks for them at the beginning, but don't help them accomplish them. This may be a little much for you, but ideally you could video tape them or screen capture their sessions, so we can have a record. As a less invasive method just watch and take notes.

Create a preferences section for users.

In particular, we will soon need an interface to specify preferences about which notifications to recieve.

Investigate adding more information to search results, like the author, date, area of text that matches, and trust relationship.

 

Also investigate showing search results for users.

 

Implement your decisions.

UI Group

Meet with Sohum and go over Silverlight XAML and JavaScript. Discuss the site design and how it can apply to the video player. Work out who, and when, will implement a more "integrated" UI on the video player.

Add dynamic video tags to the new video player.
Create the browse page, allowing users to browse through content .

Implement the UI perspective of customer deliverables.