Shell Programming and Scripting

Hi All

Need a help to understand how one can automatically correct a file name using a shell script even if it is in a completely different format...

Ex : adv_OK_0215_mem_rules_firing.txt / advex_0215_OK_me_rule_fire.txt (or in any other format as above)

to : advext_OK_2015_mem_rule_firings.txt (Final Name)

You need to depict an algorithm how to convert all the possible corrupt elements into their final forms. What corrupt elements can occur?

Hi, chatwithsaurav.

A Google search for algorithm for spelling correction produces more than 0.3 million hits.

A Google search for algorithm for language translation produces 26 million hits.

A Google search for algorithm for string substitution produces about 0.6 million hits.

A Google search for algorithm for string substitution table produces about 5 million hits.

Best wishes ... cheers, drl

Hi RudiC

Many corrupt elements can occur but the script should automatically correct it to the final name. I actually need that algorithm

Regards
Saurabh

Note that I will seriously doubt your judgement if you run either of these scripts.

With the information you have provided:

Code:

for i in *_*_*_*_*_*.txt
do     mv "$i" advext_OK_2015_mem_rule_firings.txt
done

or, if the number of underscores or the .txt could also be corrupted, you could simplify this to just:

Code:

for i in *
do      [ -f "$i" ] && mv "$i" advext_OK_2015_mem_rule_firings.txt

Of course either of these might match several files and destroy all but one of them, but if you can't be any more specific about what corruption can occur, that is the best we can do for you.

Hi Don

Thanks for your solution. Well normally the user who puts the file in a predefined directory makes spellings mistakes as close to the examples which I have shared. Assuming that the "file name sequence" remains same (i.e advext_OK_0215_mem_rule_firings.txt) he/she makes mistakes like : "ad" instead of "advext" or "firng" instead of "firings" or "me/m" instead of "mem". The script will identify each "word" and correct it if its wrong. He/she can give two or more underscores and even no underscores as well.

I'd propose you run a validity check on the users' input, then, and to avoid a file rename based on guesses (at best).