how_datvault_works
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_datvault_works [2021/11/28 07:45] – johnsanc | how_datvault_works [2022/11/20 11:01] – johnsanc | ||
---|---|---|---|
Line 4: | Line 4: | ||
{{ : | {{ : | ||
- | ===== DATVault JSON Files ===== | + | ===== When are the DATs updated? ===== |
+ | |||
+ | DATVault checks various sources for updates multiple times per day on a fixed schedule. Any updated DATs are processed and enriched with [[mia_rom_tracking|MIA tracking]] information. The table below outlines when regular DAT updates are processed and made available to download in the DATVault interface shortly thereafter: | ||
+ | |||
+ | | | ||
+ | ^ DAT Category | ||
+ | | Archive | ||
+ | | DeDupe | ||
+ | | EmuArc | ||
+ | | Emulators | ||
+ | | FruitMachine | ||
+ | | NoIntro | ||
+ | | Others | ||
+ | | Pinball | ||
+ | | Pleasuredome | ||
+ | | ReDump | ||
+ | | Scene | ||
+ | | Snaps | ||
+ | | Tosec | ||
+ | |||
+ | <WRAP info> | ||
+ | |||
+ | ===== What are the DATVault JSON files? | ||
DATVault works by detecting special JSON files in your DatRoot. Each DAT you would like to manage has its own corresponding JSON file. Each file provides info about the DAT version you currently have. | DATVault works by detecting special JSON files in your DatRoot. Each DAT you would like to manage has its own corresponding JSON file. Each file provides info about the DAT version you currently have. | ||
- | |**⚠ CAUTION:** \\ The DATVault JSON files are not meant to be manually edited. Modifying the JSON files may cause DAT updates to not work properly. The information provided is for reference only.| | + | <WRAP important> |
The DATVault JSON files contain the following keys: | The DATVault JSON files contain the following keys: | ||
- | * **'' | ||
* **'' | * **'' | ||
* **'' | * **'' | ||
Line 20: | Line 41: | ||
* **'' | * **'' | ||
* **'' | * **'' | ||
+ | * **'' | ||
+ | * **'' | ||
**Example DATVault JSON for MAME:** | **Example DATVault JSON for MAME:** | ||
< | < | ||
{ | { | ||
- | " | ||
" | " | ||
" | " | ||
- | " | + | " |
" | " | ||
- | " | + | " |
- | " | + | " |
" | " | ||
- | " | + | " |
+ | " | ||
+ | " | ||
} | } | ||
</ | </ | ||
Line 38: | Line 62: | ||
The information in the JSON file is compared against the DATVault repository to determine if there are updates available to download. If the JSON file you have does not match the latest version available by DATVault, then the corresponding DAT has an update. When you update a DAT, the JSON file is also updated. | The information in the JSON file is compared against the DATVault repository to determine if there are updates available to download. If the JSON file you have does not match the latest version available by DATVault, then the corresponding DAT has an update. When you update a DAT, the JSON file is also updated. | ||
- | |**🛈 NOTE:** \\ DATVault will download any updates into the same directory that contains the respective JSON file. Any existing DATs for that system will have a '' | + | <WRAP important> |
+ | |||
+ | <WRAP info>DATVault will download any updates into the same directory that contains the respective JSON file. Before a DAT is updated, the current DAT you have (which is referenced in your JSON file) will be renamed with a '' | ||
- | |**🛈 NOTE:** \\ Some DATs for disc based systems have accompanying cue sheets. DATVault will download cue packs to a folder called '' | + | <WRAP info>Some DATs for disc based systems have accompanying cue sheets. DATVault will download cue packs to a folder called '' |
Now that you understand how DATVault works at a high level, refer to the next section to [[datvault_setup|get started using DATVault]]. | Now that you understand how DATVault works at a high level, refer to the next section to [[datvault_setup|get started using DATVault]]. |
how_datvault_works.txt · Last modified: 2023/07/04 08:38 by johnsanc