Paul Lunde : Searching the internet, Google Scholar, and my university library I was able to find two reviews of works by Lunde, [31] and [32] , but which don't discuss Lunde himself or his role in the works at all.  When considering the case for WP:NACADEMIC , both of the reviews I would describe as faint praise for the works, nor is there any evidence of a high h-index despite publishing extensively.  One of Lunde's primary outlets has been Aramco World described as follows in an Indiana University paper [33] : As Aramco World approached its fiftieth anniversary in November 1999, a retrospective feature touted the cosmopolitan ethos of the publication in its very founding, as it supposedly emerged from Aramco's culturally sensitive priorities.  Presuming a fundamental chasm between US Americans and Saudis, the magazine sought: "to bridge the natural but enormous cultural gaps between its expatriate, largely American, workers and their Saudi counterparts and hosts … "7 Founded in 1949 in New York, Aramco World was modeled after other contemporaneous US publications like Life and Saturday Evening Post.8  In 1964, it shifted its publication headquarters from New York to Beirut, where it remained until the beginning of the Lebanese Civil War in 1975.9.. .n the case of Aramco World, for example, tight Saudi control of the magazine's contents remained in place (as it does to this day), even though the magazine was being produced in Lebanon to, in part, present an ostensibly localized and authentic—rather than propagandistic—picture of the region.12 ; -- in other words, at best a general interest magazine, at worst a propaganda venture.  In the absence of biographical sources about Lunde, I'm not seeing a case for notability.  signed, Rosguill talk 04:37, 3 June 2023 (UTC) [ reply ] Note:  This discussion has been included in the deletion sorting lists for the following topics: Authors , Saudi Arabia ,  and California .  signed, Rosguill talk 04:37, 3 June 2023 (UTC) [ reply ] Delete - Does not meet WP:GNG , WP:NSCHOLAR or WP:NAUTHOR .  Onel 5969 TT me 09:22, 3 June 2023 (UTC) [ reply ] Keep Lunde's books have been published by major publishers including Dorling Kindersley and reviewed in a number of independent, reliable publications including Library Journal (with multiple reviews in this publication including one from 2004 of his Organized Crime book and one from 2009 for The Book of Codes), Kirkus Reviews (2009 review of Book of Codes), Publishers Weekly (2002 review of Islam: Faith, Culture, History plus discussion of the book in a separate PW article), National Geographic's History Magazine (2009 review of Codes), and The Middle East Journal (2002 review of Islam), His work is also reviewed and cited in a number of other places, with all of these citations accessible through the Wikipedia Library.  In short, there are easily enough reliable and significant secondary sources to prove notability for creative professionals . -- SouthernNights ( talk ) 14:20, 4 June 2023 (UTC) [ reply ] Relisted to generate a more thorough discussion and clearer consensus.  Please add new comments below this notice.  Thanks, L iz Read!  Talk!  05:43, 10 June 2023 (UTC) [ reply ] Keep - I agree, there are plenty of reviews of his work and the fact that his books were published by Penguin and other reputable publishers should be evidence enough of his scholarship.  131.111.5.176 ( talk ) 15:50, 12 June 2023 (UTC) [ reply ] Relisted to generate a more thorough discussion and clearer consensus.  Relisting comment: More input from experienced editors would be helpful… Please add new comments below this notice.  Thanks, CycloneYoris talk!  08:55, 17 June 2023 (UTC) [ reply ] Keep Agreed and it has notable publishers.  CastJared ( talk ) 11:19, 17 June 2023 (UTC) [ reply ] The above discussion is preserved as an archive of the debate.  Please do not modify it.  Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review ).  No further edits should be made to this page.

Discussion outcome: keep