Differences

This shows you the differences between two versions of the page.

--- organizing_dats [2021/11/29 21:07] – johnsanc
+++ organizing_dats [2023/12/08 14:46] (current) – johnsanc
@@ Line 1: / Line 1: @@
 ====== Organizing Your DATs ======
-RomVault's DATRoot outlines how you want your ROMs organized. Depending on your preferred directory structure and naming conventions, there are a few approaches you can take to manage your DATs.
+RomVault's DATRoot is where you keep your DATs and it outlines how you want your ROMs organized. The ROMRoot is the location where your ROMs will be stored on your filesystem. If you have a basic setup with a single DAT in each directory, your ROMRoot will mirror your DATRoot.
-  * Automatic using the DAT's Name tag
-  * Automatic using the DAT's Description tag
-  * Manual by placing a single DAT in each directory
-These options are controlled by Directory Settings and you can mix different approaches for different parts of your DATRoot.
-|**💡 TIP:** \\ RomVault has a built in DAT downloader and updater service that can be used to keep your DATs current. For more information, please refer to the **[[what_is_datvault|DATVault]]** section.|
+{{:diagrams:datroot-basic.png?nolink&600|}}
+If you have different locations for certain ROM sets you can use [[directory_settings|Directory Rules]] to re-map certain directories in your DATRoot to an alternate location on your filesystem. It is very common for large collections to be stored across multiple drives or network locations. Any directories that are not re-mapped will fall under your ROMRoot directory.
+{{:diagrams:datroot-mapping.png?nolink&600|}}
+Depending on your preferred directory structure and naming conventions, there are a few approaches you can take to manage your DATs and address directory naming:
+  * Manual naming by placing a single DAT in each directory
+  * Automatic naming using the DAT's Name tag
+  * Automatic naming using the DAT's Description tag
+These options are controlled by [[directory_settings|Directory Settings]] and you can mix different approaches for different parts of your DATRoot.
+<WRAP tip>RomVault has a built in DAT downloader and updater service that can be used to keep your DATs current. For more information, please refer to the **[[what_is_datvault|DATVault]]** section.</WRAP>
+\\
+===== Manual by placing a single DAT in each directory  =====
+If you place a single dat in a directory then RomVault will use that directory name for where to place your ROMs. This option is best if you want complete control over your directory structure and naming conventions. For example, if you want to rename systems or categorize by system type.
+{{:autodir_singledat.png?nolink&700|}}
 \\
 ===== Automatic using the DAT's Name tag =====
@@ Line 24: / Line 39: @@
 {{:autodir_description.png?nolink&700|}}
-===== Manual by placing a single DAT in each directory  =====
+\\
-If you place a single dat in a directory then RomVault will use that directory name for where to place your ROMs. This option is best if you want complete control over your directory structure and naming conventions. For example, if you want to rename systems or categorize by system type.
+===== Merging multiple DATs in a single directory  =====
+Under normal circumstances each DAT is aligned to its own directory which is either manually or automatically named based on the options outlined above. In certain situations you may want to merge multiple DATs together in a single directory. This can be accomplished under these conditions:
+  * The DATs you wish to merge are present in the same directory in your DatRoot
+  * The DATs have no set name conflicts
+  * The directory rule for the DATs has "Don't auto-add DAT directories" enabled
-{{:autodir_singledat.png?nolink&700|}}
+If the appropriate conditions are met, the merged DATs will a appear with a smaller font in the tree. If there is a set name conflict then you will get a DAT merge warning when you apply the directory rule or update DATs.
-|**💡 TIP:** \\ The TOSEC create/move scripts that are packaged with each DAT pack will place a single DAT in each folder. You can get creative and make your own scripts to move DATs where you like them. The example below in a batch script will copy dats from a source directory and move each one into a specific destination directory and delete any old DATs in that directory that match the file name pattern specified. This is a more advanced DAT management technique, but it can be very useful if you like to update your DATs frequently, but don't want to manually add new DATs and remove old ones. \\ \\ If you use scripts for DAT pre-processing you can also use an application like SabreTools to modify DATs to your liking before moving the DATs into your DatRoot. A common use case for this might be to split DATs by region, or remove the No-Intro header skipping tag.|
+{{:screens:merge-dats.png?nolink&800|}}
-<code>
-robocopy "C:\ROMVault3\ToSort\_DATS_\Redump" "C:\ROMVault3\DatRoot\Redump\Arcade\Konami - e-Amusement" "Arcade - Konami - e-Amusement - Datfile (*) (????-??-?? ??-??-??).dat" /PURGE
+<WRAP tip>Only directories with a DAT will display in the tree. If your preferred organization setup requires ignoring a directory in your RomRoot, then you can use a placeholder DAT to make that directory appear in the tree which you can deselect or lock. The placeholder DAT only needs to contain this: ''<?xml version="1.0"?><datafile/>''</WRAP>
-robocopy "C:\ROMVault3\ToSort\_DATS_\Redump" "C:\ROMVault3\DatRoot\Redump\Arcade\Konami - Bemani FireBeat" "Arcade - Konami - FireBeat - Datfile (*) (????-??-?? ??-??-??).dat" /PURGE
-robocopy "C:\ROMVault3\ToSort\_DATS_\Redump" "C:\ROMVault3\DatRoot\Redump\Arcade\Konami - System GV" "Arcade - Konami - System GV - Datfile (*) (????-??-?? ??-??-??).dat" /PURGE
-</code>
+\\
+===== Video Tutorial =====
+{{youtube>cfvgpaV3HqQ?full}}