Gospel Translations:Technology/BrowseTranslations extension
From Gospel Translations
Line 9: | Line 9: | ||
=== Overview of functionality === | === Overview of functionality === | ||
- | Special pages are designed to accept one parameter, which is included in the URL a la [[Special:Emailuser/Mahra]]. That special page creates a form to email Andrew, where the input parameter was <code>Mahra</code>. | + | Special pages are designed to accept one parameter, which is included in the URL a la [[Special:Emailuser/Mahra]]. That special page creates a form to email Andrew, where the input parameter was <code>Mahra</code> (Andrew's user name on this wiki). |
The '''BrowseContent''' extension will work by accepting a two-part parameter delimited by a colon. Because the extension's purpose is to provide a drilldown view, the two-part parameter will be formatted as <code>Category:Member</code>. "Category" refers to the type of drill down--whether by Author, Publisher, Title, Topic, or Language. "Member" refers to the subgroup to display. | The '''BrowseContent''' extension will work by accepting a two-part parameter delimited by a colon. Because the extension's purpose is to provide a drilldown view, the two-part parameter will be formatted as <code>Category:Member</code>. "Category" refers to the type of drill down--whether by Author, Publisher, Title, Topic, or Language. "Member" refers to the subgroup to display. |
Revision as of 15:03, 8 June 2009
Contents |
Project summary
Create a SpecialPage that allows drilldown browsing of our translation library.
Assignments
- unassigned - Write PHP functions which will accept the parameters described below and return the appropriate listings [no working knowledge of Mediawiki plugin architecture required]
- Andrew - Convert functions into a SpecialPage extension on the GospelTranslations wiki
Overview of functionality
Special pages are designed to accept one parameter, which is included in the URL a la Special:Emailuser/Mahra. That special page creates a form to email Andrew, where the input parameter was Mahra
(Andrew's user name on this wiki).
The BrowseContent extension will work by accepting a two-part parameter delimited by a colon. Because the extension's purpose is to provide a drilldown view, the two-part parameter will be formatted as Category:Member
. "Category" refers to the type of drill down--whether by Author, Publisher, Title, Topic, or Language. "Member" refers to the subgroup to display.
For example,
-
Publisher:Ligonier
would return a formatted list of everything published by Ligonier, -
Author:Dave Harvey
would return everything Dave Harvey has written -
Title:C
would return a list of all titles beginning with the letter "C"
Also, for each Category you can use the special Member "Index" to list all available Members. For example,
-
Language:Index
would return a list of all the languages that are published by us -
Topic:Index
would return a list of all the topics that have at least one article assigned to them
See below for info on the database from which all this information will be pulled.
Helpful documentation
- Content database layout. Our content database is mirrored in a special multi-dimensional array stored on our servers. You'll need to know it's layout in order to access all of the Publisher, Author, Topic, Title, and Language data necessary for this extension.
- SpecialPage technical overview from MediaWiki.org
Special considerations for the Language
Category
For all Categories except Language
, the default language of the wiki will be assumed. So on an English wiki, only return English results, and so on.
But when browsing languages, another layer of functionality needs to be added. Let's say the user is on our English wiki, and is curious about what we've translated into Spanish. Well, if we just did a search in the form of Language:Spanish
, the resulting page would list several hundred items and thus be too expansive to be helpful.
For that reason, we should probably have Language:Spanish
simply return 4 options: Browse by Author, Topic, Title, or Publisher. And from there we would simply add new parameters to refine the search. Two options for doing this are:
- add a switch to our normal search which overrides the default language
-
Topic:Index/Spanish
-
Author:John Piper/Bosnian
-
- add a 3rd and 4th parameter to the Language search
-
Language:Spanish:Topic:Index
-
Language:Bosnian:Author:John Piper
-