Template talk:RequiredBy2

From Ring of Brodgar
Jump to navigation Jump to search

Needed?

It seems to me your trying to do stuff that is already covered by other templates:
- List_to_pagelinks
- List_normalize (=redirect)
- List_to_categories (=redirect)
...
What problem is this template trying to solve ?
--.MvGulik. 00:57, 17 September 2018 (EDT)


Still needed imho: now there is a problem on pages which have multiple Specific property values in Infobox, e. g. Golden Eagle Meat, see Required By row.
--Not a cat 05:12, 17 September 2018 (EDT)


Aha. The "Required By" row ... Yea, that one needed some additional work, but I never got around to it.
... Suggest adding some kind of display separation between the data from the different secondary calls to make the final list a bit more general/user-readable.
--.MvGulik. 12:21, 17 September 2018 (EDT)

Mmm. Taking a closer look at what it is that is being tried here ...

  • Page "Chicken Meat" has:
    • Specific Type of: Poultry, Raw Meat
    • Required By: Chicken Chorizo, Roast Chicken, and(EOL)
  • Page "Poultry" has:
    • Required By: (list with Poultry(Specific) items).
  • Page "Raw Meat" has:
    • Required By: (list with Raw Meat(Specific) items).

...
And where trying to add those Required-By items from the "Poultry" and "Raw Meat" pages to the Required-By list on the "Chicken Meat" page ...
...
- Potential issue one, in my mind, is that where duplicating information that is already presented on the Specific-case page.
-- ... (have no alternative idea here yet)
- Potential issue two is that that (single)Required-By list on (some at least) of the object-page(s) is probably getting so bloated that it will defeat its purpose.
-- Generating separate, per specific case, Required-By lists on the object-page would as least counteract the single/bloated Required-By listing.
--.MvGulik. 14:09, 17 September 2018 (EDT)

Parser Data Dump

For future analysing. (collapsed)(Expand button =>)