blog/archive/2017/01/01.rss

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries from January 2017</title>
   5                 <description>Entries from January 2017</description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>Introducing ical-archiver to split out old iCalendar entries</title>
  11                 <link>http://people.skolelinux.org/pere/blog/Introducing_ical_archiver_to_split_out_old_iCalendar_entries.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Introducing_ical_archiver_to_split_out_old_iCalendar_entries.html</guid>
  13                 <pubDate>Wed, 4 Jan 2017 12:20:00 +0100</pubDate>
  14                 <description>&lt;p&gt;Do you have a large &lt;a href=&quot;https://icalendar.org/&quot;&gt;iCalendar&lt;/a&gt;
  15 file with lots of old entries, and would like to archive them to save
  16 space and resources?  At least those of us using KOrganizer know that
  17 turning on and off an event set become slower and slower the more
  18 entries are in the set.  While working on migrating our calendars to a
  19 &lt;a href=&quot;http://radicale.org/&quot;&gt;Radicale CalDAV server&lt;/a&gt; on our
  20 &lt;a href=&quot;https://freedomboxfoundation.org/&quot;&gt;Freedombox server&lt;/a/&gt;, my
  21 loved one wondered if I could find a way to split up the calendar file
  22 she had in KOrganizer, and I set out to write a tool.  I spent a few
  23 days writing and polishing the system, and it is now ready for general
  24 consumption.  The
  25 &lt;a href=&quot;https://github.com/petterreinholdtsen/ical-archiver&quot;&gt;code for
  26 ical-archiver&lt;/a&gt; is publicly available from a git repository on
  27 github.  The system is written in Python and depend on
  28 &lt;a href=&quot;http://eventable.github.io/vobject/&quot;&gt;the vobject Python
  29 module&lt;/a&gt;.&lt;/p&gt;
  30
  31 &lt;p&gt;To use it, locate the iCalendar file you want to operate on and
  32 give it as an argument to the ical-archiver script.  This will
  33 generate a set of new files, one file per component type per year for
  34 all components expiring more than two years in the past.  The vevent,
  35 vtodo and vjournal entries are handled by the script.  The remaining
  36 entries are stored in a &#39;remaining&#39; file.&lt;/p&gt;
  37
  38 &lt;p&gt;This is what a test run can look like:
  39
  40 &lt;p&gt;&lt;pre&gt;
  41 % ical-archiver t/2004-2016.ics
  42 Found 3612 vevents
  43 Found 6 vtodos
  44 Found 2 vjournals
  45 Writing t/2004-2016.ics-subset-vevent-2004.ics
  46 Writing t/2004-2016.ics-subset-vevent-2005.ics
  47 Writing t/2004-2016.ics-subset-vevent-2006.ics
  48 Writing t/2004-2016.ics-subset-vevent-2007.ics
  49 Writing t/2004-2016.ics-subset-vevent-2008.ics
  50 Writing t/2004-2016.ics-subset-vevent-2009.ics
  51 Writing t/2004-2016.ics-subset-vevent-2010.ics
  52 Writing t/2004-2016.ics-subset-vevent-2011.ics
  53 Writing t/2004-2016.ics-subset-vevent-2012.ics
  54 Writing t/2004-2016.ics-subset-vevent-2013.ics
  55 Writing t/2004-2016.ics-subset-vevent-2014.ics
  56 Writing t/2004-2016.ics-subset-vjournal-2007.ics
  57 Writing t/2004-2016.ics-subset-vjournal-2011.ics
  58 Writing t/2004-2016.ics-subset-vtodo-2012.ics
  59 Writing t/2004-2016.ics-remaining.ics
  60 %
  61 &lt;/pre&gt;&lt;/p&gt;
  62
  63 &lt;p&gt;As you can see, the original file is untouched and new files are
  64 written with names derived from the original file.  If you are happy
  65 with their content, the *-remaining.ics file can replace the original
  66 the the others can be archived or imported as historical calendar
  67 collections.&lt;/p&gt;
  68
  69 &lt;p&gt;The script should probably be improved a bit.  The error handling
  70 when discovering broken entries is not good, and I am not sure yet if
  71 it make sense to split different entry types into separate files or
  72 not.  The program is thus likely to change.  If you find it
  73 interesting, please get in touch. :)&lt;/p&gt;
  74
  75 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
  76 activities, please send Bitcoin donations to my address
  77 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  78 </description>
  79         </item>
  80
  81         </channel>
  82 </rss>