Zur Generalisierung würde ich nochmal einen Absatz schreiben (vermutlich als weiteren Unterpunkt zu Kapitel 6), der versucht, Listening Histories in den generellen Kontext von Lifelogging einzusortieren und v.a. auch sagt, für welche Arten von Daten der LastHistory-Ansatz noch funktionieren könnte bzw. was man ändern müsste. Alternative wäre diese Besprechung mehr in den generellen Text zu integrieren. Meinungen? Ideen?
[DB: added section 6 (LastHistory Beyond Music) addressing that]
*Y-Axis*: "I was thinking that it might be nice to allow the user to put different variables on the y-axis for some added flexibility" (R1)
[FS: I think the 2D time-based visualization is one of the strongest points of the project and fundamentally enables the visualization of individual listening history entries and thereby of time-based patterns. Maybe this should be emphasized more? Also, I am not sure how "different variables on the y-axis" could work - what would the visualization look like?]
[DB: mentioned that in passing in section 6. TODO: write more about that in section 4.2.3 ("focus on time")]
[DB: fixed with the new 4.2.3?]
[DB: definitely fixed it with the discussion in chapter 7]
*Rectangular zoom*: "Another design feature I thought about was some kind of limited zooming capability to a rectangular region chosen by the user [DB: similar to Hochheiser/Shneiderman Timebox widgets 2004]. That might help in examining densely packed regions." (R1)
[FS: In my experience with 3-4 minute songs, a 15" or larger display using the full screen height nicely fits a full day without overlapping nodes, which was the reason why a vertical zoom/scrolling was not included (see also Diplomarbeit section 3.5.1). It might still add some value in terms of visually focusing on a specific area, so it could be mentioned in future work maybe?]
[DB: 4.3, fixed]
*Zoom+Pan*: "Zooming and panning are described, but not in detail - 1d or 2d?" (R2)
[FS: Maybe click+drag should be mentioned for panning?]
*Arcs*: "The curved lines to other appearances of a song look cool, but I'm not quite sure how helpful that really is. Perhaps another visual presentation of that information might be more effective." (R1)
[FS: The arcs enable the user to distinguish the individual lines connecting two sequences even in the case where the sequences are close to each other horizontally, because the lines never go into nodes from above or below the nodes (which would make multiple lines overlap), but always from the side. Maybe this should be mentioned as a design decision.]
[DB: added that. fixed?]
[DB: re-read the paragraph and we give a lot of reasons for using arcs. fixed.]
*Personal Mode*: "The distinction between personal and analytic mode seems a bit artificial. Why not have those features as individually selectable operations?" (R2)
[DB: We should make clear that personal and analytic mode are only shortcuts for several settings. Maybe argue with the casual users thing?]
[FS: Sounds good]
[DB: added section 4.2.1 on that, so, fixed]
*Scalability*: "Effectiveness of the approach when large amounts of data is involved. ... I can imagine the timeline-based representation would get quite busy and become incomprehensible with a large data set. ... " (R3) [DB: R3 writes in even more detail about it, basically wants to turn the thing into a visual analytics paper]
[DB: added a discussion about that to section 7 (future work). fixed.]
Ein interessanter Punkt ist dass wir in Section 2.3 mögliche Aufgaben und Muster für die Daten definieren, die in der User Study aber nur noch teilweise auftauchen. Also sollte man mal schauen, ob sich ein Mapping zwischen den beiden herstellen lässt.
"I am a bit disappointed about the case study especially the type of tasks performed by users in the study ... What about the support of tasks mentioned in section 2.3?" (R3)
*Online Study*: Außerdem müssen die aktuellen Ergebnisse der Onlinestudy noch eingearbeitet werden.
*Formatting*: "The authors have no indentation on the paragraphs and I believe that there should be based on the TVCG formatting guidelines." (R1)
*Intro*: First paragraph is weird - Sebastian: put it in the end of the introduction, sell it as a contribution (we provide an answer to these questions!) and pick it up again in the conclusion
*Figure 2:* Make text bigger (hard to read right now)
User gender [Sebastian]: Use 's/he' throughout the whole paper.
I did not change it, when the text is about a certain user from the study.
Text widows [Sebastian]: Delete single words in new lines. (on Monday)