Ring of Brodgar talk:Image Naming

From Ring of Brodgar
General Talk, Research and Info on RoB Image naming.

Why image-name scheme's/conventions

  • For one to prevent image-name collisions.
  • Making image naming more structured, and thereby more easy to name new images.
  • Lowering image names with odd, or worse complete random, names.
  • Not to forget. Code wise, anything not structured can´t be used/supported in any code.
  • Apart from having case specific scheme's, a more global scheme conventions is also useful.
  • ...


Strongly leaning towards using a overall schema where the common denominator for a given image set is used as leading keyword. --.MvGulik. 22:27, 13 October 2019 (EDT)

  • Mediawiki is kinda limited in it searching behaviors. Finding stuff based on some leading keyword/string works ok, but searching for intermediate or trailing keywords/strings is not really possible.
  • Sets of related images have generally less common denominator cases, compared to the number of individual name cases. Making searching for keywords a lesser job than searching for all individual name cases.
  • ("-" vs " - " as image-parts delimiter) ... Going for the none-spaced "-" variant.
    Although from a visual listing point of view the " - " case is very attractive. From a link-writing point of view its seems not so attractive. Might also have a potential high typo rate. And in addition its currently not clear if the spaces in the spaced " - " case might trigger some scripting issues along the way (spaces being potential subject to automatic-stripping).
    --.MvGulik. 08:30, 14 October 2019 (EDT)

Current general used

Case
(special order)
Count
1
Count
2
Style
12 34 56 78
Remark (list links)
(All Image-Names) 5328 -
"legacy-*" 921 ☐☐ ☐☐  ☐☐ - A B
"* in garden pot" 22 ☐☐ ☐ ☐☐ ☐☐
"* ingame" 43 (44/1) ☐☐ ☐ ☐☐ ☐☐
"* map" 9 ☐☐ ☐ ☐☐ ☐☐
"* terrain" 9 (11/2) ☐☐ ☐ ☐☐ ☐☐
"*-dead" 27 ☐☐ ☐☐ ☐ ☐☐
"*-skeleton" 25 ☐☐ ☐☐ ☐ ☐☐
"*-skinned" 27 ☐☐ ☐☐ ☐ ☐☐
"*ingame" 23 (67/44)  ☐☐ ☐☐ ☐☐
"*map" 28 (37/9)  ☐☐ ☐☐ ☐☐
"*terrain" 28 (39/11)  ☐☐ ☐☐ ☐☐
"act*" 25 ☐ ☐☐ ☐☐ ☐☐ - A B
"barrel - *" 33 ☐☐ ☐☐ ☐☐ ☐ - A B
"board-*" 43 ☐☐ ☐☐ ☐ ☐☐ - A B
"bone *" 14 ☐☐ ☐ ☐☐ ☐☐ - A B
"bucket-*" 42 ☐☐ ☐☐ ☐ ☐☐ - A B
"cave *" 21 (27/6) ☐☐  ☐☐ ☐☐ - A B
"character *" 13 ☐☐ ☐ ☐☐ ☐☐ - A B
"cleaned *" 13 ☐☐ ☐ ☐☐ ☐☐ - A B
"dead *" 21 ☐☐  ☐☐ ☐☐ - A B
"experience-*" 79 ☐☐ ☐☐ ☐ ☐☐ - A B
"filet of *" 28 ☐☐ ☐ ☐☐ ☐☐ - A B
"forageable *" 12 ☐☐ ☐ ☐☐ ☐☐ - A B
"fresh *" 37 ☐☐  ☐☐ ☐☐ - A B
"gem-*" 435 ☐☐ ☐☐ ☐ ☐☐ - A B
"icon *" 44 ☐☐ ☐ ☐☐ ☐☐ - A B
"leather *" 21 ☐☐  ☐☐ ☐☐ - A B
"pavement-*" 65 ☐☐ ☐☐ ☐ ☐☐ - A B
"placeholder *" 3 ☐☐ ☐ ☐☐ ☐☐ - A B
"roast *" 50 ☐☐ ☐ ☐☐ ☐☐ - A B
"roast Filet of *" 0 (25/25) ☐☐ ☐ ☐☐ ☐☐ - A B
"satiations-*" 19 ☐☐ ☐☐ ☐ ☐☐ - A B
"stage *" 3 ☐☐ ☐ ☐☐ ☐☐ - A B
"user *" 3 ☐☐ ☐ ☐☐ ☐☐ - A B
"vein-*" 31 ☐☐ ☐☐  ☐☐ - A B
"wblock-*" 54 ☐☐ ☐☐ ☐ ☐☐ - A B
"wiki-*" 10 ☐☐ ☐☐ ☐ ☐☐ - A B
"* crop stage *" 96 -
"*(on wall)*" 145 (155/10) -
"*(wearing)*" 2 -
"*brick*" 9 (23/14) -
"*icon*" 8 (75/67) -
"*ingame*" 3 (72/69) -
(Same Page-Names) 2161 -
(REST) 807 12 34 56 78

(case insensitive compare)

  • Counts:
  • Count-1: Against Rest images. (found cases removed from used Rest-set)
  • Count-2: Against All images. "(found/diff)" When count-2 differs from count-1.
  • Styles
  • 1) Al: <PARENT-TYPE/CLASS>, (None), <ITEM-NAME(Lowercase)>
  • 2) Ac: <PARENT-TYPE/CLASS>, (None), <ITEM-NAME(Capitalized)>
  • 3) Bl: <PARENT-TYPE/CLASS>, (BlankSpace), <ITEM-NAME(Lowercase)>
  • 4) Bc: <PARENT-TYPE/CLASS>, (BlankSpace), <ITEM-NAME(Capitalized)>
  • 5) Cl: <PARENT-TYPE/CLASS>, (Bare Delimiter), <ITEM-NAME(Lowercase)>
  • 6) Cc: <PARENT-TYPE/CLASS>, (Bare Delimiter), <ITEM-NAME(Capitalized)>
  • 7) Dl: <PARENT-TYPE/CLASS>, (Spaced Delimiter), <ITEM-NAME(Lowercase)>
  • 8) Dc: <PARENT-TYPE/CLASS>, (Spaced Delimiter), <ITEM-NAME(Capitalized)>
  • Capitalized: Has some capitalized characters (ie: not fully lowercase).


  • "<creature-name>-dead", "<creature-name>-skeleton","<creature-name>-skinned".
  • "<object-name> - (on wall)".
  • "<crop-name> Crop Stage <N>", with N being the crop stage (1,2,..).
  • "Gem-<size> <cut> <gem-type>".
  • "Experience-<event/guest-name>".
  • "Barrel - <resource-name>".
  • "Pavement-<resource-name>", "Pavement-Metal-<metal-name>".
  • "Satiations-<food-name>".

Rename Jobs

  • Planned special sections on the Image_Naming main-page to be filled with target images and where appropriate there proposed new name.
  • Section are generally planned to be bot-processed (at some point). Where the related image-links to those images are automatically adjusted.
    • It could also be done by manual editing, but that seems a boring heavy workload, and also a error prone, process.


  • Buckets-variations: Flip cases that use redirects, so actual image is using the most appropriate/specific name-case. (still pondering about some potential additional stuff.) --.MvGulik. 03:04, 25 September 2019 (EDT)