Trecx:IssueLog

From Bodington Wiki

Jump to: navigation, search

Back to TReCX

Issue Log

This is a list of all major decisons within the project.

Issue Log
Author Date Description Priority (L/M/H) Impact Decision Decision date Status
adam 27/02/06 what source control Med we know CVS, SVN may present a challenge SVN on SF site 01/03/2006 closed
adam 27/02/06 where to house blog Med want a stable and accessible site use ramble server 01/03/2006 closed
adam 28/04/06 project slippage High I was off sick for 1 month and work slipped badly have to scale back 25/04/2006 open
adam 05/05/06 Query language for search interface and back end tracking store database Med We had originally planned to use the Exist database to store the list of events in the remote tracking store, we would then use Exist's built in XQuery interface to query the database. This is all well and good but this means we must also implement an XQuery to SQL interface for applications that have their own event store; this is considered to be out of scope of this project. We e need to think whether to use a database other than Exist, the obvious choice is to use an SQL database (with SQL as the query language). Design considerations must be that we dont send too much data back to the Reporting Service and that we dont put too much of a computational overhead on the reporting store. We could have two levels of query I and II - level I would not support The GROUP BY clause, in other words, would not all summative reporting (say 'how many resources did little Johnny access in March 2004'). See Design Issues  ?? ??/??/2006 open

Back to TReCX