Jump to content

Template talk:Infobox museum/Archive 1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1Archive 2

Coordinates

Would anyone object to having the coordinates display in the infobox when entered as "latitude" & "longitude", as they currently do if entered as "coordinates"? Andy Mabbett 10:43, 21 May 2007 (UTC)


I suggest using the coord template in the infobox, setting the display parameters to "inline,title". papageno 14:53, 23 October 2007 (UTC)
Apologies, I see coord is already invoked by the infobox. Is there any reason why coord could not be used directly in the Infoxbox field? That would allow contributors to use additional parameters for coord like scale and region. papageno 14:58, 23 October 2007 (UTC)
the scale part could be omitted, by adding |type:landmark, the obvious choice for a museum, and it has a default scale. --Qyd (talk) 20:53, 5 March 2008 (UTC)

Space

We need to get rid of the huge gap between location and website.--NeilEvans 22:55, 2 August 2007 (UTC)

map caption

{{editprotected}} 

{{!}} colspan="2" style="font-size: smaller; text-align: center;" {{!}} <center>{{Location map|{{{map_type}}}|lat={{{latitude}}}|long={{{longitude}}}|width={{{map_size|220}}}|float=center|border=none|caption={{{map_caption|Shown within {{{map_type}}}}}}}}}}</center>

font-size: smaller; makes for a tiny font, hardly readable. could this part be removed? --Qyd (talk) 20:49, 5 March 2008 (UTC)

 Done Doesn't seem to have been any opposition. Happy‑melon 20:13, 16 March 2008 (UTC)

remove extra newline

{{editprotected}} Please remove an extra newline between the end of the template and the beginning of <noinclude>. Because of this, some pages looks poor (e.g. National Archaeological Museum of Athens). Then replace {{template doc}} with {{documentation}}, if possible. --58.89.68.123 (talk) 16:22, 12 March 2008 (UTC)

Done! --Kralizec! (talk) 17:39, 12 March 2008 (UTC)

Merge from {{Infobox Turkey museum}}

I say go for it. We can't have one for every country. --Adoniscik(t, c) 17:03, 27 March 2008 (UTC)

I remember that I created the template especially for the collection size feature. I know I have not used the feature so far, but is it possible to add the feature to this template? Then there will be no need for the other one. Thanks. --Chapultepec (talk) 04:18, 30 March 2008 (UTC)

? add to project cat WikiProject Museums

As editing on this template is locked I though I would ask here whether it could be added to Category:WikiProject Museums templates. WikiProject Museums is a very new wikiproject & we are still getting a feel for all the relevant articles, templates, lists etc which are relevant - you would be very welcome to join & help.— Rod talk 15:35, 31 March 2008 (UTC)

I support this request. --ThT (talk) 13:33, 10 January 2013 (UTC)
Categories are added via the template's documentation; in this case Template:Infobox museum/doc. These are not protected, so you could do that yourself; but I've done it on this occasion. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:43, 10 January 2013 (UTC)
Thanks! (I have no idea what the above means but appears to be an improvement) StarM 05:30, 20 January 2013 (UTC)

Website required

Not all museums have a website! This should be optional. Mjroots (talk) 08:51, 21 April 2008 (UTC)

I fully agree. Quite daft as it stands: type of museum is optional, but website is required. Hmm... Pyrope 14:57, 7 May 2008 (UTC)
Done. Plastikspork ―Œ(talk) 00:53, 7 February 2010 (UTC)

Help with displaying a map

Maybe someone can help with the new infobox on Wellcome Collection. I have tried to work out how to display a map but had to give up. I guess the trick is the right entry in the map caption field, it's not clear what this should be. ProfDEH (talk) 11:36, 3 May 2008 (UTC)

Tis done "Greater London" is the most appropriate map I think?— Rod talk 13:43, 3 May 2008 (UTC)
Thanks - but is there a central London option? ProfDEH (talk) 09:25, 4 May 2008 (UTC)
The list of maps which can be used is at Template:Location map but to see what the UK ones look like see Template talk:Infobox UK place/maps. I would suggest talking to User:Jza84 who is much more expert on (UK) maps than I am.— Rod talk 10:01, 4 May 2008 (UTC)

Minor typographical edit

Could <th>Visitor figures</th> be changed to <th>Visitor&#160;figures</th> so that the 'Visitor figures' label doesn't break over two lines? That would improve the infobox layout on pages like National Media Museum. Frankie Roberto (talk) 13:26, 29 May 2008 (UTC)

Image caption

I am unable to caption my image at Boeing Galleries.--TonyTheTiger (t/c/bio/WP:CHICAGO/WP:LOTM) 14:57, 11 June 2008 (UTC)

The infobox doesn't support one for some reason, I won't add one as I don't know about consensus (or anything about this template TBH)...... Dendodge .. TalkHelp 17:00, 11 June 2008 (UTC)

Public transit required?

Why is public transit a required field? Many museums are nowhere near public transit. —D. Monack talk 18:40, 25 July 2008 (UTC)

No longer required. Plastikspork ―Œ(talk) 00:54, 7 February 2010 (UTC)

Architect

I would like support for architect. Thanks. Americasroof (talk) 03:06, 21 October 2008 (UTC)

Me too - tend not to use this template as it stands since it is lacking this key field; less diurnal than the curator field; would certainly be great to have support, thanks, Maculosae tegmine lyncis (talk) 18:04, 8 March 2012 (UTC)
 Not done Request not specific enough; please indicate the code that is to be changed, and establish consensus before making an edit request.  Sandstein  12:51, 14 July 2012 (UTC)

Architect/architecture

MTL you raised a great point four months ago re: architect, which seems to go unanswered.
"Complete and specific description of the request": there are several fields in Template:Infobox building related to architecture that are absent from Infobox Museum -- all of them quite basic to museums, at least the museums I've worked at. E.g.: Museum of Modern Art re: renovations. Museum buildings frequently have an identifiable architectural style, are built over a period of years, and are not simply "opened" to the public. Height, floor count, and floor area are also conspicuously missing from this infobox. I propose adding the fields below, but there could be more in Infobox building that are important, also.
  1. | architectural_style =
  2. | groundbreaking_date =
  3. | start_date =
  4. | completion_date =
  5. | opened_date =
  6. | inauguration_date =
  7. | renovation_date =
  8. | height =
  9. | floor_count =
  10. | floor_area =
  11. | architect =
  12. | architecture_firm =
Prburley (talk) 18:46, 10 July 2012 (UTC)

map_type instructions missing

It currently gives caption instructions.

Should probably say something like:

  • map_type

The Location Map (see template:Location map to be used for locating subject on map)

Hohum (talk) 20:27, 28 October 2008 (UTC)

Alt attribute in infobox image

{{editprotected}} As per WP:ALT and WP:ACCESSIBILITY this template should support alt text for the image in the infobox. Could you please install this obvious edit to the template? I've tested it with the MOMA article and have already updated the documentation. Thanks. Eubulides (talk) 18:13, 26 June 2009 (UTC) (Updated, so that we have alt text for the map too.) 18:38, 26 June 2009 (UTC)

Done. --- RockMFR 19:50, 26 June 2009 (UTC)

Car park field

Should we have a field, similar to the "publictransit" one, for "car_park", to allow the details of the nearest car park to be added? Some city museums do not have a private car park, so details of where the nearest one is may be very useful for motorised visitors. -- de Facto (talk). 19:25, 26 June 2009 (UTC)

As there's been no reply to this in two years, please add a field named "car_park". Purpose: The nearest car park available for visitors. -- de Facto (talk). 08:45, 9 July 2011 (UTC)
I'm not sure the purpose of Wikipedia is primarily for visitor information (for which editors can click through to the museum's website). But as there has been no opposition in two years I have added the field. Could you update for documentation to the template? — Martin (MSGJ · talk) 16:37, 12 July 2011 (UTC)
Thanks, and documentation updated. -- de Facto (talk). 20:12, 12 July 2011 (UTC)

Map

I says "map_type: Name used to construct location map; see {{Location map}}". Please explain with example. It took too much to figure out that map type should = "India Mumbai", and not "Location map India Mumbai" on Chhatrapati Shivaji Maharaj Vastu Sangrahalaya--Redtigerxyz Talk 13:11, 13 July 2009 (UTC)

Conversion to {{Infobox}}

Would there be any objections to converting this template to use the {{Infobox}} meta-template? This would simplify the code and ease future maintenance. I have already prepared the code at {{Infobox Museum/sandbox}} and a comparison between current and new is available at {{Infobox Museum/testcases}}. PC78 (talk) 20:47, 23 August 2009 (UTC)

I think it's a good idea. For simplicity and future maintenance, perhaps you could standardise the network parameter too. It follows a convention that AFAIK is unique among infoboxen: it requires the existence of a companion template named "Template:Infobox Museum x network" (e.g. {{Infobox Museum Tate network}}). According to this, editors have gone to to the trouble of figuring out this convention only three times. I think "network" should be like the other parameters, so that (for example), Carnegie Museums of Pittsburgh could be supplied as the argument. Thanks. 72.244.207.235 (talk) 22:45, 24 August 2009 (UTC).
That may be down to poor documentation more than anything else. PC78 (talk) 23:09, 24 August 2009 (UTC)
Agreed, the documentation is poor. I thought the switch to the meta-template was motivated by an interest in simplicity and maintainability? Isn't the way that network works the same thing, and not just documentation? 72.244.207.235 (talk) 00:50, 25 August 2009 (UTC).

If I understand you correctly, you're suggesting that instead of using these subtemplates we input the data they contain manually, e.g. rather than: 

| network = Tate

which activates the subtemplate, we create the same effect without the subtemplate by entering something like: 

| network_header = [[Tate]]
| network_data = {{nowrap begin}}
[[Tate Britain]]{{·wrap}} [[Tate Liverpool]]{{·wrap}} [[Tate Modern]]{{·wrap}} [[Tate St Ives]]{{nowrap end}}

Is that correct, or have I misunderstood you? If so then I'm not sure how it would be an improvement, as it would require entering more data into the infobox with no easy way of keeping it standardised across that group of articles. For what it's worth, the updated version of {{Infobox Museum}} would use new versions of these templates (i.e. {{Infobox Museum/Tate network}} instead of {{Infobox Museum Tate network}}) which are actually (IMO) more straightforward. PC78 (talk) 15:23, 25 August 2009 (UTC)

If network is really not to your liking (I created the parameter and the three templates) another option could be to have separate templates for each network directly beneath the infobox and of the same width (300px or so). This could then be omitted where there is already a navbox at the bottom providing the links, e.g. the pages for the four Tates (example). Ham 20:51, 25 August 2009 (UTC)
Wouldn't those articles always have the navbox, though? That would mean these templates not being used at all. PC78 (talk) 22:56, 25 August 2009 (UTC)
In the case of Tate, yes, there wouldn't be a template. But there are no navboxes for National Museum of Science and Industry, Carnegie Museums of Pittsburgh etc. Ham 20:18, 26 August 2009 (UTC)
Hmmm, looking at National Railway Museum I see someone is using the template at the foot of the article as a makeshift navbox? Perhaps navboxes are a better way of doing this sort of thing? Anyway, the current setup doesn't bother me, I'm just looking for a bit of clarification from the anon user above as to what is being suggested. PC78 (talk) 21:26, 26 August 2009 (UTC)

{{editprotected}} No objections to converting the infobox, so please update using the code at {{Infobox Museum/sandbox}}. |network= parameter (discussed above) should stay as it is for now until someone can devise a better alternative. Please also move the template to {{Infobox museum}} per capitalisation guidelines at MOS:INFOBOX. Cheers! PC78 (talk) 13:18, 3 September 2009 (UTC)

 Done, with a few tweaks. One query: the documentation doesn't say that website is required, although your code made it so. — Martin (MSGJ · talk) 13:59, 3 September 2009 (UTC)
Thanks, but check the documentation again: "all are optional except for name, established, location, and website". ;) Not sure about the |name= parameter; I'm personally not a big fan of having those links in infoboxes. PC78 (talk) 22:37, 3 September 2009 (UTC)

{{editprotected}} Can we lose the line 

| name           = Template:Infobox museum

It's not necessary, and not standard practise for an infobox. Cheers! PC78 (talk) 20:24, 7 September 2009 (UTC)

I've done it, but I think I'll look into a method of making these navbars user-customisable because many users, myself included, find them useful. — Martin (MSGJ · talk) 07:42, 8 September 2009 (UTC)

Fix microformat

{{editprotected}}

Please change: 

| subheaderclass = fn org
| subheaderstyle = font-size:125%; font-weight:bold;
| subheader      = {{#if:{{{native_name<includeonly>|</includeonly>}}}|''{{{native_name}}}''}}

to: 

| subheaderstyle = font-size:125%; font-weight:bold;
| subheader      = {{#if:{{{native_name<includeonly>|</includeonly>}}}|''<span class="nickname">{{{native_name}}}</span>''}}

to fix this template's hCard microformat; and add: 

| class7 = agent
| class8 = agent
| class9 = agent

to add additional hCard properties. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 00:24, 11 September 2009 (UTC)

Would you not just want to set |subheaderclass=nickname? PC78 (talk) 00:38, 11 September 2009 (UTC)
No, because that would include the italicisation markup. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 01:05, 11 September 2009 (UTC)
Done. — RockMFR 01:46, 11 September 2009 (UTC)

Thank you. Sorry to come back so quickly, but please now change: 

| subheader      = {{#if:{{{native_name<includeonly>|</includeonly>}}}|''<span class="nickname">{{{native_name}}}</span>''}}

to 

| subheader      = {{#if:{{{native_name<includeonly>|</includeonly>}}}|''<span class="nickname"{{#if:{{{native_name_lang|}}}| lang="{{{native_name_lang}}}" xml:lang="{{{native_name_lang}}}"}}>{{{native_name}}}</span>''}}

to allow the language of the native name to be set. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 11:13, 11 September 2009 (UTC)

 Done — Martin (MSGJ · talk) 13:21, 11 September 2009 (UTC)

Dutch interwiki

I don't have the rights to edit this template, so I post it here: the Dutch Wikipedia also has an nl:Sjabloon:Infobox museum. Could someone please add this one to the interwiki list? Thanks, Afhaalchinees (talk) 20:30, 5 October 2009 (UTC)

Done, but interwiki links go on the /doc subpage which is not protected. PC78 (talk) 21:00, 5 October 2009 (UTC)

Please add de:Vorlage:Infobox Museum. Editprotection is enabled, so I cannot add it. --Scriberius (talk) 14:35, 1 November 2009 (UTC)

See above. Interwiki's go on the /doc subpage which is not protected. PC78 (talk) 14:57, 1 November 2009 (UTC)

Lose the style overrides

This template needlessly overrides some of the {{infobox}} defaults with the bodystyle and subheaderstyle attributes. Is there any need to do this? If not, they should be removed. Chris Cunningham (not at work) - talk 19:12, 3 November 2009 (UTC)

{{editprotected}} As there's been no reply to this, please remove the bodystyle and subheaderstyle lines from the infobox. They serve no purpose but to arbitrarily give this template a nonstandard styling. Chris Cunningham (not at work) - talk 11:36, 24 March 2010 (UTC)

 Done — Martin (MSGJ · talk) 12:22, 24 March 2010 (UTC)

Add to other infobox template categories

Please add this template to Category:Organization infobox templates. Jllm06 (talk) 21:37, 6 January 2010 (UTC)

Done. FYI, categories are addedto the /doc subpage which is not protected. Regards. PC78 (talk) 02:00, 7 January 2010 (UTC)

Problem with Internet Explorer

{{editprotected}} Take a look at Wikipedia:Help_desk#How to eliminate large white space?. We have to replace the current version with this code: User:Basilicofresco/test2. Basilicofresco (msg) 17:48, 1 February 2010 (UTC)

According to my tests (Template:Infobox museum/testcases2), although your version is better, there is still a large space between the photo and its caption. I suspect there is something else behind this problem ... — Martin (MSGJ · talk) 20:31, 1 February 2010 (UTC)
It's the map that's missing in Internet Explorer. I'll continue to look into this. — Martin (MSGJ · talk) 20:32, 1 February 2010 (UTC)
I have no idea. The disappearing map seems to be a separate issue, so I've installed your fix. — Martin (MSGJ · talk) 13:15, 2 February 2010 (UTC)

Coordinates move

Why have the coordinates been moved out of the infobox? Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 17:29, 27 February 2010 (UTC)

See the section above, which was alluded to in the edit summary. Chris Cunningham (not at work) - talk 13:12, 2 March 2010 (UTC)

region code for coordinates?

I don't see any way to provide a region code for the coordinates link. According to Template:Coord/doc, the region code is used to select appropriate map resources. Is there any interest in adding a parameter to {{Infobox museum}} for this purpose? --Stepheng3 (talk) 02:02, 18 March 2010 (UTC)

OK, so no interest (other than my own). Does anyone object to adding an optional parameter to do this? Probably named iso_region, to match {{Infobox building}}. The parameter would have no effect what the user sees; it would simply pass a region code to {{Coord}}. I would, of course, take care of documenting the new parameter. --Stepheng3 (talk) 16:52, 24 March 2010 (UTC)
Go for it. Matching existing template parameters is good practice, too. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 19:57, 24 March 2010 (UTC)
Looking further, I see that the coordinates_type= parameter can be used to achieve the effect I was looking for, so no additional parameter is needed. --Stepheng3 (talk) 19:12, 17 April 2010 (UTC)

Network

Maybe I'm just stupid, but in trying to set up an infobox I could not get "network" to work, though it is documented. I noticed that no museum I looked had this information, so I decided to look at the source, and it does not seem to exist. First, isn't this a field that SHOULD work? Second, if it's not supposed to work, then shouldn't the documentation be updated? I can't edit this, so someone else will need to fix it one way or the other. Donlammers (talk) 00:18, 26 July 2010 (UTC)

I was surprised myself when I tried to add an ASTC museum to its network. First, I put network=ASTC on a page and saw that it called for a new template. I created the template and saw that it got included twice. There's magic to be done, so I went here to find the other networks permissible. It looks like the creators of the network envisaged a short list of museums in the member network - not exactly the case for ASTC with its hundreds of members. I have created Template:Infobox museum/ASTC network to make it work, though I'm not entirely happy with the result. See U.S. Space & Rocket Center. By the way, it is also a Smithsonian affiliate. Multiple networks would then require a special template or a change to Infobox museum to support multiples. -- ke4roh (talk) 02:12, 20 April 2011 (UTC)
It's true that I created the network parameter with quite small networks in mind. Larger networks of museums I imagined having a dedicated template at the bottom of the page, so as to avoid visual clutter. I notice ASTC has museums in over 40 countries – that's huge! There it would seem appropriate to do as ke4roh has already done, but instead of having a link to ASTC's webpage, perhaps a link to a full list on Wikipedia, plus perhaps a template at the bottom of the page? On my talk page, ke4roh, you mentioned different kinds of sub-template for small and large networks; could you perhaps elucidate how you think the large ones would look? Drop-down lists would be a good idea for both but I think some networks, like ASTC, would be too big for an infobox template. Or perhaps they could be broken down, e.g. a sub-template for "ASTC institutions in the United States". I am all for multiple network parameters. Ham 09:43, 21 April 2011 (UTC)
Thanks, Ham. I wouldn't expect us to be able to maintain an accurate list of ASTC members because they change quarterly or so. On the other hand, the ASTC template could add a category from which all its listed members could be found. My latest thought for the appearance of large networks was more like "Network(s): ASTC (members), Smithsonian (members)". Another idea would be to have a banner (shaded row with bold text) saying "Network(s)" and enumerate each on a line similar to above, though I'm not entirely sure how to integrate either with the existing concept of smaller networks. Could we perhaps dispense with the notion of enumerating each of the smaller member museums in favor of collecting all the lists in categories? That would simplify the problem somewhat, at the expense of the lovely short member list. In short, I've got ideas, but I'm conflicted on how best to implement. -- ke4roh (talk) 12:29, 21 April 2011 (UTC)
How about a nav box for the small networks and the infobox with a "networks" heading for the large ones? -- ke4roh (talk) 19:57, 22 April 2011 (UTC)

Edit Request

Please add a paramater to the template to enable a label for the red dot on the map. Example: San Antonio Museum of Art. It looks odd with no label on the dot. A caption for the map has a parameter, but there is no parameter to label the dot on the map. I am in the process of creating a new page for a museum, and I would like to place a label beside the dot on the map, like this: Loyal Valley, Texas.

Maile66 (talk) 18:40, 10 September 2011 (UTC)
Code is in the sandbox (diff). — Bility (talk) 20:03, 10 September 2011 (UTC)
You lost me on this one. I've never known what to do with a template sandbox. How do I adapt this to what I want? Actually, I've been hoping the template would be changed, so that it will be more than just my immediate need. That anytime an editor comes across an article with this template without the label, they can just Edit the article and stick it in. Maile66 (talk) 20:25, 10 September 2011 (UTC)
You don't have to do anything with the sandbox, I just added the label parameter to make it easy for the responding admin to update the template. And yes, once it's updated any editor will be able add labels in articles where {{infobox museum}} is used. — Bility (talk) 17:25, 12 September 2011 (UTC)
Very good. Thanks for your attention to this. Maile66 (talk) 19:22, 12 September 2011 (UTC)
 Done — Martin (MSGJ · talk) 14:27, 13 September 2011 (UTC)

Edit Request for Entity

Would it be possible to add a parameter to display the entity that owns and/or manages the museum? For example, some museums are managed by private organizations, others by city govt, by state govt, etc. Thanks, Mercy11 (talk) 00:21, 26 October 2011 (UTC)

Are there any objections to this? Otherwise I can fulfil the request. Mercy11: can you make the required change to Template:Infobox museum/sandbox in preparation? — Martin (MSGJ · talk) 17:30, 13 December 2011 (UTC)
Required change made! (This was my first time modifying a template, so I don't know if I did it right! - sorry) Thanks, Mercy11 (talk) 13:33, 9 March 2012 (UTC)
No you can't have label110 (I think only up to 80 is supported). If you want it to appear between 10 and 11 you will have to renumber all of the ones above 11 and then make the new one number 11! — Martin (MSGJ · talk) 09:41, 8 June 2012 (UTC)
Martin, I am not sure what you are talking about. I am not arguing with you, I just want you to understand I do not know how these templates, etc, work and how they link to one another, etc, despite my attempt to do contribute in fulfulling what was asked of me above.
You might say "you can't have label 110" and that's OK with me, but I have no clue what you mean. (Please don't try to explain it; I have studied the infobox, the templates related and linked to it, etc, and I just can't get it.) What I do know is this much: I would like to see that the museum infobox gets a new field called "entity" or something similar where non-technical editors (like me) can enter info related to who owns or manages the museum. This should be a simple implementation for someone that has worked with this template. Hope this helps show that what has been requested of me is too technical and I dont feel capable of fulfilling. Thank you, Mercy11 (talk) 13:18, 27 June 2012 (UTC)

I have disabled the request, because there was no response. — Martin (MSGJ · talk) 19:46, 10 June 2012 (UTC)

Actually I have reactivated it, because my request went unanswered 3 months (March 9 thru June 8) w/o receiving an answer, then it was disabled just 2 days (June 8 - June 10) after a response was finally received. Pleas see above. Mercy11 (talk) 13:18, 27 June 2012 (UTC)
Not done: The problem is that two parameters are invalid. Here is the code:
| label10         = Curator
| data10          = {{{curator<includeonly>|</includeonly>}}}

| label110        = Owner
| data110         = {{{owner<includeonly>|</includeonly>}}}

| label11        = Public transit access
| data11         = {{{publictransit<includeonly>|</includeonly>}}}
For any given |labeln= or |datan= parameter, the value of n cannot be more than 80 - here we have 10, 110, 11, so the middle pair is invalid. --Redrose64 (talk) 14:34, 27 June 2012 (UTC)
Thanks for the response. However, I am not a programmer and don't understand template scripting as I indicated HERE. Seems there has been no objections to the merit of my request per se. Could you add an "owner/entity" field to the template? I don't mind if the number you use is 110 or 80 or something else. Thanks. Mercy11 (talk) 14:55, 27 June 2012 (UTC)
The order of display is not determined by the order in which the parameters are physically placed, but by the row number n used for the |labeln=/|datan= parameter pair. The higher the row number, the lower down the row will appear; the highest presently in use is 15, so a number of 16 or higher will cause the new row to appear at the bottom.
I take it that you wish the new row to appear between Curator and Public transit access. Is that the case? If so, we need to renumber Public transit access and all the rows below it to create a suitable gap. --Redrose64 (talk) 15:30, 27 June 2012 (UTC)
I really didn't think about where it should appear. I can leave that up to the rest of this community. Also, I see that WOSlinker has been successful at getting the sandbox to display Owner. It looks great!! If this can be made permanent, it would be wonderful. Thank you. Mercy11 (talk) 18:33, 27 June 2012 (UTC)
I've updated the sandbox so that that owner has beter numbers for label & data. Mercy11, do you want to check that it does what you want it to? -- WOSlinker (talk) 15:51, 27 June 2012 (UTC)
It looks wonderful!!! What else can I say, that's what I was trying to accomplish. Thank you very much!! Hopefully they can implement this if no one objects. I already have 13 museums where I can use this. Thanks once again! Mercy11 (talk) 18:33, 27 June 2012 (UTC)
Done, see here. --Redrose64 (talk) 18:59, 27 June 2012 (UTC)

Sync sandbox

Please sync from the sandbox, to make the coordinates display in the infobox, as they do in most comparable infoboxes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:26, 2 February 2012 (UTC)

I noticed in the sandbox, {{coord}} is called using |display=title if latitude/longitude parameters are specified, but it uses |display=inline,title if lat_deg/lon_deg parameters are used. Is there any particular reason for this? Tra (Talk) 08:17, 17 February 2012 (UTC)
I've checked a few articles and templates at random, and it looks as if there might be more than one standard for this. So I don't really want to try and guess how this needs to be corrected - I'll remove {{editprotected}} for now pending your response. Tra (Talk) 23:18, 18 February 2012 (UTC)
Sorry; I missed this in Feb; I've resynced and updated the sandbox, it should work, now. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:01, 15 August 2012 (UTC)
Er, I did something very similar for the section #Request for Coordinates and Architect below - was there something wrong with it? --Redrose64 (talk) 22:44, 15 August 2012 (UTC)
No; my apologies. I missed that, so I've rolled my edits back to yours (and re-added some unrelated hCard classes) However I notice you've used {{Geobox coor}} not {{Coord}}; why is that? My version also included a separate |coordinates= parameter for people who want to enter a whole instance of {{Coord}}; are you OK to include that? It's not a deal-breaker. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:19, 16 August 2012 (UTC)
I used {{geobox coor}} because that's what {{Infobox building}} uses. One feature is that it does a sanity check on the display position, so that |display=title doesn't occur, because this would leave an empty cell in the infobox. I don't recall why I omitted a straight {{{coordinates|}}} - there is one in {{Infobox building}} after all. --Redrose64 (talk) 14:59, 16 August 2012 (UTC)
Fair enough, thanks - I think we're good to go. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:55, 16 August 2012 (UTC)
Done --Redrose64 (talk) 16:40, 16 August 2012 (UTC)
Thank you. I've updated the documentation; please check it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:55, 16 August 2012 (UTC)

field: "owner"

There's a field "|owner=" listed in the template documentation but nothing in the corresponding template? The field does not exist or does not work. 66.102.83.61 (talk) 03:51, 13 May 2012 (UTC)

The field exists, and it works/displays, but it's not included under "Usage" at Template:Infobox_museum.
Place "| owner =" under "| curator =". Prburley (talk) 18:22, 10 July 2012 (UTC)
Could "| owner =" be added to "Usage" at Template:Infobox_museum?
"Complete and specific description of the request": the "Owner" field exists in Infobox_museum, but it's not included in the Usage section. Prburley (talk) 18:53, 10 July 2012 (UTC)
Not done: {{edit protected}} is usually not required for edits to the documentation, categories, or interlanguage links of templates using a documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage. --Redrose64 (talk) 19:16, 10 July 2012 (UTC)
Actually, I overlooked that "Owner" is currently not supported and does not display. For what reason, I can't imagine. Prburley (talk) 19:21, 10 July 2012 (UTC)
How do you mean? It's showing up at Casa Paoli, Casa Wiechers-Villaronga, Castillo Serrallés, Hacienda Buena Vista, Museo de Arte de Ponce, Museo de la Historia de Ponce, Museo de la Masacre de Ponce, Museo de la Música Puertorriqueña, Museo Francisco "Pancho" Coimbre, Panteón Nacional Román Baldorioty de Castro, Parque de Bombas, Residencia Armstrong-Poventud, Tibes Indigenous Ceremonial Center, possibly others; and I don't see anything unusual on any of those - to me, it looks just fine. Which article(s) are you seeing problems on? --Redrose64 (talk) 19:58, 10 July 2012 (UTC)
The problem is with the documentation. "Owner" does indeed work, I added it to Museum of the Imperial Collections today. However, the template documentation says: "Owner. The owner of the museum. This field is currently not supported and does not display." Thanks for your speedy response! Prburley (talk) 20:41, 10 July 2012 (UTC)
The documentation was amended twice in recent months: 9 March 2012, possibly as a result of a misunderstanding of the "sandbox" procedure (see #Edit Request for Entity above); and 13 May 2012. The actual template edit occurred 27 June 2012 - almost two weeks ago. There have been two doc updates today:; 19:18; 21:08. --Redrose64 (talk) 21:18, 10 July 2012 (UTC)

Request for Coordinates and Architect

Resolved

I would like to petition that a field (or fields are most appropriate) be added to the infobox for coordinates - they seem to be pretty widely used in all other sorts of infoboxes that involve a physical structure sitting somewhere on the planet. I would also like to see a field added to indicate the name of the architect responsible for designing the museum; it is also another attribute of museums. Thanks. Mercy11 (talk) 20:25, 28 July 2012 (UTC)

Coordinates are already provided, in two ways.
  • For signed decimal coordinates, use |latitude= |longitude=
  • For coordinates in degrees/minutes/seconds, use |lat_deg= |lat_min= |lat_sec= |lat_dir= |lon_deg= |lon_min= |lon_sec= |lon_dir=
Both take one further optional parameter - |coordinates_type= which defaults to type:landmark (see Template:Coord#type:T). Both systems will give coordinates upper right, and optionally a pushpin map as well.
To get the pushpin map, set either |pushpin_map= or |map_type= and optionally: |map_size= (default 250); |map_caption= (default "Location within pushpin_map"); |map dot label= (default none).
See Tate Modern for an example with a pushpin map. --Redrose64 (talk) 22:31, 28 July 2012 (UTC)
As you pointed out, the two methods above (signed and dd/mm/ss) display coordinates in the upper right. Using those methods the coordinates are displayed in the upper right of the article's page,,,not inside the infobox itself, which is where I am seeking to get them to appear. There are several other infobox templates that provide this "in-infobox" functionality. Articles with infoboxes such as Ponce City Hall (a NRHP template), Cerro Maravilla (a mountain template), and this one Centro Español de Ponce (a building template), are some examples. I guess there in no way for them to appear inside the Museum infobox itself, and this is why I asked for them to be added. Thanks, Mercy11 (talk) 00:54, 29 July 2012 (UTC)
Basically we need to move the {{coord}} from its present position just before the infobox itself, to a new row inside the infobox. At the same time we would need to change |display=title to |display=inline,title
There may be a need to suppress the display of coordinates at upper right, so we would need to add a parameter equivalent to the |display= parameter used by {{infobox mountain}}. This doesn't have all the functionality of the similarly-named parameter described at Template:Coord#Usage, since |display=title would need to be forced to behave the same as |display=inline,title - the reason for that is so that the row label "Coordinates" is not followed by something invisible. If blank or absent it would default to |coord_display=inline,title. --Redrose64 (talk) 11:32, 29 July 2012 (UTC)
Thanks. Mercy11 (talk) 22:03, 29 July 2012 (UTC)
Regarding coordinates: I've made appropriate changes to Template:Infobox museum/sandbox. There are three new parameters:
  • |coordinates_region= - as per Template:Coord#region:R, e.g. |coordinates_region=US-NY
  • |coordinates_display= - same as |coordinates_display= in {{infobox building}}
  • |coordinates_format= - this may be set to dms; if blank or omitted, coords are in decimal format
Give it a try. --Redrose64 (talk) 20:34, 9 August 2012 (UTC)

This is now implemented. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:58, 16 August 2012 (UTC)

Awesome! Thanks! I already put them to work at Museo de Arte de Ponce!! Mercy11 (talk) 03:12, 17 August 2012 (UTC)
And thank you, but please note these fixes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:33, 17 August 2012 (UTC)
Great! Just touched up the direction a bit as you may have overlooked the direction, since the place is west (or negative/left) of Greenwich. Thanks a zillion for improving the template! Mercy11 (talk) 16:03, 17 August 2012 (UTC)

Request for architect/architectural details, 3rd ed. (aka: 3rd Request)

Response to above section above on Architect: :: Not done "Request not specific enough; please indicate the code that is to be changed, and establish consensus before making an edit request." of 14 July 2012. I lack the knowledge on how to make the code specific enough. I hope the substance of my proposal will be considered over my lack of technical knowledge on coding.

Fields

| label8 = Architect | data8 = {{{architect}}}

| labelX = architectural_style | dataX = {{{architectural_style}}}

| labelX = groundbreaking_date | dataX = {{{groundbreaking_date}}}

| labelX = start_date | dataX = {{{start_date}}}

| labelX = completion_date | dataX = {{{completion_date}}}

| labelX = opened_date | dataX = {{{opened_date}}}

| labelX = inauguration_date | dataX = </includeonly>

| labelX = renovation_date | dataX = </includeonly>

| labelX = height | dataX = </includeonly>

| labelX = floor_count | dataX = </includeonly>

| labelX = floor_area | dataX = </includeonly>

Description of fields

architect
Name of original architect - wikitext (can contain links)
architecture_firm
Name of original architect - wikitext (can contain links)
groundbreaking_date
Date of the formal ground breaking, if any. Eg; 25 January 2007
start_date
Date building construction started. Eg; 25 January 2007
completion_date
Completion date of construction if know. Eg; 25 January 2007
opened_date
Date of opening. Eg; 25 January 2007
inauguration_date
Inauguration date if know. Eg; 25 January 2007
renovation_date
Removation date if know. Eg; 25 January 2007
height
Number of building expressed as a numerical value
floor_count
Number of floors expressed as a numerical value
floor_area
Area of floors expressed as a numerical value Prburley (talk) 13:03, 29 July 2012 (UTC)

Comments

I have no knowledge of coding, simply would like a template with the fields I'm looking for (currently infobox building is the best fit, despite the name), in particular architect and coordinates; the fields suggested above look very good to me, Maculosae tegmine lyncis (talk) 16:56, 29 July 2012 (UTC)

I submit my continuing support for the architect's name field. Most museums are generally located in structures specifically designed to house a museum, thus there is a 1-1 correspondency between a museum (the organization) and a museum (the structure).
Also, some museums at one point or other may close for renovations, enlargement, reconditioning, etc., oftentimes for several years. As such, it may be useful to have a field added named "Closed" where this information can be kept. The Infobox Venue template, (used for theaters, music halls, etc.) is an example of this.
Ah, just one side note: when I first read the name of this section ("Request for architect/architectural details, 3rd ed.") I didn't at first fully digest what the titled meant. I am now understanding that this request has been made multiple times, since at least 2008. It is not clear to me what reason has been given in the past not to add the field(s). If the reason is one of consensus, then -- as no objections have been raised so far, and by-passing for a second the true meaning of wp:consensus -- I can say we do have consensus: it's One in favor and Zero oppposed. (The one, of course, is myself!). Thanks! Mercy11 (talk) 22:03, 29 July 2012 (UTC)
For the record, I'm in favor of my own proposal. So that makes two. Prburley (talk) 03:03, 3 August 2012 (UTC)
I support these additions and would be happy to code them, once the coordinates issue, above, is resolved. However, we should consider how different this template would then be from {{Infobox building}} and whether a merger, or making this template wrap an updated version of that one, would be more sensible Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:28, 16 August 2012 (UTC)

Visitor figures?

Visitor figures → Visitors
Rationale: The number given is the annual number of visitors, and not the annual number of visitor figures.  --Lambiam 12:31, 9 October 2012 (UTC)

For my own edification, How are the two different? Can you provide your definition of each? My name is Mercy11 (talk) 14:49, 9 October 2012 (UTC), and I approve this message.
Take for instance template {{Infobox NASCAR driver}}, which you can see in action at Dale Earnhardt. It says Wins, Top tens and Poles, not Win figures, Top ten figures and Pole figures. The data given there are numbers, aka figures, but it is at best redundant to put that in the label and at worst misleading. In his NASCAR Sprint Cup Series career, Dale Earnhardt Sr. won a race 76 times; in other words, he had 76 wins. He did not have 76 win figures; his Sprint Cup wins can be summed up in a single figure, the figure 76. Likewise, in {{Infobox country}} we have the label Population, not Population figures, in {{Infobox magazine}} we have Circulation, not Circulation figures, in {{Infobox election}} we have Popular vote, not Popular vote figures, etc.  --Lambiam 23:17, 9 October 2012 (UTC)
Yeah, some cleanup is needed. I would second that change. My name is Mercy11 (talk) 04:32, 10 October 2012 (UTC), and I approve this message.
Done --Redrose64 (talk) 17:42, 10 October 2012 (UTC)

State relief map

Please see Carnegie Public Library (Tyler, Texas) as an example. I want to use Texas relief map on museums. I would like the map dot label (or mark label) to show on the relief map when used. — Maile (talk) 14:04, 18 October 2012 (UTC)

If I am not mistaken, that is already available. See HERE for example. My name is Mercy11 (talk) 19:02, 19 October 2012 (UTC), and I approve this message.
That's not a relief map on Museo de Arte de Ponce. That's just a regular map. Scroll down on Texas relief map. There's two maps there - the regular map on the top, and the relief map on the bottom that shows topography in varying shades of green and browns. — Maile (talk) 19:27, 19 October 2012 (UTC)
  • Not done:. Sorry, but you need to provide the actual code to be used in the template. Could you update the template sandbox with the relevant code? (Or ask someone who knows about templates to do it for you?) Let me know on my talk page if you have any questions about this. Best — Mr. Stradivarius (have a chat) 14:04, 30 October 2012 (UTC)
Replying on your talk page. — Maile (talk) 17:40, 30 October 2012 (UTC)
Per the request here, and on my talk page, I have added |map_relief=y as an option. Let me know if there is a problem. Thanks! Plastikspork ―Œ(talk) 04:45, 31 October 2012 (UTC)
Thank you. It's done - it works now. — Maile (talk) 11:26, 31 October 2012 (UTC)

Edit request on 29 March 2013

please change 

| image1         = {{#invoke:InfoboxImage|InfoboxImage|image={{{image<includeonly>|</includeonly}}}|size={{{image_size|{{{imagesize|}}}}}}|sizedefault=250px|alt={{{alt|}}}}}

to 

| image1         = {{#invoke:InfoboxImage|InfoboxImage|image={{{image|}}}|size={{{image_size|{{{imagesize|}}}}}}|sizedefault=250px|alt={{{alt|}}}}}

notice the missing > at the end of the closing includeonly. Frietjes (talk) 17:36, 29 March 2013 (UTC)

TfD

Please tag with {{TfD}}, referencing Wikipedia:Templates for discussion/Log/2013 March 30#Template:Infobox museum. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:03, 30 March 2013 (UTC)

 Done Ruslik_Zero 19:01, 4 April 2013 (UTC)

The fields "car_park" and "publictransit"

I suggest removing the fields "car_park" and "publictransit" per WP:NOTTRAVEL. Up to date and detailed information about accessibility is provided on the museum's website, and is in the scope of Wikivoyage rather than Wikipedia. Note that the field car_park has been added at the request of a single editor. --ELEKHHT 19:27, 31 March 2013 (UTC)

Please note that this is already under discussion at Wikipedia:Templates for discussion/Log/2013 March 30#Template:Infobox museum, as indicated above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:48, 31 March 2013 (UTC)

Please don't confuse things. The content of this infobox is discussed here. The merger proposal is a separate discussion. --ELEKHHT 20:18, 31 March 2013 (UTC)
I'm not confusing anything. Any one may click on the link I provided, and see that the future (not merely "merger") of this infobox, and the two parameters named, are ding discussed there. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:52, 31 March 2013 (UTC)
The scope of the TfD is "deletion or merging of templates", not individual fields. Hence the discussion there is not focused and structured in a way that leads to consensus forming about the use of specific fields. It is in the scope of this talk page to discuss and find consensus improvements. It would be much easier without distracting comments. --ELEKHHT 21:47, 31 March 2013 (UTC)
Elekhh is correct. The TfD nomination is not a nomination to remove specific fields. I would suggest that everyone wait to see how the TfD pans out and then submit a discussion in the Talk page for removal of specific field(s). My name is Mercy11 (talk) 19:38, 4 April 2013 (UTC), and I approve this message.

Add default value for |name=

Please add {{PAGENAME}} as a default value for |name=. Thanks. — Cheers, JackLee –talk– 17:23, 18 April 2013 (UTC)

 Done Ruslik_Zero 19:41, 19 April 2013 (UTC)
Thanks! — Cheers, JackLee –talk– 05:27, 20 April 2013 (UTC)

Additional fields

Could we get additional/optional fields added to this infobox? I'd like to add Chairman, Manager, Secretary, and Curator. Thanks. --Brownings 10:53, 15 May 2007 (UTC)

...and address, phone numbers. StevenBlack 01:18, 4 October 2007 (UTC)

{{editprotected}}I just want to second the addition of an "address" and "phone number" in the infobox. Douggers (talk) 02:09, 16 June 2008 (UTC)

Optional: additional online resource fields?

Yes please! Only allowing one URL seems a bit limiting. Many museums have more than just a single website to connect to potential visitors. Many will also have a blog, a Twitter account, Facebook, and so on. The template could do with either a set of dedicated (optional) fields for the main social media sites (which, e.g., take a Twitter ID and display it, but generate a link to the full Twitter page URL), and/or a more general-purpose optional field (allowing custom display names) for any additional online resources. ErkDemon (talk) 14:21, 5 August 2013 (UTC)

3 new Infobox fields

I recently supported these 3 additional field in another Wikipedia forum (HERE), with no objections. If there are no objections here either, I would like to request that these three museum-specific fields be added to the infobox:

Regards, My name is Mercy11 (talk) 22:29, 19 April 2013 (UTC), and I approve this message.

I would suggest "works" is not exactly what you mean for a museum. That's great for an art museum, but the Rosetta Stone is hardly a "work (of art)". Nor is the Saturn V Dynamic Test Vehicle or Space Shuttle Pathfinder a "work". Perhaps it should be "items" or another similarly broad term. The others look great. -- ke4roh (talk) 16:29, 20 April 2013 (UTC)
I agree with your assessment. Museums do hold items such as the Rosetta Stone, and "Key Works" would not be broad enough to encompass all categories of items held by museums. How about "Key holdings" instead? (While "Key items" could do the job, "Key holdings" would be more precise.) The request could then become:
Regards,
My name is Mercy11 (talk) 01:59, 22 April 2013 (UTC), and I approve this message.
I see 1 additional support and no objections to this request, and the request is 3 months old. Could the gurus watching this locked page implement the requested enhancement? (I would happily implement it myself, but this page has been locked.) Regards, My name is Mercy11, and I approve this message. 19:44, 5 August 2013 (UTC)
The template is not protected, I've made the changes; please finish updating the documentation. We may have problems, having both |collection= and |collections=. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:14, 5 August 2013 (UTC)
Oops...seems you beat me to it! anyway, Thanks!
As for your |collection vs. |collections concern,,,, I agree with you entirely. As a possible solution, perhaps instead of "|collections" we should name that field "|collection_size" since, anyway, that's how that field displays (it displays as "Collection size"). If you want to name it entirely different from anything starting with the root "|collection" perhaps you could try "|total_holdings" and display it as "Total holdings".
I have put the 3 new fields (|accreditation = Accreditation; |key_holdings = Key holdings; and |collections = Collections) to the test at Museo de Arte de Ponce. I also kept the potentially confusing/ambiguous --but pre-existing-- field "|collection = Collection size [amount of objects]" as I wanted to see how the whole thing behaved. My findings are that display-wise everything is currently fine. So if yu wish to rename |collection to |collection_size, that IMO should take care of the collection/s concern.
Thank you, My name is Mercy11, and I approve this message. 14:51, 6 August 2013 (UTC)
Renaming existing parameters is problematic, as every instance of the template would need to be updated. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:24, 6 August 2013 (UTC)
Thank you for considering the idea. Regards, Mercy11 (talk) 21:02, 11 August 2013 (UTC)

"Nearest" car park

Any reason why the label for the car_park parameter is "Nearest" car park (emphasis added)? What happens if a museum has on-site parking? Should I just enter "on-site parking"? It probably should instead be more general like the parking parameter on {{infobox building}}, {{infobox station}}, and others. Zzyzx11 (talk) 06:02, 7 May 2014 (UTC)

The parameter is cruft, and should be removed, WP:NOTDIRECTORY applies, Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:10, 7 May 2014 (UTC)

Hours of operation

When I'm looking for a museum, the thing I'm most interested in is what its hours of operation are. They should also have a date field, "As of blah, hours are..." This way, if the information is years out of date, someone will be prompted to update it. Banaticus (talk) 20:15, 5 July 2014 (UTC)

We don't include such information, per WP:NOTDIRECTORY. We do, though include a link to the museum's website, where such information is usually available, and more likely to be up-to-date. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:11, 5 July 2014 (UTC)
User:Banaticus, you are right that we usually look for museum hours of operation. The sister project Wikitravel is designed to contain hours of operation and other tourist-related information. You can access it from HERE. Regards, Mercy11 (talk) 14:13, 14 July 2014 (UTC)
ITYM Wikivoyage. Wikitravel is not a "sister project". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:54, 2 October 2014 (UTC)

Entrance fee

Is it worthwhile adding an element in this template for the cost of entry (excluding temporary or special events of course). Alongside "what day/time is it open" this is the most practical thing that people wanting to visit a museum ask - and in particular "free entry" is something that many museums are very proud of. For free museums it would be easy to simply have "free entry", for museums that suggest a donation amount we could write "$5 suggested", and for museums that charge a formal entry fee (with different amounts for children/elderly/adults/families...) we could list the price-range e.g. "$20-$5 entry fee". Wittylama 20:12, 28 September 2014 (UTC)

notifying Pigsonthewing esp. In regard to his comment about the "not a directory" policy (above). I'd like your take on this proposal Andy. Wittylama 14:11, 2 October 2014 (UTC)
Thanks. I think this might fall foul of NOTDIRECTORY. Also, there often isn't a single price (child, adult. member. pensioner, after 5pm... etc). What about a binary "fee: yes/no", and leaving the detail to Wikidata? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:29, 2 October 2014 (UTC)
Agreed that it's not binary (there's temporary exhibition tickets prices in free museums, and 'free days' in paid museum too). But, is that kind of detail within the scope of wikidata (both in terms of what fields it allows and the number of different variations on pricing this could extend to if it went into full details)? I imagine if we pushed "pricing structure for museums" to wikidata, then opening hours should go there too. At that point it might also be extended to the price of other things (e.g the wikidata item for a newspaper/magazine) and perhaps require different data-points for the price as it changed over time (eg. From 1995-20012 it was €10 but from 2013 it as raised to €15). I'm not sure wikidata would appreciate all that detail, but would be interested to know.
But in terms of what can/should be visible on Wikipedia (that is, until wikidata starts to serve infoboxes one day...) I am seeing three separate options: status quo, minimalist, maximalist:
1) no pricing, no opening hours, status quo.
2) simple/un-nuanced one-line info on price/opening hours with mandatory footnote to the relevant page on the museums's website (or equivalent) for the full details (e.g. "Entry: Weekdays only, €5/€10 [details]")
3) an auto-collapsed expandable box called "visiting" *within* the infobox which contains a variety of practical tourism info, including all the "visitor specific" info that is already in this infobox. This includes the fields for "parking" and "public transport" (which I think are less appropriate for the infobox than entry price or opening hours). This would allow us to have detailed /nuanced info on price and opening dates/times without filling up the visual space for those who don't need it. It could also (if we wish) include all manner of other things applicable to visiting such as photography policy, wifi, disabled access... It might also be appropriate to actually include a direct link to the applicable Wikivoyage page within this "visiting" sub-box...
Thoughts? Wittylama 16:18, 2 October 2014 (UTC)
You seem to have accidentally overlooked the "yes/no" option I suggested ;-) Wikivoyage links are a good idea. It would be good if they would reciprocate, too. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:52, 2 October 2014 (UTC)
Sorry, yes, accidentally didn't include the yes/no option. I would suggest that would fit in the "option 2" category above e.g. "Entry: weekdays, free [details]" or "Entry: Every day, paid". By combining the opening days and price into one field it would mean that a yes/no response wouldn't make grammatical sense. On the other hand, having it as only a question about price would raise the interesting point - which would be the option that would get the positive sounding "yes"? If the field was named "free entry" The non-charging museums would get a "yes". But that phrasing seems somehow to be non-neutral. On the other hand having the field named "entry fee" would near that non-charging museums would be get a "no", which seems confusingly negative. I'd prefer an open question (such as "entry" or "price") which would therefore give a small amount of scope for short but contextually relevant answers rather than a closed question which forces a yes/no. Thoughts? Wittylama 21:21, 2 October 2014 (UTC)

"Embedded" parameter?

The usage section of the documentation lists an embedded = parameter, but it is not defined in the description of fields. Would somebody be able to define its usage? If not, could we remove it from the usage code for copying and pasting? Thanks! – voidxor (talk | contrib) 07:22, 26 November 2014 (UTC)

Description provided. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:00, 26 November 2014 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Template_talk:Infobox_museum/Archive_1&oldid=1147274042"