You are here

Collaborative LaTeX System - Remedial Work

Project ID: 
206
Current stage: 
Manager: 
Unit: 
What: 

Description: The Collaborative LaTeX system has been running for a number of years using prototype code. Although this is still working there have been an increasing number of bugs, particularly associated with the move to F13, causing user frustration. The original repository framework was designed for a small number of users but now there are many more repositories and it has become very slow and could do with being changed to accommodate this. An earlier project did some redesign work on the Coltex client command but was ultimately de-prioritised and stalled and this work was left unfinished. Backup is still only a daily mirror and with the large number of users and amount of data held there could now be quite a lot of lost effort were the disks to fail.

Deliverables: A completed production client with bug fixes. Changes made in client code and backend code for a re-structured repository model. An svnsync backup mechanism to complement the existing mirroring.

Fix and/or resolution to RT #s
46005,
37181,
48853,
48907,
51299,
51858,
51931,
52024,
52178,
52256,
52319,
52375,
52375,
52624,
52684,
52953,
53763,
54779,
56091,
54778

Why: 

Customer: All School Staff, but primarily Academic/Research.

Case statement: Day to day operational maintenance load for Coltex had been effectively non-existent up until the last year or so where it has started to ramp up significantly (more tickets in the last six months than the last few years put together). This is a sign that the prototype code is starting to creak. The admin commands have become very slow and unwieldy, particularly in initial use, due to the large number of repositories now being managed. Substantially more critical data is now held in the system and the use of an svnsync (near real time) like backup is increasingly necessary.

When: 

Status:

Timescales: Although the existing system has been patched up to work it is costing increasing effort to maintain the code base now. The risk of disk failure is ever present.

Priority: Medium -> High

Time: 4 FTE Weeks

How: 

Proposal:

Resources:

Plan:

Other: 

Dependencies: None of note.

Risks:

Milestones

Proposed date Achieved date Name Description