|
|
|
|
Milestone report for 11-07-2007.
1. Name
|
| | Sohum Misra |
| | | 1 (8%) | |
|
|
| | Hubert Lee |
| | | 1 (8%) | |
|
|
| | Derek Sessions |
| | | 1 (8%) | |
|
|
| | Matt Freeburg |
| | | 1 (8%) | |
|
|
| | Yuan Gao |
| | | 1 (8%) | |
|
|
| | Felipe Serrano |
| | | 1 (8%) | |
|
|
| | Jeeyun Lim |
| | | 1 (8%) | |
|
|
| | Kevin Le |
| | | 1 (8%) | |
|
|
| | Corey Shaw |
| | | 1 (8%) | |
|
|
| | Rae Alty |
| | | 1 (8%) | |
|
|
| | Brad Dodson |
| | | 1 (8%) | |
|
|
| | Aaron Cottle |
| | | 1 (8%) | |
|
|
| | Dave Eng |
| | | 1 (8%) | |
|
|
Total: 13 |
2. Percentage complete
|
| | 85% |
| | | 4 (31%) | |
|
|
| | 90% |
| | | 4 (31%) | |
|
|
| | 100% |
| | | 2 (15%) | |
|
|
| | 95% |
| | | 3 (23%) | |
|
|
Total: 13 |
3. What milestone objectives were actually attained? Be specific!
|
| | My milestones can be found here.
- The page design has been pretty much finalized and been applied to all pages on the site. We met a lot with Luke and his wife to discuss the logo and design and seem to have come up with something that everyone likes and will work.
- Worked more on the user profile page. It now shows the content in a thumbnail-ed list. Also added AJAX tabs so that users can edit their profiles.
- Deliverables
- Homepage shows featured content. It is more a proof of concept than anything, though, because there is no way to just pull out random content.
- Content page theoretically can show comments however this has not been implemented in backend properly so it cannot be functionally tested. Loading a static list worked, though.
- Edit tab for content was put in, but authoring team is still working on implementing it.
- Search results are now thumbnail based in a grid format rather than a table.
|
| | | 1 (8%) | |
|
|
| | Milestone can be found here.
- I completed the implementation of the IAccessControlAuthorization interface. This involved introducing a number of permissions-related methods to IBackendObject and retrieving data from the database.
- Created a permissions table in the database from which to draw permissions
- I've been working with Dave on the relations team to get support for retrieving the parents and ancestor groups of users and content. This has been a bit difficult, since support for content groups doesn't currently exist. I've drafted a document on our proposed solution here.
|
| | | 1 (8%) | |
|
|
| | Milestone for the week is here.
Right now the code for the Search part of this should mostly be complete. However, there are 4 dependences: UI team, Relationship Team, Backend team. At this point, all should be working except the UI team (which I just need to talk to them about how they want to integrate it and send the information.) The sorting is pushed along in the Search tree, attached to parsed variables in the Relationship team and put into SQL there, and passed to the back-end. Basic functionality that is being included in this version is sort by GlobalRank, Author, Creation Date, and Name (for content) and Name (for Author). We will be adding more and more functionality in future weeks. |
| | | 1 (8%) | |
|
|
| | Milestones are listed here.
To accomplish these objectives, I:
- purged the database on friday night
- removed all old, deprecated/unused tables from the database
- fixed several bugs reported by other teams here
- added property dictionary support to Tag, to allow for spatial image tags for authoring team
- added property dictionary support to Entity, to allow for profile page "blurbs" for authoring team
- added property dictionary support to Content for future extensions
- created database tables for the above dictionary item storage
- added RemoveTag function to IBackend for authoring team
- created and implemented RemoveRelations and RemoveFromTable functions for internal backend use, in order to implement the above RemoveTag function |
| | | 1 (8%) | |
|
|
| | Milestones can be found here
1. I've implement Text content editing function.
If the content does not exist, or the user does not have the authority to edit the content, a new content will be created.
2. I've implement Profile description editing function
3. I've created a class to clean html/text.
All the tags and attributes will be checked.
4. I've check the html to ensure it's well-formed.
I use stack to implement this. If an end tag is encountered, a start tag will be popped from the stack. If there's no match start tag, the end tag will be removed. If there's no enough end tags, they will be added to the content.
5. I've put Text editor and profile description editor to its own controls |
| | | 1 (8%) | |
|
|
| | Milestones located here.
In addition to "completing" the milestones, I also cleaned up a lot of the content display format and how tagging works.
Tagging of a recently uploaded content is no longer automatic, but instead the content is first displayed with the option to click on the tag tab and tag the content.
Tags can be added and deleted from any type of content, including image tags from images. |
| | | 1 (8%) | |
|
|
| | My milestone can be found here .
In advanced search, earching for contents now works for:
- search by name
- search by tag
- search by creation date (created after a certain date)
- search by creation date (created before a certain date)
- combination of the above
In simple search (search box on the top right corner), it searches for any match in either content name or tag as expected
Search UI was re-written so that the search tree is created largely by the search module and not the web app as was last week. |
| | | 1 (8%) | |
|
|
| | This week's milestones.
- Talked with the Backend and Corey on how sorting priorities and types are stored as OrderedPairs in the backend for subjects, objects, and predicates.
- Talked with the Search Team (and Corey) on how sorting is represented in the Abstract Search Trees so that we could decide how the AbstractTreeParser would handle them.
- Implemented loops in the Node visitors for Content and Entities (tags are not yet supported by the Search Team) that translate the sort priorities into sparql queries.
|
| | | 1 (8%) | |
|
|
| | Assigned milestones: Tasks, under Relationships Group
Additional work that was done by request of other teams or due to bugs: Trac
- We have a testing suite for testing basic functionality of the relationships model
- We can handle sorting parameters specified in the search tree, and the results are sorted as such
- Search trees now support OR nodes
- A start of the Implicit Trust calculator is up, but somehow we should try and integrate this into the relationships
- Everything should be ready to go in terms of getting relationship info and modifying it, such as tags, comments, ratings, and trust
- We were asked by Hubert to work with the backend for implementation of groups (to go with the access control system). This should be functional now. |
| | | 1 (8%) | |
|
|
| | P1: I connected the string parser, but it was hard to tell if it worked because of the lack of substring matching by the backend.
P2: I added what Jeeyun asked of me, and it has been mostly debugged.
P3: I've organized several 'meetings'/'coding sessions' to try and get things working. It seems like search is pretty much working, minus a few bugs we're continuing to fix. |
| | | 1 (8%) | |
|
|
| | I don't believe matt got around to posting my milestones for this week (I should have done it though, and I apologize for that).
My goals for the week were:
- Meet our deliverables goals for tomorrow's deadline.
- Consult and work through the access control, notifications and messaging specifications.
- Collaborate with Hubert to implement the access control system.
- Begin implementation of the notifications system, particularly to verify that key technical components of the system will work.
- Shift our atmosphere to focus on big-picture quality, so that we take ownership of making sure our results are usable.
Of these I believe that I've completed most of each of them (with the percentage complete above based on an uneven weighting of the priorities of these points). Here's a description of what has been completed:
- While it's about 18 hours to early to say if we will truly meet our deliverables goal, I'm extremely confident we can do it. Last night the site was operational with but minor issues, and I believe we'll have a useable functional site up tomorrow. In fact, it will have a few features I didn't expect, including background search indexing and image tagging.
- Hubert, Dave and I (and less so myself actually lately) have been working through the issues in the access control, and Hubert has made some strides towards implementing it. I believe it will be operational within a week or so. The notifications system design document is nearly complete, but still needs review (and I still have to find someone to own this system). The messaging specification is little more than a powerpoint explaining at a high-level how the system will work, although that's actually probably enough for someone to implement it, but the feature has basically been pushed back to later deliverables, so it's a little off the radar.
- Hubert has taken over the access control work fairly well. It's not moving as quickly as I'd hoped (I'd actually hoped it might be working tomorrow as recently as about 4 days ago). It's good to see him take ownership of it.
- I've been working through a prototype/skeleton of the notifications system, which is actually becoming fairly complete. There are still a lot of unhandled cases and work to be done in crafting all of the scenarios, but I've been working through the worrisome technical issues. The only one left is to ensure that I can connect to an SMTP relay, which I hope to get completed tonight. Other than that, the double-visitor system and SQL based queue seem to be working, although I encountered some hiccups in object serialization (XML serialization can't serialize interfaces so I had to switch to using a BinaryFormatter).
- I've done a lot on this front. I think a lot of this has happened because of trac coming online, but essentially I've been assigning bugs for things that don't work. In general I can sense a real shift in the individual responsibility toward tracking down and fixing bugs that affect usability. In addition, Sohum has really ramped it up in streamlining the user interaction with the site.
|
| | | 1 (8%) | |
|
|
| | My milestones are in the same place as always. To summarize, this week I
- Create unit tests for the sparql translator
- Create a master Guid table containing the type information for each guid
- Add ordering to searches
- Add substring matching to searches |
| | | 1 (8%) | |
|
|
| | The actual list of milestones is as follows:
- Construct a testing platform to perform tests on the relationship model - ensure the code we have is not broken in a more formal manner.link
- Expand and complete the Abstract Search Tree Parserlink
- Commenting, rating, and comment ratings must work.link
- "Make sure everything's good to go with search from your end. We need abstract searches to work completely."link
The first two items are from the last milestone which have been moved over to this milestone. The other milestone from the 10/30/07 period is deprecated.
3, and 4 are completed as best as we can get it by the following:
I am working on creating the test platform to verify that the relationship model is working as intended. Beyond this, Corey went ahead and finished off the AbstractSearchTree parser earlier this week.
My own personal milestones are as follows:
- Create testing framework for Relationship modellink
- Concrete implementations of the interfaces IGroupInfo, IObjectInheritanceInfolink
I am currently in the midst of finishing off the first one. The testing framework is complete - what's missing are the tests. A large portion of the work is unusable for now by way of there being no deletion methods for objects in the backend. A ticket was created for this. What is being done instead is having the dummy objects get created once and only once - they will be deleted in the morning but we will at least verify that everything is working properly right now. A more robust platform will exist once the delete methods are incorporated into the backend.
The second one is described in detail below. |
| | | 1 (8%) | |
|
|
Total: 13 |
4. What milestone items were left uncompleted? Be specific!
|
| | - The profile page still is not complete in that the trust network isn't as intuitive as we'd like it to be. I'm working on this and hopefully cook up something better for release.
- Deliverables
- Content page needs to show more info. This is a simple augmentation which I have just overlooked and will probably fix in an hour sometime. Things like ratings or related content need more support from other teams.
- Search results currently have no pagination because I didn't really get too many results. I just realized I could have solved this by creating dummy results. Pagination will be in later this week.
|
| | | 1 (8%) | |
|
|
| | Many of the methods I implemented have not been tested yet, since my test cases are dependent on the database, which was purged twice recently. Now that the database has data again, I need to rewrite my test cases and then begin integration of permissions into the system. Brad has offered to help me with this. I'd recommend that you set up some way to automate repopulating the databases after purging so your test cases aren't broken. Also, kudos for having test cases. --Chelsea |
| | | 1 (8%) | |
|
|
| | Testing [coming soon(TM)] and integration with the front end. Otherwise things should be looking good. What exactly does integration with the front end entail--do interfaces need to be designed or simply implemented? A little more detail on integration issues would make this clearer. --Chelsea |
| | | 1 (8%) | |
|
|
| | There is nothing outstanding, unless there are more bugs yet to be reported. A couple bug fixes are awaiting verification from the reporters, but I have already tested the fixes from my end. |
| | | 1 (8%) | |
|
|
| | Felipe reported there's a bug in image plugin of WYSIWYG editor, but everything works fine on my machine. |
| | | 1 (8%) | |
|
|
| | Video tags...again. I just have so many little things to do, or so many things to fix up that I haven't had the time to sit down and think about it.
Profile editing is still dependent on the backend fixing a bug. We'll see if it gets done by tomorrow. |
| | | 1 (8%) | |
|
|
| | It doesn't properly work for searching within trust network. How does it break? --Chelsea |
| | | 1 (8%) | |
|
|
| |
- Priority and and Tag sorting is currently unsupported by the Search team, so the system is currently assigning priority by the order it appears in the node list and tags are unsorted.
- Corey and I are in agreement that the abstract search tree parser should be revamped to streamline the code, as it is currently contains redundant code.
|
| | | 1 (8%) | |
|
|
| | - Some of the sorting and groups code needs to be redesigned, we'll look into this next week. At least for now it's functional.
- The authority system was pushed back, because Categories were not a high priority. Hopefully we can get these by next week.
- NOT nodes are not supported in search trees... we'll have to figure out how to do this.
- We can always add more tests. We don't have 100% coverage yet, but it's something to aim towards. |
| | | 1 (8%) | |
|
|
| | P1: As substring matching was not checked in until 11, haven't had the chance to make sure it all works.
P2: The only parameter not fully debugged is WithinTrustNework, but I think I fixed it. |
| | | 1 (8%) | |
|
|
| | There are a few caveats:
- Luke had wanted a payment system for the demo. I think we were rather ambivalent about it, but I don't see any chance of it getting in the project (Hubert simply hasn't finished the necessary access control stuff which it's dependent on). This MUST happen this week.
- The messaging system design document needs to be expanded. Also I should update the access control design document to reflect the changes in design made by Dave and Hubert.
- I need to work to ramp up our progress rate on this. It is not good that the access control isn't functional even in minimal form yet.
- Notifiations should be handed off very soon to someone who can own it.
- Actually I don't think there are caveats to this one, except that in the mix, I think we may have lost some off the concretenes of "milestones", etc. I agree that you have shifted to big-picture; I also think milestones have slid a bit more out of control than you're letting on here. --Chelsea
|
| | | 1 (8%) | |
|
|
| | I did not
- Prepare our production server for the big show
- Convert our code to use stored procedures
The server is almost ready, and will be done before the meeting tomorrow. Stored procedures are an way to optimize our system to make it faster. To meet Thursday's deadline, we were more concerned about getting a functional system than a fast one.
|
| | | 1 (8%) | |
|
|
| | The big thing assigned to me that's incomplete still is the implementation of IGroup, IContentInheritance, etc. The problem that's arisen is that the design we currently have is not suitable to have an extensible grouping system. If we wish to have groups of people, groups of content, and groups of groups then there is no clean way to do this without a lot of rewritten code. Currently I am in the process of communicating with Hubert, Aaron, and Matt to come up with a better design and have it implemented. Primitive designs have been made and discussed, but nothing final has come of it as of yet. Since this is a low priority task, it has been moved to the next milestone, but should be completed fairly early on. |
| | | 1 (8%) | |
|
|
Total: 13 |
5. Additional Comments
|
| | Thanks for cleaning up your posted milestones! --Chelsea |
| | | 1 (17%) | |
|
|
| | Thanks for fixing your posted milestones. |
| | | 1 (17%) | |
|
|
| | Good report, and congrats on the 100% completion. --Chelsea |
| | | 1 (17%) | |
|
|
| | Things are looking up, at least for my team and me. I feel that my team got a lot of our own work done this week. We finished what we needed to, we fixed our bugs in a timely manner, and we're prepared for tomorrow's release. What I'm most concerned about is the fact that since we're in the middle, we're depending on a lot of stuff in the backend, and we have a lot of people depending on us. I have a scary feeling that other people were not as forward with what they needed from us, or what wasn't working, and we'll be in a bad situation tomorrow. I've done as best as I could to keep in contact with all of the team leaders and other people that are working closely with what we're doing, especially today. If everyone had finished their stuff earlier, we'd be able to have pounded on it tonight but it looks like it's going to come down to the last minute. I'll just have to rely on people getting their stuff done as soon as possible so if issues arise we will hear about it sooner than later.
Good report; very helpful. --Chelsea |
| | | 1 (17%) | |
|
|
| | Actual milestones:
P1: Connect the string parser into searching. make sure it works and properly returns results with just one of the words in the search query. found here
P2: Add new selection parameters for Jeeyun to make it easier for her, and so that she does not need to understand the tree as much to search. That is, decouple the view and tree a bit more. found here
P3: Ensure that search is working. Communicate with Jeeyun, Corey, and Aaron to ensure this is ready for the big day! found here |
| | | 1 (17%) | |
|
|
| | I'd rather turn this in about an hour from now after the server is up, but alas, it's due at midnight.
I'm a bit confused as to how your percentage relates to your listed milestones. All that's posted is the server bit, but you haven't mentioned doing any of it. There is no detail on that point; I can't tell if you've made any progress on it or not (it looks like not, but your comment above indicates otherwise). If you have other tasks, please post them with your milestones so we can give you credit for them and accurately grade your percentage completed. --Chelsea |
| | | 1 (17%) | |
|
|
Total: 6 |
|
|
|
|
|
|