On Sun, Mar 21, 2010 at 8:56 AM, jacobbrett <[email protected]> wrote:
> > Here's a list of changes to be made to this style, based upon the above > discussion: > > 1. Remove definitions > I'm not sure what you mean here, I think the page should definitely give brief overviews of what the various fields represent (date, country, label, format, packaging, type, comment etc.) In fact, I'd go as far as to say that this page is essentially *only* a definition page (longer definitions/sections may need to be split into a separate page of course). I recommend dropping the "release" suffix in the definition headers. Saying "Release date", "Release format", etc. is just tedious and unnecessary because we're on a release specific documentation page. It's only when you need to (for example) start referring to both artist type and release type that you'd need that additional disambiguation prefix. 2. Move identifying section to a new doc "How to Identify Release Details", > merge "How to Identify Labels" into this new doc. > I quite like this section/concept. I don't think I've ever come across documentation that walks you through how to "identify a release based on" and then lists several different options like this, It's quite handy. I agree that this section should be moved to its own page, it will get quite large. I also think it would be totally appropriate if you did not want to take on a "how to identify labels" page in this rewrite. 3. Move various Release Field style guidlines from other docs to this doc. > Yes! Like I said before, the new UI doesn't segregate any of the data and I feel the documentation shouldn't either. However, this does not mean that separate pages *have* to disappear, in some cases they may be necessary to provide additional clarification and/or more in-depth examples (for example, we may need an additional separate page that lists all the packaging types and a reference picture). But I believe the page you're working on should be the "central" page, and it should touch on everything at a minimum. 4. Hyperlink keywords in the "Identifying Release Details" section to their > respective pages. > Sounds good. Pavan, can you please explain what is wrong with using "Release Event"? > I notice "The Lord of the Rings: The Complete Songs & Poems" is a Reylease, > with 4 CDs listed under it: > > http://test.musicbrainz.org/release-group/993ad43b-d173-3388-8c6a-90783df763c3 > are they now called "Release Information"s? > The reason I believe the term "release event" is incorrect is because that term is no longer used in the new UI. The current server really segregates everything, it splits the date/country/label/catalog/barcode/format data from any of the other editable fields (script/language, status/type, artist, title). This is not the case in NGS. It's also a confusing term because conceptually what we referred to as a "release event" in the current server is now referred to as a "release" in NGS (as Frederic has also pointed out). The page you're linking to is a release group page, the contents of that table are the various releases in that release group (in this case there is only one). A better example might be Nirvana's Nevermind release group. Currently there are four releases in that release group [1], but in NGS those four become eleven releases [2]. Why? Because the four pre-NGS releases had multiple release events (eleven in total to be exact) and the eleven post-NGS releases all *are* one release event each. I recommend that you, and anyone else who's interested, read [3] (if you haven't already done so). It's a user-friendly overview of the release model changes that NGS will bring, as opposed to the developer-friendly (i.e. someone who can look at a schema diagram and say "ah yes, that's some amazing stuff right there") overview like what is written on the NGS documentation page. 5. Therefore, replace "A Release Event is the event when a Release is first > sold on a market." > with "A release date is the date a release was made available." > Yes, but I suggest you not make that the first line of the page :) 6. Also, rename the style to "Release Information Style"(?) > The data being covered on the page could be referred to by many different names (information, properties, attributes, etc.) but I don't think the page title needs to include that term in it. The way I see it we have two options, either we drastically change the new UI to replace all instances of the term "release" with "release event" and then title this page "Release Event Style", or we keep the new UI the way it is and we title the page "Release Style" (because that is what it's describing - the entire release). I strongly suggest the latter :) I think it's really great that you're taking on such a huge and important page in the documentation, I look forward to seeing what you come up with! [1] http://musicbrainz.org/release-group/1b022e01-4da6-387b-8658-8678046e4cef.html [2] http://test.musicbrainz.org/release-group/1b022e01-4da6-387b-8658-8678046e4cef [3] http://musicbrainz.org/doc/Server_Release_Notes/NGS_Beta_1#Releases_model_changes Pavan Chander // navap
_______________________________________________ Musicbrainz-style mailing list [email protected] http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-style
