← Back to team overview

openlp-core team mailing list archive

[Bug 903773] [NEW] Support a more open format for service files

 

Public bug reported:

Currently service files are very much bespoke to OpenLP, using a python
pickle object format which is difficult for other systems to create or
read (such as web-based service management systems).

Therefore having a more open format for these service files would be
ideal to allow easier integration with other products.

Keep the zip file format, but this would contain an XML file containing
a simple service list, plus other OpenLyric files containing the content
for the text-based media items.

Then allow this to be imported and exported.

E.g. (quick example, it would need more thought and discussion with
sites such as servicebuilder.net)

Files in zip:
   service.xml
   ToGodBeTheGlory.xml
   john316.xml
   notices.xml
   funnyVideoToMakeTheSermonInteresting.mp4


where service.xml contains:

<service>
   <item index="1" mediatype="song">
        <title>To God be the Glory</title>
        <authors>Fanny Crosby</authors>
        <file>ToGodBeTheGlory.xml</file>
        <theme>Clouds</theme>
  </item>
   <item index="2" mediatype="scripture">
        <title>John 3:16 NIV</title>
        <file>john316.xml</file>
        <theme>Bible</theme>
  </item>
   <item index="3" mediatype="custom">
        <title>Notices</title>
        <file>Notices.xml</file>
        <theme>Sky</theme>
  </item>
     <item index="4" mediatype="media">
        <file>funnyVideoToMakeTheSermonInteresting.mp4</file>
  </item>
</service>

** Affects: openlp
     Importance: Wishlist
         Status: New

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/903773

Title:
  Support a more open format for service files

Status in OpenLP - Worship Presentation Software:
  New

Bug description:
  Currently service files are very much bespoke to OpenLP, using a
  python pickle object format which is difficult for other systems to
  create or read (such as web-based service management systems).

  Therefore having a more open format for these service files would be
  ideal to allow easier integration with other products.

  Keep the zip file format, but this would contain an XML file
  containing a simple service list, plus other OpenLyric files
  containing the content for the text-based media items.

  Then allow this to be imported and exported.

  E.g. (quick example, it would need more thought and discussion with
  sites such as servicebuilder.net)

  Files in zip:
     service.xml
     ToGodBeTheGlory.xml
     john316.xml
     notices.xml
     funnyVideoToMakeTheSermonInteresting.mp4

  
  where service.xml contains:

  <service>
     <item index="1" mediatype="song">
          <title>To God be the Glory</title>
          <authors>Fanny Crosby</authors>
          <file>ToGodBeTheGlory.xml</file>
          <theme>Clouds</theme>
    </item>
     <item index="2" mediatype="scripture">
          <title>John 3:16 NIV</title>
          <file>john316.xml</file>
          <theme>Bible</theme>
    </item>
     <item index="3" mediatype="custom">
          <title>Notices</title>
          <file>Notices.xml</file>
          <theme>Sky</theme>
    </item>
       <item index="4" mediatype="media">
          <file>funnyVideoToMakeTheSermonInteresting.mp4</file>
    </item>
  </service>

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/903773/+subscriptions


Follow ups

References