Some available time for this came up again, so I implemented the 'Patching Information' field as previously outlined as well as a 'ROM / ISO Information' text field to get this started. It is for hacks and translation and it's required for all new submissions.
Intended usage of the 'ROM / ISO Information' field is to include ROM database filenames, ISO identification (SLUS ids, common filenames) and hashes (Any and all one wishes to provide). I imagine something like the
ROM Information section at the bottom of this page.
More info:
http://www.romhacking.net/?page=help&action=GetHelpItem&item=ROM%20/%20ISO%20InformationThis is all information that SHOULD be in the description anyway, but majority omit. At least by making this field separate and required for new submissions, we can do some arm twisting to hopefully get some of this information!
I think this goes a long way to addressing the cause. It may discourage many casual patch creators from submitting though. A number of them have no idea what a hash or ROM database, or SLUS id is... Trust me, I field their questions and lousy submissions often!
Lastly, expect a few bugs. I did this very quickly and didn't do more than a few simple tests.
No individual hash fieldsNo individual or uniformed hash fields were added because it seems like there are still unresolved platform specific items based on our discussions. It seems if we ever want to do that, we would need a rulse-set listing what the hash would encompass for each platform. In addition, whatever is decided seems too hard for the end user without a utility that can compute said hashes with aforementioned rule-set. So, it looks like no discrete hashes until there is a rule-set and a program to do so. I'm not too interested in shepherding that anytime soon. Feel free if interested.