Template talk:Infobox restaurant/Archive 1

Archive 1

Street addresses and phone numbers

Please do not include street addresses or phone numbers in articles. Wikipedia is not a directory. Kingturtle (talk) 19:04, 24 June 2008 (UTC)

I've added a coordinates parameter, as seen in many other infoboxes. Using {{coord}} in this field will also add pages to the Google Earth/ Wikipedia layer. Andy Mabbett | Talk to Andy Mabbett 20:29, 21 August 2008 (UTC)

Chef

I have added a generic "chef" field, because not all restaurants use the title "head chef". Besides, the term "head chef" is redundant, like "hot water heater". The word "chef" means "chief" in French, and by English definition means "chief cook". ~Amatulić (talk) 00:01, 31 July 2010 (UTC)

I realize this is an ancient comment, but I came here to make exactly the same point: 'head chef' is meaningless. It's like saying 'head boss.' The correct term is either chef, period, or executive chef (e.g. Thomas Keller at Per Se), with either chef or chef de cuisine being the person who's actually in charge on a day-to-day basis. If there are no objections I'm going to change this soon. — The Potato Hose 17:57, 27 May 2013 (UTC)

Remove some fields?

I like to propose the removal of a two fields in this template: dress-code and reservations. In my opinion, both fields can only contain information that can be seen as advertising. Beside that, in my opinion, it is of no encyclopaedic interest. The Banner talk 18:40, 21 January 2013 (UTC)

I don't have an issue with that. --Jeremy (blah blah • I did it!) 18:49, 21 January 2013 (UTC)

Thankfully these didn't get removed. I can kinda see a point in removing the dress code field; almost no restaurant notable enough to make it in Wikipedia is going to turn people away for being improperly dressed (as long as they are dressed). But for some high end restaurants, the reservations policy is relevant and notable for the restaurant. elBulli basically had to have a lottery in their final years (2MM+ reservation requests per year for ~8K seats), Momofuku Ko only takes reservations once a day, for that day, etc etc etc. It's not advertising to state a fact. — The Potato Hose 18:02, 27 May 2013 (UTC)

To my opinion, adding reservation details is advertising. Would there by any top class restaurant without the reservation policy Reservations recommended, especially on weekends and public holidays.? The Banner talk 20:16, 27 May 2013 (UTC)

You have a point. I still don't think it should be removed, but maybe the correct solution is to note reservations policies where they are relevant (e.g. Momo, Duck, Laundry, Noma, etc). — The Potato Hose 20:25, 27 May 2013 (UTC)

Pastry Chef

I added a pastry chef Whoisjohngalt (talk) 16:59, 21 January 2013 (UTC)

Why do you think that a pastry chef should be named in this info box? The article Chef identifies identiefies 10 types of chefs, do you really think they need to be added? Is there any chance that a lower ranking chef will get a standalone article? How do you keep the info up to date? The Banner talk 18:35, 21 January 2013 (UTC)

Pastry chefs kind of work in a world of their own. While it's true that (almost) nobody is going to become famous for working in garde manger, pastry chefs are very often notable in their own right. E.g. Albert Adria, Alex Stupak, Elizabeth Falkner, etc etc. So yes, pastry chef is something that should be added here, and of course only used when that person is also notable. — The Potato Hose 17:52, 27 May 2013 (UTC)

Auuuuugh why are thos redlinks aauuuugh — The Potato Hose 18:04, 27 May 2013 (UTC)

<TEASING MODE>njek, njek, njek</TEASING MODE> Nah, I don't think they are exceptionally notable. The whole category Pastry chefs contains only 29+2 articles, including an article about the "White House Pastry Chef" (does the location where you work make you notable, don't think so. Or do we also have articles about the "White House Dish Wasser"?) The Banner talk 20:45, 27 May 2013 (UTC)

To a point, yes, where you work makes you notable in the sense that you're not going to be the White House Pastry Chef without having serious chops in the industry. I can name probably half a dozen pastry chefs off the top of my head who are notable--I listed a couple above. (Albert Adria might be an odd case though, for a lot of reasons.) In a high end kitchen (except for probably elBulli, Alinea, anywhere doing deconstructivist cooking), the pastry kitchen is a world unto itself, and in many ways might as well be its own restaurant. — The Potato Hose 20:58, 27 May 2013 (UTC)

I guess that White House Executive Pastry Chefs are already notable before they get the invitation to work in the White House. They won't hire a student fresh from catering college. The Banner talk 22:02, 27 May 2013 (UTC)

Quite. The point that I'm making is that in high-end restaurants the position of patissier is generally regarded as being the same 'rank' (in terms of achievement, not in terms of who tells who what to do) as chef de cuisine, which in most restaurants that make it to Wikipedia is not going to be the same person whose name is on the door (the executive chef; that 'head chef' nonsense above is an Americanism). — The Potato Hose 22:12, 27 May 2013 (UTC)

That is certainly true. When working in the hotel (4 stars, Irish classification) we had three kitchens: the kitchen (serving 2 restaurants and events), de barfood kitchen (serving the two bars) and the pastry kitchen. The Banner talk 23:34, 27 May 2013 (UTC) And even with three kitchens I never got the hot meals I was entitled to. For some strange reason no chef was willing to show up to serve me my dinner at 3 AM. The Banner talk 23:34, 27 May 2013 (UTC)

Hah! How did you not learn the golden rule? "Feed yourself, ain't nobody else gonna." ;)

Back on topic: shall we add pastry chef as a parameter or no? — The Potato Hose 01:44, 28 May 2013 (UTC)

I am afraid that it will lead to an avalanche of other restaurant staff to be added, like the restaurant manager, Maître d'hôtel, sommelier and owners. So, I won't see yes but also won't protest when you add it. The Banner talk 08:30, 28 May 2013 (UTC)

Proposed field - Chef patron

I'd like to propose an additional field to be added to the template - Chef patron. My reasoning is this - in the Michelin star end of the market there seems to be a growing trend where certain famous chefs will open restaurants under their names/influence but with head chefs placed there. Joël Robuchon, Gordon Ramsay, Alain Ducasse - they all do this in quite a number of restaurants. Right now we (well at least when I've done it anyway!) place the Chef patrons in the chef field, and the head chefs in the head chef field. But it seems like we could be a bit more specific and provide some greater clarity in the infobox than that. Example here: Alain Ducasse at the Dorchester. What do people think? Miyagawa (talk) 21:53, 3 September 2013 (UTC)

Former owners

We should consider adding the parameter "Former owners", or change the "Current owners" parameter to just "Owners". The "Former owners" parameter would allow the display of previous owners of existing establishments and the inclusion of owners for closed businesses. --Another Believer _(Talk) 18:51, 27 February 2014 (UTC)

Good idea. I've added |previous-owner=. It's always better to have separate fields for such things, to maintain data granularity. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:51, 27 February 2014 (UTC)

Template:Infobox restaurant not displaying name= parameter

@PrimeHunter and Frietjes:

The name= parameter of Sir and Star stopped showing up using the template:infobox restaurant. It used to show up right above the restaurant information.

The name= parameter of the hotel, The Olema, is showing up using the Template:Infobox hotel.

Infobox restaurant is embedded within infobox hotel using embedded= and embed=yes, but both names showed up for a while. I'd like to have both names displaying in their respection portions of the infobox. Please advise. Please ping me back. Thank you. Cheers! {{u|Checkingfax}} {Talk} 08:33, 14 November 2015 (UTC)

@Checkingfax: name isn't supposed to show up. Before [1] the embed parameter was ignored and it looks like there must have been an ugly design with an infobox with its own borders inside another infobox. It's supposed to look like a single long infobox with a single name as heading for the combined infobox. Template:Infobox#Optional control parameters says about the child parameter: If this is set to "yes", this child infobox should be titled but have no name parameter. It seems the solution is to allow a title parameter with title = {{{title|}}}, so the caller can use title instead of name when it's embedded. Alternatively the name parameter could be passed on as title in embeddings: title = {{#ifeq:{{{embed|}}}|yes|{{{name}}}}}. I don't know whether the latter is against infobox practice. A title parameter makes a subheading and not a big name heading. PrimeHunter (talk) 11:58, 14 November 2015 (UTC)

@Checkingfax:, I believe the philosophy is that an infobox is embedded if the two boxes are about the same entity. in this case, since the restaurant has a different name, it would seem you could just not embed the restaurant box. to make them float together, and not disrupt the left floating image, you could wrap them both inside a {{stack}}. I would have liked to see more discussion before this change, but if there are no objections, then I suppose no problem. Frietjes (talk) 13:36, 14 November 2015 (UTC)

@Frietjes and PrimeHunter: The restaurant infobox is wider than the hotel infobox and it does not center the difference. Even if it did, it looks odd. Not sure if {{stack}} would rectify the width issue. Wondering too why the hotel infobox does not have lat/long parameters. Sigh. Cheers! {{u|Checkingfax}} {Talk} 13:59, 14 November 2015 (UTC)

@Checkingfax:, {{infobox hotel}} is a redirect to {{infobox building}}, which does have lat/long parameters (see the documentation). the boxes are the same width, but the coordinates are by default not wrapped, which expands the width. here is a demonstration for you. Frietjes (talk) 14:09, 14 November 2015 (UTC)

@Frietjes and PrimeHunter: OK, that looks pretty darn good. How are the boxes the same width if the coordinates are not wrapping? I thought I wanted to move the map up, but now I don't. I like the separation of the hotel and restaurant broken up by the map. Cheers! {{u|Checkingfax}} {Talk} 14:26, 14 November 2015 (UTC)

@Checkingfax:, if the coordinates are not wrapped, then the width of the infobox is the minimum of the default width and the width of the coordinates. since the precision you are using for the coordinates is so high, you get a very long coordinates string. by adding |coordinates_wrap=yes it allows the coordinates string to wrap over two lines, which makes the infobox more narrow. let me now if you have more questions or problems. Frietjes (talk) 14:28, 14 November 2015 (UTC)

Rating → ratings

I find the "rating" parameter and its corresponding label "Rating" somewhat strange. Restaurants don't have one single rating—they have many, and a rating depends on whom you ask. For instance, the Michelin Guide rating is just one of many opinions and does not reflect any kind of truth, only the opinion of one or a few employees in a private French tire company that creates a guide whose entire raison d'être seemingly is to make people drive as much as possible for restaurants "worth a detour" or "worth a special journey" to wear out as many tires as possible (okay, maybe I took this a little too far, but I hope you get my point). To call one rating the rating is absurd, but the parameter name "rating" and the label "Rating" seems to suggest that there is only one.

I suggest changing the parameter name to "ratings" and the label to "Ratings" (of course with transitional handling of existing 'rating' parameter use; the 'rating' parameter could just be a deprecated alias for 'ratings'). Then the users of the template can insert all kinds of ratings there, including many different co-existing ratings. It would also remind the readers that it doesn't make sense to have only one rating, and that too much trust should not be put on one single rating: A rating is just one opinion among many; it's not a fact about the restaurant. --Jhertel (talk) 10:00, 13 March 2018 (UTC)

Map not working

Ben's Chili Bowl
Ben's Chili Bowl, Northwest Washington, D.C.
Location within Washington, D.C.
Restaurant information
Coordinates	38°55′01″N 77°01′43″W

Ben's Chili Bowl
Ben's Chili Bowl, Northwest Washington, D.C.

Why is this not working? It’s a stripped down testcase from Ben's Chili Bowl which is also not working. It’s got a map, and is specifying the coords as described at Template:Infobox restaurant#Map and coordinates. I could probably fix it by changing the coordinates to latitude and longitude instead, but if that’s needed then either the template is broken or the documentation is wrong. It’s only just appeared in Category:Pages with script errors but I can’t see a recent change that put it there.--JohnBlackburne^words_deeds 23:52, 15 July 2016 (UTC)

Just co confirm it works with lat + long I’ve added that below the non-working example. And there’s nothing wrong with the coord template – it displays properly in the broken infobox and I used it to find the decimal coordinates.--JohnBlackburne^words_deeds 03:49, 16 July 2016 (UTC)

JohnBlackburne, the documentation should be more clear now. basically, the template cannot parse the coordinates template, but can parse the raw numbers. there is some discussion about how to make your first example work at Village Pump. Frietjes (talk) 14:22, 12 August 2016 (UTC)

Responding a long time later: This template has been updated to support the coord template. I have updated the template to require coordinates if a pushpin map is specified. – Jonesey95 (talk) 16:11, 26 January 2018 (UTC)

I can't get the map to work either. Sheila1988 (talk) 20:03, 10 October 2018 (UTC)

 Fixed. Responding a long time later again: the map code was broken in a couple of places. I have fixed it so that it will display the map and the caption, neither of which were coded correctly. The first infobox to the right is currently showing the map and a caption. The second one shows no map or coords because it uses the no-longer-supported |longitude= and |latitude=. – Jonesey95 (talk) 12:39, 5 April 2019 (UTC)

Map errors

@Jonesey95: Would you please check the recent edit to this template with regard to these articles which are showing "Lua error in Module:Location_map at line 488: Unable to find the specified location map definition: "Module:Location map/data/[...]" does not exist."

• Frog and the Peach
• L'Atelier de Joël Robuchon (London)
• Martick's Restaurant Francais
• Ox (restaurant)
• Restaurant Andrew Fairlie
• Stortorvets Gjæstgiveri

Sorry I can't look myself at the moment. Johnuniq (talk) 08:44, 6 April 2019 (UTC)

All fixed. Thanks for the note. They just had invalid map names in the infobox. I was able to find valid map names using this search page. (P.S. The invalid map names were in these articles for a while, but since the mapping code didn't work, the error messages did not appear. See sections above.)– Jonesey95 (talk) 21:37, 6 April 2019 (UTC)

Edit request: Add "postal_code_type" field

@Muboshgu, Onesey95, Hameltion, MusikAnimal, and Jonesey95: Greetings and felicitations, recent (loosely speaking) editors. Since this template includes a postal code field ("postcode"/"zip", displayed as "Post code/ZIP Code" (sic)), would someone please be so kind as to add a "postal_code_type" field, as is used in Template:Infobox settlement? As it currently is, it looks a bit clumsy. —DocWatson42 (talk) 08:55, 29 February 2020 (UTC)

Hello? —DocWatson42 (talk) 09:02, 4 April 2020 (UTC)

Done as |postcode-type= to match the format of other parameters. Feel free to update the documentation. If there is some way to verify that all uses of |postcode= should render as "Postal code" and all uses of |zip= should render as "ZIP code", I can probably automate that instead of someone having to add postcode-type to every article. |postcode-type= could then be used for anything other than "Postal code" or "ZIP code". – Jonesey95 (talk) 17:15, 4 April 2020 (UTC)

Thank you. ^_^ Though I'll note that it's "ZIP Code"—see the article's first four references. —DocWatson42 (talk) 04:03, 10 April 2020 (UTC)

Yes, that's how it renders. I typed it wrong above, but the template should have the correct capitalization. – Jonesey95 (talk) 04:25, 10 April 2020 (UTC)

Okay. :-) —DocWatson42 (talk) 05:35, 13 April 2020 (UTC)