Data Sample: Navigation
Navigation
Over the course of the project, it became clear that blog navigation was an important topic. Sabatino often focused on this clarity of navigation to help organize the pattern of the blog. As time progressed, it became clear that we needed a focused way to track what we were doing so the blog posts did not become too much to handle. This is an important consideration within the classroom. If the group members do not agree on blog formatting to help this navigation, or if they do not have the skills to implement this, the blog could become more of a challenge to the writing process rather than a complement to it. We discussed F2F issues that we were having tracking the blog and brainstormed ways to improve this process.
After a F2F meeting, Sabatino made comments to Jessica's blog post. However, by this point, there were several posts in between. Because there was so much information, and it was necessary to ensure the person saw it, Sabatino offered the following post, which became a format for the future:
“When you get a chance, please take a look at my comments to the meeting minutes. As this blog grows, it might be a good idea to provide heads-up posts such as these to make sure we don't lose the good communication we have going on.”
“Just a suggestion: I've found it easier to navigate our posts by scrolling through the text on the "edit posts" page...the blog itself is getting a bit long. As we continue blogging, I see how the length, depth, and number of postings could become a bit overwhelming for developmental students--anyone for that matter. Then again, developmental students wouldn't be using the blog for such an in-depth, research-driven assignment.”
Sabatino noted: “I see that we are both kind of narrowing our searches to particular scholars/experts in the fields of blogging, process writing, collaborative writing, developmental writers, etc. I think this is a good trend. So if I find more info on Peter Elbow, I will continue to return to the initial post about him and add the new-found text there.Seeing the names helps me contextualize the conceptual framework of the paper.Unless you think we should use the concepts as an organizing tool. For example: Process Writing... Elbow and those to follow?”
Jessica responded: “Either way is fine with me. You start a pattern and I will follow. If authors help, then let's do that.” Because of the previous discussions regarding our topic and paper, it was easy to agree with Sabatino on an organizational method. This communication and compromise is so important to the collaborative writing process.
I first thought we should include all the data samples in one continuous post so we could avoid having other posts (such as this one) interrupt the flow of data sample posts. I thought that creating a distance between these data posts would make it more difficult to coral the material and organize into one cohesive piece.But I think labeling the data posts the way you have is better. If we put all the data samples into one post, it will grow very long and make the organizing process more laborious. So the compromise, I think, is to create separate data posts based upon content (technology, navigation, initial perspectives of the project, etc.) and keep adding content-specific material in the original post. In other words...you have the technology post. Any information I want to add about technology, I will just edit into the existing technology post--instead of creating a new post. Make sense? Hope so.
I first thought we should include all the data samples in one continuous post so we could avoid having other posts (such as this one) interrupt the flow of data sample posts. I thought that creating a distance between these data posts would make it more difficult to corral the material and organize into one cohesive piece.But I think labeling the data posts the way you have is better. If we put all the data samples into one post, it will grow very long and make the organizing process more laborious. So the compromise, I think, is to create separate data posts based upon content (technology, navigation, initial perspectives of the project, etc.) and keep adding content-specific material in the original post. In other words...you have the technology post. Any information I want to add about technology, I will just edit into the existing technology post--instead of creating a new post. Make sense? Hope so.
(note - I know this is informal and changing from 1st to 3rd, but wanted to start making comments that we can modify in our actual write up. As usual, please feel free to insert any other threads you might want here).
Thursday, June 26, 2008
Subscribe to:
Post Comments (Atom)
1 comment:
"This communication and compromise is so important to the collaborative writing process".
Here is a good article about this issue, regarding a necessity of functional project management in collaborative writing:
Collaborative Writing - The Winning Concept
Post a Comment