Closed barichello closed 7 years ago
Thanks for the feedback!
I think I have fixed the problem. It was related to the different way that NVivo for Mac indexes annotations and taggings. Strangely enough it wasn't a problem with the NVivo for Mac sample project, but appears to be with user data.
Let me know if it works for you.
Problem solved! Thank you
Good news. I've updated the script on wooey.barraqda.org
Great! Thank you, Jonathan. It was very useful for my girlfriend.
Best, Leo
2017-03-15 11:20 GMT+00:00 Jonathan notifications@github.com:
Good news. I've updated the script on wooey.barraqda.org
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/BarraQDA/nvivotools/issues/2#issuecomment-286713249, or mute the thread https://github.com/notifications/unsubscribe-auth/ALNauhuFxgWBaS53PtFkY_0Y0RhqZeqqks5rl8l8gaJpZM4McpZa .
-- PhD Student | Centre for Research in Mathematics Education School of Education | University of Nottingham http://barichello.coffee
I have got a nvpx file that was exported from Nvivo 11 (Windows version). This file was generated with the sole purpose of being normalized by me (on Linux).
However, when I use the scripts NormalizeNVPX or NVPX2RQDA, the output I get does not have the boundaries of the fragments right. All the taggings with an associated node have -1:0 as their fragment, while the taggings without an associated node (originally annotations on Nvivo) are correct.
I am not sure if the fact that the file was exported from Nvivo 11 (Windows version) is the reason, but it sounds likely.