Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-13218

UI: Resource "Availability and Access" properties settings should be split into "Availability" and "Access" properties settings

    Details

    • Type: Feature Request Feature Request
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.4.0, 2.4.1, 2.4.x, trunk
    • Fix Version/s: None
    • Labels:
      None
    • Previous Issue Keys:

      Description

      Availability and access have the following different display conditions:
      #if(!$model.isDropbox() && ! $model.isSiteCollection())
      #if($availability_is_enabled && !$model.isUserSite() && !$model.isDropbox() && ! $model.isSiteCollection())

      In MyWorkspace Resources, only access is displayed.

      In other sites Resources, access is displayed and availability is only displayed if it's enabled.

      Under the title "Availability and Access", whichever way availability is set, we can have different controls available.

      If we separate Acces and Availability, we will show the access settings under an "Access" title and we will only show the "Availability" title and settings if availability is enabled and available in the current content model type (UserSite, other Site, ...).

        Gliffy Diagrams

          Activity

          Hide
          David Horwitz added a comment -

          MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly

          Show
          David Horwitz added a comment - MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly
          Hide
          Aaron Zeckoski added a comment -

          CLE team bulk inactive issues cleanup - if this is important then reopen or create a new issue

          Show
          Aaron Zeckoski added a comment - CLE team bulk inactive issues cleanup - if this is important then reopen or create a new issue

            People

            • Assignee:
              Unassigned
              Reporter:
              Jean-François Lévêque (old account)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development