creating reading plans
I have created several reading plans in the past without any problem. Since getting Logos 6, instead of having page numbers per day, I am getting book outline headings. Also, it is not assigning a reading to every day even though I have selected "read every day." Also, as some other posters have noted elsewhere, there are significant variations in the length of the assigned portions. Do I need to change a setting somewhere? Any suggestions?
Thanks
Comments
-
-
Note sure how to do a screen shot. I am using Logos 6 on a computer with windows 8
0 -
Hi, Billy. You're running into a bug that was introduced in Logos 6 but has been fixed internally and should ship out in an update very soon. I'm sorry for the inconvenience.
0 -
Thanks for the info. We will wait for the update.
0 -
I think Eli might have been think about restoring a feature that let you limit the reading range by page number (read pages 20-250 in 4 weeks). That fix will be available in 6.1, but this will not affect the boundaries generated for the plan.
In your situation, the reading plan generator is working as designed. With 6, we made the decision to remove the generation of reading plans using page numbers as boundaries. That's because this resulted in reading plans that would end the day in the middle of sentences or in otherwise unhelpful places. Instead, reading plans will generate using the table-of-contents as boundaries. That means if the book has fewer table-of-contents entries than days, some days will be blank. It also means that some days may have short readings where table-of-contents entries are in close proximity.
We do have an internal tracking case for revisiting this issue and making improvements, but I do not have any information on when this will happen.
For now, the only alternative if you are not happy with the generated reading plan is to instead create a custom reading plan and define selections or page number ranges exactly the way you want.
Andrew Batishko | Logos software developer
0 -
Andrew
This really does need to be bumped up the priority list.
It is not a 'Plan' if, because the table of contents is of the form
3 Title,
(i) the first point
(ii) the second point
then the Title (on its own) should be considered an acceptable portion of text for a days reading.
Nor should Logos shrug its metaphorical shoulders and tell us that is just the way it is for the foreseeable future.
Reading Plans are an advertised feature of the environment we payed for - they should work - at least in a reasonable manner. The current behaviour is ludicrous.
tootle pip
Mike
How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
Thank you for the feedback, Mike. I'll make sure it's heard by the people who are making prioritization decisions.
Andrew Batishko | Logos software developer
0 -
Mike Binks said:
Nor should Logos shrug its metaphorical shoulders and tell us that is just the way it is for the foreseeable future.
Reading Plans are an advertised feature of the environment we payed for - they should work - at least in a reasonable manner. The current behaviour is ludicrous.
No shrugging here. I'm the knucklehead who thought that segmenting by contents entry would be a good idea (for the reasons Andrew cited), and it worked well in the resources and scenarios we tested (clearly not enough). I agree that suggesting that you only read a heading today and a heading tomorrow is outrageous, and we should stop it..
Clearly the best solution would be to give you the control to decide for yourself whether you want to break on pages or headings. Failing that, to segment on pages (if there are any). I've categorized this as a regression bug and asked for the case to be given high priority. Look for a fix in an upcoming incremental release.
0 -
Thank you Eli
You might want to look here for examples?
Actually it would be better to refine the algorithm so that in cases like this...
1 and 1(1) and 2 and 2(i) and 3 and 3(i) are not separated - i.e. the heading is combined with the following section.
Much nicer than throwing in the towel and reverting to crude page divisions.
tootle pip
Mike
How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
Mike Binks said:
...and 3 and 3(i) are not separated
'cos if they are separated this is what you get...
tootle pip
Mike
How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
Eli, in testing I had run into a case where a book has absolutely no divisions. It apparently got lost in later testing as I didn't go back and double check myself as somewhere I'd gotten the idea you were dividing at paragraphs in lieu of pages.
Wright, William. A Short History of Syriac Literature. Piscataway, NJ: Gorgias Press, 2001.
LLS:SHHSTSYRLIT2011-10-10T20:44:41ZSHHSTSYRLIT.logos4
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Thanks, Mike, MJ for the examples. I've let Andrew know.
0 -
Hi Eli
If the Reading Plan algorithm is being reviewed.
You might like to reflect on the likelihood of your customers wanting these sections included in any plan.
These appear to take up the last 9 days of my current plan. [:(]
tootle pip
Mike
How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
Eli Evans said:
I'm the knucklehead who thought that segmenting by contents entry would be a good idea (for the reasons Andrew cited), and it worked well in the resources and scenarios we tested (clearly not enough). I agree that suggesting that you only read a heading today and a heading tomorrow is outrageous, and we should stop it..
Clearly the best solution would be to give you the control to decide for yourself whether you want to break on pages or headings. Failing that, to segment on pages (if there are any). I've categorized this as a regression bug and asked for the case to be given high priority. Look for a fix in an upcoming incremental release.
I remember at least one user loudly complaining about readings stopping mid-sentence just because someone ran out of paper at the end of a page. You could blame it on this guy, who was so glad to get meaningful reading breaks in a cursory look at that feature that he didn't test it thoroughly on a larger sample of texts.
But then: I strongly hope the current beta 6 "fix" (throwing the code oway and reverting to Logos 4.0 modus of operation for this feature) is not what you intend to be the solution for release - was this really easier than just making sure that a heading break is not to be introduced when the following text is a heading, too?
Have joy in the Lord!
0 -
NB.Mick said:
But then: I strongly hope the current beta 6 "fix" (throwing the code oway and reverting to Logos 4.0 modus of operation for this feature) is not what you intend to be the solution for release - was this really easier than just making sure that a heading break is not to be introduced when the following text is a heading, too?
As I have stated on another thread - the impact of poor implementation of this feature must be disproportionally effective in discouraging new customers from being continuing customers. Why buy more resources when you find out how little you can actually do with the ones that you have?
tootle pip
Mike
How to get logs and post them.(now tagging post-apocalyptic fiction as current affairs) Latest Logos, MacOS, iOS and iPadOS
0 -
NB.Mick said:
But then: I strongly hope the current beta 6 "fix" (throwing the code away and reverting to Logos 4.0 modus of operation for this feature) is not what you intend to be the solution for release - was this really easier than just making sure that a heading break is not to be introduced when the following text is a heading, too?
The reversion fix is a temporary solution. Yes, reverting code is almost always much easier (that is, quicker to do and less error-prone) than designing and building new code from scratch.
0 -
Eli Evans said:
The reversion fix is a temporary solution. Yes, reverting code is almost always much easier (that is, quicker to do and less error-prone) than designing and building new code from scratch.
Thanks. Seeing that the RC for L6.1 just shipped, I understand that you wanted a temporary solution that brings stability. Looking forward to L6.2 beta!
Have joy in the Lord!
0
