4 htsn-import \- Import XML files from The Sports Network into an RDBMS.
8 \fBhtsn-import\fR [OPTIONS] [FILES]
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?
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
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.
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.
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.
46 .SH SUPPORTED DOCUMENT TYPES
48 The XML document types obtained from the feed are uniquely identified
49 by their DTDs. We currently support documents with the following DTDs:
51 AutoRacingResultsXML.dtd
53 Auto_Racing_Schedule_XML.dtd
57 Injuries_Detail_XML.dtd
78 Matchup_NBA_NHL_XML.dtd
80 MLB_Gaming_Matchup_XML.dtd
90 NBA_Gaming_Matchup_XML.dtd
92 NBA_Playoff_Matchup_XML.dtd
98 NCAA_FB_Preview_XML.dtd
100 NFL_NCAA_FB_Matchup_XML.dtd
108 WorldBaseballPreviewXML.dtd
116 Cbask_All_Tourn_Teams_XML.dtd
124 Cbask_Conf_Standings_XML.dtd
126 Cbask_DivII_III_Indv_Stats_XML.dtd
128 Cbask_DivII_Team_Stats_XML.dtd
130 Cbask_DivIII_Team_Stats_XML.dtd
138 Cbask_Indv_Scoring_XML.dtd
144 CBASK_ReboundsXML.dtd
146 CBASK_ScoringLeadersXML.dtd
148 Cbask_Team_ThreePT_Made_XML.dtd
150 Cbask_Team_ThreePT_PCT_XML.dtd
152 Cbask_Team_Win_Pct_XML.dtd
154 Cbask_Top_Twenty_Five_XML.dtd
156 CBASK_TopTwentyFiveResult_XML.dtd
158 Cbask_Tourn_Awards_XML.dtd
160 Cbask_Tourn_Champs_XML.dtd
162 Cbask_Tourn_Indiv_XML.dtd
164 Cbask_Tourn_Leaders_XML.dtd
166 Cbask_Tourn_MVP_XML.dtd
168 Cbask_Tourn_Records_XML.dtd
170 LeagueScheduleXML.dtd
174 Minor_Baseball_League_Leaders_XML.dtd
176 Minor_Baseball_Standings_XML.dtd
178 Minor_Baseball_Transactions_XML.dtd
182 mlbdoublesleadersxml.dtd
184 MLBGamesPlayedXML.dtd
190 mlbhitsleadersxml.dtd
208 mlbrunsleadersxml.dtd
216 mlbsluggingpctxml.dtd
220 mlbstandxml_preseason.dtd
224 mlbtotalbasesleadersxml.dtd
226 mlbtriplesleadersxml.dtd
230 mlbwalksleadersxml.dtd
232 MLBXtraBaseHitsXML.dtd
234 MLB_Pitching_Appearances_Leaders.dtd
238 MLB_Pitching_Balks_Leaders.dtd
240 MLB_Pitching_CG_Leaders.dtd
242 MLB_Pitching_ER_Allowed_Leaders.dtd
244 MLB_Pitching_Hits_Allowed_Leaders.dtd
246 MLB_Pitching_Hit_Batters_Leaders.dtd
248 MLB_Pitching_HR_Allowed_Leaders.dtd
250 MLB_Pitching_IP_Leaders.dtd
252 MLB_Pitching_Runs_Allowed_Leaders.dtd
254 MLB_Pitching_Saves_Leaders.dtd
256 MLB_Pitching_Shut_Outs_Leaders.dtd
258 MLB_Pitching_Starts_Leaders.dtd
260 MLB_Pitching_Strike_Outs_Leaders.dtd
262 MLB_Pitching_Walks_Leaders.dtd
264 MLB_Pitching_WHIP_Leaders.dtd
266 MLB_Pitching_Wild_Pitches_Leaders.dtd
268 MLB_Pitching_Win_Percentage_Leaders.dtd
270 MLB_Pitching_WL_Leaders.dtd
272 NBA_Team_Stats_XML.dtd
302 nbateamleadersxml.dtd
304 nbatripledoublexml.dtd
308 NCAA_Conference_Schedule_XML.dtd
312 NFLFumbleLeaderXML.dtd
320 NFLMondayNightXML.dtd
326 NFLSackLeadersXML.dtd
330 NFLTeamRankingsXML.dtd
332 NFLTopPerformanceXML.dtd
334 NFLTotalYardageXML.dtd
336 NFL_KickingLeaders_XML.dtd
338 NFL_NBA_Draft_XML.dtd
341 The GameInfo and SportInfo types do not have their own top-level
342 tables in the database. Instead, their raw XML is stored in either the
343 \(dqgame_info\(dq or \(dqsport_info\(dq table respectively.
347 At the top level (with two notable exceptions), we have one table for
348 each of the XML document types that we import. For example, the
349 documents corresponding to \fInewsxml.dtd\fR will have a table called
350 \(dqnews\(dq. All top-level tables contain two important fields,
351 \(dqxml_file_id\(dq and \(dqtime_stamp\(dq. The former is unique and
352 prevents us from inserting the same data twice. The time stamp on the
353 other hand lets us know when the data is old and can be removed. The
354 database schema make it possible to delete only the outdated top-level
355 records; all transient children should be removed by triggers.
357 These top-level tables will often have children. For example, each
358 news item has zero or more locations associated with it. The child
359 table will be named <parent>_<children>, which in this case
360 corresponds to \(dqnews_locations\(dq.
362 To relate the two, a third table may exist with name
363 <parent>__<child>. Note the two underscores. This prevents ambiguity
364 when the child table itself contains underscores. The table joining
365 \(dqnews\(dq with \(dqnews_locations\(dq is thus called
366 \(dqnews__news_locations\(dq. This is necessary when the child table
367 has a unique constraint; we don't want to blindly insert duplicate
368 records keyed to the parent. Instead we'd like to use the third table
369 to map an existing child to the new parent.
371 Where it makes sense, children are kept unique to prevent pointless
372 duplication. This slows down inserts, and speeds up reads (which are
373 much more frequent). There is a tradeoff to be made, however. For a
374 table with a small, fixed upper bound on the number of rows (like
375 \(dqodds_casinos\(dq), there is great benefit to de-duplication. The
376 total number of rows stays small, so inserts are still quick, and many
377 duplicate rows are eliminated.
379 But, with a table like \(dqodds_games\(dq, the number of games grows
380 quickly and without bound. It is therefore more beneficial to be able
381 to delete the old games (through an ON DELETE CASCADE, tied to
382 \(dqodds\(dq) than it is to eliminate duplication. A table like
383 \(dqnews_locations\(dq is somewhere in-between. It is hoped that the
384 unique constraint in the top-level table's \(dqxml_file_id\(dq will
385 prevent duplication in this case anyway.
387 The aforementioned exceptions are the \(dqgame_info\(dq and
388 \(dqsport_info\(dq tables. These tables contain the raw XML for a
389 number of DTDs that are not handled individually. This is partially
390 for backwards-compatibility with a legacy implementation, but is
391 mostly a stopgap due to a lack of resources at the moment. These two
392 tables (game_info and sport_info) still possess timestamps that allow
393 us to prune old data.
395 UML diagrams of the resulting database schema for each XML document
396 type are provided with the \fBhtsn-import\fR documentation.
398 .SH XML Schema Oddities
400 There are a number of problems with the XML on the wire. Even if we
401 construct the DTDs ourselves, the results are sometimes
402 inconsistent. Here we document a few of them.
407 The <Notes> elements here are supposed to be associated with a set of
408 <Game> elements, but since the pair
409 (<Notes>...</Notes><Game>...</Game>) can appear zero or more times,
410 this leads to ambiguity in parsing. We therefore ignore the notes
411 entirely (although a hack is employed to facilitate parsing).
416 There appear to be two types of weather documents; the first has
417 <listing> contained within <forecast> and the second has <forecast>
418 contained within <listing>. While it would be possible to parse both,
419 it would greatly complicate things. The first form is more common, so
420 that's all we support for now.
424 .IP \fB\-\-backend\fR,\ \fB\-b\fR
425 The RDBMS backend to use. Valid choices are \fISqlite\fR and
426 \fIPostgres\fR. Capitalization is important, sorry.
430 .IP \fB\-\-connection-string\fR,\ \fB\-c\fR
431 The connection string used for connecting to the database backend
432 given by the \fB\-\-backend\fR option. The default is appropriate for
433 the \fISqlite\fR backend.
435 Default: \(dq:memory:\(dq
437 .IP \fB\-\-log-file\fR
438 If you specify a file here, logs will be written to it (possibly in
439 addition to syslog). Can be either a relative or absolute path. It
440 will not be auto-rotated; use something like logrotate for that.
444 .IP \fB\-\-log-level\fR
445 How verbose should the logs be? We log notifications at four levels:
446 DEBUG, INFO, WARN, and ERROR. Specify the \(dqmost boring\(dq level of
447 notifications you would like to receive (in all-caps); more
448 interesting notifications will be logged as well. The debug output is
449 extremely verbose and will not be written to syslog even if you try.
453 .IP \fB\-\-remove\fR,\ \fB\-r\fR
454 Remove successfully processed files. If you enable this, you can see
455 at a glance which XML files are not being processed, because they're
456 all that should be left.
460 .IP \fB\-\-syslog\fR,\ \fB\-s\fR
461 Enable logging to syslog. On Windows this will attempt to communicate
462 (over UDP) with a syslog daemon on localhost, which will most likely
467 .SH CONFIGURATION FILE
469 Any of the command-line options mentioned above can be specified in a
470 configuration file instead. We first look for \(dqhtsn-importrc\(dq in
471 the system configuration directory. We then look for a file named
472 \(dq.htsn-importrc\(dq in the user's home directory. The latter will
475 The user's home directory is simply $HOME on Unix; on Windows it's
476 wherever %APPDATA% points. The system configuration directory is
477 determined by Cabal; the \(dqsysconfdir\(dq parameter during the
478 \(dqconfigure\(dq step is used.
480 The file's syntax is given by examples in the htsn-importrc.example file
481 (included with \fBhtsn-import\fR).
483 Options specified on the command-line override those in either
488 Import newsxml.xml into a preexisting sqlite database named \(dqfoo.sqlite3\(dq:
491 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
492 .I " test/xml/newsxml.xml"
493 Successfully imported test/xml/newsxml.xml.
494 Imported 1 document(s) total.
497 Repeat the previous example, but delete newsxml.xml afterwards:
500 .I $ htsn-import --connection-string='foo.sqlite3' \\\\
501 .I " --remove test/xml/newsxml.xml"
502 Successfully imported test/xml/newsxml.xml.
503 Imported 1 document(s) total.
504 Removed processed file test/xml/newsxml.xml.
507 Use a Postgres database instead of the default Sqlite. This assumes
508 that you have a database named \(dqhtsn\(dq accessible to user
509 \(dqpostgres\(dq locally:
512 .I $ htsn-import --connection-string='dbname=htsn user=postgres' \\\\
513 .I " --backend=Postgres test/xml/newsxml.xml"
514 Successfully imported test/xml/newsxml.xml.
515 Imported 1 document(s) total.
521 Send bugs to michael@orlitzky.com.