Ring of Brodgar talk:Image Naming

From Ring of Brodgar
Revision as of 21:38, 13 October 2019 by MvGulik (talk | contribs) (Current general used: Remark field (setup).)
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.
  • (not sure yet about "-" vs " - " as image-parts delimiter)

Current general used

Count Case Style
12 34 56 78
Remark (list links)
5284 All Image-Names -
-2164 Same Page-Names -
-921 "legacy-*" cases ☐☐ ☐☐ ☐ ☐☐ A B
-435 "gem-*" cases ☐☐ ☐☐ ☐ ☐☐ A B
-152 "*(on wall)*" -
-2 "*(wearing)*" -
-37 "* terrain" & "*terrain" -
-37 "* map" & "*map" -
-96 "* crop stage *" -
-3 "stage *" (...crop) -
-54 "wblock-*" ☐☐ ☐☐ ☐ ☐☐ A B
-31 "vein-*" ☐☐ ☐☐  ☐☐ A B
-19 "satiations-*" ☐☐ ☐☐ ☐ ☐☐ A B
-65 "pavement-*" ☐☐ ☐☐ ☐ ☐☐ A B
-44 "icon *" (combat stuff) ☐☐ ☐ ☐☐ ☐☐ A B
-8 "*icon*" (others) -
-79 "experience-*" ☐☐ ☐☐ ☐ ☐☐ A B
-43 "board-*" ☐☐ ☐☐ ☐ ☐☐ A B
-33 "barrel - *" ☐☐ ☐☐ ☐☐ ☐ A B
-13 "character *" -
-25 "act*" (game menu icons) ☐ ☐☐ ☐☐ ☐☐ A x
-22 "* in garden pot" -
-27 "*-dead" -
-25 "*-skeleton" - - x
-27 "*-skinned" -
-65 "* ingame" & "*ingame" -
-1 "*ingame*" -
-12 "forageable *" ☐☐ ☐☐ ☐ ☐☐ A B
-9 "*brick*" (multiple different cases) -
-10 "wiki-*" ☐☐ ☐☐ ☐ ☐☐ A B
-3 "placeholder *" ☐☐ ☐ ☐☐ ☐☐ A B
-3 "user *" ☐☐ ☐ ☐☐ ☐☐ A B
819 (REST) (includes rnd/odd cases) 12 34 56 78

(case insensitive compare)

  • 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 (but is not fully uppercased).


  • "<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)