Venue And Event Proposal: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(3 discussions started (Imported from MoinMoin))
m (double redirect)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
#REDIRECT [[:History:Location Proposal]]
This is a page describing as enhancement proposal for the [[MusicBrainz]] server. It is paralleled by [http://bugs.musicbrainz.org/ticket/2371 this trac ticket].

==Rationale==

We found it is often useful to record a physical location related to tracks and releases in [[MusicBrainz]]. For example, we would like to record the studio where an album was recorded, or the venue where a concert was performed. The "location" object resulting from this proposal will be used similarly to the Label objects used in the "release" fields of a release.

==Description==

Enter below a list of features such an object will need.

===Name===

The name is an identifier similar to what the [[Artist]]s and [[Label]]s have. It will certainly need a "comment" to distinguish between same-named objects.

===Type===

There are many kinds of possible "locations" we need to enter, so it is important that this field be well thought out.

Examples:
* "studio" -- this is probably going to be used often for the recording place of "normal" albums, singles and EPs.
* "venue" -- this is for places usually specialized for "artistic events" like concerts. This includes concert halls, theatres & amphitheatres, stadiums, clubs. We may want a list of options or use an annotation to be more precise.
* "festival" -- often many concerts are performed in a certain location that doesn't have any specific use outside the concert's duration. Since many concerts are performed in such places, it is necessary to be able to retain everything together.
<ul><li style="list-style-type:none">Sometimes a "festival" is performed in a location of the other kinds, for example on a stadium where other concerts were held independently of the festival. We should consider if we need location-to-location relationships, to say that "Festival X" happened at "Stadium X"; this could cause, for instance, the address to be copied/linked from one location to another.
</ul>
* "other" -- I've seen things recorded in hotel rooms (there's a Roxette album for instance), private homes, and other funny places like this. We'll need to use annotations to explain some of these.

===Dates===

Similar to creation date for Labels, birth/death date for [Artist]s, etc. It's less important for studios and venues -- though by no means completely irrelevant -- but it's very important for festivals and similar events.

===Address===

Of course we're most interested in where a location is. I suggest a specialized country field that works exactly like the one for the [[Release]]s, and a free-form text field for the address (as the format can be different for different countries). We can also add an (automatically-generated) URL to the Google Maps location of the address.

===Annotation===

This is certainly going to be useful for many locations

===Relationships===

Add any relationships here
* URL relationships:
** official home page -- Many locations will have an official home page; this includes studios, venues, and festivals.
** other -- Especially for festivals there will be both official and unofficial sites. Bootleg sites may also have pages with bootlegs organized by location.

* Recording events: of course we'll need to link the venues with many release events; perhaps we need a separate wiki page for discussing those.

==Discussion==

First of all I think we should make a change in terminology. It's already becoming a bit confusing by calling it a VenueAndEventProposal since we have to deal with different things like 'studio', 'festival', etc. I should have been more careful in the initial ticket. I suggest to move this page to [[Location Proposal|LocationProposal]] where a Location is a general name we can use for the lot and use this term for discussing the global concept. The location section on this page can than be changed to 'Address' which is a more accurate name for it. Except for the page move I already made the changes. -- [[User:Prodoc|Prodoc]] 13:14, 02 May 2007 (UTC)

Personally I don't think the description in the Rationale section should be the way to do it but I might be misinterpreting the last line. At the moment it seems you want to link a a venue to a release event. A release event, however, doesn't have much to do with the location. Instead, what I mean in the initial ticket was to basically be able to specify a location with the different available AR's. This will provide much more flexibility than to link it to a release event and reduce the amount of duplicate data. When you enter e.g. a Recorded By AR, there can be a location section where you can specify where it was recorded. At the same place you can already give the date when it was recorded. The idea to add the locations as a new entity next to Artist and Label remains the same. -- [[User:Prodoc|Prodoc]] 13:14, 02 May 2007 (UTC)

The Address is a tricky but very valuable part of this concept but should not be limited to just being used for the locations. I'm almost tempted to say that the address part should be the first thing we should implement separately from this location concept. The location concept can also be implemented without the address part at first. The reason for this is that, as stated above, the address part is very tricky to do right and a lot of work to collect information from different resources (lists of states, provinces, municipalities, cities, towns, etc. for each country). I got the hint to contact Russ about this since he worked on this for last.fm as well. It could save a lot of time. When we have the address functionality figured out we can implement this as part of the Artist information. This would be a smaller step and allow us to test it on a smaller scale first. By including the address functionality in the artist information you can specify the 'birth' place of an artist or group. I am, however, reluctant to allow users to specify a very accurate address in this situation. It should only be until town/city level to prevent any privacy issues. In case of a location address it can and should be as accurate as possible down to the street name and number. -- [[User:Prodoc|Prodoc]] 13:14, 02 May 2007 (UTC)
[[Category:To Be Reviewed]] [[Category:Development]] [[Category:Proposal]]

Latest revision as of 18:51, 27 August 2016