Commons: Help:Magic words redirects to MediaWiki page "Help:Magic words". Page-dependent magic words will affect or return data about the current page.
The following statements were excerpted from the MediaWiki page "Commons: Help:Magic words" (all quoted links were adapted to refer the corresponding MediaWiki pages):
Behavior switches: these are usually written as uppercase words surrounded by double underscores, e.g.__FOO__.
Variables: these are uppercase words surrounded by double braces, e.g.{{FOO}}. As such, they look a lot like templates.
Parser functions: these take parameters and are either of the form {{foo:...}} or {{#foo:...}}, e.g.{{#invoke:...}}. See also mw:Help:Extension:ParserFunctions and mw:Extension:Scribunto.
Variables and parser functions can use subst, just like templates. Page-dependent magic words will affect or return data about the current page (by default), even if the word is added through a transcluded template or included system message.
{{DEFAULTSORT:sortkey|noerror}} → Set default sort order for file or category when displayed within another category. This overrides the standard enlisting via file or category name.
File name "2021-03-29 - Old church in Aplerbeck" would normally be listed beginning with the digits "2020 ...". By stating {{DEFAULTSORT:Old church|noerror}} this file will be enlisted beginning with the letters "Old ...". By stating {{DEFAULTSORT:church|noerror}} this file will alternatively be enlisted beginning with the letters "chu ...".
The parameter "noerror" prevents an error being reported when SORT definitions collide.
Alternative method to determine sort order within the stated category (and only within this exact category): Example: [[Category:Focus stacking images by subject|unc]]:
Special:SpecialPages > Sections: Maintenance reports, Lists of pages, Login / create account, Users and rights, Recent changes and logs, Media reports and uploads, Data and tools, Redirecting special pages, High use pages, Page tools, Wikibase, Other special pages, Legend.
Special:GlobalUsage/filename: List of pages that use this file:
Special:PrefixIndex > Usage: Find items within reserved wikimedia.org namespaces by their initial letter(s); choose namespace from the namespace dropdown list, e.g. category or template, ...
Special:Preferences > Usage: Click on one or more gadgets to enable these in your browser.
Commons FAQ: What resolution should the images I upload be? Excerpt from above FAQ: "The highest resolution available for images is more than welcome. You don't have to worry about server disk space and the load-time of the Wikipedia pages that refer to them, since the software automatically generates and caches smaller (as specified in the articles) versions." However, scaling of images may fail if the image is very large and rendering takes too much time or memory (in that case, either no scaled image is shown, or the full image is served to the browser, often causing it to lock up). - For PNG images, a hard limit of 25 megapixels is in effect. - Large JPEGs are only problematic if they are saved in progressive mode, since the entire image has to be processed at once. Use baseline mode instead. In case the full scale original is too large to process for the software, upload it anyway, but then please overwrite it with a scaled down version (around 6 megapixels in size); the full scale version will still be available in the upload history, and you can add a reference to it in the image description.
The quality images project aims to identify and encourage users who provide images of high technical quality to Commons.
Featured pictures are the cream of the crop at Commons and the project is reserved for images of both extraordinary value and technical quality.
Valued images, on the other hand, are those that are the most valuable of their kind for use in an online context, within other Wikimedia projects.
The technical requirements for valued images are typically much lower, as there is no concern about suitability for print usage. A built-in camera in a modern mobile phone should be sufficient if the subject is of high value and the photo illustrates it well at a viewing size of 480×360 pixels or equivalent.
Valued images are less about technical quality and more about your ingenuity in finding good and valuable subjects which matter, and about the usability of the information on the image page.
Template:Cat see also > Usage: {{Cat see also| 1=name of category to link to | 2,3,4,...=names of further categories to link to | iw=interwiki prefix | for=descriptive text to append}}
A typical template (code: {{template_title}}) consists of a number of interacting sub-templates. But not all templates offer a method to add other language versions.
Those templates that do provide a method to add other language versions contain a sub-template usually designated as {{template_title/text}} which contains all text snippets that are to be displayed within the corresponding template.
Open the sub-template {{template_title/text}} for editing.
The basic struture is as follows:
<includeonly>{{#switch:{{{ispure}}} |parameter_value_used_within_template={{LangSwitch |en = English text. |fr = French text. |ru = Russian text (in Cyrillic). }} ...
Now, to add a German text for example, just add a line containing the language identifier de in alphabetical order. Although this is not strictly keeping in line with the proposed alphabetical order, I prefer to keep the English version to the top, as it usually is the reference version for all other languages.
<includeonly>{{#switch:{{{ispure}}} |parameter_value_used_within_template={{LangSwitch |en = English text. |de = German text. |fr = French text. |ru = Russian text (in Cyrillic). }} ...
The individual text may contain almost all code elements that wikimedia provides, although it is good practice to constrain use mostly to plain text formatting and links.
Note: links should point to items existing within the Wikipedia with the same language version. Only where not applicable, say a link to an internationalised template or a link to a Commons Help site, or no suitable counterpart exists in the proposed language Wikipedia, should links be set otherwise (see example below). Of course, you may create new content in that language's Wikipedia, based on an existing entry in another language.
The template Template:Stereoscopic 3D contains a sub-template Template:Stereoscopic 3D/text
The sub-template's master switch contains numerous entries together with the corresponding language text, some entries sporting multiple variants, e.g. line
|en = The stereogram uses the [[:en:Stereoscopic#Side-by-side|side-by-side]] cross-view method. The left frame shows the right eye's perspective, and the right frame the left eye's perspective. It might be possible to view this image [[:en:Stereoscopic#Freeviewing|without a viewing device]] by ''crossing'' your eyes to visually combine the frames.
This newly added text contains content from various German texts, in order to display usage of 4 different links: 2 links to the German Wikipedia, 1 link to this template, 1 link to a Commons Help site, and, due to lack of a German counterpart, 1 link directly to the English Wikipedia, but at least with a German description:
|de = Dieses Stereogramm benutzt die [[:de:Stereoskopisches_Sehen#Der_Kreuzblick|Überkreuz-Betrachtungsmethode]], bei der die beiden Aufnahmen zwar [[de:Stereoskopie#Stereobildpaar|nebeneinander angeordnet]], jedoch seitenvertauscht sind. Hilfestellung hierzu unter [[Template:Stereoscopic 3D|{{lang|en|Template:Stereoscopic 3D}}]]. Hilfestellung hierzu auf der englisch-sprachigen Seite [[Commons:Overwriting existing files|Richtlinien, die vor dem Überschreiben vorhandener Dateien zu beachten sind (engl.)]]. [[:en:wiggle stereoscopy|Wackelbild-Verfahren ({{lang|en|wiggle stereoscopy}})]].
How to Test a Language Version Newly Added to a Template
While editing a template the Wikipedia editor provides an opportunity to preview a page with the current template before publishing. I.e. one may enter the name of a page or a file from within the Wiki realm into the assigned field and press the button Preview page with this template.
The preview described above works for pages and files for Wikipedias in any language, also for pages and files within Wiki Commons. But, alas, even if that language is included in the said template the text will not be displayed in that language!
As of sofar I am sorry to say that haven't yet discovered a viable method to correctly test changes within language text contained within templates while in the edit mode of that template. Even the Template Help page provided no further information. Maybe I'm simply asking for too much.
Thus it is up to testing language versions after having published the modification within the language text.
This includes a thorough check that all text variants are correctly processed.
I advise using the sandbox on your Wikipedia Commons user page for this purpose. Just make an entry for each and every combination of parameter values for this template:
This file is a stereogram. Stereograms are stereoscopic images or animations which combine left and right frames showing slightly different visual angles to allow for 3D perception.
The stereogram uses the side-by-side parallel-view method. The left frame shows the left eye's perspective, and the right frame the right eye's perspective. It might be possible to view this image without a viewing device by diverging your eyes to visually combine the frames, or a stereoscope may be used.
{{Stereoscopic 3D | parallel}}
This file is a stereogram. Stereograms are stereoscopic images or animations which combine left and right frames showing slightly different visual angles to allow for 3D perception.
The stereogram uses the side-by-side cross-view method. The left frame shows the right eye's perspective, and the right frame the left eye's perspective. It might be possible to view this image without a viewing device by crossing your eyes to visually combine the frames.
{{Stereoscopic 3D | cross-eye}}
When this page is displayed in standard mode, all text within a template obstinately refer to the English text only. This is true, even if the template is applicable in another Wikipedia.
By pure chance I discovered this wonderful solution:
To force a language switch one must leave the precincts of Wikipedia and enter the URL to the page containing the template AND add a language-related parameter call ?uselang=language_identifier, e.g. ?uselang=de as follows:
FINALE: This took some time and was also a bit tricky to find out, but eventually led to a viable solution. Should anyone know of a better solution, please give me a hint. Thank you!
The following templates show the encased content only when placed on page of the English Wikipedia. (I haven't found a way to circumvent this restriction for use in other Wiki branches.)
Template:C > Establishes a link to a category, either within Wiki Commons or to another Wikipedia
> Usage: {{ C | 1=category name, optional namespace | 2=displayed text | 3=interwiki access, via language code | 4=+/- precedes category name with namespace "Category:" }}
> Note: {{c | Category:XYZ | ...}} is seemingly identical to {{w | c:Category:XYZ | ...}}
Category:Ice ages > links within Wiki Commons to the category "Ice ages" - Code variant 01: [[:Category:Ice ages]]
Category:Ice ages > links from any Wiki to Wiki Commons category "Ice ages" - Code variant 02: {{w|c:Category:Ice ages}} (will have to test this assumption!)
Here is an interplay between two related categories: I assume that the metacat|background color of the top category relates to the parameter white of the subcategory.
Master category:
Category:Cameras by background color
'''{{metacat|background color}}'''
[[Category:Cameras | ]]
[[Category:Objects by background | Cameras]]
[[Category:Images by color of background | Cameras]]
One of 6 subcategories:
Editing Category:Cameras and lenses on white background
{{de|Kameras und Objektive vor weißem Hintergrund}}
{{en|Cameras and lenses on white background}}
[[Category:Electronic devices on white background]]
[[Category:Photographic lenses]]
[[Category:'''Cameras by background color | white''']]
Extended Jumps within the Alphabetic Order of Categories
Categories normally display only up to 200 images at once, usally in alphabetical order. Whenever one occurs upon a category with a large number of images and requires one or more images near the end of the alphabet one must repetitively stride through numerous pages in a somewhat tiresome manner.
The following HTML code fragment allows one to jump straight to a file name beginning with the stated text: &filefrom=YYYY, replace the string "YYYY" with the desired beginning of file name. A single letter will suffice, case is ignored. If no file beginning with this string exists subsequent files will be displayed in rising alphabetical order.
E.g. adding &filefrom=ng to a category displaying a list of camera lenses will show up to 200 lens files beginning with a file name such as Nikon or e.g. Olympus if no Nikon lens exists in this category.
CAVEAT: The above described method is NOT compatible with the Wiki Commons standard category statement: [[:Category:Cameras_and_lenses_on_white_background&filefrom=Sony]] as this is coded as https://commons.wikimedia.org/wiki/Category:Cameras_and_lenses_on_white_background&filefrom=Sony, which results in an invalid statement! On the contrary this call only offers to create a new page.
Simple queries without special characters ("/", ":", ")", etc.) may easily be constructed as follows: https://commons.wikimedia.org/w/index.php?title=Category:category_designation&filefrom=string_containing_initial_character(s)_of_first_file_name_to_be_displayed NOTE: replace all blanks within the category designation and the initial file name string with underscores.
These pages provide hints and help as how to assemble a correctly written, correctly formatted, and correctly referenced wiki article, avoiding most pitfalls that "newbies" such as I will surely encounter:
Wikipedia: Article wizard → Getting started - what to consider and what to do to create your fírst Wikipedia article.
Wikipedia: Policies and guidelines Excerpt: "Wikipedia's policies and guidelines are developed by the community to describe best practices, clarify principles, resolve conflicts, and otherwise further our goal of creating a free, reliable encyclopedia. There is no need to read any policy or guideline pages to start editing. The five pillars are a popular summary of the most pertinent principles."
Wikipedia: Disambiguation > resolve conflicts that arise when a potential article title is ambiguous, i.e. refers to more than one subject covered by Wikipedia.
Problem: Whenever you try to access a Wikipedia page that contains a REDIRECT statement, the REDIRECT will automatically apply and you will be catapulted to the destination page stated in the REDIRECT statement.
Template:C > Establishes a link to a category, either within Wiki Commons or to another Wikipedia
> Usage: {{ C | 1=category name, optional namespace | 2=displayed text | 3=interwiki access, via language code | 4=+/- precedes category name with namespace "Category:" }}
> Note: {{c | Category:XYZ | ...}} is seemingly identical to {{w | c:Category:XYZ | ...}}
Another attempt at using a template declared in another wiki. In the following I will try to call a template defined within Wikipedia from this Wiki Commons userpage.
{{picture of the day|2021-11-01}} => calling this code from Wiki Commons causes an error, although valid in Wikipedia.
(2) wikipedia:en:template:POTD displays template page of "template:POTD", but doesn't resolve the template itself.
(3) wikipedia:en:template:POTD/2021-11-01 displays template page of "template:POTD/2021-11-01", including the POTD image, but also doesn't resolve the template itself.
Portrait of French novelist Jules Verne taken in 1884 by Étienne Carjat. Known for his adventure novels taking into account the technological progress of his time, he's the second most-translated author in the world. He died on this day 120 years ago.
Portrait of French novelist Jules Verne taken in 1884 by Étienne Carjat. Known for his adventure novels taking into account the technological progress of his time, he's the second most-translated author in the world. He died on this day 120 years ago.
Found a simple, concise method to send a simple "thank you" to another wiki user.
Method 1: via talk pages.
Method 2: send a "thanks for editing" in the edit history of files and wiki commons pages.
Method 3: Using template Reply to, described as follows as Method C.
This template takes advantage of the new user mention notification to ping the user(s) you are replying to in a discussion (so you don't have to use the {{talkback}} template).
It works on any talk page or Project namespace page. It also works on the Support Desk.
This template is particularly helpful in discussions that are not threaded, to indicate which user's comment is referenced. If you feel that this template unnecessarily personalizes the discussion, you may still use the {{talkback}} template on the user's talk page to indicate that you have replied to a comment.
Note that it isn't necessary to use this template to ping (indicate) the user if you are already linking to their username from your post.
Portrait of French novelist Jules Verne taken in 1884 by Étienne Carjat. Known for his adventure novels taking into account the technological progress of his time, he's the second most-translated author in the world. He died on this day 120 years ago.
Portrait of French novelist Jules Verne taken in 1884 by Étienne Carjat. Known for his adventure novels taking into account the technological progress of his time, he's the second most-translated author in the world. He died on this day 120 years ago.
The page that describes the theme "Picture of the Day" on Wikipedia can be referenced as such:
Now this is a pleasing combination of a link connected to a text followed by the same link connected to a minimised image (takes a second or two for size reduction):
Wiki Commons: use template {{Wikidata Infobox}} to display an Infobox containing information from the Wikidata item where the statement "Commons category" points to the Wiki Commons entry.
Example:
Name of Wiki Commons entry: Canon FD 500 mm f8.0
Name of Wikidata entry: Canon FD 500mm F8 reflex lens (Q96954124)
Commons category for above Wikidata entry: Canon FD 500 mm f8.0
Problem: Image notes / image annotations won't show up since a new version of the image was uploaded.
Check: Check whether the image dimensions have changed, this is sometimes barely perceptible.
Reason: The positions of image notes are strictly linked to the image's dimensions. This is to prevent wrong positioning if someone changes the image size, even by simply one single pixel.
Possible causes: Any tilt / perspective correction of your image after your initial upload could reduce or sometimes even slightly enlarge image size.
Template:CSS image crop
From Wikipedia, the free encyclopedia
Jump to navigation
Jump to search
Template documentation[view] [edit] [history] [purge]
{{CSS image crop}} creates a crop of an image inline for previewing the look and feel of a page, or for linking to full images when a slight crop is preferred in an article, but the full image is more encyclopaedic in general. Where only a small section of the image is used after the crop, it's best to upload the crop as a new file, to avoid sending the extra image data to users.
{{CSS image crop
|Image = The Name of the image file, or may accept {{Annotated image}}.
|bSize = The Base Image width in pixels (the image we are cropping on)
|cWidth = Crop Image Width in pixels
|cHeight = Crop image Height in pixels
|oTop = Offset Top in pixels, optional and defaults to 0 when omitted
|oLeft = Offset Left in pixels, optional and defaults to 0 when omitted
|Location = 'right', 'left', 'center' or 'none'. Determines placement of the image on the page
Defaults to 'right' when description is provided (as is default for thumb images)
When description is blank, location on left (as is default for non-thumbs)
|Description = Description (will render out using thumbnail class)
|Link = Name of an article to be linked by clicking on the image (omit unless there is a
good reason to link to an article instead of the image).
|Alt = The alt text for the image.
|Page = The page of the file, if there are multiple pages (such as pdf files).
|magnify-link = The image to be linked by the magnify icon (Use if the Image parameter is set to
{{Annotated image}} or the Link parameter leads to something other than the image).
}}
Caveat: Only works for links to pages (also template, special, etc. pages) within other wikis, but cannot resolve templates which are only defined on that other wiki, such as {{Picture of the day}} defined within the english wikipedia.
On which page within Wikipedia do I find the basis of the claim that an image must have been included within a wikipedia article for at least 7 days before it may be proposed as a "Featured picture"?
Advance to criterion no. 5: "Adds significant encyclopedic value to an article ..."
Read bullet no. 1: "... It is preferable to wait a reasonable period of time (at least 7 days) after the image is added to the article before nominating it. ..."
Where within Wikipedia do I find a list of Featured pictures that have not appeared on the main page?
Whenever an image has been uploaded to Wikimedia Commons and after the appropriate file information has been provided, a request appears asking you to provide so called "structured data".
Structured data has a well-defined structure, which sets off from simple statements, but may also be combined to amazingly complex statements.
Most (all?) structured data is stored in the Wikidata database.
Each "item = noun " and "property = verb" used to create structured data has a key number.
The noun "farmhouse" e.g. has a key number of Q489357.
The verb "depicts" e.g. has a key number of P180.
Caption as initial example of using Structured Data
First choice for images is the "depicts" statement, which is the default statement provided for new entries.
If your image displays a horse galloping across the yard in front of a farmhouse, you will at least provide the following statements by typing the catchword into the input field and press the [ENTER] kay:
horse [ENTER]
Choose the correct entry from the dropdown list, i.e. horse domesticated (work) animal [ENTER]
Repeat for other terms applicable to the "depicts" statement:
farmhouse [ENTER]
farmhouse chief dwellings attached to farms, ... [ENTER]
yard [ENTER]
yard area of land ajacent to a building ... [ENTER]
gallop [ENTER]
gallop gait of a horse [ENTER]
Close data entry by clicking on [Publish changes] or discard changes by clicking on [Cancel].
Once a Wikimedia Commons entry has been stored, you will find the "Structured data" tab to the right of the "File information" tab. Click on tab to reveal the list of already stored structured data and allow adding editing.
NOTE: Wikimedia Commons adds a certain number of data overnight. The following items are extracted from the file information you initially provided:
Creator, copyright status, copyright license, source of file, inception, and coordinates of the point of view.
You will find the key number for an item by hovering over the catchword in the list.
horse => d:Special:EntityPage/Q726
farmhouse => d:Special:EntityPage/Q489357
yard => d:Special:EntityPage/Q1623185
gallop => d:Special:EntityPage/Q1766807
How to add additional entries to Structured Data List
The above example was kept very simple and will suffice for most purposes.
Should a full description require more than just a "depicts" statement, you must find the appropriate property to match your needs.
Finding the correct verb is not a trivial process!
To add a new structured data item scroll down to the end of the list and click on the button [+ Add statement].
The input field that now unfolds sports looking glas icon and the phrase "earch to add properties (part of, media type, etc.) from Wikidata".
As you type in the desired property the search engine displays up to six of the best-matching suggestions.
NOTE 1: The phrase "part o" does not display the same list of matches as the phrase "part of" does.
NOTE 2: Trailing blanks are ignored, but the phrase "part of" with two blanks between characters matches nil.
NOTE 3: When you type in a statement that already exists in the list, you are shown only a blank drop-down list, but not, as one would normally assume, a warning stating such as "Please avoid creating duplicate entries".
How to find additional entries to Structured Data List
The following properties require at least one additional so called "item", which in turn may require at least one so called "qualifier".
Only "items" with special connection properties are allowed, but one may seemingly choose a multitude of items, of wich, alsas, only very few are eligible.
E.g. one may add the "item" "plant" to the statement "part of", but after a few seconds a lightning bolt icon appears, which, when hoverering over, states "This statement has some issues". By clicking on this icon an explanation appears, e.g. "Issues / allowed entity types constraint / The property 'part of' should not be used on this type of entity, the only valid entity type is 'Wikibase item'.".
On the other hand, the item "camera" is allowed, although it is certainly not the object the depicted subject "plant bud" is a part of!
On the whole, the treatment of statements that go beyond the most simple statements is a very tricky business, and, at least for me, is a matter of trial and error.
Information about property "part of"
part of [ENTER]
part of object of which the subject is a part (...). Inverse property of "has part" (P527, see also "has parts of the class" (P2670)). [ENTER]
part of => d:Special:EntityPage/P361
Information about property "media type"
media type [ENTER]
IANA-registered identifier for a file type (MIME). [ENTER]
part of object of which the subject is a part (...). Inverse property of "has part" (P527, see also "has parts of the class" (P2670)). [ENTER]
part of => d:Special:EntityPage/P4082
Note: Accepted items are:
Sony α7R IV (Q65976324), camera (), model series (), and surely more ..., but not a lens such aus "Canon MP-E 65mm f/2.8 1–5x Macro lens". The lens model is accepted at first, but an exclamation mark icon appears within seconds that states "This statement has some issues". By clicking on this icon an explanation appears, "Potential issues / value type constraint / Values of 'image captured with' statements should be instances of one of the following classes (...), but ... currently isn't: camera model, model series, cell phone model".
And as only one camera was employed in the making of this image, one should choose the exact camera make "Sony α7R IV".
First by adding the property "connects with" to the above created "Sony α7R IV" (which in turn is enable via the property "image captured with").
Second by adding a specific lens, such as "Canon MP-E 65mm f/2.8 1–5x Macro lens" into the "sub-qualifier" input field just beside on the right.
Information about property "connects with"
connects with [ENTER]
connects with item with which the item is physically connected [ENTER]
connects with => seemingly, no key number specified (d:Special:EntityPage/Pnnnnn)!
Enter lens name:
To the right of the property "connects with" is an input field that accepts a specific lens, such as "Canon MP-E 65mm f/2.8 1–5x Macro lens".
Entering the phrase "canon mp" suffices to whittle down the selection to a single entry in the drop-down list, which you must now click on to accept as the desired entry.
Close data entry by clicking on [Publish changes] or discard changes by clicking on [Cancel].
How to add fabrication method and specific "Manufacturer" to Structured Data List
(d) item "Zerene Stacker" (doesn't exist, thus click on button "..." and choose "No value exists for this property"). But comparable item "Helicon Focus" (Software) exists.
Information about statement "fabrication method"
fabrication method [ENTER]
fabrication method item with which the item is physically connected [ENTER]
fabrication method => d:Special:EntityPage/P2097
Information about item "focus stacking"
focus stacking [ENTER]
focus stacking digital image processing technique [ENTER]
focus stacking => d:Special:EntityPage/Q1435078
Information about qualifier "manufacturer"
manufacturer [ENTER]
manufacturer item with which the item is physically connected [ENTER]
manufacturer => seemingly, no key number specified (d:Special:EntityPage/Pnnnnn)!
Information about item "Zerene Stacker"
Zerene Stacker [ENTER]
Zerene Stacker software producer [ENTER]
Zerene Stacker => d:Special:EntityPage/Qnnnnnn (yet to be defined)
Remedy: click on button "..." and choose "No value exists for this property".
Close data entry by clicking on [Publish changes] or discard changes by clicking on [Cancel].
The following structured data elements remain to be explored as to within which context they may be used:
Statement "photos by lens used" (Q63633670)
Statement "participant in"
Statement collection for "creator":
"object has role: photographer"
(qualifier) role or generic identity of the value of a statement ("object") in the context of that statement; For the role of the item the statement is on ("subject"), use P2868.
"subject has role: photographer"
role/generic identity of the item ("subject"), also in ther context of a statement. For the role of the value of the statement ("object"), use P3831 ("object has a role"). For acting roles, use P453 ("character role"). For persons, use P39.
NOTE: "subject has role: photographer" prvokes a "Potential issues" warning:
allowed qualifiers constraint: "subject has role" is not a valid qualifier for "creator" - the only valid qualifiers are:
Within the subpage Structured data of a Wikimedia Commons item one may add additional properties or add a qualifier to an existing property.
This can sometimes be quite frustrating as the structure checking mechanism will unerringly annonunce:
Potential issues
allowed entity types constraint
The property YYYY should not be used on this type of entity, the only valid entity type is Wikibase ZZZZ.
It took me quite a time to figure out why such properties are not rejected immediately, but are marked as "having potential issues" a few seconds after they have been published.
EXAMPLE:
The property media legend (P2096) may preside as both a main property or as a qualifier. First choose this property, then the appropriate language identifier en, and then enter the desired text, e.g. Retail company: Ensign Ltd, UK.
After publishing this will result in the line: media legend : Retail company: Ensign Ltd, UK(English)..
The structure checking mechanism will take a few seconds and will then annex an icon to the statement, usually an exclamation mark enclosed in a circle.
Click on the icon to view the cause, in this case:
Potential issues
allowed entity types constraint
The property media legend should not be used on this type of entity, the only valid entity type is Wikibase item.
EXAMPLE continued:
The property media legend will always be annotated here by the structure checking mechanism because the whole page is a Wikimedia Commons file and NOT a Wikibase item. Wikibase items are displayed in Wikidata where the property media legend may be applied to almost any Wikidata entry, except when forbidden by some constraint stated within the property declaration.
Even though marked as mildly incorrect, the entry will still remain. Other icons may behave differently.
How to add unstructured information to any property within Commons:Structured data
To state with which lens the image was taken one would normally use the property connects with (P) and choose the corresponding lens, e.g. Sony Carl Zeiss Sonnar T* FE 55mm F1.8 ZA (Q30646072), from the Wikidata database.
In this special case the lens Sony FE 200-600mm F5.6-6.3 G OSS (now established as Q110096014) had not yet been described within the Wikidata database.
In such a case I take resort to either the property inscription or catchphrase to add a preliminary text such as connects with: Sony FE 200-600mm F5.6-6.3 G OSS to preserve this information until the hitherto undescribed lens has been added to the Wikidata database.
Once this has been achieved add the property connects with to the newly described lens and do not forget to delete the preliminary, now superfluous property.
You can use the Wikimedia Commons search function to find files with structured data. Just enter the query string into the search input field at top right.
A few examples:
Note: all results are sorted by "date of latest edit"
All files that do not have a depicts statement → -haswbstatement:P180. → NOTE: Stating the query form as haswbstatement:-P180 (with the "-" character set just after the colon) is invalid!
You can extend a query to include qualifiers by suffixing the qualifier statement within brackets "[...]".
General format haswbstatement:Pnnnn=Qmmmm[Pxxxx=Qyyyy].
Example query 01 including qualifier: haswbstatement:P180=Q39053219[P462=Q23445] → searches for "depicts (P180) Zeiss Batis Distagon T* 2.8/18mm (Q39053219)" in combination with a QUALIFIER stating "color (P462) = black (Q23445)".
Example query 02 including qualifier: haswbstatement:P4082=Q65976324[P2789=Q20720780] → searches for "captured with (P4082) = Sony α7R IV (Q65976324)" in combination with a QUALIFIER stating "connects with (P2789) = Sony FE 90mm F2.8 Macro G OSS (Q20720780)".
Common query operators: plain text (multiple words enclosed in ""), insource, incaption, incategory, intitle, hascaption, hastemplate, filesize, filewidth, fileheight, fileres, filetype, filemime, filebits, prefix, nearcoord, deepcat, hastemplate, haswbstatement, help and more.
Found this example at "Commons talk:Quality images candidates".
Search for insource:/Quality (images (of|from|in)|black and white|night shots)/ -incategory:"Quality images" → The accompanying text (i.e.. source) contains one of the expressions "quality images of", "quality images from", "quality images in" "quality black and white", "quality night shots", but the file is explicitly not a member of the category "Quality images".
Result: found 426 images on Thu., 2021-05-13. These are in QI (sub) categories, but not in Quality images.
Result: found 671 images on Tue., 2023-01-31. Note: the above search applies to "search in" files only (see trailing "&ns6=1" in browser string).
The following result appears when no restrictions apply to "search in": 13,055 images on Tue., 2023-01-31. Note: see trailing "&ns0=1&ns6=1&ns12=1&ns14=1&ns100=1&ns106=1" in browser string.
NOTE: Removal is possible via batch task VisualFileChange. I guess one must have administrator permissions to make use of this batch job. It must somehow be related to [[Category:VisualFileChange]].
Nevertheless, even though I have no access to this batch task these are the parameters required for this batch task:
Search: insource:/Quality (images (of|from|in)|black and white|night shots)/ -incategory:"Quality images"
Replace (by nothing): /\[\[Category:Quality (images (of|from|in)|black and white|night shots)[^\[\]\:]*\]\]\s*/g
Preserve: /(\[\[Category:Quality [^\[\]]* by [^\[\]]*\]\])/
Summary: rm qi cat (never nominated as qi) - see COM:QI
→ To negate the 'incategory' section of the query apply a minus sign as follows:
author:"Franz van Duns" hastemplate:"QualityImage" -incategory:"Valued images by Franz van Duns"
→ One can also negate the 'incategory' section of the query by alternatively placing the minus sign as follows (applies to 'incaption' ONLY, and ONLY when the query subject is enclosed within ".."!):
author:"Franz van Duns" hastemplate:"QualityImage" incategory:-"Valued images by Franz van Duns"
→ Astoundingly, a "double-minus" combination cancels both terms, thus resulting in a positive statement (applies to 'incaption' ONLY, and ONLY when the query subject is enclosed within ".."!):
author:"Franz van Duns" hastemplate:"QualityImage" -incategory:-"Valued images by Franz van Duns"
Commons Photo Challenge winners by Franz van Duns:
→ The following information has been copied from the master article:
Usage: This template defines a bot-generated list based on Wikidata. It must begin as {{Wikidata list|sparql=
SELECT ... and must be "closed" with {{Wikidata list end}}. The text between these two templates will be periodically (once every 24h) replaced by the bot-generated list.
This list is automatically generated from data in Wikidata and is periodically updated by Listeriabot. Edits made within the list area will be removed on the next update!
Caveat 01: At this moment, only one list per page is possible.
Caveat 02: The query MUST include the ?item variable - do not rename it.
Caveat 03: Acording to the template documentation the Template:Wikidata list may be blocked for use on your Wikipedia, including the English (main) version. I understand that this template may function on your Wikipedia Userpage. This template is workable on Wikidata, maybe also on Commons - I'll simply try.
Examples
Example 01: This Commons page contains a list of predefined database reports: Database reports.
Example 02: This Commons page contains a database report which results in a tabular list of cameras with corresponding Wikidata values: Database reports/Cameras
Code: Query: SELECT ?item WHERE { { ?item wdt:P2009 ?dummy0 . } UNION { ?item wdt:P2010 ?dummy1 . } UNION { ?item wdt:P2033 ?dummy2 . } }
Basic problem: Most articles about camera bodies or camera lenses (objectives) remain in the basic classification "|class=start" or "|class=stub", as stated on the Talk page. A few articles have been ascended to classification "|class=C". Haven't, as yet, found any articles of a higher classification "|class=B|C|FA|..."
My goal: create a list that displays the class rating "|class=???" of those pages that contain the phrase "camera" or "lens" in the corresponding article.
Use template {{PD-scan|PD-old-100}} as proof of valid license for the following constellation:
This image is in the public domain because it is a mere mechanical scan or photocopy of a public domain original, or – from the available evidence – is so similar to such a scan or photocopy that no copyright protection can be expected to arise. The original itself is in the public domain for the following reason: This work is in the public domain in its country of origin and other countries and areas where the copyright term is the author's life plus 100 years or fewer.
This image is in the public domain because it is a mere mechanical scan or photocopy of a public domain original, or – from the available evidence – is so similar to such a scan or photocopy that no copyright protection can be expected to arise. The original itself is in the public domain for the following reason:
This work is in the public domain in its country of origin and other countries and areas where the copyright term is the author's life plus 100 years or fewer.
You must also include a United States public domain tag to indicate why this work is in the public domain in the United States.
This tag is designed for use where there may be a need to assert that any enhancements (eg brightness, contrast, colour-matching, sharpening) are in themselves insufficiently creative to generate a new copyright. It can be used where it is unknown whether any enhancements have been made, as well as when the enhancements are clear but insufficient. For known raw unenhanced scans you can use an appropriate {{PD-old}} tag instead. For usage, see Commons:When to use the PD-scan tag.
Note: This tag applies to scans and photocopies only. For photographs of public domain originals taken from afar, {{PD-Art}} may be applicable. See Commons:When to use the PD-Art tag.
{{ImageNote|id=1|x=4880|y=2254|w=1094|h=376|dimx=7952|dimy=5304|style=2}}
Remnant of the primary contrail within the distrail. A narrow, contorted white vortex just above the lower edge of the transparent wake.
{{ImageNoteEnd|id=1}}
{{ImageNote|id=2|x=2050|y=3530|w=266|h=170|dimx=7952|dimy=5304|style=2}}
Presumably another trace of the primary contrail. The white vortex almost merging with the cloud's edge.
{{ImageNoteEnd|id=2}}
Excerpt from article: A cultivar name consists of a botanical name (of a genus, species, infraspecific taxon, interspecific hybrid or intergeneric hybrid) followed by a cultivar epithet. The cultivar epithet is enclosed by single quotes; it should not be italicized if the botanical name is italicized; and each of the words within the epithet is capitalized (with some permitted exceptions such as conjunctions)
To search for a Wikidata entry of which the code number (Qnnnn) is known, type this statement into the Wiki Search field (usually positioned at the top of every Wiki page): haswbstatement:P180=Qnnnn. > Example: haswbstatement:P180=Q21233320.
How to link Commons categories to Wikidata categories: Help:FAQ#Other Wikimedia sites > When on that page, scroll to entry no. "7. How do I link a Commons category to Wikidata?". Full text of entry 7 as follows:
Where possible, a Commmons category should be linked to a Wikidata category item, in the "other sites" section, e.g., as on Category:London (Q7149656) code: {{Q|7149656}}. A Commons category (P373) statement is also added on the corresponding main item, London (Q84), since some software won't search category items to find the Commons category. If there is no category item the Commons category can be added to the "other sites" section of a main item, e.g., as on Old War Office Building (Q58454576). There's a bot that will add Commons category (P373) statements, so these don't usually need to be done by hand. Code example:
This section is based on my past experience with Exif data in general. It is both a compendium of basic facts about Exif data and Exif tags and a selection of examples that solve some real-life cases for persons challenged with working with image metadata in single or multiple files.
See this Commons page that describes what Exif data is and how individual Exif tags are accessed or modified.
Refer to Commons list of Exif-editing tools for various operating systems: Edit Exif fields.
One of these tools is the highly versatile and well-documented Exif editor ExifTool (or at this mirror site), which is available for Unix, Windows, and other operating systems
View a short selection of code examples with commands in UNIX notation: Commons: Exif examples.
View an extended selection of code examples with commands in Microsoft Windows notation: see below.
View the the original compilation of code examples containing commands in both UNIX and/or Microsoft Windows notation in the latter part of the ExifTool manual, especially the chapters: READING EXAMPLES, WRITING EXAMPLES, COPYING EXAMPLES, RENAMING EXAMPLES, GEOTAGGING EXAMPLES, PIPING EXAMPLES.
The ExifTool manual is not directly accessible, but must be extracted from the installed EXE file via a command (Windows notation) such as:
"exiftool(-k).exe" > ExifTool_manual.txt
You may, of course, use any other of the tools mentioned above in the list of Exif-editing tools.
Very many image files contain a hidden EXIF data block.
An EXIF data block contains a series of tags that supply additional information about an image.
EXIF tags are arranged in groups: e.g. FILE, EXIF, IPTC, XMP, ICC_Profile, Abobe, Photoshop, various manufacturers of photographic equipment (CANON, NIKON, MINOLTA, SONY, ...), ...
The image files produced by a stills camera (e.g. .JPG, .DNG, .HEIF, various RAW files, ...) or by a video camera (e.g. MOV, MP3, MP3, ...) contain
(a) a basic set of EXIF data tags and
(b) a set of tags specifically for each manufacturer, some tags even specified for only one series of cameras.
NOTE 01: The basic set of EXIF data tags may be spread over many groups.
NOTE 02: The manufacturer-specific set of EXIF data tags may also be spread over many groups.
The internal name of the EXIF tags must not contain a space character. Only the external representation, e.g. as displayed by Wiki Commons Metadata, may contain spaces and are available in a number of languages.
Most internal tag names are simple concatenations of the external name. Example: "Metering mode" is concatenated to "MeteringMode", but "ISO speed rating" is abbreviated to "ISO".
Note that all tags written into the EXIF data block in a file, i.e. into the "EXIF datablock storage area", are numeric. All internal and external tag names are stored in a master table that defines which text to supply for each numeric value.
VERY IMPORTANT FACT: Every imaging software that modifies, crops, or merges an image and subsequently writes it to storage is sure to modify the EXIF data. This applies even if the image is simply viewed and then stored, i.e. rewritten to the same file without having changed a single value!
The EXIF data may be altered as follows:
(a) Tag content is altered or replaced. Example: date/time set to new values.
(b) Tag content is extended with additional information. Example: add additional (comma-space-separated) keywords to previously existing keywords in tag "Keywords".
(c) Tag is deleted. Example: Adobe Photoshop deletes many SONY tags, i.e. "LensModel", when the EXPORT fuction is applied.
(d) Content of tag is copied to another tag. Example: contents of "ExposureTime" copied to "ShutterSpeedValue".
(e) Content of tag is copied to tag in another group. Example: ....
(f) The contents of two or more tags are combined to a new tag. Example: "ImageSize" ("9504x6336") combines "ImageWidth" ("9504") and "ImageHeight" ("6336"), separated by an "x".
Disallowed operations:
(g) A tag may not be renamed, but the content may be copied to a new tag, then delete the original tag. Example: the tag "FullImageSize" within a SONY .ARW file is copied to tag "ImageSize" in the destination JPG file, then tag "FullImageSize" is deleted..
Some actions by imaging software may lead to incorrect content of EXIF Tags.
Adobe Photoshop may in certain instances add a time zone modifier to "Date/Time Created".
Example:
Date/time in SONY (.ARW) RAW file: Date Created: 2019:03:07 18:10:37 Displayed in Wiki Commons metadata as: 18:10, 7 March 2019
Date/time after Export to JPG format with Adobe Photoshop: Date/Time Created: 2019:03:07 18:10:00+02:00 Displayed in Wiki Commons metadata as: 20:10, 7 March 2019
Incorrect EXIF data such as explained in above example may be corrected with an appropriate tool.
The Wiki Commons section "Metadata" at the end of every Commons image file description page displays a selection of EXIF tags. Click on "Show extended details" to display an additional set of EXIF tags.
Even the extended set doesn't display all the EXIF tags within the image. Only a specialised tool such as the freeware "ExifTool" will expose all EXIF-based information stored within an image file.
If you intend to discover "hidden" EXIF tags and/or repair incorrect EXIF tags (e.g. wrong date or time) contained in your images, then you should address the freeware "EXIFTool" by Phil Harvey at ExifTool, as already mentioned above.
After have become accomodated to using Exif data you will notice that quite often a tag which you know is embedded within an image is shown in one programme's list of Exif data, but not in another's. Or, various programmes and/or operating systems may display different values for the same tag. Why is this the case?
The most common explanation that a tag which you know to be contained in an image is not shown is that it is not within the selection of Exif tags this programme and/or operating system is intended to display. That tag is thus ignored.
Another common explanation is that this is a duplicate tag, i.e. this tag name is contained within two (or more) Exif groups.
Example: Both the Exif groups [File] and [EXIF] contain tags named "ImageWidth" and "ImageHeight".
The Exif documentation defines a precedence order for identical tags within different groups, but your programme and/or operating system may simply choose to ignore this order and display the hitherto suppressed value.
Example 1 (these values should normally be identical, but due to incorrect image processing and/or manipulation this is not always the case!):
Programme A displays "ImageWidth" correctly as 7952. This value is retrieved from [File:ImageWidth].
Programme B doesn't display "ImageWidth" at all. This happens when the value of [EXIF:ImageWidth] is not set / empty.
Example 2 (these values should normally be identical, but due to incorrect image processing and/or manipulation this is not always the case!):
Programme C displays "ImageWidth" as 7952. A value retrieved from [File:ImageWidth] = 7952, which wasn't corrected after cropping.
Programme D displays "ImageWidth" as 7500. This is the value of [EXIF:ImageWidth] = 7500, the correct new value after cropping.
The following examples require that the freeware "ExifTool" be installed on your windows computer. Refer to the link mentioned in the previous section. All examples are rendered in Microsoft Windows CMD notation, to be modified and/or copied directly into the Windows CMD window.
Note that I assume that you are acquainted with how to access and use the Microsoft Windows CMD window, how to refer to EXE files stored in another location, and when to add double quote marks to override the standard processing of special characters, such as space, "<",">", and others. Processing of double-byte characters in certain EXIF tags is explained in the ExifTool manual (see above on how to retrieve the manual directly from the EXE file).
Display all EXIF tags (herewith named "tags") contained within your image. All examples in Microsoft Windows CMD format.
View all tags of all files in current folder, including tag duplicates (-a). Write external tag name and content:
"exiftool(-k).exe" -a *.*
View all tags within the group [File] (-FILE:all) of all files in current folder, including tag duplicates (-a). Write external tag name and content:
NOTE: There is also a group named "EXIF". All tags within the group [EXIF] form a part of the overarching EXIF data collection that is embedded in an image file and which comprises all EXIF tags.
"exiftool(-k).exe" -a -FILE:all *.*
Export all EXIF tags of all files, excluding .TXT files (--ext txt), including tag duplicates (-a), into file "EXIF_EXTERNAL_TagNames.txt". Write external tag name and content:
"exiftool(-k).exe" -a --ext txt *.* > EXIF_EXTERNAL_TagNames.txt
Export all EXIF tags of .JPG and .TIF files within the current directory, including tag duplicates (-a), into file "EXIF_INTERNAL_TagNames.txt". Write database tag name (-s) and content:
"exiftool(-k).exe" -a -s *.jpg *.tif > EXIF_INTERNAL_TagNames.txt
Export all EXIF tags of file "test.arw", including tag duplicates (-a), into file "EXIF_INTERNAL_TagNames.txt". Write group name, database tag name (-s), and content:
This command enables you to see within which groups tag duplicates (or even triplicates, all with identical tag name) are actually stored.
"exiftool(-k).exe" -a -s -g:0:1:2:3:4:5:6:7:8:9:10 -groupNames test.arw > EXIF_INTERNAL_TagNames.txt
How to import EXIF tags from another image file. Source and destination files may be of completely different formats, e.g. you may copy all kinds of tags from .TIF or .RAW to .JPG. All examples in Microsoft Windows CMD format.
For German-speaking users, the site SelfHTML is the most popular free reference for HTML code, CSS, Javascript, and SVG (alas, no English translation available).First of all, this fact is important: One may use, and in some instances, even interweave Markup code and HTML code, provided every opening mark is correctly balanced with a terminating mark of the same code type (Markup or HTML).
Examples:
Either use Markup code such as '''text''' or HTML such as <b>text</b> to emphasize text - result: xyz.
Here's an eclectic collection containing examples of advanced or unusual formatting code that I have found useful within the realm of Wikipedia / Commons:
Reduce text size in a table element (e.g. to 80% of standard size):
First attempt at adding an image map to an existing image which already has at least one ImageNote has led to the following situation:
Clicked on the ImageMapEdit > text that is now displayed underneath the Wiki Commons Image.
Both the line and the icon that indicate that annotations exist disappear, the ImageNote is no longer active on this page, no outline appears when placing the mouse over the image.
Created a circular "image map" as a first example, copied the displayed code, entered a relevant link into the "[[]]" brackets and saved the altered page.
The top image is now displayed in full size (9504x6336) beneath the regular image.
No outlines visible, but placing the mouse on the circular area defined above does let the before defined link pop up.
NOTE: ImageNote now completely inactive:
Although the code for the ImageNotes still exists, it is no longer active on this image.
Reloaded page -> to no avail.
Reloaded page with forced reloading -> to no avail.
Forced purge: https://commons.wikimedia.org/w/index.php?title=File:Ensign_Midget_-_model_22_camera_in_comparison_to_a_type_135_film_roll.jpg&action=purge instead of "&action=purge". -> to no avail.
Cleared browser cache and reloaded / purged page -> all to no avail.
RESUMEE: As long as "image map" code exists on a page, "ImageNotes" are deactivated.
Removed "image map" code:
Removed "image map" code and saved page.
Reloaded page -> to no avail.
Reloaded page with forced reloading -> to no avail.
Forced purge: https://commons.wikimedia.org/w/index.php?title=File:Ensign_Midget_-_model_22_camera_in_comparison_to_a_type_135_film_roll.jpg&action=purge instead of "&action=purge". -> to no avail.
Cleared browser cache and reloaded -> EUREKA! That did the trick!
Image Map and ImageNotes are mutually exclusive.
Insert code for one or the other, but not both on the same image page.
By the way, the "ImageNoteEditor" may remain active within one's preferences. Just do not click to use it on a page that already has ImageNotes.
Anyone know a solution to this conundrum? Let me know. Thanx.
.jpg){kind=link}
.jpg){kind=link}
