View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001315 | Composr non-bundled addons | [Composr] core | public | 2013-07-18 14:18 | 2017-05-01 15:58 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Summary | 0001315: Resource view limits | ||||
| Description | The ability to set up limits to say how many resources they may view. Each limit would have: 1) A codename, e.g. video_restriction 2) A maximum quantity that may be viewed, e.g. 10 3) A time period within which the limit applies, e.g. 1 week (the limit would apply to a moving time window) 4) Overrides for each usergroup, to define 2/3 separately for that usergroup 5) An error message to show if the limit is hit The limit would be maintained via code inserted into the top of screen templates, e.g. {$APPLY_VIEW_LIMITS,video_restriction} This provides great flexibility on deciding exactly what screen types have exactly what shared limits. For guest limitation it would need to somehow do it via IP address, as cookies are not secure. If a member is in multiple usergroups, Composr would pick the best possible limit for that member (i.e. highest normalised view limit). | ||||
| Additional Information | See: http://compo.sr/forum/topicview/misc/deploying/limit-video-views.htm | ||||
| Tags | Type: Cross-cutting feature | ||||
| Time estimation (hours) | 7 | ||||
| Sponsorship open | |||||
|
|
The APPLY_VIEW_LIMITS symbol would be implemented via the same backend tracking that the HAS_READ/MARK_READ symbols uses. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-01 15:58 | Chris Graham | Tag Attached: Type: Cross-cutting feature |
