VbzCart/tables/cat topic - Revision history

Woozle: tidying, reorganizing, updating; note about sorting

2016-03-24T00:58:34Z

tidying, reorganizing, updating; note about sorting

← Older revision		Revision as of 00:58, 24 March 2016
Line 1:		Line 1:
	==About==		==About==
			===Usage===
	* '''Used by''': {{vbzcart\|table\|cat_title_x_topic}}, {{vbzcart/query\|qryTitleTopic_Titles}}		* '''Used by''': {{vbzcart\|table\|cat_title_x_topic}}, {{vbzcart/query\|qryTitleTopic_Titles}}
	* '''History~~''':~~
	** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add		Generally, Topics are to be used in the following places:
	** '''2011-02-04''' working		* Topic pages (show what titles are assigned)
	** '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''		* Topic index (show what item types are [(1) available (2) in stock] for each topic)
	** '''2011-02-24''' New fields: '''cntTiHere''' and '''cntTiSub''' to support lookup-free indication of where to find active titles		* Title pages
	** '''2011-09-28''' renamed from '''brs_topics''' to '''cat_topic'''		** show what topics the title is in
	* '''Notes''':		** summarize how many other titles are available for each topic
	** Fields I'm considering adding ~~here~~:		** (future) show thumbnails for titles in topics with the A flag
	*** A) a flag to indicate that thumbnails of other items in the same category should be shown
	*** B) a prefix to be added to NameFull for all child nodes (and maybe a flag to override it)		In most display context, Topics should be sorted properly. (I thought I had already documented this but can't find it anywhere, so this is a first-pass reconstruction.) Sorting should generally be:<mysql>ORDER BY Sort, Name</mysql>
	*** C) a way of creating "virtual" nodes to cross-link to related topics in other branches		===History===
	* '''Uses''': Topics are (eventually) to be used in the following places:		* '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add
	** Topic pages (show what titles are assigned)		* '''2011-02-04''' working
	** Topic index (show what item types are [(1) available (2) in stock] for each topic)		* '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''
	** Title pages		* '''2011-02-24''' New fields: '''cntTiHere''' and '''cntTiSub''' to support lookup-free indication of where to find active titles
	*** show what topics the title is in		* '''2011-09-28''' renamed from '''brs_topics''' to '''cat_topic'''
	*** summarize how many other titles are available for each topic		===Future===
	*** (future) show thumbnails for titles in topics with the A flag		* Fields I'm considering adding:
			** A) a flag to indicate that thumbnails of other items in the same category should be shown
			** B) a prefix to be added to NameFull for all child nodes (and maybe a flag to override it)
			** C) a way of creating "virtual" nodes to cross-link to related topics in other branches
	==SQL==		==SQL==
	~~<section begin=sql />~~<mysql>DROP TABLE IF EXISTS `cat_topic`;		<mysql>DROP TABLE IF EXISTS `cat_topic`;
	CREATE TABLE `cat_topic` (		CREATE TABLE `cat_topic` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
Line 37:		Line 41:
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE = MYISAM;</mysql>		) ENGINE = MYISAM;</mysql>
	~~<section end=sql />~~

Woozle: renamed

2011-09-28T23:27:16Z

renamed

← Older revision		Revision as of 23:27, 28 September 2011
Line 1:		Line 1:
	==About==		==About==
	* '''Status''': Working (2011-02-04)		* '''Used by''': {{vbzcart\|table\|cat_title_x_topic}}, {{vbzcart/query\|qryTitleTopic_Titles}}
	* '''Used by''': {{vbzcart\|table\|~~brs_titles_x_topics}}~~
	* '''Future''': rename to {{vbzcart\|table\|cat_topic}}~~; rename~~ {{vbzcart\|~~table\|brs_titles_x_topics}} to {{vbzcart\|table\|cat_title_x_topic~~}}
	* '''History''':		* '''History''':
	** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add		** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add
			** '''2011-02-04''' working
	** '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''		** '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''
	** '''2011-02-24''' New fields: '''cntTiHere''' and '''cntTiSub''' to support lookup-free indication of where to find active titles		** '''2011-02-24''' New fields: '''cntTiHere''' and '''cntTiSub''' to support lookup-free indication of where to find active titles
			** '''2011-09-28''' renamed from '''brs_topics''' to '''cat_topic'''
	* '''Notes''':		* '''Notes''':
	** Fields I'm considering adding here:		** Fields I'm considering adding here:
Line 20:		Line 20:
	*** (future) show thumbnails for titles in topics with the A flag		*** (future) show thumbnails for titles in topics with the A flag
	==SQL==		==SQL==
	<section begin=sql /><mysql>DROP TABLE IF EXISTS `~~brs_topics~~`;		<section begin=sql /><mysql>DROP TABLE IF EXISTS `cat_topic`;
	CREATE TABLE `~~brs_topics~~` (		CREATE TABLE `cat_topic` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
	`ID_Parent` INT DEFAULT NULL COMMENT "~~brs_topics~~.ID of parent topic",		`ID_Parent` INT DEFAULT NULL COMMENT "cat_topic.ID of parent topic",
	`Name` VARCHAR(128) NOT NULL COMMENT "generic name (context-free, but as short as possible)",		`Name` VARCHAR(128) NOT NULL COMMENT "generic name (context-free, but as short as possible)",
	`NameTree` VARCHAR(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",		`NameTree` VARCHAR(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",

Woozle: moved VbzCart/tables/brs topics to VbzCart/tables/cat topic: for consistency

2011-09-28T23:11:57Z

moved VbzCart/tables/brs topics to VbzCart/tables/cat topic: for consistency

← Older revision	Revision as of 23:11, 28 September 2011
(No difference)

Woozle: new fields: cntTiHere, cntTiSub

2011-02-24T19:37:35Z

new fields: cntTiHere, cntTiSub

← Older revision		Revision as of 19:37, 24 February 2011
Line 6:		Line 6:
	** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add		** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add
	** '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''		** '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''
			** '''2011-02-24''' New fields: '''cntTiHere''' and '''cntTiSub''' to support lookup-free indication of where to find active titles
	* '''Notes''':		* '''Notes''':
	** Fields I'm considering adding here:		** Fields I'm considering adding here:
Line 32:		Line 33:
	`Variants` VARCHAR(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",		`Variants` VARCHAR(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",
	`Mispeled` VARCHAR(255) DEFAULT NULL COMMENT "same as Variants, but these are WRONG spellings; avoid displaying",		`Mispeled` VARCHAR(255) DEFAULT NULL COMMENT "same as Variants, but these are WRONG spellings; avoid displaying",
			`cntTiHere` INT DEFAULT NULL COMMENT "calculated: number of active titles for this topic",
			`cntTiSub` INT DEFAULT NULL COMMENT "calculated: sum of active titles for all subtopics",
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE = MYISAM;</mysql>		) ENGINE = MYISAM;</mysql>
	<section end=sql />		<section end=sql />

Woozle: fields: +NameMeta, +Usage

2011-02-05T18:39:15Z

fields: +NameMeta, +Usage

← Older revision		Revision as of 18:39, 5 February 2011
Line 1:		Line 1:
	==About==		==About==
	* '''Status''': ~~Coding in progress~~		* '''Status''': Working (2011-02-04)
	* '''Used by''': {{vbzcart\|table\|brs_titles_x_topics}}		* '''Used by''': {{vbzcart\|table\|brs_titles_x_topics}}
	* '''Future''': rename to {{vbzcart\|table\|cat_topic}}; rename {{vbzcart\|table\|brs_titles_x_topics}} to {{vbzcart\|table\|cat_title_x_topic}}		* '''Future''': rename to {{vbzcart\|table\|cat_topic}}; rename {{vbzcart\|table\|brs_titles_x_topics}} to {{vbzcart\|table\|cat_title_x_topic}}
	* '''History''':		* '''History''':
	** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add		** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add
			** '''2011-02-05''' New fields: '''NameMeta''' and '''Usage'''
	* '''Notes''':		* '''Notes''':
	** Fields I'm considering adding here:		** Fields I'm considering adding here:
Line 25:		Line 26:
	`NameTree` VARCHAR(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",		`NameTree` VARCHAR(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",
	`NameFull` VARCHAR(255) DEFAULT NULL COMMENT "descriptive standalone name (context free, can be long)",		`NameFull` VARCHAR(255) DEFAULT NULL COMMENT "descriptive standalone name (context free, can be long)",
			`NameMeta` VARCHAR(144) DEFAULT NULL COMMENT "plain text for HTML META description tag",
			`Usage` VARCHAR(255) DEFAULT NULL COMMENT "usage instructions for this topic - show when editing topic",
			/* `Details` VARCHAR(255) DEFAULT NULL COMMENT "additional information of interest to regular users (may include HTML)", */
	`Sort` VARCHAR(15) DEFAULT NULL COMMENT "optional sorting key",		`Sort` VARCHAR(15) DEFAULT NULL COMMENT "optional sorting key",
	`Variants` VARCHAR(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",		`Variants` VARCHAR(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",

Woozle: saving work; still revising

2011-01-19T12:54:58Z

saving work; still revising

← Older revision		Revision as of 12:54, 19 January 2011
Line 1:		Line 1:
	==About==		==About==
	* '''Status''': Coding in progress		* '''Status''': Coding in progress
			* '''Used by''': {{vbzcart\|table\|brs_titles_x_topics}}
			* '''Future''': rename to {{vbzcart\|table\|cat_topic}}; rename {{vbzcart\|table\|brs_titles_x_topics}} to {{vbzcart\|table\|cat_title_x_topic}}
	* '''History''':		* '''History''':
	** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add		** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add
	* '''Notes''':		* '''Notes''':
	** This should probably be renamed cat_topic
	** Fields I'm considering adding here:		** Fields I'm considering adding here:
	*** a flag to indicate that thumbnails of other items in the same category should be shown		*** A) a flag to indicate that thumbnails of other items in the same category should be shown
	*** a prefix to be added to NameFull for all child nodes (and maybe a flag to override it)		*** B) a prefix to be added to NameFull for all child nodes (and maybe a flag to override it)
	*** a way of creating "virtual" nodes to cross-link to related topics in other branches		*** C) a way of creating "virtual" nodes to cross-link to related topics in other branches
			* '''Uses''': Topics are (eventually) to be used in the following places:
			** Topic pages (show what titles are assigned)
			** Topic index (show what item types are [(1) available (2) in stock] for each topic)
			** Title pages
			*** show what topics the title is in
			*** summarize how many other titles are available for each topic
			*** (future) show thumbnails for titles in topics with the A flag
	==SQL==		==SQL==
	<section begin=sql /><mysql>DROP TABLE IF EXISTS `brs_topics`;		<section begin=sql /><mysql>DROP TABLE IF EXISTS `brs_topics`;
	CREATE TABLE `brs_topics` (		CREATE TABLE `brs_topics` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
	`ID_Parent` INT DEFAULT NULL COMMENT "brs_topics.ID of parent topic",		`ID_Parent` INT DEFAULT NULL COMMENT "brs_topics.ID of parent topic",
	`Name` ~~varchar~~(128) NOT NULL COMMENT "generic name (context-free, but as short as possible)",		`Name` VARCHAR(128) NOT NULL COMMENT "generic name (context-free, but as short as possible)",
	`NameTree` ~~varchar~~(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",		`NameTree` VARCHAR(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",
	`NameFull` ~~varchar~~(255) DEFAULT NULL COMMENT "descriptive standalone name (context free, can be long)",		`NameFull` VARCHAR(255) DEFAULT NULL COMMENT "descriptive standalone name (context free, can be long)",
	`Sort` ~~varchar~~(15) DEFAULT NULL COMMENT "optional sorting key",		`Sort` VARCHAR(15) DEFAULT NULL COMMENT "optional sorting key",
	`Variants` ~~varchar~~(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",		`Variants` VARCHAR(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",
	`Mispeled` ~~varchar~~(255) DEFAULT NULL COMMENT "same as Variants, but these are WRONG spellings; avoid displaying",		`Mispeled` VARCHAR(255) DEFAULT NULL COMMENT "same as Variants, but these are WRONG spellings; avoid displaying",
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE = MYISAM;</mysql>		) ENGINE = MYISAM;</mysql>
	<section end=sql />		<section end=sql />

Woozle: status update; possible fields to add later

2010-10-13T09:40:32Z

status update; possible fields to add later

← Older revision		Revision as of 09:40, 13 October 2010
Line 1:		Line 1:
	==About==		==About==
	* '''Status''': ~~Under development. May end up not being used.~~		* '''Status''': Coding in progress
			* '''History''':
			** '''2010-10-13''' Coding (store and admin) in progress; noted 3 possible fields to add
			* '''Notes''':
			** This should probably be renamed cat_topic
			** Fields I'm considering adding here:
			*** a flag to indicate that thumbnails of other items in the same category should be shown
			*** a prefix to be added to NameFull for all child nodes (and maybe a flag to override it)
			*** a way of creating "virtual" nodes to cross-link to related topics in other branches
	==SQL==		==SQL==
	<section begin=sql /><mysql>DROP TABLE IF EXISTS `brs_topics`;		<section begin=sql /><mysql>DROP TABLE IF EXISTS `brs_topics`;

Woozle: New page: ==About== * '''Status''': Under development. May end up not being used. ==SQL==
DROP TABLE IF EXISTS `brs_topics`; CREATE TABLE `brs_topics` ( `ID` INT...

2009-03-08T19:17:30Z

New page: ==About== * '''Status''': Under development. May end up not being used. ==SQL== <section begin=sql /><mysql>DROP TABLE IF EXISTS `brs_topics`; CREATE TABLE `brs_topics` ( `ID` INT...

New page

==About==
* '''Status''': Under development. May end up not being used.
==SQL==
<section begin=sql /><mysql>DROP TABLE IF EXISTS `brs_topics`;
CREATE TABLE `brs_topics` (
`ID` INT NOT NULL AUTO_INCREMENT,
`ID_Parent` INT DEFAULT NULL COMMENT "brs_topics.ID of parent topic",
`Name` varchar(128) NOT NULL COMMENT "generic name (context-free, but as short as possible)",
`NameTree` varchar(64) DEFAULT NULL COMMENT "name within context of parent; defaults to Name",
`NameFull` varchar(255) DEFAULT NULL COMMENT "descriptive standalone name (context free, can be long)",
`Sort` varchar(15) DEFAULT NULL COMMENT "optional sorting key",
`Variants` varchar(255) DEFAULT NULL COMMENT "synonyms and other keywords which should find this topic",
`Mispeled` varchar(255) DEFAULT NULL COMMENT "same as Variants, but these are WRONG spellings; avoid displaying",
PRIMARY KEY(`ID`)
) ENGINE = MYISAM;</mysql>
<section end=sql />