Talk:WBGI (AM)

Latest comment: 2 years ago by Wcquidditch in topic Proposed merge of WBGI (AM) with WBGI

Article's extensive wikipedia issues edit

There are several problems with this article.

The extensive quote of what is likely the entire article from the newspaper is probably a copyright violation issue. Attribution is not a substitute for permission. The Pittsburgh Tribune Review is available on microfilm at the Carnegie Library in Pittsburgh, but its limited availability makes it not a very useful source for editors to verify the content.

The quote is then used to justify making conclusions about the condition of the station that are not readily seen in the source material, hence it is original research, where the author used sourced material to draw inferences and state conclusions that were not directly stated in the source material.

The text reads like it was written by someone who was personally involved with some aspect of the station, which creates a presumption of a difficulty presenting a neutral point of view on the subject matter.

Finally, the subject of this article is WYJK-AM, not the history of Mar Com communications or Keymarket - the companies that owned it and all of their business activiies in other stations they owned.StreamingRadioGuide (talk) 22:53, 8 February 2009 (UTC)Reply

Proposed merge of WBGI (AM) with WBGI edit

How did we end up with two articles for the same station? (And *both* titled at more-or-less the same call sign; usually when this happens it is an earlier phase of the station's history having a separate article from the current one.) Merging them may be more complicated than usual, though — WBGI is clearly the more-developed article and has the longer article history, but WBGI (AM) has the more-correct title, as there is also a still-operational WBGI-FM. (Combined with the Malaysian airport that has a hatnote on pretty much all the WBGI radio station articles, there should really be a disambiguation page at WBGI when the dust settles.) WCQuidditch 02:25, 26 April 2022 (UTC)Reply