Forum Replies Created
-
Posts
-
I noticed something else this morning about opening documents. I had a document open, then, without closing it, opened another one. I expected to have both of them open at that point – but instead I had just the second one; the first one had been closed.
I tried it again and it did work – not sure why nothing happened last time, since my browser tabs were visible. Thanks!
Actually, it’s not working that way for me. I’m in the same tab, I close the document I’m working on using the menu at upper left, then choose OPEN from the same menu and I’m back at the screen that includes Example Documents.
Never mind – I figured it out. For others, the answer is:
“TEXT”
Important – no equals sign, but important to have the quotes, otherwise it’s interpreted as a variable.
Taking a hint from Excel (which I rarely do), I was thinking that one type of attribute could be “ordered” and you could enter in a list the order from smallest to largest of the attribute values. I would do this at the attribute definition level, not at the graph level, since it’s a pain to do every time you plot an attribute. So I’d want to enter the list (small, medium, large) just once in the attribute definition.
I wanted to add an observation to this thread. A central part of the issue is that there are really THREE variables here: year, state and rate – notice that in any of your data tables in the original dataset, any row has a mixture of values. In one table, both the state name and the rates are in a row (and the years are the columns); in another table, both the year and the rates are in a row (and the states are the columns). There’s something about the structure of the dataset that requires a something other than a flat structure. The attribute stacker fixes the problem, but it would help to have a more semantic description of the problem that it fixes and the way it does so. We wouldn’t necessarily share this reasoning with the middle school kids, but it’s very helpful for the staff of Data Clubs (and maybe also for CODAP folks).
I think I waited too long, and I can’t tell WHEN the errors on the console were logged…but now that I know about the console, I will use it if such a thing happens again.
Of course, I love this answer!! (and, in case you hadn’t already realized this, Traci is working with me on the Data Clubs project…)
I finally started over – restarted CODAP and reopened the file and now it’s saving fine. It’s possible that something just got in a weird state, since I’ve never had this problem before – and it was just one file. I will see if anything was written to the Chrome inspector and let you know, just in case this isn’t an isolated situation, caused by a random cosmic ray.
