Sermon Workflow with multiple scriptural references

I don't know if this has been asked elsewhere (I tried to search for it and couldn't find anything -- but that might be because I didn't search well). If it has been asked somewhere else, I'd appreciate a link to that post.

Is it possible to use the sermon workflow on multiple scriptural references?

The upcoming reading for the Narrative Lectionary is: Micah [1:3-5]; 5:2-5a; 6:6-8. I'm not looking for L8 to parse the optional verses, or even the partial verses. (I'd be happy using Micah 1:3-5; 5:2-5; 6:6-8 in the sermon workflow). However when I try even my resetting of the reference ranges (without the square brackets and the partial verse reference) L8 doesn't seem to be able to work with this type of reference.

Is anyone else experiencing this?

What is the work around? (Starting three different workflows would be possible, but it would make it more difficult to produce a cohesive sermon.)

Thanks.

Peace & Blessings,

Colin+

Find more posts tagged with

Desktop App

Comments

Mark Smith

Colin, you bring up a good point. There is no work-around. Currently the Workflow only handles one contiguous scripture reference.

There are plenty of people that use a lectionary for sermon direction. I'm not sure how FL could implement a workflow for this, but it would need to be customized for this purpose.

Colin Cameron

https://community.logos.com/discussion/comment/1009924#Comment_1009924

Thanks Mark.

If I remember correctly it took a while for the copy bible verses tool to have the ability to work with non-contiguous scriptural references.

I've been around long enough to know that the good people at Faithlife are smart enough to figure it out (and savvy enough to know if it isn't worth devoting time to from a business perspective.)

The Sermon Workflow is just such a game changing addition that I'd hate to not be able to use it when I've got non-contiguous readings to deal with.

MJ. Smith

https://community.logos.com/discussion/comment/1010175#Comment_1010175

There is no where that Logos handles noncontiguous references; it also does not handle the multple passages inherent in lectionaries. We have a long ways to go ...

Colin Cameron

https://community.logos.com/discussion/comment/1010326#Comment_1010326

Where is the right spot to raise the issue then?

With the creation of Verbum and the Anglican and Lutheran product lines, there must be more users who work with lectionaries than there were in the early days. While I've got no idea the % sales of those product lines to the business, as an uneducated outsider, the lack of ability to deal with uncontiguous pericopes seems to be a missed opportunity.

The sermon workflow (with the ability to keep all sorts of different resources tied together) is really what amplified the need. In the past, since all of the different resources sat separately, it made sense to study each portion of a pericope separately. Now, there will be weeks when a sermon workflow won't make a lot of sense to develop, which means I won't have the richness of using the full set of tools some weeks.

MJ. Smith

https://community.logos.com/discussion/comment/1010410#Comment_1010410

Where is the right spot to raise the issue then?

In the Suggestion forum here and on Uservoice.

The Narrative Lectionary is unusual in the degree to which this is a problem. In most lectionaries, there are only a handful of readings that are not best studied as contiguous despite having been edited for length. There are a number of people pushing for workflows that handle multiple passages so that all the readings of the lectionary can be read - again the Narrative Lectionary is unusual in that only one reading is mandatory. When workflows handle multiple passages, then you'll have a workaround for non-contiguous readings.

Reuben Helmuth

https://community.logos.com/discussion/comment/1010410#Comment_1010410

Where is the right spot to raise the issue then?

You could add your voice of support here!