[SHA-304] Quota improvements Created: 04-May-07  Updated: 17-Jul-20

Status: Open
Project: Share Application
Component/s: Repository, Share Application
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Pascal Vuylsteker (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 30
Labels: Big, Customer_Success
Σ Remaining Estimate: 0 minutes Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SHA-376 Add quota on a space Done
Related
is related to by MNT-13439 The Usage does not immediately decrea... Closed
is related to by MNT-12610 Need to have ability to view 'My User... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
SHA-375 Add quota on a user Sub-task Done Closed Issues  
SHA-376 Add quota on a space Sub-task Done Gabriele Columbro [X]  
SHA-377 Limit the size of a file that could p... Sub-task Open Mike Farman  
SHA-378 Limit the size of a file that could p... Sub-task Open Paul Holmes-Higgin [X]  
SHA-379 Limit the size of a file that could p... Sub-task Open Paul Holmes-Higgin [X]  
SHA-380 Report quota per space Sub-task Open Paul Holmes-Higgin [X]  
SHA-381 Add usages for a DM store Sub-task Open Paul Holmes-Higgin [X]  
SHA-382 Set quota on multiple/single users up... Sub-task Open  
Epic Link: Administration & Control

 Description   

It should be possible :

  • to add quota on user and/or on space
  • to limit the size of a file that could possibly be uploaded, on a server, space or user basis.


 Comments   
Comment by Nick Heylen (Inactive) [ 01-Aug-07 ]

yes, this would be a very usefull important feature.
Than it is also possible to use Alfresco for the personal documents of users.
Now we can't do this,because there's no limit on the disk quota

Comment by Nick Heylen (Inactive) [ 24-Sep-07 ]

any progress on this important feature?

Comment by Oleg Burlaca (Inactive) [ 02-Nov-07 ]

This feature will be useful when running Alfresco in ASP mode, i.e. when having multiple Alfresco projects on the same server. It is also good for administrators, they can pre-configure who and how much can store (For example, setting a quota for the total size of files per owner).

Comment by Miguel Angel Bayona (Inactive) [ 02-Nov-07 ]

This definetely a VERY interesting feature and easy to implement (check before adding content to see if a limit has been reached). Maybe, it can even be implemented as an aspect. In any case a MUST-HAVE feature.

Comment by K Madhavan Nair (Inactive) [ 04-Nov-07 ]

This really is a MUST-HAVE feature

Comment by Roeland Hofkens (Inactive) [ 14-Nov-07 ]

Very interesting feature, especially for bigger installations with thousands of users.

Comment by Jan Vonka [ 14-Nov-07 ]

Initially, we're looking to add user usage tracking (based on content ownership) and quotas to Alfresco ECM.

However, since the title of the enhancement request refers to spaces, I've added some sub-requests. Please vote/comment on these if you feel that some (or all) are as equally important as user quotas. Thanks.

Comment by Simon S (Inactive) [ 14-Nov-07 ]

Good idea Jan, here is my preference list with priorities (important, usefull, not needed)

1. usefull
2. important (this is the single most important feature we would like to see)
3. usefull
4. usefull
5. not needed
6. not needed

Comment by K Madhavan Nair (Inactive) [ 15-Nov-07 ]

I would say 1,2 and 3 are important and really useful from a server resource management point of view. The rest do not seeem to very useful.

Comment by Carry Megens (Inactive) [ 04-Dec-07 ]

For a large enterprise this is a MUST have 2 and 3,7are usefull.
Hint: provide a template to display space(s) usage.

Comment by Roeland Hofkens (Inactive) [ 04-Dec-07 ]

My preferences:

1. usefull
2. very important
3. important
4. important
5. not needed
6. usefull
7. simple usage reports.

Comment by Nick Heylen (Inactive) [ 11-Dec-07 ]

1. usefull
2. important! e.g. the homeSpace
3. usefull
4. usefull
5. not needed
6. not needed
7.usefull

Comment by Robby (Inactive) [ 25-Mar-08 ]

This would be a very usefull important feature.
1. usefull
2. important!!!
How is possible from now using the first point on 2.9.0Bdev ???

Comment by e.spindler (Inactive) [ 21-Aug-08 ]

1. usefull
2. VERY IMPORTANT !
3. usefull
4. usefull
5. not needed
6. usefull
7. usefull
8. nice to have

Comment by Fabrizio Corsaro [X] (Inactive) [ 23-Apr-09 ]

Hi guys,

Can we set a default value quota that is used for new users?
Also can we enable the quota check box for a group (as already done for single users)?

Cheers, Fab

Comment by Gabriele Columbro [X] (Inactive) [ 21-Feb-14 ]

After review with Product Management (John Iball), this issue was accepted as a valid enhancement for the product.

Given the number of subtasks and related issues we decided that the right course of action is:

  • Better specify the scope of this issue, by limiting it to adding the space quota feature in Share
  • Close ENH-1269 and ALF-16109 as duplicates of this issue
  • Treat subtask ACE-681 (mail notifications for quota) as a separate enhancement, that we'll move to MNT for further tracking
  • Treat subtask ACE-687 (group quota) as a separate enhancement, that we'll move to MNT for further tracking
  • Move this issue to ACE for backlog prioritization

I will also take care of consolidating the ACT numbers in this issue, so that we can track all the customers interested in this extension.

Comment by Gabriele Columbro [X] (Inactive) [ 21-Feb-14 ]

For complete information on the contribution implementing this see https://issues.alfresco.com/jira/browse/ALF-16109?focusedCommentId=191546&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-191546.

More information can be asked to Nathan McMinn [X] Richard Mcknight Mehdi Belmekki [X] Maurizio Pillitu [X]

Comment by Jay Sinha [X] (Inactive) [ 24-Apr-14 ]

00154619 Premier is also very interested in this (actually in per-site quota).
"Here is our business case.

1. Why do we need quotas:

  • Our storage is limited, we don't want someone to dump enormous amounts of data into the repository.
  • We don't want our system to turn into the storage of outdated content instead of being a collaborative platform.

2. Why can't we use User Quota:

  • Our system is built around collaboration inside teams. The user can be a member of many sites which represent different teams and we don't want to limit his ability to contribute to all of them.
  • We need the ability to adjust a particular site quota depending on the team's needs."
Comment by Ian Crew (Inactive) [ 24-Apr-14 ]

Re Fabrizio Corsaro's comment on 23-Apr-09 at 04:39 AM:

See http://jared.ottleys.net/alfresco/alfresco-default-quota-policy/ and https://code.google.com/p/alfresco-defaultquota-policy/ (Still works fine for us on 4.1.7.3....)

Hope that helps.

Generated at Mon Aug 10 17:15:43 BST 2020 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.