Re: [mb-users] Should catalog numbers be capitalised?
Tom Crocker <[email protected]> Mon, 22 Sep 2014 18:42:09 +0100
| Newsgroups | gmane.comp.audio.musicbrainz.user |
|---|---|
| Message-ID | <CAHmUbmeEoMj6NFzBkTVQDNm8vBxzGVuG6zwRak6v6bo0K+67ew@mail.gmail.com> |
--===============1362468805== Content-Type: multipart/alternative; boundary=f46d0444814f62e4ee0503aaf80d --f46d0444814f62e4ee0503aaf80d Content-Type: text/plain; charset=UTF-8 On 22 September 2014 17:18, caller#6 <[email protected]> wrote: > On 09/21/2014 06:21 PM, Alex Mauer wrote: > > OK, fair enough; MusicBrainz *release entities* are about the releases > > though, IMO. For an entity that represented the catalog itself or the > > label, it's appropriate to normalize; but not for the release. > > If there's value to storing the as-on-cover catno in a text field (we > already have it in cover art, hopefully), then I agree that no > normalization should be done until we have a way to store both forms > (as-on-cover and normalized). > > But I'm not clear on what that value is. > I guess where differences in the various ways of presenting the catno would reduce searchability or automated matching, depending on the particular version you had available --f46d0444814f62e4ee0503aaf80d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= te">On 22 September 2014 17:18, caller#6 <span dir=3D"ltr"><<a href=3D"m= ailto:[email protected]" target=3D"_blank">[email protected]</a>></s= pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex= ;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 09/21/201= 4 06:21 PM, Alex Mauer wrote:<br> > OK, fair enough; MusicBrainz *release entities* are about the releases= <br> > though, IMO. For an entity that represented the catalog itself or the<= br> > label, it's appropriate to normalize; but not for the release.<br> <br> </span>If there's value to storing the as-on-cover catno in a text fiel= d (we<br> already have it in cover art, hopefully), then I agree that no<br> normalization should be done until we have a way to store both forms<br> (as-on-cover and normalized).<br> <br> But I'm not clear on what that value is.<br> </blockquote><div><br></div><div>I guess where differences in the various w= ays of presenting the catno would reduce searchability or automated matchin= g, depending on the particular version you had available<br></div></div><br= ></div></div> --f46d0444814f62e4ee0503aaf80d-- --===============1362468805== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MusicBrainz-users mailing list [email protected] http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-users --===============1362468805==--