Talk:UCWCE - Revision history

Nybble: Question to think about

2006-02-26T05:23:08Z

Question to think about

← Older revision		Revision as of 05:23, 26 February 2006
Line 45:		Line 45:

	--[[User:Nybble\|Nybble]] 10:56, 24 Feb 2006 (EST)		--[[User:Nybble\|Nybble]] 10:56, 24 Feb 2006 (EST)

			Question to think about:

			What happens to date (timestamp) that is placed on a news post when it is attached to a comic that is scheduled to go live at a date in the future? Should the time stamps still be set to the initial posting? Or should they be changed to the date that the comic was made live?

			If you keep the old date, then it will inform your readers just how far in advance you may be working (haha...). If you use the new date, you are eliminating some of the point of this information. It also means that later posts that were attached to earlier comics could have dates that are earlier than the posting date of the entry for the new comic even though they were written in the other order. (Maybe I could write this in as a configurable option for webcomic sites.

			--[[User:Nybble\|Nybble]] 00:23, 26 Feb 2006 (EST)

Nybble at 15:56, 24 February 2006

2006-02-24T15:56:40Z

← Older revision		Revision as of 15:56, 24 February 2006
Line 37:		Line 37:

	That's my two cents. --[[User:Chadius\|Chadius]] 15:59, 23 Feb 2006 (EST)		That's my two cents. --[[User:Chadius\|Chadius]] 15:59, 23 Feb 2006 (EST)

			At the very least, the plan was to have the system have a https site with a password to view uncommitted comics. I suppose a status element directly in the comic table is a solution to that.

			I'm considering ditching several of the tables. It seems I can have MySQL handle indexing of text for searching for me, so I don't need to implement it myself. MySQL would then handle relevancy itself. I could possibly index the columns for title and content separately to perform our own weighting, but I'm not sure if that would a have negative impact on the resulting query speeds.

			The initial design of the comic table includes a field for plot summaries: "Text Description".

			--[[User:Nybble\|Nybble]] 10:56, 24 Feb 2006 (EST)

Chadius at 23:58, 23 February 2006

2006-02-23T23:58:23Z

← Older revision		Revision as of 23:58, 23 February 2006
Line 27:		Line 27:

	In the script = high		In the script = high

	In the title or topic = good		In the title or topic = good

	In quick summary of plot = OK		In quick summary of plot = OK

Chadius at 20:59, 23 February 2006

2006-02-23T20:59:29Z

← Older revision		Revision as of 20:59, 23 February 2006
Line 21:		Line 21:

	--[[User:Ratri\|Ratri]] 14:01, 23 Feb 2006 (EST)		--[[User:Ratri\|Ratri]] 14:01, 23 Feb 2006 (EST)

			Ratri's live/working/expired status idea is gold. It'll help us out a lot. It'll also help us if we realize, for example, that the color of the comic clashes with the site, or there's a continuity error we didn't notice until now.

			How will we measure the weights of keywords in the search field? I guess we can make simple heuristics:

			In the script = high
			In the title or topic = good
			In quick summary of plot = OK

			or something like that.

			Also: We should add quick, terse summaries of plots to the keywords for each comic.

			That's my two cents. --[[User:Chadius\|Chadius]] 15:59, 23 Feb 2006 (EST)

Ratri at 19:01, 23 February 2006

2006-02-23T19:01:30Z

← Older revision		Revision as of 19:01, 23 February 2006
Line 6:		Line 6:

	--[[User:Aurora\|Aurora]] 09:39, 23 Feb 2006 (EST)		--[[User:Aurora\|Aurora]] 09:39, 23 Feb 2006 (EST)

			Modules:
			...but I...

			Schema:

			Book/Chapter -- are the chapter start/end values supposed to specify a range of comic ID's (cid)? And do the book start/end specify a range of chapter ID's (chapter)?

			An alternate suggestion would be to have a chapter column in the comic table. Then the chapter table would have chapter_id, title, and book. The book table would have book_id and title. This makes sure each comic is individually linked, in case we ever, for example, take one down out of the middle and want to replace it later, or anything random that otherwise disrupts nice, neat ordering and breaks the ranges.

			The other thing you might want is a status setting that would allow de-activating an individual comic (eg, working, live, expired) so we could potentially upload it in working, view it, post an initial news on it, blah blah...then the cron that launches on a specific date would just have to flip the status to live. If one ever needs to be taken down for any reason, it could be manually switched to working or expired. Whether that's worth it would depend on how likely it is for us to want that kind of preview ability or shutoff switch. It would also allow us to play with/test the system to see how everything works and looks without disrupting the actual comic site.

			For the search table, I'm not sure I understand it here...is the lookup supposed to combine information from the 'type' and 'id' columns to look up based on comic.cid or news.nid?

			--[[User:Ratri\|Ratri]] 14:01, 23 Feb 2006 (EST)

Aurora at 14:39, 23 February 2006

2006-02-23T14:39:54Z

← Older revision		Revision as of 14:39, 23 February 2006
Line 2:		Line 2:

	--[[User:Nybble\|Nybble]] 22:07, 22 Feb 2006 (EST)		--[[User:Nybble\|Nybble]] 22:07, 22 Feb 2006 (EST)

			Looks great! but I have no idea what most of it means...

			--[[User:Aurora\|Aurora]] 09:39, 23 Feb 2006 (EST)

Nybble: Request for Comments

2006-02-23T03:07:51Z

Request for Comments

New page

Request For Comments

--[[User:Nybble|Nybble]] 22:07, 22 Feb 2006 (EST)