libretro / libretro/libretro-database
missing name in rdb files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 877
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 24
Description
Some entries in the rdb file does not contains any name,
I'm wondering if this is a failed or if its "wanted as it" (I don't get how it can be useful to have just a CRC for example)
Example: Atari - Jaguar.rdb
Its last entry only contains : { developer: '', publisher: '', crc: 0x40e1a1d0 }
Scanning the whole file list, I found 592 entries without a name property:
Atari - Jaguar.rdb: 6
Bandai - WonderSwan Color.rdb: 3
Bandai - WonderSwan.rdb: 17
Coleco - ColecoVision.rdb: 86
DOOM.rdb: 2
Epoch - Super Cassette Vision.rdb: 2
GCE - Vectrex.rdb: 2
HBMAME.rdb: 14
NEC - PC Engine - TurboGrafx 16.rdb: 24
Nintendo - Family Computer Disk System.rdb: 164
Nintendo - Game Boy Advance.rdb: 48
Nintendo - Game Boy Color.rdb: 12
Nintendo - Game Boy.rdb: 8
Nintendo - Nintendo 64.rdb: 11
Nintendo - Nintendo 64DD.rdb: 1
Nintendo - Nintendo DS.rdb: 15
Nintendo - Nintendo Entertainment System.rdb: 19
Nintendo - Satellaview.rdb: 16
Nintendo - Super Nintendo Entertainment System.rdb: 67
Nintendo - Virtual Boy.rdb: 1
RCA - Studio II.rdb: 3
SNK - Neo Geo Pocket Color.rdb: 4
SNK - Neo Geo Pocket.rdb: 1
Sega - 32X.rdb: 1
Sega - Game Gear.rdb: 5
Sega - Master System - Mark III.rdb: 4
Sega - Mega Drive - Genesis.rdb: 48
Sega - SG-1000.rdb: 2
Sony - PlayStation Portable.rdb: 1
Sony - PlayStation.rdb: 4
Watara - Supervision.rdb: 1
Is it "normal"? is there somewhere a kinda spec for the entries consistency?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the nameless entries in the listed .rdb files and compare them with the repository's other RDB records. Check whether the repository documents a consistency specification; done means establishing whether CRC-only records are valid and, if not, identifying the affected records and required correction.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100