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

Rename of folder via Resources not reflected in WebDAV

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0, 2.3.1, 2.3.2, 2.4.0, 2.4.1
    • Fix Version/s: None
    • Component/s: WebDAV
    • Labels:
      None
    • Environment:
      WinXPSP2

      Description

      Rename of folder via Resources not reflected in WebDAV. For instance if I created "Folder1" and "Folder2" and accesses my files via WebDAV, all shows up alright. If at somepoint I go in and rename "Folder2" to "Folder2 Revised" via the resources tools, the next time I access my resources via WebDAV, the folder is still named "Folder2"

      Refreshing does not resolve this, nor does rebooting and reconnecting. If a rename is performed via WebDAV, it does refelct with the resourses tool.

      This occurs on stable (2.0.0.rc3)
      Site 5cbf2a40-2f4e-4048-006b-492aa7b9f2eb

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              knoop Peter A. Knoop added a comment -

              Continued confusion between title and "ID".

              Show
              knoop Peter A. Knoop added a comment - Continued confusion between title and "ID".
              Hide
              smarquard Stephen Marquard added a comment -
              Show
              smarquard Stephen Marquard added a comment - Same issue as described in http://bugs.sakaiproject.org/jira/browse/SAK-222
              Hide
              csev Charles Severance added a comment -

              This is "broken as designed". The rename is only the display information in the resources tool. In a future version of Sakai (likely beyond 2.1) there will be a real rename operation.

              Show
              csev Charles Severance added a comment - This is "broken as designed". The rename is only the display information in the resources tool. In a future version of Sakai (likely beyond 2.1) there will be a real rename operation.
              Hide
              josh.baron Joshua Baron added a comment -

              Just want to quickly note that I've found the reverse to be true as well...

              If you rename a folder in the Resource tool that has been placed there via WebDav the name does not change and the original title remains (it also remains the same in WebDav).

              We're running 2.1.1.

              Josh

              Show
              josh.baron Joshua Baron added a comment - Just want to quickly note that I've found the reverse to be true as well... If you rename a folder in the Resource tool that has been placed there via WebDav the name does not change and the original title remains (it also remains the same in WebDav). We're running 2.1.1. Josh
              Hide
              knoop Peter A. Knoop added a comment -

              Will this be resolved for 2.3.0?

              Show
              knoop Peter A. Knoop added a comment - Will this be resolved for 2.3.0?
              Hide
              josh.baron Joshua Baron added a comment -

              Just checking in on this issue again to see what the status is at this point for a fix.

              The problem is becoming more significant as we move deeper into full implementation. As much as we warn instructors about the issue they still use it and then get very upset when they cannot make folder/file name changes. They often had to remove and then reload all of their resources.

              If possible, if this issue cannot be addressed (may it already has been?) then it might be best to at least change the information on the tool to alert user to the problem or remove the link to it from the Resources area.

              Just some thoughts.

              Josh

              Show
              josh.baron Joshua Baron added a comment - Just checking in on this issue again to see what the status is at this point for a fix. The problem is becoming more significant as we move deeper into full implementation. As much as we warn instructors about the issue they still use it and then get very upset when they cannot make folder/file name changes. They often had to remove and then reload all of their resources. If possible, if this issue cannot be addressed (may it already has been?) then it might be best to at least change the information on the tool to alert user to the problem or remove the link to it from the Resources area. Just some thoughts. Josh
              Hide
              breezley Marc Brierley added a comment -

              Seems like this issue should be a bit more important. The issue is whether the design of a split between resource name and file name is usable and should be evaluated by real users. Support staff are find problems with this issue; constantly having to educate users about this.

              Show
              breezley Marc Brierley added a comment - Seems like this issue should be a bit more important. The issue is whether the design of a split between resource name and file name is usable and should be evaluated by real users. Support staff are find problems with this issue; constantly having to educate users about this.
              Hide
              hmtruscott Harriet Truscott added a comment -

              Have assigned this to me to look at for Resources 2.5

              Show
              hmtruscott Harriet Truscott added a comment - Have assigned this to me to look at for Resources 2.5
              Hide
              knoop Peter A. Knoop added a comment -

              [Bulk Change] This issue is currently Unresolved, however, it has a Fix Version set. In keeping with the newly added Target Version, Fix Versions should only be set for Resolved Issues, and only after it has been merged to that version specifically. The Fix Version is being reset to Unknown for this issue. Please use the Target Version to indicate when you plan to address this issue.

              Show
              knoop Peter A. Knoop added a comment - [Bulk Change] This issue is currently Unresolved, however, it has a Fix Version set. In keeping with the newly added Target Version, Fix Versions should only be set for Resolved Issues, and only after it has been merged to that version specifically. The Fix Version is being reset to Unknown for this issue. Please use the Target Version to indicate when you plan to address this issue.
              Hide
              hmtruscott Harriet Truscott added a comment -

              Assigning this to you for a technical answer, Jim.

              Is it possible to really rename a file? If so, do people envisage the URL staying the same or changing?

              Show
              hmtruscott Harriet Truscott added a comment - Assigning this to you for a technical answer, Jim. Is it possible to really rename a file? If so, do people envisage the URL staying the same or changing?
              Hide
              branden Branden Visser added a comment -

              Linking this to SAK-13822 as both these issues will probably need to be considered together

              Show
              branden Branden Visser added a comment - Linking this to SAK-13822 as both these issues will probably need to be considered together
              Hide
              dhorwitz David Horwitz added a comment -

              MAINTANCE TEAM: Unassigned so these get reviewed by the Maintance Team

              Show
              dhorwitz David Horwitz added a comment - MAINTANCE TEAM: Unassigned so these get reviewed by the Maintance Team
              Hide
              steve.swinsburg Steve Swinsburg added a comment -

              Adding the comment that I made on the maintenance team list:

              Whilst I think its a good idea to keep the title and ID in sync (if the title must be initially used as the ID), the issue arises when there are links to that file. If the ID and hence URL change, links will break. Perhaps the ID could be a UUID instead then the links will be preserved and the title of that file can change as required.

              For the WebDAV v Resources renaming problem, both should operate on the same value, and IMO that should be title. Using a UUID as the id in the background would complement this nicely.

              Show
              steve.swinsburg Steve Swinsburg added a comment - Adding the comment that I made on the maintenance team list: Whilst I think its a good idea to keep the title and ID in sync (if the title must be initially used as the ID), the issue arises when there are links to that file. If the ID and hence URL change, links will break. Perhaps the ID could be a UUID instead then the links will be preserved and the title of that file can change as required. For the WebDAV v Resources renaming problem, both should operate on the same value, and IMO that should be title. Using a UUID as the id in the background would complement this nicely.
              Hide
              seththeriault Seth Theriault added a comment -

              My own reply comment from the same list:

              Perhaps the link really needs to be one of those "short urls" that we have talked about so much.

              Show
              seththeriault Seth Theriault added a comment - My own reply comment from the same list: Perhaps the link really needs to be one of those "short urls" that we have talked about so much.
              Hide
              aaronz Aaron Zeckoski added a comment -

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

              Show
              aaronz 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:
                  mmmay Megan May
                • Votes:
                  3 Vote for this issue
                  Watchers:
                  17 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code