"This article is longer than our AI tools can effectively summarize."
Has anyone else experienced this when trying to use the Summarize feature in Logos Pro? I tried it on a chapter of a non-academic monograph that was about 25 pages long. Wondering what the page limit is for summarizing?
Comments
-
Yes, I noticed that too, and forgot to report it back to the beta forum.
If that can be fixed, that'd be a huge improvement.
0 -
Logos—What is the page limit for the summarize tool? It has worked well for journal articles, but I haven't tried it on other documents.
0 -
For articles/chapters that are too long, I would like if we could get the summarization tool to work on a selected portion of the text.
0 -
Yasmin Stephen said:
For articles/chapters that are too long, I would like if we could get the summarization tool to work on a selected portion of the text.
Or provide longer summaries when the text is too long.
0 -
We need a authentic response from FL.
0 -
Report as BUG!Christian Alexander said:We need a authentic response from FL.
Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.
International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.
MacBook Pro MacOS Sequoia 15.4 1TB SSD
0 -
This is not a bug. The AI summarization tools have limitations on the amount of text that can be summarized. I don't have an exact number to share. It could change in the future depending on a variety of factors. It's not a page count. It's related to word count.
Andrew Batishko | Logos software developer
0 -
We need to know exact numbers because this lets us quantify the basis for the study.
0 -
Christian Alexander said:
We need to know exact numbers because this lets us quantify the basis for the study.
I'm shortsighted - how would knowing the word count help? Presently, the summarization seems to follow the major outlining in the resource (e.g. article or chapter); if the article/chapter is within the word count (whatever that is), we'll get a summarization; if it is over the word count, we'll get the 'article is too long' message. What good is knowing the word count then? Can you explain some more?
0 -
Yasmin Stephen said:
the summarization seems to follow the major outlining in the resource (e.g. article or chapter); if the article/chapter is within the word count (whatever that is), we'll get a summarization; if it is over the word count, we'll get the 'article is too long' message.
This is correct.
Andrew Batishko | Logos software developer
0 -
So is that the official answer then? Just that sometimes AI summarize works and sometimes it doesn’t?
0 -
It would help us to know better what to look for and when to outsource for summarization. It makes it a better process.
0 -
Christian Alexander said:
It would help us to know better what to look for and when to outsource for summarization. It makes it a better process.
I am guessing that Logos is already outsourcing to AI cloud tools for summarization. When the tools they use have limitations on how much text they can summarize, Logos can't do it for us.
If you have access to some other tool that you can use to summarize some longer text, you will know to use that other source after Logos says the text you tried to summarize is too long. Why do you need to know now what the cutoff of text length is beyond which you might have to use some other tool? Just try it in Logos first, and if Logos can't do it, use the other tool. Are you going to do a word-count on the article in question (which would likely require copying it and pasting it into a tool like Word that can do word-counts for you) and decide if it's longer than some threshold and then send it to that other tool if so, bypassing an attempt in Logos altogether? That would be more time consuming than simply trying it in Logos first, and if it fails, trying it in the other tool.
0 -
The Summarization tool will now summarize much longer articles. Whole chapters should now not be a problem.
0 -
Mark Barnes (Logos) said:
The Summarization tool will now summarize much longer articles. Whole chapters should now not be a problem.
Thanks, that's great news!
0 -
I think it would be best if the tool had a dual operating mode as well as auto-translation:
1) follow its own delimitation of what to summarize when nothing is selected manually (auto-translation does this);
2) or summarize only the text selected by the user (auto-translation does this when we select only a part of the paragraph or more paragraphs).
This would solve the problem of summarizing long texts because we could select a smaller part.
____________
"... And do not be grieved, for the joy of the LORD is your strength." (Ne 8.10)
0 -
Andrew Batishko said:
The AI summarization tools have limitations on the amount of text that can be summarized.
Given that there is also a limit to how much of the AI tool a user can utilize in a month, it would be very helpful to have an option to set the summarization tool to only work when text is selected. This would prevent wasting the monthly allocation and speed up the system when a user does not want a summarization. Perhaps there could be options in the Panel menu for when the text will be summarized, such as Automatic or Selection or On Click.
0 -
Harry Hahne said:Andrew Batishko said:
The AI summarization tools have limitations on the amount of text that can be summarized.
Given that there is also a limit to how much of the AI tool a user can utilize in a month, it would be very helpful to have an option to set the summarization tool to only work when text is selected. This would prevent wasting the monthly allocation and speed up the system when a user does not want a summarization. Perhaps there could be options in the Panel menu for when the text will be summarized, such as Automatic or Selection or On Click.
Unlike the translation tool, Summarization requires you to click on the "Summarize" button every time you want a summary. It shouldn't be possible to "accidentally" request a summary.
0
