Template talk:Setting

From Savagepedia

Additional Fields for Setting Table

I would like to consider adding a "projected release date" as a date field to this table, but not sure how yet. In the infobox it should should say something like Year Published: 2021 (projected), or even offer the chance to get more specific (to the date of release). I don't want to split up that data though into "expected dates" and "actual dates", and not force a specific single date...rather, keep it flexible to only store the year if that's all we have.

Perhaps changing the field type to Date (from "Year"), and setting an {{#if}} function that adds "(projected)" to the display if the date is in the future. One issue here would be if the release date gets pushed back or is never published, we would like some sort of notice, or an alert that pops when that date comes along so the release can be verified.--Grivander (talk) 06:30, 21 October 2020 (UTC)

Going to also clear up the "SupportingWorks" field to better identify what is "required" and what is "recommended" and what is a "jumpstart". Each of the three will be it's own field in the table. When queried for "list of ___" lists the three fields will be concatenated into a single return field and each value will have a (value) suffix at the end, such that is displays like "Savage Core Rules (required), Heroes Supplement (recommended), Flashpoint (jumpstart)". --Grivander (talk) 16:44, 21 October 2020 (UTC)
Both the Release Date and Supporting Works fields have been reworked and calling those finished for now. If I come back to it, the release date field could be tweaked: Want to allow entry of either of a specific date or just a year, and have the displayed value in the infobox work both ways depending on what was entered. Currently I can only figure out how to display either just a Year, or the M-D-Y. Probably need some IF statements but not sure how to do target them. --Grivander (talk) 01:03, 22 October 2020 (UTC)

Creating Documentation for Template

I need to create documentation for this template and explain how it works, and why choices were made. There will be a guide in the Help namespace that covers Cargo and Page Forms. The docs on this Template will focus on what specifically the template is doing or what its role is in regards to Cargo.--Grivander (talk) 06:32, 21 October 2020 (UTC)

Seller Field

Finally, I would like to figure out how best to store the "Seller" field (which should be renamed to "Marketplaces" or something). I think ideally the Form would display a list of typical marketplaces such as DTRPG, Amazon, PEG, etc from which an option (or options) could be selected, and then a text box appears for entry of a link directly to the item page to buy it. The selected option would be the link display text, and the url would just be the link. Together, they would be stored in the table as wikitext...? --Grivander (talk) 06:37, 21 October 2020 (UTC)

Issue with queries not accepting special characters like "&" and accented characters.

The queries on this template and similar do not search on "&" and accented characters. Ideally an "escape" character can be found for these records to be stored queried correctly, but in the meantime I just removed those characters and replaced them with non-accented versions. Not ideal.