Author Topic: Error Listings and rejected edits 2024  (Read 20996 times)

Re: Error Listings and rejected edits 2024
« Reply #225 on: Today at 07:38:27 am »
While the two items you've presented may have been released in those countries, figuring that information is not as straightforward as you're employing the practice. Items vary from one country to the next, and especially when regional distribution and import labels exist (and have been known to be present in some of those countries you've listed) which means, for the purposes of our site, they would be two separate items.

Also, licensing text seems to matter little in providing useful information for us. Take, for instance, these various regional copies of Resident Evil 4 for PlayStation 4. Based on language text, publisher item numbers, and even regional rating systems, we know that they're specific to individual countries. However, there is a lot of overlap in which regions each specific item is "licensed" for sale in, including Russia. Meanwhile, Russia has its own regional item that's clearly indicated.

There isn't any requirement for TLDs to be exhaustive when attaching them to entries. We'd rather them be researched and utilized correctly than otherwise. Entries can always be updated to add more information as it's discovered and confirmed.

Whereas using ISO 639 would be easy (easier?), straightforward, explicit as using only intrisic information (available on the item itself), and reduce significantly the length of such entries, simplifying [AR][BO][CL][CO][CR][EC][SV][GT][HN][MX][NI][PA][PE][VE][…] with [ES], while actually making this sole information both correct and complete in what distinguish such items from the “default” ones (generally US for NA, UK for Europe, etc.) of the same region.

Similarly [EN] instead of [US][CA] / [UK][IR][MT][…]

Can that actually be discussed? If so, how and where?

dhaabi

Re: Error Listings and rejected edits 2024
« Reply #226 on: Today at 08:45:28 am »
Whereas using ISO 639 would be easy (easier?), straightforward, explicit as using only intrisic information (available on the item itself), and reduce significantly the length of such entries, simplifying [AR][BO][CL][CO][CR][EC][SV][GT][HN][MX][NI][PA][PE][VE][…] with [ES], while actually making this sole information both correct and complete in what distinguish such items from the “default” ones (generally US for NA, UK for Europe, etc.) of the same region.

Similarly [EN] instead of [US][CA] / [UK][IR][MT][…]

Can that actually be discussed? If so, how and where?

Again, here are specific topics which I proposed yesterday.

Not one individual has authority to create or alter rules. Generally, community discussion and a democratic vote determine what sort of amendments are added as guidelines. If you disagree with anything or have suggestions, then refer below to the two topics.

Advanced Style Guide update and feedback thread
Style Guide Update Poll Idea Submissions

Unless someone is needing to ask why a specific edit submission was rejected or is wanting to report an entry error, then refer to those two topics if you have alternatives to propose.

But let me also reference the very same conversation we've already had about this very subject after you've raised concerns, in this very forum topic, during this very year.

- Consider the English language. What sort of tag are you implying be given to it? Be aware that [EN] is not a TLD.

There is no need to rehash this conversation, we already have the format for identifying language. It is the standard ISO-639+ISO-3166 locale combination. We just do not use it on the site anywhere as it does not actually help in regards to making the site easier to use. They would be used if we were to attach language information to an entry, either privately (as a var) or publicly likely would be a hidden value that would load a different resource like an image to represent the value. This particular format would allow separation between locales, such as en-US vs en-GB, or for French there are fr-CA, fr-FR, fr-BE or fr-CH...

Use of TLD is not ideal and is only required based on how the site is designed.

Also, current categories or how they appear are also due to the original design of the site which has not changed. Remember that the site was not originally designed for the amount of items we currently cover. A different design to the site could eliminate the way categories are viewed and could also eliminate the usage of TLDs (or even descriptors) in item titles. Until something like that happens, we will continue to use the TLD and descriptors the way we do now.

Keep in mind that there are a lot of database entry rules that only exist due to the limitations of the site. Instead of us side-stepping to another imperfect system, we should wait until development updates take place.
« Last Edit: Today at 09:19:54 am by dhaabi »

tripredacus

Re: Error Listings and rejected edits 2024
« Reply #227 on: Today at 11:13:50 am »
Re original conversation for Watch Dogs 2 on Xbone
https://vgcollect.com/item/115089

This item exists in a physical games category, so the entry is for the physical product. Publisher should be reflective of that. The game itself (the game data) is not part of the entry and any information about the game data would be put into description. The game data also has an entry, which is here: https://vgcollect.com/item/202909

So for this instance, the physical game entry would have Ubisoft but the game data entry would have Ubisoft Montreal. It looks like those entries already are like this.