Template:MuGlobe/genre: Difference between revisions

@@ Line 1: / Line 1: @@
-This is the published first-pass outline for '''Genre''' articles on MuGlobe.com, extrapolated from Ed's Country template at his request on October 17, 2026.
+Genre article outline and catalogue policy.
-Required sections must contain substantive text. Optional sections may be omitted; when included they must contain substantive text. Keep sections in the listed order. Subheadings are allowed within each section. Cite sources and use representative musical examples where available.
+Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.
-* '''Summary:''' Introduce the genre and its recognizable musical identity.
+Published instructions and table fields are retained in the native protected definition. The latest October19 catalogue policy supersedes the former ten-year exclusion and introductory-sample limit.
-* '''Contemporary and trending:''' Describe its present musical life and recent developments; acknowledge limited or revival activity where appropriate.
-* '''History:''' Explain origins, development and influences without inventing a single birthplace or date when these are uncertain.
-* '''Musical characteristics:''' Describe rhythm, instruments, singing, form or dance in approachable language.
-* '''Geography and communities:''' Distinguish origin, later adoption and diaspora scenes, linking countries and regions.
-* '''Artists:''' Introduce representative musicians and groups and examples of their music.
-* '''Related genres (optional):''' Explain useful connections and distinctions.
-These are editable editorial guidelines. Existing articles retain their recorded template version until deliberately migrated.
+== Recording curation fields ==
+All media rows use sixteen columns, ending with '''MuGlobe favorite''', '''Current hit''' and '''Authentic'''. Each cell contains a canonical <nowiki><muglobe-flag video="VIDEO_ID" field="muglobeFavorite" /></nowiki> tag (use field currentHit and authentic for the next cells). Click the displayed value to edit through [[Special:RecordingCuration]]. Only superadministrators can save these independent, global recording flags. New recordings default false; never infer editorial approval from metadata. Native curation revisions are authoritative and project to the playback database.
@@ Line 2: / Line 2: @@
 	"id": "genre",
 	"label": "Genre",
-	"version": 6,
+	"version": 14,
 	"published": true,
 	"sections": [
@@ Line 52: / Line 52: @@
 			"requireContent": true,
 			"allowSubsections": true
+		},
+		{
+			"key": "representative-performances",
+			"label": "Representative performances",
+			"level": 2,
+			"required": true,
+			"requireContent": true,
+			"allowSubsections": true,
+			"starter": "Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{| class=\"wikitable\"\n|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain available for listening with truthful descriptive metadata.\n\n{| class=\"wikitable muglobe-performances\"\n|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note !! MuGlobe favorite !! Current hit !! Authentic\n|} Every recording row has sixteen columns, ending with MuGlobe favorite, Current hit and Authentic. Use canonical \u003Cmuglobe-flag video=\"VIDEO_ID\" field=\"muglobeFavorite\" /\u003E, currentHit and authentic tags. These independent global booleans default false; only the superadministrator changes them through Recording curation. Duplicate video IDs share flags. Preserve original music, evidence and start offsets."
 		},
 		{
@@ Line 60: / Line 69: @@
 			"requireContent": true,
 			"allowSubsections": true
+		},
+		{
+			"key": "hotspot-mushrooms",
+			"label": "Hotspot mushrooms",
+			"level": 2,
+			"required": true,
+			"requireContent": true,
+			"allowSubsections": true,
+			"starter": "Mushrooms describe our understanding of a musical landscape. Identify the broad heartland, connected communities and distinct adopted scenes first, then use the fewest useful circles to represent them. Nearby cities often sample one shared region: include the countryside and smaller communities between them instead of drawing a separate mushroom for every documented city. A center may lie between cities. Use Notes to explain the regional judgment.\n\nEach row defines one circular field. Location describes the represented area; latitude and longitude are decimal degrees, with south/west negative. Strength is from 0 to 1. Radius is in kilometers (0.01 to 5,000) and marks the distance where the field reaches zero, not the edge of a uniformly strong core. Make it large enough that the heartland and its intervening communities remain strong, then review transitions on the globe. Overlapping mushrooms of this genre combine by their strongest contribution.\n\nAdd, remove or revise ordinary table rows. Keep each surviving ID stable and use this genre's lowercase identifier followed by a descriptive region name. The table has no per-mushroom source requirement: it records informed judgment, experience and synthesis. Article references and broader research can explain the context. The numbers are editorial map settings, not listener percentages. Compilation remains a deliberate operation.\n\n{| class=\"wikitable muglobe-hotspots\"\n|+ MuGlobe hotspot mushrooms\n! ID !! Location !! Latitude !! Longitude !! Radius (km) !! Strength !! Notes\n|}"
 		}
 	],
-	"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples."
+	"instructions": "Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes. Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use.  Representative recordings use the required listening-profile and thirteen-column performance tables, with evidence and explicit uncertainty. Historical is descriptive age information, not an exclusion from listening. Keep native revisions authoritative and compilation deliberate."
 }

Latest revision as of 02:36, 22 October 2026

Genre article outline and catalogue policy.

Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.

Published instructions and table fields are retained in the native protected definition. The latest October19 catalogue policy supersedes the former ten-year exclusion and introductory-sample limit.

Recording curation fields

All media rows use sixteen columns, ending with MuGlobe favorite, Current hit and Authentic. Each cell contains a canonical <muglobe-flag video="VIDEO_ID" field="muglobeFavorite" /> tag (use field currentHit and authentic for the next cells). Click the displayed value to edit through Special:RecordingCuration. Only superadministrators can save these independent, global recording flags. New recordings default false; never infer editorial approval from metadata. Native curation revisions are authoritative and project to the playback database.