Difference between revisions of "ReNamer:Renaming to another folder"

From den4b Wiki
Jump to navigation Jump to search
(cleanup)
Line 1: Line 1:
You can optionally '''move''' the renamed item to another folder.
 
If you have loaded multiple files in ReNamer, you can also sort them into multiple folders.
 
  
== Moving the item to another folder ==
+
You can optionally '''move''' renamed files/folders to another location. You can also sort files into multiple folders based on their meta tag properties.
  
Just specify a new folder path in the '''New Name''' field.
+
== Moving to another folder ==
*Although you can use this trick in multiple rules, the easiest is the [[ReNamer:Rules:Insert|Insert rule]].
 
*You can use either absolute path (e.g. '''"D:\Utilities\"''') or relative path (e.g. '''"..\"''').
 
  
For example, let us imagine that we have just [[ReNamer:Adding files and folders|added few files]] to [[ReNamer]].  
+
To move items to another folder you need to specify a new folder path in the '''New Name''' field.
 +
* Although you can use this trick in multiple rules, the easiest is the [[ReNamer:Rules:Insert|Insert rule]].
 +
* You can use either absolute path (e.g. "<code>C:\Example\</code>") or relative path (e.g. "<tt>..\Example\</tt>").
  
{| class="wikitable"
+
For example, let us imagine that we have just [[ReNamer:Adding files and folders|added few files]] to [[ReNamer]].
|-
 
! Name
 
|-
 
| Text.txt
 
|-
 
| Song.mp3
 
|-
 
| Document.doc
 
|}
 
  
We want to move those files to a new folder "'''C:\New Folder'''". What we need to do is to add a single [[ReNamer:Rules:Insert|Insert rule]], inserting "'''C:\New Folder\'''" as prefix. This will result in the following:  
+
We want to move those files to a new folder "<code>C:\New Folder</code>". What we need to do is to add a single [[ReNamer:Rules:Insert|Insert rule]], inserting "<code>C:\New Folder\</code>" as prefix. This will result in the following:  
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 39: Line 28:
  
 
Now you can proceed with the renaming as usual.
 
Now you can proceed with the renaming as usual.
*If the target folders do not exist already, ReNamer will create them and then move the file into these newly created folders.
 
  
[[Tip:]] Make the '''New Path''' column visible in the '''Files''' table, so that you can see the final destination for each item. This can be particularly useful when working with relative paths, because ReNamer displays the relative paths as if they are absolute paths (you do not have to guess the final destination).
+
* If the target folder does not already exist, ReNamer will create it automatically.
 +
 
 +
'''Tip:''' Make the "New Path" column visible in the files table so that you can see the final destination for each item. This can be particularly useful when working with relative paths, because ReNamer will resolve all relative paths to absolute paths, so you do not have to guess the final destination.
  
 
== Sorting files into multiple folders ==
 
== Sorting files into multiple folders ==
Line 47: Line 37:
 
When you have loaded multiple files in ReNamer, you can use the properties of these files to sort them into different folders (also called "binning").
 
When you have loaded multiple files in ReNamer, you can use the properties of these files to sort them into different folders (also called "binning").
  
To do this, instead of hard-coding the path, use a [[ReNamer:Meta_Tags|meta tag]] in the new path [[ReNamer:Rules:Rearrange Examples#Example_3_2|(see this example, which uses the '''Replace''' rule)]].
+
To do this, instead of hard-coding the path, use a [[ReNamer:Meta_Tags|meta tag]] in the new path ([[ReNamer:Rules:Rearrange Examples#Example_3_2|see this example, which uses the Replace rule]]).
*If the folders do not exist already, ReNamer will create them.
+
 
*You can even create a hierarchy in a single renaming operation (just use multiple meta tags in the '''New Path''').
+
* If the folders do not exist already, ReNamer will create them.
*:For example, '''C:\MetaTag1\MetaTag2\NewName''' will create two levels of folders and sort the files into them.
+
* You can even create a hierarchy in a single renaming operation (just use multiple meta tags in the "New Path").
 +
*: For example, "<code>C:\MetaTag1\MetaTag2\FileName</code>" will create two levels of folders and sort the files into them.
 +
 
 +
== Instead of ''moving'' the file, can we ''copy'' it?  ==
  
== Instead of ''moving'' the file, can we ''copy'' it into another folder?  ==
+
As we saw above, to move a file to a another folder ReNamer changes the whole path of the file, which effectively moves the file. Copying a file, however, requires creating a new instance of the file and copying the content to the new location. ReNamer is designed for renaming files and does not directly support copying.
  
Well, as we saw above, ReNamer actually changes the <u>path</u> of the file, which effectively moves the file. But copying a file requires creating a new instance of the file, which ReNamer cannot do.  
+
A simple workaround is to manually create a copy of files with an external application (such as Windows Explorer) and then rename the copied files. This will let you keep the original files as they were and create a renamed copy using ReNamer's functionality as normally.
  
The best we can do is to copy the files in the same folder first (with an external application, such as Windows Explorer) and then rename them as shown above to move them.But even this can save a lot of work, as ReNamer can create new folders and distribute the files into them at once.<br>
 
 
[[Category:ReNamer]]
 
[[Category:ReNamer]]

Revision as of 15:35, 18 April 2013

You can optionally move renamed files/folders to another location. You can also sort files into multiple folders based on their meta tag properties.

Moving to another folder

To move items to another folder you need to specify a new folder path in the New Name field.

  • Although you can use this trick in multiple rules, the easiest is the Insert rule.
  • You can use either absolute path (e.g. "C:\Example\") or relative path (e.g. "..\Example\").

For example, let us imagine that we have just added few files to ReNamer.

We want to move those files to a new folder "C:\New Folder". What we need to do is to add a single Insert rule, inserting "C:\New Folder\" as prefix. This will result in the following:

Name New Name
Text.txt C:\New Folder\Text.txt
Song.mp3 C:\New Folder\Song.mp3
Document.doc C:\New Folder\Document.doc

Now you can proceed with the renaming as usual.

  • If the target folder does not already exist, ReNamer will create it automatically.

Tip: Make the "New Path" column visible in the files table so that you can see the final destination for each item. This can be particularly useful when working with relative paths, because ReNamer will resolve all relative paths to absolute paths, so you do not have to guess the final destination.

Sorting files into multiple folders

When you have loaded multiple files in ReNamer, you can use the properties of these files to sort them into different folders (also called "binning").

To do this, instead of hard-coding the path, use a meta tag in the new path (see this example, which uses the Replace rule).

  • If the folders do not exist already, ReNamer will create them.
  • You can even create a hierarchy in a single renaming operation (just use multiple meta tags in the "New Path").
    For example, "C:\MetaTag1\MetaTag2\FileName" will create two levels of folders and sort the files into them.

Instead of moving the file, can we copy it?

As we saw above, to move a file to a another folder ReNamer changes the whole path of the file, which effectively moves the file. Copying a file, however, requires creating a new instance of the file and copying the content to the new location. ReNamer is designed for renaming files and does not directly support copying.

A simple workaround is to manually create a copy of files with an external application (such as Windows Explorer) and then rename the copied files. This will let you keep the original files as they were and create a renamed copy using ReNamer's functionality as normally.