.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "SREVIEW-IMPORT 1p"
.TH SREVIEW-IMPORT 1p 2024-05-26 "perl v5.38.2" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH NAME
sreview\-import \- Import an event schedule from an event's upstream
.SH SYNOPSIS
.IX Header "SYNOPSIS"
sreview-import
.SH DESCRIPTION
.IX Header "DESCRIPTION"
\&\f(CW\*(C`sreview\-import\*(C'\fR instantiates a \f(CW\*(C`schedule_format\*(C'\fR schedule parser, and
makes sure that first, all events and talks in the parsed schedule exist
in the SReview database, and second, that all events and talks which
exist in the SReview database for a found event but which do \fInot\fR
exist in the parsed schedule are marked as \f(CW\*(C`ignored\*(C'\fR. Parsers are implemented
as classes under the \f(CW\*(C`SReview::Schedule::\*(C'\fR namespace; e.g., the
SReview::Schedule::Penta class implements the \f(CW\*(C`penta\*(C'\fR parser.
.PP
The location of the event schedule is to be passed to the schedule
parser using the relevant option of that parser; most support the \f(CW\*(C`url\*(C'\fR
option for a URL.
.SH CONFIGURATION
.IX Header "CONFIGURATION"
\&\f(CW\*(C`sreview\-import\*(C'\fR considers the following configuration values:
.IP dbistring 4
.IX Item "dbistring"
The DBI string used to connect to the database. Required.
.IP schedule_format 4
.IX Item "schedule_format"
The format of the schedule. Required. Must be implemented as a subclass
of \f(CW\*(C`SReview::Schedule::Base\*(C'\fR.
.IP schedule_options 4
.IX Item "schedule_options"
Any options to be provided to the parser. Should be a hash; which keys
are supported depends on the relevant parser. See the parser's
documentation for details (e.g., SReview::Schedule::Penta for the
\&\f(CW\*(C`penta\*(C'\fR parser.
.SH "POD ERRORS"
.IX Header "POD ERRORS"
Hey! \fBThe above document had some coding errors, which are explained below:\fR
.IP "Around line 37:" 4
.IX Item "Around line 37:"
=over without closing =back