voc / voctosched Goto Github PK

Quite often, input data is available via http. Extend util.read_file to detect URLs and download them automatically.

We also want to export the schedule as JSON.
See https://programm.froscon.de/2016/schedule.json for an example.

We want to be able to merge multiple schedules.
Was in #4 before.

implement a way to add multiple speakers to the CSV
For tracker usage speaker IDs dont be unique this may differ for other consumers of the XML, this should kept in mind.

suggested format "1:speaker one | 2:speaker two | ..." this of course can make problems with speakers who spell their name in leadspeak

c.f. frab/schedule.xml#2

Calendar import ftw. Was in #5 before.
Example file:
https://programm.froscon.de/2016/schedule.ics

Maybe https://github.com/SFTtech/kevin
Depends on #15

Build an importer for OpenConf Schedules
https://www.openconf.com/

OpenConf has an XML export which we probably can use, sample is requested

I'm currently exporting the data for Linux Audio Conference 2018, using voctosched to build a fahrplan.xml from a DIY csv (with the demo csv as guidance). This seems to work without issues (now), but the generated XML doesn't lint using the xsd validator.
Running the script as explained in the README, leads to:

../lac2018/files/lac2018.xml:34: element links: Schemas validity error : Element 'links': Character content other than whitespace is not allowed because the content type 
is 'element-only'.

And sure enough, in the XML I'll find

<links>None</links>
<attachments>None</attachments>

per event!

Is the import_handler for csv broken and inserts None to those nodes or am I missing something import?

additional fileds like the download URL which are not part of the normal frab export can confuse 3thparty apps. We should export a "frab style" and an "enhanced" xml.

logging setup, argparse, configparser, selection of import and export module should be centralized.

linuxtag11-201-open_source_hlt_was_die_cloud_verspricht
The ä should have been rewritten to ae.

Depends on #15

To be able to use all frab based tools it would be convenient to export also JSON and Ical

We need proper schemas for validation for all flavours, see #8.

It would be awesome if schedule.py could read the csv from stdin and write the xml to stdout.
One could pipe like this
wget URL | ./voctosched.py | tee STH

It would be very nice feature when using docker

Importing one or more schedule xmls to either merge them or enhance them with additional tags