Jamovi Min and Max Error - Possible Glitch I'm wondering

[Jaz11]

I am in the process of data cleaning for my thesis and one of the very first steps is to check the descriptive statistics which includes the minimum and maximum stats for each question asked to identify any errors. As the first scale I am using uses a 1-5 answer system, the minimum and maximum should reflect this, which is does for all questions...yay!

However, when checking the second scale I am using, which should be 0-10, only questions 1,2 and 4 of this scale reflect this. Questions 3 and 5 do not, question 3 is showing 0-7 and question 5 is showing 0-8, which is incorrect. Now the next step would be to see if the levels are correct in Jamovi, which I have done and the levels for questions 3 and 5 are the same as 1,2 and 4, which is 0-10.

I think this could be a Jamovi glitch/error, so I tried downloading a new file form Qualtrics and checking it without touching anything else (like deleting unwanted variables or transforming the variables) however it was still showing the exact same problem.

I am wondering if someone would be able to give me some insight into what has happened/how to resolve this? I am on a strict deadline and stressed about what to do from here.

[jonathon]

hi,

so in the case of `SIDAS3 - Minus 1`, i think you'll find that no-one has answered with a value greater than 7.

you might have levels which are defined up to a value of 10, but if a value greater than 7 has never been observed, then the max value is going to be 7.

jonathon

[Jaz11]

Hi Jonathon,

Thanks for that! that makes sense. You are right no one had a answer higher than 7 for that question, so in this case would be okay to leave it and continue on?

[jonathon]

you've essentially asked jamovi what the minimum and maximum values are for each of those variables/columns, and for `SIDAS3 - Minus 1` jamovi has told you that the maximum value is 7 ... which sounds like it's correct. so this hopefully addresses your concern:

I think this could be a Jamovi glitch/error

... there is nothing here to suggest a problem that would prevent you from continuing to analyse this data.

cheers

jonathon