Talk:Adventist Youth Honors Answer Book - Revision history

Jomegat: /* Requirements Restructuring */ new section

2020-12-01T04:38:47Z

Requirements Restructuring: new section

Show changes

Jomegat: /* Plumbing Update */

2020-11-24T00:25:05Z

Plumbing Update

Show changes

Jomegat: /* Page Organization */

2020-11-22T19:59:02Z

Page Organization

Jomegat: /* Page Organization */

2020-11-22T19:55:28Z

Page Organization

Jomegat: /* Future Directions */ new section

2020-11-22T18:13:43Z

Future Directions: new section

Jomegat: /* Plumbing Update */

2020-11-22T17:45:20Z

Plumbing Update

Jomegat: /* Plumbing Update */

2020-11-21T14:18:39Z

Plumbing Update

Jomegat: /* Plumbing Update */

2020-11-21T03:19:58Z

Plumbing Update

W126jep: /* Plumbing Update */

2020-11-14T03:18:42Z

Plumbing Update

Jomegat: /* Plumbing Progress */

2020-11-13T21:59:34Z

Plumbing Progress

@@ Line 254: / Line 254: @@
 The landing pages would include a description of the honor, a link to the answer key, a link to the requirements, and if we go there, a link to the worksheet.  Also a link to the lesson plans we don't have yet, but voted to create.  It would show the banner we fly at the top of each answer page now, so that would include the name, authority, year, skill level, and patch.  We will leave redirects from the old location to the new.  Note that this scheme omits the honor category from the page names.  We already capture that using the categories, and we've found that when an honor is moved from one category to another it causes major pain.  It also causes problems when a Regional honor is adopted at a higher level, since those honors ''belong'' to a category, but they are filed under the ''Regional'' hierarchy.
-Answer keys would go under ''Honors/<honor name>/Answer_Key'' and the Requirements would go under ''Honors/<honor name>/Requirements'' - even though I just created all the Requirements pages under the old scheme. A bot can move them.
+Answer keys would go under ''Honors/<honor name>/Answer_Key'' and the Requirements would go under ''Honors/<honor name>/Requirements'' - even though I just created all the Requirements pages under the old scheme. A bot can move them.  If there are variants of the honor, I think we'd include that in the honor name itself as in ''Stars (South American Division)''. Though we might want to think think through why the variant exists: some variants have different requirements.  Others have the same requirements, but vastly different answers.
 Each requirement would be filed under ''Honors/<honor name>/Requirement/<requirement id>'' - and those get included via templates wherever they are needed, including in the Requirements page, Answer keys, worksheets, and IA pages that call them out.  Editing the requirement on its page ripples out everywhere.

@@ Line 254: / Line 254: @@
 The landing pages would include a description of the honor, a link to the answer key, a link to the requirements, and if we go there, a link to the worksheet.  Also a link to the lesson plans we don't have yet, but voted to create.  It would show the banner we fly at the top of each answer page now, so that would include the name, authority, year, skill level, and patch.  We will leave redirects from the old location to the new.  Note that this scheme omits the honor category from the page names.  We already capture that using the categories, and we've found that when an honor is moved from one category to another it causes major pain.  It also causes problems when a Regional honor is adopted at a higher level, since those honors ''belong'' to a category, but they are filed under the ''Regional'' hierarchy.
-Answer keys would go under ''Honors/<honor name>/Answer_Key'' and the Requirements would go under ''Honor/<honor name>/Requirements'' - even though I just created all the Requirements pages under the old scheme. A bot can move them.
+Answer keys would go under ''Honors/<honor name>/Answer_Key'' and the Requirements would go under ''Honors/<honor name>/Requirements'' - even though I just created all the Requirements pages under the old scheme. A bot can move them.
 Each requirement would be filed under ''Honors/<honor name>/Requirement/<requirement id>'' - and those get included via templates wherever they are needed, including in the Requirements page, Answer keys, worksheets, and IA pages that call them out.  Editing the requirement on its page ripples out everywhere.

← Older revision		Revision as of 18:13, 22 November 2020
Line 243:		Line 243:

	OK, '''''Now''''' the bot has extracted requirements from all the honors, including the Regionals. --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 12:45, 22 November 2020 (EST)		OK, '''''Now''''' the bot has extracted requirements from all the honors, including the Regionals. --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 12:45, 22 November 2020 (EST)
		+
		+	== Future Directions ==
		+
		+	Here are some thoughts we will discuss at a Zoom meeting later today.
		+
		+	===Page Organization===
		+	We might want to create the Honor structure under a new top-level page: Honors, or AY_Honors.
		+	The main page of each honor: ''Honors/<honor name>'' would be a landing page for the honor. The honor_desc would be added to that page. This means that all of the honor indices created with [[Template:honor_index]] - such as on the main page - would link to the landing page.
		+
		+	The landing pages would include a description of the honor, a link to the answer key, a link to the requirements, and if we go there, a link to the worksheet. Also a link to the lesson plans we don't have yet, but voted to create. It would show the banner we fly at the top of each answer page now, so that would include the name, authority, year, skill level, and patch. We will leave redirects from the old location to the new. Note that this scheme omits the honor category from the page names. We already capture that using the categories, and we've found that when an honor is moved from one category to another it causes major pain. It also causes problems when a Regional honor is adopted at a higher level, since those honors ''belong'' to a category, but they are filed under the ''Regional'' hierarchy.
		+
		+	Answer keys would go under ''Honors/<honor name>/Answer_Key'' and the Requirements would go under ''Honor/<honor name>/Requirements'' - even though I just created all the Requirements pages under the old scheme. A bot can move them.
		+
		+	Each requirement would be filed under ''Honors/<honor name>/Requirement/<requirement id>'' - and those get included via templates wherever they are needed, including in the Requirements page, Answer keys, worksheets, and IA pages that call them out. Editing the requirement on its page ripples out everywhere.
		+
		+	Alternatively, we could leave the honors under the old AYHAB top-level, but that is really a hold-over from the Wikibooks days which demanded that no abbreviations be used in book titles.
		+
		+	===Division Variants===
		+	The other thing we want to do with the restructuring is create new index pages based on which division the reader selects. This doesn't affect the layout of the honor pages (I think), but it will affect pages that make lists of honors. The dream is to add a user profile element to specify a division. All existing users will be assigned to the NAD, but maybe we'll have a pop-up notice that says "we put you in the NAD, change it over here if you want to".
		+
		+	We can add tabs or maybe links to the left pane to allow the user to look at other divisions and see what honors are available there. Another option might be to write our own custom extension (not easy!) to make the division selection appear the same way that the language selection does at the top of the answer keys and IA pages. Selecting the division and selecting the language are independent.
		+
		+	I think I want to go through and tag all the honors as being in effect in each division. So if an honor is in effect in the GC, it will belong to all the division categories (NAD, SAD, IAD, SPD, etc). If it is in effect only in that division, it will belong to only that division's category.
		+
		+	These changes are not small, and we might find some of them difficult (or impossible) to pull off.
		+
		+	--[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 13:13, 22 November 2020 (EST)

← Older revision		Revision as of 17:45, 22 November 2020
Line 241:		Line 241:
	::Fun times! (P.S. The bot is done. All requirements have been extracted... except abseiling which I skipped because it's a mess). --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 22:19, 20 November 2020 (EST)		::Fun times! (P.S. The bot is done. All requirements have been extracted... except abseiling which I skipped because it's a mess). --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 22:19, 20 November 2020 (EST)
	:::Haha... There are 12,481 requirement pages. Also, I've not done the regional honors yet. --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 09:18, 21 November 2020 (EST)		:::Haha... There are 12,481 requirement pages. Also, I've not done the regional honors yet. --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 09:18, 21 November 2020 (EST)
		+
		+	OK, '''''Now''''' the bot has extracted requirements from all the honors, including the Regionals. --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 12:45, 22 November 2020 (EST)

← Older revision		Revision as of 14:18, 21 November 2020
Line 240:		Line 240:
	Once all of that is done I'll need to put yet-another-bot together to edit the answer keys themselves so that they replace the TOC with the internal link index [[template:reqreqlink]] template and then replace each requirement with the [[template:ansreq]] templates. ''Then'' we need to check over everything.		Once all of that is done I'll need to put yet-another-bot together to edit the answer keys themselves so that they replace the TOC with the internal link index [[template:reqreqlink]] template and then replace each requirement with the [[template:ansreq]] templates. ''Then'' we need to check over everything.
	::Fun times! (P.S. The bot is done. All requirements have been extracted... except abseiling which I skipped because it's a mess). --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 22:19, 20 November 2020 (EST)		::Fun times! (P.S. The bot is done. All requirements have been extracted... except abseiling which I skipped because it's a mess). --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 22:19, 20 November 2020 (EST)
		+	:::Haha... There are 12,481 requirement pages. Also, I've not done the regional honors yet. --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 09:18, 21 November 2020 (EST)

← Older revision		Revision as of 03:19, 21 November 2020
Line 226:		Line 226:

	:It really is exciting! It is one of the few joys I can easily think of during this crazy year! -- [[User:W126jep\|w126jep]] ([[User talk:W126jep\|talk]]) 22:18, 13 November 2020 (EST)		:It really is exciting! It is one of the few joys I can easily think of during this crazy year! -- [[User:W126jep\|w126jep]] ([[User talk:W126jep\|talk]]) 22:18, 13 November 2020 (EST)
		+
		+	::Feel free to tweak the colors (should be in the [[template:ansreq]]). I was looking to match the background jpg so I went towards the blue end of the spectrum. That selection was done back in 2012-ish when we added the IA pages. I basically modified the IA requirements template to make one for the honor pages. DesignerThan has made significant improvements since then.
		+	::The Good news is that as I write, the bot is extracting the requirements from the last honor. It will be done before I finish this note. There are several things to do after that:
		+
		+	# Backup the wiki Just In Case
		+	# Give DesignerThan admin privs here so he can change protected templates, etc.
		+	# Figure out the screen-scraping bot to extract the translations. This bot will have to mark all the new pages for translation, and then navigate the translation software.
		+	# Make a header template for the <honor>/Requirements pages. What do we want in there? (Anyone can take a shot at making this). The idea was to display the honor name in some aesthetic way, and maybe suppress the page title. We might want to think about how we can grab the skill level and intro year too. That might require some mediawiki magic to extract data from the skill level categories.
		+	# Use a wikibot to add that header to all the requirements pages.
		+	# Protect the requirements templates from editing.
		+	# Use a wikibot to protect all the requirement pages (including the main req page for each honor and all the individual requirement pages that those transclude - there must be ten thousand of those).
		+	# Backup the wiki in case the next phase goes tragically astray.
		+	Once all of that is done I'll need to put yet-another-bot together to edit the answer keys themselves so that they replace the TOC with the internal link index [[template:reqreqlink]] template and then replace each requirement with the [[template:ansreq]] templates. ''Then'' we need to check over everything.
		+	::Fun times! (P.S. The bot is done. All requirements have been extracted... except abseiling which I skipped because it's a mess). --[[User:Jomegat\|Jomegat]] ([[User talk:Jomegat\|talk]]) 22:19, 20 November 2020 (EST)

@@ Line 203: / Line 203: @@
 == Plumbing Update ==
-[[User:DesignerThan]] has done some excellent work on the requirements templates, so I think those are good-to-go.  I've also created some templates to replace the TOC with something very TOC-like, but it only links to the requirements, and not to every section within the answers.
+[[User:DesignerThan|DesignerThan]] has done some excellent work on the requirements templates, so I think those are good-to-go.  I've also created some templates to replace the TOC with something very TOC-like, but it only links to the requirements, and not to every section within the answers.
 I have extracted the requirements from 409 honors so far.  For those 409, each requirement lives on its own page, and each honor has a requirements-only page.
@@ Line 218: / Line 218: @@
 The times, they are exciting!  Comments and ideas are welcome and appreciated! --[[User:Jomegat|Jomegat]] ([[User talk:Jomegat|talk]]) 16:57, 13 November 2020 (EST)

@@ Line 186: / Line 186: @@
 {{anssubreq|page=Adventist Youth Honors Answer Book/Nature/Amphibians|num=11a|boxtype=firstsub}}
 Blah, blah, blah
 {{anssubreq|page=Adventist Youth Honors Answer Book/Nature/Amphibians|num=11b}}
 Blah, blah, blah
 ::Note that ''how'' the requirements are rendered is done without changing the requirement pages, and without affecting how other pages might want to render them either. We could make decisions on a case-by-case basis.  I'm sure we'll find some sub-requirements that lend themselves to the box rendering better than to the bold text rendering. --[[User:Jomegat|Jomegat]] ([[User talk:Jomegat|talk]]) 10:35, 18 October 2020 (EDT)