If you have a means to select individual objects with something like your Select column, then you do not need separate command buttons like your Actions column, and vice versa. Choose one or another approach. The action-selection-object approach is preferable when the space is reduced and / or has many commands. Have a single sidebar menu (web application) or drop-down / pop-up (mobile) menu that displays each command once. The user selects one or more objects and then selects the actions that will be executed on the selected objects. Each command only appears once, so you can use longer text labels, which are generally easier to understand than the icons. You may want to consider abbreviated commands with especially long labels. Use the information on tools to provide the full name of the command for users who are still learning the application.
Drop-down menus in particular can be relatively laborious to use, so you can also have context menus (right-click). However, contextual menus are generally considered backup access experts, since they have little detection capability, especially in a web application, where users can assume that clicking with the right button only displays the contextual menu of the browser. Therefore, they should be used in addition to a pull-down menu / sidebar.
You can also provide expert shortcuts using acceleration keys and gestures, including double-clicking and drag-and-drop. Unfortunately, there are no standard gestures for CRUD functions for mobile devices; We need them. For a web application, the Insert and Delete keys are obvious options as accelerators for the Create and Delete functions. Obtaining details (ie, Properties or Details) can be achieved by double-clicking on the object or by clicking on the identifier of the object represented as a link. The latter is easier and more visible, but it makes it problematic to admit the edition instead of the identifier.
Yes, the ideal is to use the edition in place to support the update function. Use the appropriate control to support the editing of each field wherever it appears. This not only eliminates the Edit command, it simplifies the menu, it also keeps the focus on the main content and eliminates the navigation steps and even the entire pages, thus simplifying the entire application. A Save command can save all changes (including Deleted and Created), or, better yet, can save automatically, delete another command and prevent data loss.
The recovery function is usually best handled through a separate query dialog, although that may divert the user's attention away from the main content. To minimize that, keep the simple and simple query basic dialog box, admitting only the three to five main types of queries that probably represent 80% of all queries made, then provide an Advance or More button to get a further dialogue detailed. for general ad hoc consultations. It may also make sense for controls for a basic type of query (for example, by object identifier) to be shown full-time at the top of the main content page (for example, as "search").