Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: The Likert scale (answer options) is not fully enumerated. #2669

Open
1 of 3 tasks
romanogino opened this issue Apr 17, 2024 · 2 comments
Open
1 of 3 tasks

[Bug]: The Likert scale (answer options) is not fully enumerated. #2669

romanogino opened this issue Apr 17, 2024 · 2 comments

Comments

@romanogino
Copy link

JASP Version

0.18.3

Commit ID

No response

JASP Module

Unrelated, Descriptives, Other

What analysis are you seeing the problem on?

No response

What OS are you seeing the problem on?

Windows 11

Bug Description

In my scale of choices, there were from 1 to 6, but no one answered that, they only answered from 2 to 5. So they don't appear in the choices to code, but I need to show that those choices of 1 and 6 were present for the choice. Perhaps there is som activation button that I have checked before...

Expected Behaviour

I expect the entire scale from 1 to 6 to appear, even if some options have not been checked.
Imagen de WhatsApp 2024-04-17 a las 15 50 25_86377d1c

Steps to Reproduce

...

Log (if any)

No response

Final Checklist

  • I have included a screenshot showcasing the issue, if possible.
  • I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
  • I have accurately described the bug, and steps to reproduce it.
@tomtomme
Copy link
Member

@romanogino
At the moment JASP can not know which numbers or strings comprise the full scale of a variable. There is no button to tell JASP "this should be likert scale from 1-6" and no button that could add missing numbers of a scale. This is also a problem for "automatically" reverse coding of variables. I pointed this out here:
#2325

I would not consider this a bug, but a missing feature that probably would need following fields to be set by the user for each variable:

  • Minimum value of the scale
  • Maximum value of the scale
  • stepsize within the scale

This could make sense for ordinal and scale data. Joris Goosen already explained in #2325 that this might be implemented in the long run. Not in the short run, because it would require quite some work within the GUI.

@JorisGoosen
Copy link
Contributor

I was thinking more along the lines of an R-field where you write a function that converts x -> level you want by applying it in order to the labels as they are. (So the default formula would just be X (maybe better i or level)

This would also allow for non-linear scales etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants