Browse Prior Art Database

A method of command correction by analyzing historical records Disclosure Number: IPCOM000247600D
Publication Date: 2016-Sep-19
Document File: 5 page(s) / 35K

Publishing Venue

The Prior Art Database


This disclosure provides a method which can correct user's wrong command, such command can be Linux/Unix command, SQL (Structured Query Language) clause, LDAP (Lightweight Directory Access Protocol) statement etc. The core idear is anylazing history record from either the user's personal input or his team member's input to give a more accurate command suggestion, so that the user doesn't need a strong skill foundation to handle technical support work.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 5

A method of command correction by analyzing historical records

In our daily maintainence work we need remember many Linux command and some of command have complex syntax and hard to remember. Also in our team someone may have rich experience and may work a long time in this team so have executed many command on his/her daily work. When new employee coming there are many daily used command need to transfer, not only the command syntax but also the parameter. For example the file name in file system, the directory path we often put files to, the table name/column name we lookup in database, etc.

We want a solution that when user type wrong command syntax the user can be prompt with correct syntax of automatically correct and executed. Also team member can share their command so when new employee type wrong command a tool can automatically search in shared database the find some command successfully executed by user or other team member.

The solution may help user in two dimension. The first one is syntax correction. For example user may combine 'find' and 'ls' command to firstly find file with special command and use 'ls' command to list file details, but user may provide wrong syntax when combine these 2 command. In this case this solution see the 'find' and'ls' command and guess user want to 'find' a file and then 'ls' it so automatically run the correct command. Another example is command like 'tar' which the option order may be important, like -f must just before the file name and user may put it at first option so the soution may just automatically correct the order from 'tar -fzv' to 'tar -zvf'.

The second case is user may know the correct syntax but don't know the parameter, for example file name, directory path, table/column name. For example we often copy same file to some folder when there is a fix and new jar file is released. We may forget the directory path since usually it's very deep. In this case user can lookup the history command database and see if there is similar command that copy same file. Or user may just type 'cp' and file name but miss target folder and the solution will prompt user with similar that have been executed (may by other team member). This also apply to other work for example we want to list some table/column in DB but forget the name.

The wrong syntax's suggestion(s) are rendered from two perspectives, namely, the users' histories and the total possibilities of correct syntax. And these two aspects can be evaluated and adopted one of them to be the main dependence, for instance, if a user entered a command which never appears in the history record, then the history aspect can be belittled when generating the suggestion(s). but on the other hand , if the user entered a command has very little information that to provide any suggestions (such as a command with wrong spelling and no parameters), but it's similar or the same as a command used in the history, then


Page 02 of 5

the previous comman...