FIRST: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362009-05-11T14:35:45ZEcoinformatics Redmine
Redmine Bug #4058 (New): Question 46 on Fall05-Exam3.pdf causes error in recognitionhttps://projects.ecoinformatics.org/ecoinfo/issues/40582009-05-11T14:35:45ZRyan McFallmcfall@hope.edu
<p>(This is a resubmission of a bug lost due to fire. The old bug number was 4057; that number seems to have taken by a newer bug submitted after the restore. We talked about this bug during the videoconference on 2009-05-06).</p>
<p>Question 46 on the exam private/samples/Fall05-Exam3.pdf is not recognized<br />correctly. This question contains some text, followed by a line of text on<br />it's own line that represents a string of DNA, and then contains several<br />choices which are all numbers.</p>
<p>Not all of the prompt is put into the question text, and the last choice (E)<br />also contains the question text for the next question.</p>
<p>Sandeep, can you investigate this and make a report back as to why this is<br />occurring?</p> Bug #3924 (New): Searching for choices in multiple choice question can cross question boundarieshttps://projects.ecoinformatics.org/ecoinfo/issues/39242009-03-31T20:09:11ZRyan McFallmcfall@hope.edu
<p>In doc10.pdf, if the user selects the labels for question 28 as part of user-specified images, then it seems like the MultipleChoice question type is searching for options, and doesn't stop searching until it finds some. In this particular case, this causes it to go past the boundary for question 28 and into question 29.</p>
<p>It seems like it would be best to stop when it sees the next question number in sequence and give up looking for choices, rather than compounding the error by combining two questions incorrectly.</p> Bug #3880 (New): Handle exceptions when parser is runninghttps://projects.ecoinformatics.org/ecoinfo/issues/38802009-03-10T21:17:58ZRyan McFallmcfall@hope.edu
<p>When the parser throws a runtime exception during parsing, the whole process basically comes to a halt and nothing happens. We need to catch these exceptions in the extract/parse process and at least give the user as many questions as possible. We'll also need to keep a list of the questions that errors are thrown on and use this list to give feedback to the user indicating where things might have gone wrong.</p> Bug #3866 (In Progress): Undo does not work on question type change actionhttps://projects.ecoinformatics.org/ecoinfo/issues/38662009-03-08T20:53:43ZJay Leeleejon20@msu.edu
<p>when undo button is clicked, it's not actually doing the right job. it does not go back to previous stage but some point, and it messed up somehow.</p>