5 deleted 2 characters in body
source | link

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/deleteall permissions except read to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2); I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

This approach is consistent with approach in large enterprises where tickets are used for IT needs. Later you can extend the tracker also for other types of requests so this can be a basis for more universal user care solution in the future.

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2); I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

This approach is consistent with approach in large enterprises where tickets are used for IT needs. Later you can extend the tracker also for other types of requests so this can be a basis for more universal user care solution in the future.

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny all permissions except read to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2); I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

This approach is consistent with approach in large enterprises where tickets are used for IT needs. Later you can extend the tracker also for other types of requests so this can be a basis for more universal user care solution in the future.

4 edited body
source | link

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2),; I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

This approach is consistent with approach in large enterprises where tickets are used for IT needs. Later you can extend the tracker also for other types of requests so this can be a basis for more universal user care solution in the future.

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2), I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2); I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

This approach is consistent with approach in large enterprises where tickets are used for IT needs. Later you can extend the tracker also for other types of requests so this can be a basis for more universal user care solution in the future.

3 edited body
source | link

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2), I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion onor renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2)) where users have to fill a request (ticket) for deletion on renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

I don't know about such a product, too. But I can give you idea for a workaround:

What can be done is to

  1. deny move/delete permissions to files in the library
  2. set up a request tracker (ticketing tool, there are many: (1), (2), I'm using self-hosted open source MantisBT) where users have to fill a request (ticket) for deletion or renaming. After admin's approval, the action can be done automatically. I mean, if request form is filled correctly, there is not a big problem to issue necessary move/delete command based on its data. If you make entering requests simple enough by removing unnecessary default form fields (severity, priority, subject, etc.), then this might be very easy to use because the entire form could have only two fields:

    Full Path of File:   [...............................]
    New File Name*:      [...............................]
       *enter new file name with or without path OR enter 'd' to delete the file
                         [Submit]  [Cancel]
    

    Tip: Users can be taught one simple trick to copy full path of desired file into the form:
    If the file is clicked with Shift+Right Click, its context menu reveals Copy as path command. Then user can instantly paste full path of the file into request form – no typing needed.

2 added 112 characters in body
source | link
1
source | link