CURATOR Planning Record
Planned Changes for Next Release
Updated On:
What We're Working On
These are the improvements currently planned for the next CURATOR release. Development is still underway, so the final list may change before release.
MAME support in myOrganizer: CURATOR is a VERY EARLY, experimental implementation. It must NOT be relied upon as a proven means of organizing MAME sets. Continue using clrmame as the definitive MAME ROM manager.
Every BETA release requires a clean run. Databases, saved run state, and output plans from earlier BETA releases are not backward compatible.
Adding
- Retain MAME software-list disk declarations without treating logical disk hashes as physical ROM identities. Disk matching/output support remains experimental and incomplete; mixed ROM/disk sets stop explicitly.
- Add template-based mappings for DAT fields, keeping set names, descriptions, member filenames and checksums distinct.
- Retain declared MD5 checksums throughout DAT authority publication. Physical-file MD5 matching when SHA1 is absent remains deferred.
- Add independent language folders alongside geographic region folders, using the region and language mapping table.
Changing
- Refresh the four guides for schema 22, complete-set deduplication, current review destinations and bounded Naomi/CDI support; remove obsolete software-list DTD setup instructions.
- Organize the AtariMania ST catalogue into individual disk-image sets, retaining supporting documents and sidecars separately.
- Simplify unknown-file review destinations by removing the redundant Unresolved Media folder level.
- Assign DAT profiles from configured source-metadata rules instead of guessing from DAT filenames.
- Name set packages from the mapped authoritative set name while retaining declared member filenames inside each package.
- Move DAT authority processing into the database while retaining original definitions, source information, every set membership and rollback safeguards.
- Preserve every DAT definition and set membership while sharing matching content using Size, CRC and SHA1, with MD5 compared when both declarations supply it. Filename comparison is case agnostic.
- Remove the unused software-list DTD dependency.
Fixing
- Correct preparation of certain DiscJuggler CDI data tracks, including decoded sector sizes and sector addresses. Remove a stored data-track pregap only when the resulting content matches a loaded authoritative DAT.
- Recognize Redump Sega Naomi disc sets and create complete-set CHD output using the authoritative DAT filename.
- Accept optional game identifiers in XML DATs while keeping them separate from output filenames.
- Recognize redump.info publisher metadata alongside existing redump.org headers.
- Deduplicate complete sets using their full member contents, then select the winning source through the configured authority hierarchy. Preserve distinct sets that merely share some files and retain all source declarations and memberships.
- Preserve DAT-declared publication files instead of excluding them merely because their names or folders contain image-related terms.
- Keep DAT analysis progress in its taskbar instead of repeatedly displaying generic FileCopy completion messages.
- Interpret declared file sizes according to each DAT format and retain their original declarations.
- Correct GoodTools Atari 2600 set names to match their ROM filenames without the final extension.
- Avoid unnecessary Conflicts output for equal content declared through different DAT names or formats, without losing definitions or memberships.
- Avoid false ambiguous matches caused solely by a missing MD5 declaration.
- Keep unbound review files separate under Unknown File, adding incremental suffixes when filenames collide.
Known limitations
- CDI input support remains partial. The four tested Dreamcast CDI games do not form complete matched sets; this correction does not establish complete-game CHD output or repair differing audio.
- Complete Redump Naomi sets have verified standalone CHD output with authoritative names. Creation of new RVZ files and converted-media collision/recovery cases still need acceptance testing; copying an existing RVZ does not establish conversion support.
- Locked platform files may produce a generic error; release the file lock before rerunning preparation.