Forum Discussion
Rename files to get the year, month and day of the creation in front of the file?
Here's a three-line example on how you can do this. I've gone with the assumptions that:
- The prefix date format should be "yyyyMMdd_";
- You do indeed want the creation date used in the prefix, not the last modified date.
$ParsedDate = [datetime]::MinValue; $Path = "D:\Data\SomePath"; Get-ChildItem -File -Path $Path -Recurse | Where-Object { (-not [regex]::IsMatch($_.Name, "^\d{8}_", [System.Text.RegularExpressions.RegexOptions]::IgnoreCase)) -or (-not [datetime]::TryParseExact($_.Name.Substring(0, 8), "yyyyMMdd", [cultureinfo]::CurrentCulture, [System.Globalization.DateTimeStyles]::None, [ref] $ParsedDate)) } | ForEach-Object { Rename-Item -Path ($_.FullName) -NewName "$($_.CreationTime.ToString("yyyyMMdd"))_$($_.Name)"; }Cheers,
Lain
Here's a three-line example on how you can do this. I've gone with the assumptions that:
- The prefix date format should be "yyyyMMdd_";
- You do indeed want the creation date used in the prefix, not the last modified date.
$ParsedDate = [datetime]::MinValue;
$Path = "D:\Data\SomePath";
Get-ChildItem -File -Path $Path -Recurse |
Where-Object { (-not [regex]::IsMatch($_.Name, "^\d{8}_", [System.Text.RegularExpressions.RegexOptions]::IgnoreCase)) -or (-not [datetime]::TryParseExact($_.Name.Substring(0, 8), "yyyyMMdd", [cultureinfo]::CurrentCulture, [System.Globalization.DateTimeStyles]::None, [ref] $ParsedDate)) } |
ForEach-Object { Rename-Item -Path ($_.FullName) -NewName "$($_.CreationTime.ToString("yyyyMMdd"))_$($_.Name)"; }
Cheers,
Lain
This is working perfectly. If I want to add the hours and minutes in 24hr to the prefix, like 202303271430 for a file created at 14:30 today. Would that be easy to work in? tried to just put hhmm after the tostring but that's actually putting it in as 202303270230. Must be something about 12 vs 24 hr format.
Looks like you have something smart in there to ignore files already with the prefix added.Just be aware that the special format characters are case-sensitive. For example:
Format string Meaning hh Two-digit hour using 12-hour clock. HH Two-digit hour using 24-hour clock. Months (MM) and minutes (mm) is another one to be wary of.
You can find the full reference here:
Cheers,
Lain
Hey that was fast. Thank you so much.
Yes the year musst be in front.
I will try it as soon as possible, but it looks great.
By the way where should I start with training for Powershell? Is there a course or a training book or something else?
pspBugs
EDIT:I tested the code and it worked, but it did not take the creation date of each file every time.
So it takes the date from when the script was executed. Is there any way to loop this and get the individual creation date of each file?
And on repeated execution, the already renamed files are not ignored.pspBugs
Are you sure you don't want the last modified date instead? Here's an example to illustrate why I ask.
Here's the sample files I tested against. Windows Explorer shows the date modified by default, not the creation date.
It's important to note I copied these files from a different location, meaning the originals have a different creation date. This diminishes the value of the creation time since it may not actually be the date the author created the file at all, but simply the last time it was copied.
Just to be sure, let's have a look at the dates on the "input.settings" file in PowerShell, noting CreationTime in particular.
Here, you can see that the CreationTime is today (the actual time I performed the file copy) and that it is actually greater than the LastWriteTime. Now, this is all well and good from the file system perspective where it makes sense, but it's probably counterintuitive to what you're hoping to achieve.
In short, the CreationTime is somewhat unreliable, whereas the LastWriteTime is preserved even during the any copy process. This is why I was wondering if you wouldn't prefer the last modified date.
The script itself is not using the current date through some indirect means (like, say, [datetime]::Now). It really is pulling the CreationTime from the file.
Cheers,
Lain
I just noticed your second comment about existing prefixes not being ignored.
I'm not seeing that reflected when I run it multiple times over the test files. It's putting the prefix in the first time then ignoring it on subsequent runs.
Maybe you can drop an example into this thread so we can get an idea of what's going on behind the scenes?
If you could drop in the following for one of the repeatedly-changing files, that might help:
- File name;
- File creation date;
- Which version of PowerShell you're running (I'm running under Windows PowerShell 5.1.)
You can get points 1 and 2 via:
Get-Item -Path ".\SomeFileName" | Select-Object -Property Name, CreationTimeYou can get point 3 from the following:
$PSVersionTableCheers,
Lain
