What would be done? An additional [XW] release event would be created in the database? Not only displayed?
I guess this would be possible, although it would not help much for statistics. Release events could already be excluded in a query if more than x release events are found for the same item. Picard does that if you use the suggested script for multi-country releases. But Picard (the script) does it only for a single item.
I think I could live with this, as long as this is included in the data returned by API (to avoid the guessing game for each implementation) and we adopt some guidelines for the treatment of semi-independent country entries (like Curaçao) and countries where it couldn’t realistically be available (e.g. North Korea or Russia for the moment), and certain country entries are removed entirely (e.g. the aforementioned British Indian Ocean Territories) .
Ideally the editor UI should also get a redesign, because entering more than a couple of release events manually using the current style is incredibly annoying. A possible design might be entering a date, and then selecting countries for that date afterwards.
If neither this “practice” nor the release editor changes it will drive editors away:
(why is the formatting messed up when quoting?)
The performance aspect is still one of the main reasons why I rarely bother with anything that has more than x countries. It takes extra time and energy. (and if my current device wasn’t fan-less it would also cause extra noise)
Surely it can’t be the goal to have 6 duplicate releases just because the encoding is different (or presentation of the tracklist for that matter).
Which revealed another detrimental effect of the long country list “spam” in the user interface.
Scroll wheel version (actually touchpad):
Arrow keys version:
(no video uploads in the forum allowed? not even a meager 40.8 KB one?)
Also, I’ve noticed the release duplicates tab in the release editor doesn’t collapse countries either:
BTW, I still have a pretty small screen (1366 x 768) which makes all of this even more of a nuisance. Are there any stats for screen resolution of MB editors/visitors?
Last but not least, even if all of this was somehow solved I’d probably still not be in favor of the country list “spam” as long as the manual labor of data maintenance burden remains.
If you long for accurate data MB might want to consider ingesting DDEX feeds:
Here is an example of the data a RIN file can supply (previously introduced on IRC):
The discussion here is more about a flood of excess data about a digital shop and where is is selling today drowning out Release data. Spotify choosing to deliver to limited countries world wide is like Amazon’s ability to ship a CD to anywhere on the planet. MB has an impossible task to find a way to handle this different type of data with a different meaning in the digital world.
The rear cover I just added? LOL. (Neeed to get back OT…) A Scottish band, on a Scottish label - then it clearly requires a list of 179 different countries. Plus Mars and the Moon. /sarcasm I am JOKING with people.
another similar digital issue is releases that are now worldwide, but once excluded a few small countries. i’ve been adding these as “worldwide” with the new countries seperate, but i’d like to know what other people think.
I might be getting a bit late to this but I really think @aerozol is right with their mockup.
I understand the concerns of losing data because, well, this is a database.
But we need a really user friendly UI and what we currently have is anything but user friendly.
It’s just a lot of info dumping at the same time and takes a lot of space in a screen, specially in smaller ones as pointed by @chaban
Having a [XW - a few countries] format is a pretty cool solution, even if it only works at a UI level and doesn’t impact on the db.
The downside to this will always be that it’s nearly impossible to maintain. We can’t always be aware of the whimsical changes big platforms make regarding streaming licenses…
Just because we can enter 200 countries doesn’t mean we should. I still think it’s a Style issue barring schema changes.
Personally, I care about the country of origin / primary market of the release, as that is a way I classify my music into different groups. I’m constantly having to fix and ignore the junk Digital Media data in MusicBrainz.