doc/man1/htsn-import.1

   1 .TH htsn-import 1
   2
   3 .SH NAME
   4 htsn-import \- Import XML files from The Sports Network into an RDBMS.
   5
   6 .SH SYNOPSIS
   7
   8 \fBhtsn-import\fR [OPTIONS] [FILES]
   9
  10 .SH DESCRIPTION
  11 .P
  12 The Sports Network <http://www.sportsnetwork.com/> offers an XML feed
  13 containing various sports news and statistics. Our sister program
  14 \fBhtsn\fR is capable of retrieving the feed and saving the individual
  15 XML documents contained therein. But what to do with them?
  16 .P
  17 The purpose of \fBhtsn-import\fR is to take these XML documents and
  18 get them into something we can use, a relational database management
  19 system (RDBMS), otherwise known as a SQL database. The structure of
  20 relational database, is, well, relational, and the feed XML is not. So
  21 there is some work to do before the data can be imported into the
  22 database.
  23 .P
  24 First, we must parse the XML. Each supported document type (see below)
  25 has a full pickle/unpickle implementation (\(dqpickle\(dq is simply a
  26 synonym for serialize here). That means that we parse the entire
  27 document into a data structure, and if we pickle (serialize) that data
  28 structure, we get the exact same XML document tha we started with.
  29 .P
  30 This is important for two reasons. First, it serves as a second level
  31 of validation. The first validation is performed by the XML parser,
  32 but if that succeeds and unpicking fails, we know that something is
  33 fishy. Second, we don't ever want to be surprised by some new element
  34 or attribute showing up in the XML. The fact that we can unpickle the
  35 whole thing now means that we won't be surprised in the future.
  36 .P
  37 The aforementioned feature is especially important because we
  38 automatically migrate the database schema every time we import a
  39 document. If you attempt to import a \(dqnewsxml.dtd\(dq document, all
  40 database objects relating to the news will be created if they do not
  41 exist. We don't want the schema to change out from under us without
  42 warning, so it's important that no XML be parsed that would result in
  43 a different schema than we had previously. Since we can
  44 pickle/unpickle everything already, this should be impossible.
  45
  46 .SH SUPPORTED DOCUMENT TYPES
  47 .P
  48 The XML document types obtained from the feed are uniquely identified
  49 by their DTDs. We currently support documents with the following DTDs:
  50 .IP \[bu] 2
  51 AutoRacingResultsXML.dtd
  52 .IP \[bu]
  53 Auto_Racing_Schedule_XML.dtd
  54 .IP \[bu]
  55 Heartbeat.dtd
  56 .IP \[bu]
  57 Injuries_Detail_XML.dtd
  58 .IP \[bu]
  59 injuriesxml.dtd
  60 .IP \[bu]
  61 newsxml.dtd
  62 .IP \[bu]
  63 Odds_XML.dtd
  64 .IP \[bu]
  65 scoresxml.dtd
  66 .IP \[bu]
  67 weatherxml.dtd
  68 .IP \[bu]
  69 GameInfo
  70 .RS
  71 .IP \[bu]
  72 CBASK_Lineup_XML.dtd
  73 .IP \[bu]
  74 cbaskpreviewxml.dtd
  75 .IP \[bu]
  76 cflpreviewxml.dtd
  77 .IP \[bu]
  78 Matchup_NBA_NHL_XML.dtd
  79 .IP \[bu]
  80 MLB_Gaming_Matchup_XML.dtd
  81 .IP \[bu]
  82 MLB_Lineup_XML.dtd
  83 .IP \[bu]
  84 MLB_Matchup_XML.dtd
  85 .IP \[bu]
  86 MLS_Preview_XML.dtd
  87 .IP \[bu]
  88 mlbpreviewxml.dtd
  89 .IP \[bu]
  90 NBA_Gaming_Matchup_XML.dtd
  91 .IP \[bu]
  92 NBA_Playoff_Matchup_XML.dtd
  93 .IP \[bu]
  94 NBALineupXML.dtd
  95 .IP \[bu]
  96 nbapreviewxml.dtd
  97 .IP \[bu]
  98 NCAA_FB_Preview_XML.dtd
  99 .IP \[bu]
 100 NFL_NCAA_FB_Matchup_XML.dtd
 101 .IP \[bu]
 102 nflpreviewxml.dtd
 103 .IP \[bu]
 104 nhlpreviewxml.dtd
 105 .IP \[bu]
 106 recapxml.dtd
 107 .IP \[bu]
 108 WorldBaseballPreviewXML.dtd
 109 .RE
 110 .IP \[bu]
 111 SportInfo
 112 .RS
 113 .IP \[bu]
 114 CBASK_3PPctXML.dtd
 115 .IP \[bu]
 116 Cbask_All_Tourn_Teams_XML.dtd
 117 .IP \[bu]
 118 CBASK_AssistsXML.dtd
 119 .IP \[bu]
 120 Cbask_Awards_XML.dtd
 121 .IP \[bu]
 122 CBASK_BlocksXML.dtd
 123 .IP \[bu]
 124 Cbask_Conf_Standings_XML.dtd
 125 .IP \[bu]
 126 Cbask_DivII_III_Indv_Stats_XML.dtd
 127 .IP \[bu]
 128 Cbask_DivII_Team_Stats_XML.dtd
 129 .IP \[bu]
 130 Cbask_DivIII_Team_Stats_XML.dtd
 131 .IP \[bu]
 132 CBASK_FGPctXML.dtd
 133 .IP \[bu]
 134 CBASK_FoulsXML.dtd
 135 .IP \[bu]
 136 CBASK_FTPctXML.dtd
 137 .IP \[bu]
 138 Cbask_Indv_Scoring_XML.dtd
 139 .IP \[bu]
 140 CBASK_MinutesXML.dtd
 141 .RE
 142 .P
 143 The GameInfo and SportInfo types do not have their own top-level
 144 tables in the database. Instead, their raw XML is stored in either the
 145 \(dqgame_info\(dq or \(dqsport_info\(dq table respectively.
 146
 147 .SH DATABASE SCHEMA
 148 .P
 149 At the top level (with two notable exceptions), we have one table for
 150 each of the XML document types that we import. For example, the
 151 documents corresponding to \fInewsxml.dtd\fR will have a table called
 152 \(dqnews\(dq. All top-level tables contain two important fields,
 153 \(dqxml_file_id\(dq and \(dqtime_stamp\(dq. The former is unique and
 154 prevents us from inserting the same data twice. The time stamp on the
 155 other hand lets us know when the data is old and can be removed. The
 156 database schema make it possible to delete only the outdated top-level
 157 records; all transient children should be removed by triggers.
 158 .P
 159 These top-level tables will often have children. For example, each
 160 news item has zero or more locations associated with it. The child
 161 table will be named <parent>_<children>, which in this case
 162 corresponds to \(dqnews_locations\(dq.
 163 .P
 164 To relate the two, a third table may exist with name
 165 <parent>__<child>. Note the two underscores. This prevents ambiguity
 166 when the child table itself contains underscores. The table joining
 167 \(dqnews\(dq with \(dqnews_locations\(dq is thus called
 168 \(dqnews__news_locations\(dq. This is necessary when the child table
 169 has a unique constraint; we don't want to blindly insert duplicate
 170 records keyed to the parent. Instead we'd like to use the third table
 171 to map an existing child to the new parent.
 172 .P
 173 Where it makes sense, children are kept unique to prevent pointless
 174 duplication. This slows down inserts, and speeds up reads (which are
 175 much more frequent). There is a tradeoff to be made, however. For a
 176 table with a small, fixed upper bound on the number of rows (like
 177 \(dqodds_casinos\(dq), there is great benefit to de-duplication. The
 178 total number of rows stays small, so inserts are still quick, and many
 179 duplicate rows are eliminated.
 180 .P
 181 But, with a table like \(dqodds_games\(dq, the number of games grows
 182 quickly and without bound. It is therefore more beneficial to be able
 183 to delete the old games (through an ON DELETE CASCADE, tied to
 184 \(dqodds\(dq) than it is to eliminate duplication. A table like
 185 \(dqnews_locations\(dq is somewhere in-between. It is hoped that the
 186 unique constraint in the top-level table's \(dqxml_file_id\(dq will
 187 prevent duplication in this case anyway.
 188 .P
 189 The aforementioned exceptions are the \(dqgame_info\(dq and
 190 \(dqsport_info\(dq tables. These tables contain the raw XML for a
 191 number of DTDs that are not handled individually. This is partially
 192 for backwards-compatibility with a legacy implementation, but is
 193 mostly a stopgap due to a lack of resources at the moment. These two
 194 tables (game_info and sport_info) still possess timestamps that allow
 195 us to prune old data.
 196 .P
 197 UML diagrams of the resulting database schema for each XML document
 198 type are provided with the \fBhtsn-import\fR documentation.
 199
 200 .SH XML Schema Oddities
 201 .P
 202 There are a number of problems with the XML on the wire. Even if we
 203 construct the DTDs ourselves, the results are sometimes
 204 inconsistent. Here we document a few of them.
 205
 206 .IP \[bu] 2
 207 Odds_XML.dtd
 208
 209 The <Notes> elements here are supposed to be associated with a set of
 210 <Game> elements, but since the pair
 211 (<Notes>...</Notes><Game>...</Game>) can appear zero or more times,
 212 this leads to ambiguity in parsing. We therefore ignore the notes
 213 entirely (although a hack is employed to facilitate parsing).
 214
 215 .IP \[bu]
 216 weatherxml.dtd
 217
 218 There appear to be two types of weather documents; the first has
 219 <listing> contained within <forecast> and the second has <forecast>
 220 contained within <listing>. While it would be possible to parse both,
 221 it would greatly complicate things. The first form is more common, so
 222 that's all we support for now.
 223
 224 .SH OPTIONS
 225
 226 .IP \fB\-\-backend\fR,\ \fB\-b\fR
 227 The RDBMS backend to use. Valid choices are \fISqlite\fR and
 228 \fIPostgres\fR. Capitalization is important, sorry.
 229
 230 Default: Sqlite
 231
 232 .IP \fB\-\-connection-string\fR,\ \fB\-c\fR
 233 The connection string used for connecting to the database backend
 234 given by the \fB\-\-backend\fR option. The default is appropriate for
 235 the \fISqlite\fR backend.
 236
 237 Default: \(dq:memory:\(dq
 238
 239 .IP \fB\-\-log-file\fR
 240 If you specify a file here, logs will be written to it (possibly in
 241 addition to syslog). Can be either a relative or absolute path. It
 242 will not be auto-rotated; use something like logrotate for that.
 243
 244 Default: none
 245
 246 .IP \fB\-\-log-level\fR
 247 How verbose should the logs be? We log notifications at four levels:
 248 DEBUG, INFO, WARN, and ERROR. Specify the \(dqmost boring\(dq level of
 249 notifications you would like to receive (in all-caps); more
 250 interesting notifications will be logged as well. The debug output is
 251 extremely verbose and will not be written to syslog even if you try.
 252
 253 Default: INFO
 254
 255 .IP \fB\-\-remove\fR,\ \fB\-r\fR
 256 Remove successfully processed files. If you enable this, you can see
 257 at a glance which XML files are not being processed, because they're
 258 all that should be left.
 259
 260 Default: disabled
 261
 262 .IP \fB\-\-syslog\fR,\ \fB\-s\fR
 263 Enable logging to syslog. On Windows this will attempt to communicate
 264 (over UDP) with a syslog daemon on localhost, which will most likely
 265 not work.
 266
 267 Default: disabled
 268
 269 .SH CONFIGURATION FILE
 270 .P
 271 Any of the command-line options mentioned above can be specified in a
 272 configuration file instead. We first look for \(dqhtsn-importrc\(dq in
 273 the system configuration directory. We then look for a file named
 274 \(dq.htsn-importrc\(dq in the user's home directory. The latter will
 275 override the former.
 276 .P
 277 The user's home directory is simply $HOME on Unix; on Windows it's
 278 wherever %APPDATA% points. The system configuration directory is
 279 determined by Cabal; the \(dqsysconfdir\(dq parameter during the
 280 \(dqconfigure\(dq step is used.
 281 .P
 282 The file's syntax is given by examples in the htsn-importrc.example file
 283 (included with \fBhtsn-import\fR).
 284 .P
 285 Options specified on the command-line override those in either
 286 configuration file.
 287
 288 .SH EXAMPLES
 289 .IP \[bu] 2
 290 Import newsxml.xml into a preexisting sqlite database named \(dqfoo.sqlite3\(dq:
 291
 292 .nf
 293 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
 294 .I "              test/xml/newsxml.xml"
 295 Successfully imported test/xml/newsxml.xml.
 296 Imported 1 document(s) total.
 297 .fi
 298 .IP \[bu]
 299 Repeat the previous example, but delete newsxml.xml afterwards:
 300
 301 .nf
 302 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
 303 .I "              --remove test/xml/newsxml.xml"
 304 Successfully imported test/xml/newsxml.xml.
 305 Imported 1 document(s) total.
 306 Removed processed file test/xml/newsxml.xml.
 307 .fi
 308 .IP \[bu]
 309 Use a Postgres database instead of the default Sqlite. This assumes
 310 that you have a database named \(dqhtsn\(dq accessible to user
 311 \(dqpostgres\(dq locally:
 312
 313 .nf
 314 .I $ htsn-import --connection-string='dbname=htsn user=postgres' \\\\
 315 .I "              --backend=Postgres test/xml/newsxml.xml"
 316 Successfully imported test/xml/newsxml.xml.
 317 Imported 1 document(s) total.
 318 .fi
 319
 320 .SH BUGS
 321
 322 .P
 323 Send bugs to michael@orlitzky.com.