SREVIEW-IMPORT(1p)

💖 SREVIEW-IMPORT(1p) 💖

okay bestie, so this is sreview-import from the User Contributed Perl Documentation — a whole lil' utility for yeeting an event schedule into your SReview database, and she's lowkey iconic. sit down, grab a strawberry, let's go 🍓

---

✨ NAME ✨

sreview-import — Import an event schedule from an event's upstream 🦋

---

🌸 SYNOPSIS 🌸

sreview-import

that's it. that's the whole synopsis. no flags, no arguments, just vibes 💅

---

👑 DESCRIPTION 👑

so sreview-import does two things, and it does them in order, no cap:

1. It instantiates a schedule_format schedule parser, and makes sure that first, all events and talks in the parsed schedule exist in the SReview database. Like, every single one. If it's in the schedule, it's gotta be in the DB. ✨
2. Second, it checks all the events and talks which exist in the SReview database for a found event but which do not exist in the parsed schedule, and marks them as ignored. Yeah. If the upstream schedule ghosted them, SReview marks them ignored. it's giving "you're not on the list, bestie" 💀

Parsers are implemented as classes under the SReview::Schedule:: namespace — super clean, super modular, we love a namespaced queen 🎀 So for example, the SReview::Schedule::Penta class implements the penta parser.

Now, the location of the event schedule? That gets passed to the schedule parser using the relevant option of that parser. Most of them support the url option for a URL. so if you're wondering where to put the link... it's url. most of the time. check your parser 🫶

---

💜 CONFIGURATION 💜

sreview-import considers the following configuration values, and you do need to know about them:

• dbistring — The DBI string used to connect to the database. Required. no dbistring, no party. 🙈
• schedule_format — The format of the schedule. Required. Must be implemented as a subclass of SReview::Schedule::Base. if it's not a subclass of that, she will not be parsing for you, sorry bestie ✨
• 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 penta parser). iykyk 📖

---

💀 POD ERRORS 💀

not the pod errors 😭

Hey! The above document had some coding errors, which are explained below:

• Around line 39:

=over without closing =back

like. the documentation itself has a lil oopsie in it. an =over that never got its =back. we've all been there. balance is hard. 🌈

---

and that's the whole page, bestie — written by the Perl crew, and this copy is from perl v5.40.1, dated 2026-02-15. slay, go import a schedule, you got this 💖✨🎀