I would suggest that the protocol have a very first step of having the coordinator create a stable, simple entry web page on the collaboration portal (whether Drupal side or Wiki page) which all materials can be accessed through.
This is already done by collaboration groups for emergency response that make use of collaboration tools, such as the Multinational Planning Augmentation Team (MPAT). They set up a single web page for entry for each mission (case) to act as the virtual collaboration portal, and give people a simple way to access and manage information, imagery, maps, and access collaboration tools. Examples of the MPAT web site for missions are shown at http://openvce.net/mpat-web-examples
I think the coordinator should also early on in the protocol identify a name, case number or something unique with which to refer to the case/mission. All pages and protocol defined information can then be tagged or named with this.. so "Austin Tate Problem Map" would become "Case VCEE-0 Austin Tate Problem Map" or something along those lines.
I think the coordinator shoud also early on in the protocol identify a name, case number or somethig unique with which to refer to the case/mission. All pages and protocol defined infromation can then be tagged or named with this.. so "Austin Tate Problem Map" would become "Case VCEE-0 Austin Tate Problem Map" or something along those lines.
I suggest that group posts into the Team A group area on http://easdale.aiai.ed.ac.uk allow group members to reply and post comments. I.e., so that the area performs as a Forum as seen on http://openvce.net. At present only top level new additions can be made on easdale. A separate forum would otherwise need to be set up to allow for this very useful functionality.
Continue to explore how an internet form can be used vs. the wiki for usability purposes. The wiki is not easy and intuitive to use, especially for wiki newcomers. Having an easier interface to support the workflow through the collaboration protocol is critical. We take the user out of the openVCE site structure and tools when we push them to the wiki. We also want the user only 1-3 levels deep or away from the top level main site.
Eliminate the SOP objective pages for each subtask. None of the subtasks require more than 1 procedure so the SOP objective page just adds a delay and extra mouse click to get to the procedure.
Procedure:Introduce Process Coordinator to Team and Communicate Case for Team Members to Establish Core Problem Dimensions (Pre-Meeting) – Embed the email and discussion communication options inside the page.
Procedure: Create Individual Problem map – Again, need this in a form where you need 1 sentence of instruction instead of a whole page.
Procedure:Organize Team Meeting – Only include needed and non-intuitive information and instructions (e.g., #2, 4, 5… are not required or don’t need instructions). This page should be linked to the coordination section of the main site working with the shared calendar and other capabilities like doodle.
Integrate individual problem maps needs to be easier and faster. Fully or semi-automated process for this is highly desirable.
A short SL meeting before the current SL #1 meeting? I’d like to get Rob’s input.
Agree to not explicitly use a rating process for each of the problem dimensions but to rely on team consensus and discussions to determine general priority. Additional comments on this? If the integrated problem dimensions were in a dynamic web form, a priority field could be used to dynamically re-order the problem dimension items.
I like the idea of using a tabular format pre and post meeting #1 and taking advantage of Cmaps during the meeting. Need to iron-out the conversion processes and requirements for this tabular-network-tabular format. Need to lay-out the requirements and procedure for both a shared screen in SL for cmaps and a lower-tech/backup option (work on cmaps on local computer and periodically output PDF to display in SL?)
Need an outline/cheat sheet/checklist for each of the coordinators in the collaboration protocol (downloadable resource)
Team A VCEE-0 Web Page
Team A are using http://easdale.aiai.ed.ac.uk and the Team A group area there for its experiments in VCEE-0 (14-17 Dec 2009)
Virtual Collaboration Protocol Adjustment and Web Site Support
I would suggest that the protocol have a very first step of having the coordinator create a stable, simple entry web page on the collaboration portal (whether Drupal side or Wiki page) which all materials can be accessed through.
This is already done by collaboration groups for emergency response that make use of collaboration tools, such as the Multinational Planning Augmentation Team (MPAT). They set up a single web page for entry for each mission (case) to act as the virtual collaboration portal, and give people a simple way to access and manage information, imagery, maps, and access collaboration tools. Examples of the MPAT web site for missions are shown at http://openvce.net/mpat-web-examples
I think the coordinator should also early on in the protocol identify a name, case number or something unique with which to refer to the case/mission. All pages and protocol defined information can then be tagged or named with this.. so "Austin Tate Problem Map" would become "Case VCEE-0 Austin Tate Problem Map" or something along those lines.
I think the coordinator shoud also early on in the protocol identify a name, case number or somethig unique with which to refer to the case/mission. All pages and protocol defined infromation can then be tagged or named with this.. so "Austin Tate Problem Map" would become "Case VCEE-0 Austin Tate Problem Map" or something along those lines.
Allow Reply and Comment on Group Posts on Expt Sites
I suggest that group posts into the Team A group area on http://easdale.aiai.ed.ac.uk allow group members to reply and post comments. I.e., so that the area performs as a Forum as seen on http://openvce.net. At present only top level new additions can be made on easdale. A separate forum would otherwise need to be set up to allow for this very useful functionality.
Protocol feedback