Hi Team, I'd like to tighten up our WEBLOG table a bit, I've identified
eight columns that look like good candidates for removal and two columns
for renaming:
Suggested columns to remove:
1.) emailfromaddress: presently not used in the application, we just
rely on the email address configured at the server level, and the blog's
standard email address is available if we ever want to get more
granular. If we ever recode again, we can easily add this column in, I
suspect in most cases though, where commenting is so heavy that two
email addresses would be useful, such blogs would be using Disqus or
similar third-party tools anyway.
2.) pagemodels: The only configuration Roller has for this is at the
server-level (in the roller-custom.properties file) applicable for all
blogs, a situation I'd like us to continue. Techies capable of
configuring their own page models are likely going to be running their
Roller instance so they won't be affected, and altering page models for
individual bloggers of a corporate site would appear to be beyond the
scope of what most blog administrators would be comfortable in allowing.
3.) customstylesheet: No longer used. Custom stylesheets are stored in
the custom_template_rendition table.
4.) bloggercatid: There are two columns, "defaultcatid" (which is no
longer used or configurable) and bloggercatid (i.e., the default
category for articles created using a blogging client.) The latter is
configurable on the User Settings page. I'd like to copy the
bloggercatid values to defaultcatid, have the settings page alter the
defaultcatid, and get rid of bloggercatid. This way, defaultcatid can
be used in multiple places whenever a default category may be of use
(UI, blog client, feeds perhaps). As an alternative, I can just get rid
of defaultcatid and keep bloggercatid as-is. Somehow I just want to go
from two columns to one here.
5.) ignorewords: not referenced anywhere in the application or in any
POJO, just defined in the createdb.vm script.
6.) defaultPageId: hardcoded to "dummy", being set in a few places but
not actually used anywhere in the app.
7.) weblogDayId: hardcoded to "dummy", not used anymore in the app.
8.) defaultplugins: Always null, no place to configure at the
blog-level, as with #2 above, perhaps best to let the blog admin
configure this for all bloggers in the roller-custom.properties file.
Suggested columns to rename:
1.) description, rename to "tagline": Our "description" column is called
the "tagline" in the UI. We have another description-like column in the
weblog table called "about", so keeping "about" and "description"
columns together is kind of confusing as it's not clear what the
difference is between the two.
2.) isenabled, rename to "isvisible" -- the Weblog class comments for
this item indicate this setting is used just to determine whether the
blog may appear on the Internet, not whether it may be edited, articles
written/deleted, etc., something that "isenabled" would be a better flag
for. Presently this flag isn't editable within the UI, nor does setting
it cause the blog to return 404s. Arguably we can remove this column
entirely until we code "isvisible", or keep it in, expecting us to soon
implement the logic for this value.
Regards,
Glen
