Giter VIP home page Giter VIP logo

imagemap's People

Contributors

123andy avatar blainevlan avatar chemikyle avatar frgeof avatar lewisa2 avatar marlycormar avatar pbchase avatar tom-e-lynch avatar wibeasley avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

imagemap's Issues

MBody Map changes to image size and output.

Hello,

I developed the html and json for the MBody map for a user. When viewing the image in the REDCap system, the image is bigger then expected and they would like for it to be smaller. The output of the selections are listed in one field. They would prefer to have each selection as a checkbox and the values be 1 or 0. Can you let me know what I would need to do to accomplish these changes?

Thanks,
Angelica Allen
University of Kansas Medical Center - Medical Informatics

PAINMAP_MALE not loading correctly 1st time

I am trying to simply use @ImageMap=PAINMAP_MALE for one of my surveys. I followed all of the written instructions. When testing my survey: the first question asks what type of pain you have (i.e., none, musculoskeletal, abdominal). Branching in the survey for answering yes to musculoskeletal pain causes the @ImageMap pain map to appear...but it appears twice! (one after the other). When you try and click on a body region it resets the whole page without highlighting any region and sends you back to question 1. If you hit 'submit' - an error message appears letting you know you haven't completed the required questions - and THEN the imagemap appears only once (as it should) and works perfectly. Every single time you have to go through the steps of hitting 'submit' and going back into the question for the imagemap to work.
I have NO idea why this is happening. Any clues how I can get this sorted?

Data entered on survey disappearing when using @IMAGEMAP action tag (REDCap 9.4.1, Imagemap v1.4.4)

The issue here is that I had data entered into a survey that was disappearing when I went to the next page. At Rob Taylor's suggestion, I determined that this issue is resolved when the @ImageMap action tag is removed. The screenshots are provided below and the demonstration xml file is available on the REDCap Community page: https://community.projectredcap.org/questions/78059/data-entered-on-survey-disappearing-due-to-section.html .

Project Design: I have 2 instruments, Pre and Post. In both instruments, I have an imagemap (@ImageMap=DO_TOUCH_NET_BODY_GREY) and fields for each body region where the severity of the pain is assessed, if the body region is selected on the imagemap. Additionally on the Post instrument, there is a matrix field where the rows show up if the severity on the Post instrument is worse than the severity on the Pre instrument.

Issue: When more than one body region has worse severity, only the first one in the list shows up in the matrix field. Additionally if you return to the previous page on the Post instrument, the severities for the other body regions have disappeared. This behavior only happens in Survey Mode, not Data Entry Mode.

Notes: After many hours of testing, @frgeof and I found how to prevent this from happening. Method 1: Change the survey setting Question Display Format to "All on one page". Method 2: Change the matrix field to separate fields and remove the Section Break. Additionally at Rob Taylor's suggestion, we found that removing the @ImageMap action tag on the Post instrument solves the issue.

S1
S2
S4
S5
S6
S7

PainMap image not quite consistent with international definitions

Hi

I love the PainMap implementation of ImageMap and think it will be very well utilised by researchers all over the world. However, this is why I thought I should make the programmers aware that the current CHOIR diagrams are not consistent with some of the anatomical regions that have been formally developed and endorsed by international groups of researchers.
painmap_male

Here is the agreed region definition for neck pain:
neck pain spatial definition region

You can see that, even when combining multiple regions of the CHOIR image, these regions cannot be defined using the PainMap module. Therefore, many researchers will be put off from using the current implementation, which would be a shame.

Here is the current defining region for low back pain:
back pain spatial definition region
You can see that this low back pain region is a pretty close fit to a combination of those currently used in the CHOIR diagram, but there still needs to be a little bit of adjustment.

Given that the CHOIR maps are under copyright, I'm not sure how best to fix this. Should we amend the current versions (if permission is given), or start afresh?

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.