Open main menu

Info non-talk.svg Template:Information has been protected indefinitely because it is a highly-used or visible template. Use {{Edit request}} on this page to request an edit.
Please test any changes in the template's /sandbox or /testcases subpages, or in a user subpage, and consider discussing changes at the talk page before implementing them.

Contents

Propose inclusion of location parameterEdit

Propose to add the parameters of the 2009 {{Information2}} to this one, adding a "location" field to this by default. The location field could take any input, include a string of text, a Wikidata item, {{Institution}}, or {{Location}}. Various people have proposed this often over the years. It seems that there is some resistance but I fail to understand it and maybe someone else can clarify.

{{Information2}} has been available as an option since May 2006. It has 1400 uses as compared to 42 million for the default template. Problems with Information2 is that it is in limbo between approval and being fringe. As I show below with the list of links, location seems like a popular field request for the information template.

This is not the most urgent request because the 2017-2019 roll out of Commons:Structured data seems likely to change the interface anyway, but I thought that it would be useful to check in about changes for now and to get advice about current best practices.

My own project need is to mark collections of images depicting museum objects and archival documents which are from single institutions and not art. My preference would be to incorporate an {{Institution}} template somewhere that says that an object is at an institution. The objects I am considering are texts and objects from science museum collections.

Here are previous conversations talking about either putting location in the {{Information}} template:

Here is one more discussion from the art template seeking a use for museum objects which are not art:

Thanks Blue Rasberry (talk) 16:19, 21 May 2018 (UTC)

Example caseEdit

Consider File:Informed Consent Agreement Between Antonio Benigno and Walter Reed (English).jpg. I have some archival documents like this and a collection of medical devices in a university collection. I would like to note somehow that these objects are at the university, or even a particular collection.

Right now I just have an institution template in the description field of the information template. What better way is there for images of this kind of content? Blue Rasberry (talk) 20:19, 21 May 2018 (UTC)

wikidataEdit

May we have wikidata parameter as it is in Template:Artwork ?. Is there some alternative template with this parameter, instead?. Thanks, --amador (talk) 04:44, 6 June 2018 (UTC)

In case of {{Artwork}} wikidata parameter has clear meaning: an item which stores metadata for a given artwork. {{Information}} template used by great majority of files, is meant to be used mostly for photographs taken by the uploaders and 2/3 of images on Commons use one of CC license templates( mostly used by such files). Such files do not have associated items on Wikidata, and the danger is that people will be adding Wikidata items for subjects or creators instead. --Jarekt (talk) 11:21, 19 June 2018 (UTC)

machine-readabilityEdit

I noticed that this template adds all pages with the parameter "Author" capitalized to Category:Files with no machine-readable author. If the parameter is lower-case, then everything is OK. Could anybody with edit rights resolve this issue? --Jarash (talk) 18:12, 10 July 2018 (UTC)

Transcription parameterEdit

Please can we have a |Transcription= parameter, like in {{Artwork}}? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:08, 3 August 2018 (UTC)

Artwork doesn't have a transcription field. Did you mean the inscriptions field? I don't think it make sense to add an inscriptions field to the Information template as it intended for items with basic information. However, if you can't use {{Artwork}}, don't want to use {{inscription}} inside the description, and you need to add an inscriptions field to {{Information}}, you can use the other fields field to add a custom field. For example, you could do something like the following:
{{Information 
 |description    = 
 |date           = 
 |source         = 
 |author         = 
 |permission     = 
 |other versions = 
 |other fields={{Information field |name={{int:wm-license-artwork-inscriptions}} |value={{inscription |1=example inscription |position=bottom right}}}}
}}
RP88 (talk) 14:53, 3 August 2018 (UTC)
Yes, I meant |inscriptions=. Thank you for the work-around, but a dedicated parameter would be far less kludgy and so more user-friendly. My request stands. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:04, 31 August 2018 (UTC)

I am still finding regularly cases where such a parameter would be useful. Can anyone help, please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:41, 19 January 2019 (UTC)

{{Information}} is our basic template with only a couple of fields to cover simple cases. If you want to add more fields you either use the "other fields" or use one of the dedicated domain templates like {{Artwork}}, {{Photograph}}, {{Book}}, {{Map}}, etc. Multichill (talk) 15:49, 19 January 2019 (UTC)
Having been a user of Commons for over a decade, I'm familiar with the range of templates available, and use them. Nonetheless, I still regularly finding cases where a specific |transcription= parameter would be useful in this template, not least for the reasons I have already given, above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:31, 19 January 2019 (UTC)
  Not done this template is used about 46657156 times and about 8660 times in combination with {{Inscription}}, so about 0,019 % of these files. Too much of an edge case. Multichill (talk) 00:02, 20 January 2019 (UTC)
Oddly enough, you don't have a veto. This is something for the community to decide. Your statistic is meaningless, because not all transcribed text uses {{Inscription}}; it took seconds to find File:2015.211296.Punch-Vol-cxxxvii 0425.jpg, for example. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:52, 20 January 2019 (UTC)
This template has a quite a long history of denied feature requests. My response is in in line with that. As an admin I evaluate requests for edits to protected templates (and pages) and either mark them as done or not done. If you think I'm being unfair, you can go to Commons:Administrators' noticeboard to ask another admin to have a look.
Please don't change my comments. Changing other user's comments is not considered acceptable behavior on Commons and might result in a block. Multichill (talk) 20:20, 20 January 2019 (UTC)
You're not entitled to make an edict as an admin, especially once you've commented as a participant in the discussion; as you well know. You can dick around adding a bright red cross by inappropriately using {{not done}} all you like, but you still don't get a veto over community discussion. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:11, 20 January 2019 (UTC)
  • I like this idea. -- Tuválkin 02:27, 21 January 2019 (UTC)
  • strongly oppose, our template {{Information}} is the simple description one, we are describing something rather rare in usage and our practice have always been to extend (inherit) a new description template for thoses cases such as {{Book}}, {{Artwork}}. Moreover I'd like to remind everyone that attacking admin not wanting to do a protected edit after giving a rationale is wrong and is more likely to escalate into a conflict, when you can reach other admin on COM:AN or try for the village pump, and get wider audience, and build a consensus. --PierreSelim (talk) 09:48, 21 January 2019 (UTC)
    • "attacking admin not wanting to do a protected edit" No-one has done this. Please avoid false insinuations.
      There is already a pointer to this discussion on village pump.
      How is adding a bogus {{not done}} template helping to "build consensus"?
      We don't need a whole new fork of {{Information}} just for items which include text, albeit there are many thousands of them, across a vast range of types of subject. I note that you give no substantive argument as to why such a parameter should not be added.
      As to the argument of simplicity, how is |other fields={{Information field |name={{int:wm-license-artwork-inscriptions}} |value={{inscription |1=example inscription |position=bottom right}}}} simpler than |transcription=? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:14, 21 January 2019 (UTC)
      How about something like {{Inscription field}}? Jean-Fred (talk) 20:17, 21 January 2019 (UTC)

Unexpected filename in file descriptionEdit

Looking at Special:Search/dokkum, I noticed that many results have their excerpt start with a repetition of the file name, which looks messy and unprofessional (in my opinion). For example:

  File:Windmill Zeldenrust in Dokkum.jpg

DescriptionWindmill Zeldenrust in Dokkum.jpg English: Windmill Zeldenrust in Dokkum build on the cities bulwark defence. Date 9 February 2013, 16:39:57

(3,464 × 2,309 (3.16 MB)) - 01:18, 24 November 2016

The part that is unexpected is that the excerpt contains the filename, causing it to show up twice. (In addition to lacking of space between it and the word "Description"). I traced this back to Template:Information, which contains the following code (simplified):

<td class="fileinfo-paramfield" lang="{{int:lang}}">
{{int:wm-license-information-description}}<span class="summary fn" style="display:none">{{PAGENAME}}</span><!-- required for hCalendar and hProduct microformat; though hMedia would be more appropriate -->
</td>
<td class="description">{{{description|{{{Description|}}} }}}</td>

It is intentionally being added (albeit visually hidden). It has a comment explaining that it is "required for hCalendar and hProduct microformat", but I am unsure to verify whether this is actually working and being used. Does anyone know?

Also, if we want to keep it, I'd propose we move it toward the end of the Template output, rather than on top, and consider adding the class searchaux so that it is not indexed as part of the text content (mw:Help:CirrusSearch). We may want to do the same for the word "Description" as well. --Krinkle 02:19, 27 September 2018 (UTC)

Krinkle, I was just wandering about this and other irregularities of the html produced by this template:
  1. why do we have <span class="summary fn" style="display:none">{{PAGENAME}}</span> in the space where one expects translated word "Description"
  2. why <td> cell for date has "lang" field, which is often wrong. For example HTML of File:Radomsko ul. Reymonta 58.jpg has <td lang="en">styczeń 2015 r.</td> which is incorrect as the cell content is in Polish not English.
Looking at the edit history it looks like user:Rillke first added <span class="summary fn" style="display:none">{{PAGENAME}}</span> with this edit to the cell with the description text and later moved it with this edit to the cell with description field name, explaining that he was fixing HTML-Tidy-hack issues. user:Rillke was not active in last 2 years except for few edits yesterday, but maybe he can help to figure out if this is still used. Also pinging @Pigsonthewing: who often advocates for microformat issues. As for wrong language labels in date <td> cell, that was added by user:Ebrahim with this edit. Ebrahim since we can not determine the language of the content of the date field (if not in standard YYYY-MM-DD format) can we remove the lang field? --Jarekt (talk) 16:02, 1 November 2018 (UTC)

Rewrite in LuaEdit

Module:Information is designed to replace wikitext implementation of Template:Information, and it can be tested through Template:Information/sandbox. The module is designed pr produce exactly the same html as the current template and it is being tested on small number of files using {{Information2}} template, which at the moment calls Template:Information/sandbox. The rewrite was motivated by future Commons:Structured data when {{Information}} might have to interact with Structured data the way {{Artwork}} or {{Creator}} interacts with Wikidata, but in the mean time it offers 50% faster load time, smaller expansion depth and smaller memory use. Please test {{Information/sandbox}} by temporarily replacing {{Information}} in the most complex and messy description pages you can find. I will do the same. --Jarekt (talk) 12:42, 2 November 2018 (UTC)

I don’t see any traces of {{Information/author processing}} and {{Parse source}}, nor any parameter check (done by Module:TemplatePar in the wikicode version). Maybe the former two should be rewritten in Lua, too, to avoid invoking templates from Lua code (especially the author one: it’s really simple, while the current wikicode implementation runs these tests twice in order to ensure {{author missing}} is not marked as machine-readable author; this could be made even more simple in Lua, at lest in terms of time complexity). —Tacsipacsi (talk) 14:18, 2 November 2018 (UTC)
{{Information/author processing}} was used to find and correct thousands of files with bad metadata. It is done now and Module:Information will ignore any fields with only punctuation. {{Information/author processing}} was also used for checking if there is a creator page matching author name and using that instead. That feature was turned off as it was creating great many wrong creator names. So I thing all current tasks of {{Information/author processing}} are being done by the module. As for {{Parse source}} I also do not think it is necessary anymore, In the past we used it to correct thousands of local translations of "own work" phrase to {{Own}}, but now it is done and with very few being added I do not think we need to perform a check on 50M files to find occasional new case. So in my opinion those 2 templates should be disabled, except that I do not want to do unnecessary edits to the template, if they can be avoided. --Jarekt (talk) 17:23, 12 November 2018 (UTC)
OK, but I would like to have a bot check all usages just before the switch, so that nothing breaks out of a sudden. (Maybe a regular, e.g. monthly, check is also worth to find the new wrong inclusions. This latter can even be narrowed down to the pages that changed since the last run, so it uses far less resources than the template/module version.) Such a test seems pretty easy using Pywikibot. —Tacsipacsi (talk) 20:27, 12 November 2018 (UTC)
Any bot runs that have to go through 50M files would take forever. Maybe if you run it off a data dump, but to run it of the live website I ca usually visit 10-20k pages per day. Also there are no plans for deployment in near future. I was [[Commons_talk:Structured_data#Lua_version_of_the_{{Information}}_template|asked not to deploy for time being]]. BTW, Files affected by {{Information/author processing}} go into Category:Bad author info and files affected by {{Parse source}} can be found here. So anybody can check and fix files that are corrected by those 2 templates. --Jarekt (talk) 00:08, 13 November 2018 (UTC)
Sorry for not having checked the figures. However, I think the 10-20k/day is a realistic number for bots writing the wiki (because of their performance constraints). I’ve just ran a bot doing nothing but printing the article size, and it went through 180,000 pages in around an hour (it preloads pages in 50-article packets, which can be increased to 500 for bot accounts, resulting in an even faster script). It means approximately 4.3 million pages a day, and I think it’s closer to the performance of the bot resolving this task than your 10-20k. So 50M files can be checked within two weeks, which is not instant, but neither something we should call forever. Although the category/template is just as good, except that the category contains only the file-namespace pages, maybe this could be expanded to all pages (hopefully there’s not much). —Tacsipacsi (talk) 00:11, 14 November 2018 (UTC)

Additional informationEdit

There are ~190K images in en.WP waiting to be copied (moved) here. An unknown number of them have a |additional_information= parameter (example). Can we accommodate that, to facilitate quick transfers? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:03, 17 January 2019 (UTC)

We could concatenate |description= and |additional_information= before displaying it in the description field. --Jarekt (talk) 03:02, 18 January 2019 (UTC)
@Jarekt: Yes, that would work. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:46, 18 January 2019 (UTC)
Andy, Yes we can do that, but I realized that I do not understand why. We transfer files all the time from other language Wikis and for all the other ones we do not need to modify Information template. I am not exactly sure how that is done by I belive it involved some sort of mapping mechanism, which is not always 1 to 1. Another approach I used in the past to fix files moved from other wikis with their native infoboxes is to use "subst:". For example, we have files transferred which use {{Изображение}}, {{파일 정보}} or {{Зображення}} templates. For those I occasionally would run a bot to replace "{{Изображение" with "{{subst:Изображение" which neatly inserts {{Information}} template and renames all the fields. Perhaps as we move en.WP files here we can use some temporary template like Information_en_wp which would have to be substituted. template:Information_en_wp could do all the concatenating of |description= and |additional_information= fields. What transfer tool will be used for this? --Jarekt (talk) 13:37, 18 January 2019 (UTC)
@Jarekt: The new "FileExporter" gadget. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:16, 21 January 2019 (UTC)
Andy, I looked through the documentation and it is not clear how to deal with such parameters. So I asked about it at mw:Help_talk:Extension:FileImporter. --Jarekt (talk) 16:16, 21 January 2019 (UTC)

Make description optional ?Edit

It might be a bit early for that, but I think that now that we captions outside this template, the description parameter can be made optional.--Zolo (talk) 17:05, 16 February 2019 (UTC)

I think the template should make sure at least one (or even at least the English) description is given before not warning for empty description field. As far as I know, it’s not possible yet, but will be once. —Tacsipacsi (talk) 23:35, 16 February 2019 (UTC)
Return to "Information" page.