Re: [Bodington-developers] Quotas Implementation

[Selwyn L. <sel...@ph...>]

Matthew Buckett wrote:

> 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


in the varied *system *architectures we are adapting to, there are 
usecases for portable data and or a holding repository for a lifelong 
learners 'stuff'...

in SHELL we [shell team] developed the suzy story of a Lifelong Learner 
who goes from school 2 college 2 HE and back 2 college... different 
locals etc....
 a regional learner record was developed to collect data such as 
registrations and results....

in the last year with LMX, EELLS, PDP4Life and now the iceBox we 
[collective] added pdp, eportfolio, cv, blog, file repository... there 
are no clear views on content quota or expiry of the various tool based 
service[s] hence *varied* system architectures [bear in mind all these 
projects link multiple institutions each ED I with its own business 
processes]

now we are faced with either regional repository pilots, portable 
personal repositories or hybrids [perhaps still with a disaster recovery 
service] i have put out a call in a different email... for the biometric 
portable lifelong piece...

in practical terms with or without biometric credentials a pack up your 
bodington stuff would be interesting to us as we would be..
a) looking for ways to allow a lifelong learner to continue to use their 
artifacts and data
b) looking for ways to provide data for input into bodington systems...
c) doing similar loading and unloading work with other projects in the 
next month or two...

>
> 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.
>
even in the portable personal repository scenario you would want either 
an independent disaster recovery service or to be able to go back to 
your original service provider...

>> 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?
>
yahoo accounts seem to go through a period of redundancy, then content 
deletion and then limbo. an interesting model where you can always keep 
your email identity i've done this a few times over the years :)