1) Exporting codes in Excel format does not create a spreadsheet that MAXQDA can import! This is a serious mistake.
2) The system should allow export to Excel, where I can edit the codes, then re-import.
3) The system should allow import of a table of codes from Excel that looks exactly like your export!
4) The use of the ">" for sub-codes is just silly, that is an engineer's solution. No one writes their codes that way. Therefore, a human has to figure out how to convert codes from a table into your format. That is what computers are for — silly format conversions.
MAXQDA should be able to read an Excel sheet created in "human" form, e.g. a table.
5) You have a bug or a documentation failure: ">" does not work as a separator, it requires spaces around it to be recognized, so only " > " works as a separator.
1) Exporting codes in Excel format does not create a spreadsheet that MAXQDA can import! This is a serious mistake.
2) The system should allow export to Excel, where I can edit the codes, then re-import.
3) The system should allow import of a table of codes from Excel that looks exactly like your export!
4) The use of the ">" for sub-codes is just silly, that is an engineer's solution. No one writes their codes that way. Therefore, a human has to figure out how to convert codes from a table into your format. That is what computers are for — silly format conversions.
MAXQDA should be able to read an Excel sheet created in "human" form, e.g. a table.
5) You have a bug or a documentation failure: ">" does not work as a separator, it requires spaces around it to be recognized, so only " > " works as a separator.
0 Votes
0 Comments
Login or Sign up to post a comment