Borewit, perhaps change the type to "Other" rather than "Front" and leave an annotation that this is the digital image that was used when printing the packaging? Also, please try to get into the habit of leaving an edit note citing the source of your information / images / etc. Please see https://musicbrainz.org/doc/How_to_Write_Edit_N... for more information.
I agree that it would be a shame to lose the image.
Borewit
Sometimes I dont want to reveal the source.
But I put ¨Press release, print quality¨ in the comment
What about cover type poster?
Does imply that it was shipped with the release isnt it
rdswift
Understood, but realize that not providing source information makes it difficult for other editors to veryify the information, and may collect "No" vites as a result. I suggest that the "Press release, print quality" be entered as the description for the image rather than (or in addition to) the edit note comment.
Borewit
I did put it in the description
But the description is called ¨comment¨ in the web interface
rdswift
I'd stick with "Other" because I'm not aware that there was a poster issued with the release, and this isn't really a poster but more of a higher quality digital image used to produce other items that were included with the release.
Borewit
What about combination of cover and raw/unedited?
rdswift
<Borewit> But the description is called ¨comment¨ in the web interface. You're right. Sorry, I missed that.
Borewit
No problem, logical misunderstanding.
rdswift
Strictly speaking it isn't the front image for this release. It's the image used to create the front image for the release. That's why I suggested "Other".
Borewit
Would be great if a dedicated category could be created for this, you want you thumbnails based on digital source, not some kind of cheap scan.
rdswift
You *might* get away with marking it as "Front" and "Raw / unedited", but I suspect that the "purists" (no ill will intended in that title) will still vote it down because it isn't strictly the cover for this release.
Borewit
There is one way to find out. So many HQ covers purist didnt detect yet...
rdswift
There was a LENGTHY and HEATED discussion about this topic in the forums a year or two ago. It was eventually (sort of) agreed that MusicBrainz was first and foremost an archive of information, and not so much a supplier of "nice" images. Other sources for that include things like fanart.tv
(so not poster, but it's definitly something interesting)
and a valid thing information ot keep
rdswift
I was instrumental in getting that type made available, and yes, it is primarily intended to describe images that have not beel altered.
CatQuest
(and i'm not sure about wanting especially "high qulaity only for thmbnails")
yvanzo
There should probably be an additional type for press kit or whatever as you suggested.
CatQuest
erh but spelled right idk what's wrong with me especially today
+1
rdswift
Since we don't currently have a "Press Kit" option, that's why I suggested "Other".
CatQuest
leaving it unselected is also not a sin
(and yu can put in a comment)
rdswift
True. I never thought of that.
CatQuest
you*
heh :)
whne in doubth. leave it empthy
Borewit
Or digital cover art, maybe with some characteristics you can check on or off.
CatQuest
(I was told atleast :D)
rdswift
Makes it a bit difficult selecting in Picard though.
CatQuest
:idk:
erh
¯\_(ツ)_/¯
Borewit
Exactly
So what is the difference between no type and ¨Other¨? By having no type I basically do not admin that it doesnt fall in one of the other categories right?
admit*
CatQuest
by using no category you're saying "this doesn't have any category" like the category this is isn't in mb yet
That's the best way to get things looked at "officially". Also, it doesn't get missed or lost.
Borewit
In theory.
rdswift
In practice. The team here is VERY good at looking at things. Sometimes things get left for a long while, but that's only because of limited resources.
CatQuest
or difficult of coding
so yes
Borewit
I am experienced with coding also in open source project, I know the challenges.
Voted up the issue
rdswift
Lack of resources and competing priorities are the enemies of open source.