Re: [Bodington-developers] Quotas Implementation

[Matthew B. <mat...@ou...>]

Selwyn Lloyd wrote:
> I also agree that disk pace is cheap, perhaps the unnamed project who 
> put forward the student leaves and must take stuff with them usecase was 
> thinking of the cost of managing users, support etc...
> 
> the main issue I was putting up for discussion was based on this.... 
> letting the student know their quota expires....
> 
> get / set quota expiry

Presumably the quota expiry time is tied to the time when a user leaves 
the institution? Eg:

User leaves - day 0
Access card gets stopped - day 0
Email gets stopped + 1 month
Users website removed + 1 month
Email gets deleted + 3 months
Backups get deleted + 6months

Isn't removing the quota for a PDP/VLE system part of this process and 
should be tied to the leaving date? While I can see that it would be 
helpful to tell a user when their quota will expire I don't really see 
it as data that the system should look after as it is tied to the 
process of leaving.

For implementation reasons it may be useful to store this though.

> in the agreeable world of cheap disk space perhaps you can consider its 
> the other human services which expire when you leave the Ed Ins... such 
> as support contract expired, file recovery service expired etc... 
> perhaps a business op for HEi's??

I think universities miss an opportunity of giving all graduates a email 
address (forwarding only), now good email services are a everywhere but 
5 years ago it might have worked and could have been good advertising 
for the university and maybe a reminder to donate back to the university?

-- 
  -- Matthew Buckett, VLE Developer
  -- Learning Technologies Group, Oxford University Computing Services
  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/