{"id":52423,"date":"2009-09-21T03:01:00","date_gmt":"2009-09-21T03:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2009\/09\/21\/hey-scripting-guy-how-can-i-clean-up-file-names\/"},"modified":"2009-09-21T03:01:00","modified_gmt":"2009-09-21T03:01:00","slug":"hey-scripting-guy-how-can-i-clean-up-file-names","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/hey-scripting-guy-how-can-i-clean-up-file-names\/","title":{"rendered":"Hey, Scripting Guy! How Can I Clean Up File Names?"},"content":{"rendered":"

<\/p>\n\n\n\n
Share this post: <\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/span> <\/p>\n

\"Hey,<\/span>Hey, Scripting Guy! We have a number of files that were manually created by various people in a common folder. Unfortunately, they did not follow a specific naming convention as well as they should, and as a result they do not sort very well. Some people preceded the file names with the word \u201cFile,\u201d and others appended their name to the file. In the middle are numbers that correspond to purchase order numbers. I would like to get rid of the word \u201cFile\u201d and the person’s name from the files and be left with only the purchase order numbers for the file names. There are hundreds of files in this folder, and it will take an entire weekend to clean this junk up. With football season starting up in the United States, I would much rather watch football and consume junk food than spend the weekend cooped up in an office cleaning up after clueless users. <\/p>\n

— JPC <\/p>\n

\"Hey,<\/font><\/p>\n

Hello JPC, <\/p>\n

Microsoft Scripting Guy Ed Wilson here. You are right. Football season in the United States is a special time of the year. Because it is often accompanied by the transition from hot summer months to more temperate fall weather, it is a special time of the year. Or maybe it is just the marching bands and their half time shows that make things interesting. In Charlotte, North Carolina<\/font><\/a>, we have a professional football team<\/font><\/a> as well as several college and university teams we can watch. It makes things interesting on the weekend if you are trying to consume as much football and junk food as possible. Speaking of interesting, a similar question was asked a few years ago by RE when RE wanted to know how to delete specified characters from the beginning and end of file names<\/font><\/a>. In that article, a pretty cool VBScript was created. It is seen here. <\/p>\n

DeleteCharactersFromBeginningAndEndOfFileNames.vbs <\/p>\n

<\/strong><\/p>\n

strComputer = "." <\/p>\n

Set objWMIService = GetObject("winmgmts:\\\\" & strComputer & "\\root\\cimv2") <\/p>\n

Set colFiles = objWMIService.ExecQuery _
    <\/span>("ASSOCIATORS OF {Win32_Directory.Name=’C:\\Test’} Where " _
        <\/span>& "ResultClass = CIM_DataFile") <\/p>\n

For Each objFile In colFiles
    <\/span>strPath = objFile.Drive & objFile.Path
    <\/span>strExtension = objFile.Extension
    <\/span>strFileName = objFile.FileName <\/p>\n

    <\/span>If Left(strFileName, 5) = "File " Then
        <\/span>intLength = Len(strFileName)
        <\/span>strFileName = Right(strFileName, intLength – 5)
    <\/span>End If <\/p>\n

    <\/span>If Right(strFileName, 7) = " George" Then
        <\/span>intLength = Len(strFileName)
        <\/span>strFileName = Left(strFileName, intLength – 7)
    <\/span>End If <\/p>\n

    <\/span>strNewName = strPath & strFileName & "." & strExtension
    <\/span>errResult = objFile.Rename(strNewName)
Next <\/p>\n

<\/font><\/font><\/span><\/p>\n

JPC, a Windows PowerShell script could be produced that would use the Associators Of<\/b> query from WMI and could mimic rather closely the syntax of the VBScript. But this script points out the danger of blindly translating VBScript code into Windows PowerShell code<\/font><\/a> because in Windows PowerShell there is a much better way of performing this task than using the rather complicated Associators Of<\/b> WMI query. For more information about translating Associators Of<\/b> WMI queries from VBScript to Windows PowerShell (and why you might need to do such a thing), see the How Do I Migrate My VBScript Queries to Windows PowerShell?<\/font><\/a> article. <\/p>\n

I actually wrote two Windows PowerShell scripts that will delete words from the beginning and end of the file names that are stored in the folder. The folder containing the target files is seen here: <\/p>\n

\"Image <\/p>\n

Both scripts use the replace<\/b> operator to replace the strings with an empty space. The first script is called DeleteCharactersFromBeginningAndEndOfFileName.ps1 and is shown here. <\/p>\n

DeleteCharactersFromBeginningAndEndOfFileName.ps1 <\/p>\n

<\/strong><\/p>\n

Get-ChildItem -path c:\\fso -Filter *.txt |
ForEach-Object {
 <\/span>$name = $_.name -replace "file ",""
 <\/span>$name = $name -replace " george",""
 <\/span>Rename-Item -Path $_.fullname -NewName $name
}
Get-ChildItem -path c:\\fso -Filter *.txt <\/p>\n

<\/font><\/font><\/span><\/p>\n

In the DeleteCharactersFromBeginningAndEndOfFileName.ps1 script, the first thing that is done is to retrieve all of the text files. Because text files have a .txt extension, the \u2013filter<\/b> parameter is used to limit the search results that are returned by the Get-ChildItem<\/b> cmdlet. The \u2013path<\/b> parameter tells the Get-ChildItem<\/b> cmdlet where to begin looking for all the text files. The results of this command are piped to the ForEach-Object<\/b> cmdlet. This is seen here: <\/p>\n

Get-ChildItem -path c:\\fso -Filter *.txt | <\/p>\n

<\/font><\/span><\/p>\n

The ForEach-Object<\/b> cmdlet is used to allow Windows PowerShell to work with each file as it comes across the pipeline. The first thing that is done is to replace the word \u201cfile\u201d <\/i>with an empty string. The replace<\/b> operator is used to do pattern matching on a string. The name<\/b> property from the System.IO.FileInfo class returns a string, and therefore the tostring<\/b> method is not required to convert the name to a string. The replace<\/b> operator takes two parameters: the first is the pattern to be matched, and the second is the value to replace the matched pattern with. This is illustrated here: <\/p>\n

PS C:\\> $a = Get-Item C:\\fso\\a.txt <\/p>\n

<\/font><\/span><\/p>\n

PS C:\\> $a.Name <\/p>\n

<\/font><\/span><\/p>\n

a.txt <\/p>\n

<\/font><\/span><\/p>\n

PS C:\\> $a.Name  <\/span>-replace "a","b" <\/p>\n

<\/font><\/span><\/p>\n

b.txt <\/p>\n

<\/font><\/span><\/p>\n

PS C:\\> <\/p>\n

<\/font><\/span><\/p>\n

After the word \u201cfile\u201d has been replaced, the resulting string is stored in the variable $name<\/b>. This is seen here: <\/p>\n

$name = $_.name -replace "file ","" <\/p>\n

<\/font><\/span><\/p>\n

This line of code takes care of the problem of the word \u201cfile\u201d when it is found at the beginning of the string. Now you need to replace the word \u201cGeorge,\u201d which occurs at the end of some of the strings. To do this, use the string stored in the $name<\/b> variable, and the replace<\/b> operator to clean up the end of the file names. This is seen here: <\/p>\n

$name = $name -replace " george","" <\/p>\n

<\/font><\/span><\/p>\n

After the second replace<\/b> operation has completed, the new file name is used in a call to the Rename-Item<\/b> cmdlet. When using the Rename-Item<\/b> cmdlet, the first parameter is the path<\/b> parameter that must give the complete location to the file. The second parameter is the new name for the file. You cannot use the Rename-Item<\/b> cmdlet to rename and move a file to a new location. To move a file, you must use the Move-Item<\/b> cmdlet. The renaming of the file is seen here: <\/p>\n

Rename-Item -Path $_.fullname -NewName $name <\/p>\n

<\/font><\/span><\/p>\n

After all of the files have been renamed, the Get-ChildItem<\/b> cmdlet is used to produce a listing of the folder to ensure the file names have been changed. This is seen here: <\/p>\n

Get-ChildItem -path c:\\fso -Filter *.txt <\/p>\n

<\/font><\/span><\/p>\n

The renamed files are seen in this image: <\/p>\n

\"Image <\/p>\n

The second script is a little more efficient and a bit shorter, but is also more complicated to read. The change to the script involves using one replace<\/b> command instead of two. For this scenario, the results of the two scripts are exactly the same, but the two replace<\/b> operations are not the same. The second form is more flexible because it will remove everything that is not a number from the file name. To do this, it uses the regular expression pattern \\D<\/b> that matches everything that is not a number. <\/p>\n

\n

For more information on using regular expressions from within Windows PowerShell, you can refer to this collection of Hey Scripting Guy! articles<\/font><\/a>. Pay particular attention to the ones from the week of April 13, 2009, because that was Regular Expression Week on the TechNet Script Center. <\/p>\n<\/blockquote>\n

The use of the \\D<\/strong> regular expression pattern is shown here: <\/p>\n

PS C:\\> $filz = "file 123 ed.txt","fyle 145556 bob.txt" <\/p>\n

<\/font><\/span><\/p>\n

PS C:\\> $filz | foreach-object { $_ -replace "\\D","" } <\/p>\n

<\/font><\/span><\/p>\n

123 <\/p>\n

<\/font><\/span><\/p>\n

145556 <\/p>\n

<\/font><\/span><\/p>\n

PS C:\\> <\/p>\n

<\/font><\/span><\/p>\n

The modified line of code from the RegexRemoveCharactersFromFileName.ps1 script is seen here: <\/p>\n

$name = ($_.name -replace "\\D","") + ".txt" <\/p>\n

<\/font><\/span><\/p>\n

The complete RegexRemoveCharactersFromFileName.ps1 script is seen here: <\/p>\n

RegexRemoveCharactersFromFileName.ps1 <\/p>\n

<\/strong><\/p>\n

Get-ChildItem -path c:\\fso -Filter *.txt |
ForEach-Object {
 <\/span>$name = ($_.name -replace "\\D","") + ".txt"
 <\/span>Rename-Item -Path $_.fullname -NewName $name
}
Get-ChildItem -path c:\\fso -Filter *.txt <\/p>\n

<\/font><\/span><\/p>\n

 <\/p>\n

Well, JPC, that is about all there is to renaming folders that are named after a specific pattern. If you want to know exactly what we will be covering tomorrow, follow us on Twitter<\/font><\/a> or Facebook<\/font><\/a>. If you have any questions, send e-mail to us at scripter@microsoft.com<\/font><\/a> or post them on the Official Scripting Guys Forum<\/font><\/a>. See you tomorrow. Until then, peace. <\/p>\n

\n

 <\/p>\n<\/p>\n

Ed Wilson and Craig Liebendorfer, Scripting Guys <\/p>\n

<\/span><\/b><\/p>\n","protected":false},"excerpt":{"rendered":"

Share this post: Hey, Scripting Guy! We have a number of files that were manually created by various people in a common folder. Unfortunately, they did not follow a specific naming convention as well as they should, and as a result they do not sort very well. Some people preceded the file names with the […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[38,174,3,4,12,21,45],"class_list":["post-52423","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-files","tag-regular-expressions","tag-scripting-guy","tag-scripting-techniques","tag-storage","tag-string-manipulation","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Share this post: Hey, Scripting Guy! We have a number of files that were manually created by various people in a common folder. Unfortunately, they did not follow a specific naming convention as well as they should, and as a result they do not sort very well. Some people preceded the file names with the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=52423"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/52423\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=52423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=52423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=52423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}