Workspace Design Tools and Methods
Review of Previous Workspaces[edit | edit source]
The workspace design form is developed by looking at all of the workspaces that we have already created and identifying their 'features'
- Create observation table that identifies workspaces, components and other pieces
- Harvest workspaces, observe what are pieces that emerge as normally present in the workspace
Workspace Patterns Identified[edit | edit source]
- Work Group Pattern - AQ Workgroup copied by 3 others
- Activities/Events | Active Collaborations
- Resources | Get Involved
- AIP Pattern - CCRM example. Workspaces were initially set up for each group and then the groups used them as they wanted
- News/Events | Issues/Discussion
- Work Items | Capabilities/Results
- Resources | Participants
- Each type of content was structured. Sites enforces a hierarchy for pages.
- Proposal pattern - initially created for NSF proposal. Modified for NASA Roses 08 and the exact same pattern was used for NASA ACCESS 09
- News | Schedule
- Context | Proposal | Participants/Forum/Resources
- Also includes template breadcrumb included on every page of the workspace with links to all other parts of workspace
- Class front page
- News | Resources | Project (2008)
- Lectures | Assignments | Project (2009)
- All had -
- Summary or intro to what workspace is about
- What's New,
- Place for Product, purpose of workspace
- Participants/Get Involved
- Work Items/Schedule both task oriented could be combined?
Workspace Parts[edit | edit source]
This is the 'Workspace Observations' form. To add a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page.
A WikiProject [Workspace] is fundamentally a social construct; its success depends on its ability to function as a cohesive group of editors working towards a common goal. Much of the work that members must do to sustain a successful WikiProject (quality assessment and peer review in particular, but almost anything beyond the actual writing of articles) is tedious, often unrewarding, and usually unappreciated. To be effective, a WikiProject must foster not only interest in the topic of the project, but also an esprit de corps among its members. When group cohesion is maintained—where, in other words, project members are willing to share in the less exciting work—a WikiProject can muster the energy and direction to produce excellent articles systematically rather than incidentally.
The workspace is a collection of parts that all relate to the outcome product or object of the workspace. The parts may also be connected to each other. Some of the parts are relatively static, others are dynamic and change as the work progresses. The Goal/Project Plan and how to get involved stay relatively static. While the product, participants, resources and discussion will continue to evolve as the product develops.
Goal Statement/Project Plan[edit | edit source]
Each workspace has a goal statement that links to more information in a project plan. The project plan is an extension of the goal. The project plan is a proposal of work that lays out what the group wants to accomplish, the approach the group will follow.
Who's this for: The goal statement is helpful for the core group of participants to agree on the purpose of the workspace and the desired outcome. It is also helpful and necessary for new participants to find this information
How does this help the product: The goal and project plan align the group goals and activities making it more likely that there will be a systematic, positive product outcome.
- GEO User Requirements had an overall goal and steps laid out to achieve that goal.
- GEOSS Architecture Demo Barcelona laid out an approach to demo
Need a rich document that is annotated with who works on this, what is there to be done, resources, ...
Services that support:
- Collaborative editing
- Threaded discussion
- template or at least a tag to denote that this is a project plan/goal (in order to display project plans?
Participants[edit | edit source]
Participants list allows people in the group to know who else is working on this project and connect directly to those people. It allows new members points of contact for more information and acts as a history to show who was involved for future use of the product. Beyond just name, expertise could be given to facilitate trust.
- Could use profile or tag/badge? to put on their user page so that they would be identified as part of the project...
- Similar to bloggers using badges.
- Community membership service - expertise, other projects, ...
Examples of Participant List:
- Barcelona GEO Architecture Demo
- NSF Proposal Participants - GENERATED BY ADDING A TAG TO YOUR USER PAGE
- EECE 449-09 Beginning of a profile
- Data Summit Participants - no links not so usefull?
Workspace Resources[edit | edit source]
Each workspace has links, papers, datasets, tools and methods that are associated with it and related to the product/object. The benefit to the group is that useful resources don't need to be known by all members to be included. The list is collaboratively curated
Types of resources:
- Links to group stuff (mailing list, background, kickoff)
- previous work
- related projects
- use cases
Successful use of resources:
- GEOSS Architecture Demo - Barcelona - Datasets used were identified using dataspaces format and could be viewed as a catalog.
- GEO User Requirements for Air Quality - documents found were structured and connected to the report through either document IDS or reference to the author.
- Data Summit - Data System Profiles allowed comparison between datasets?
- Datafed wiki - captures resources: presentations, ideas in structured
Ideas the idea blog is also a resource, structured pages are created with tags that allow it to end up in the appropriate idea list. It is a special resource where the group can just identify ideas/thoughts about the project and follow-up on them later or not.
Workspace-related ideas. Tags for workspace and idea are added to each idea page. Create an idea template for the workspace, then use the auto page generator, create another page to show all of the ideas listed. Main workspace page will show the most recent ideas and have link to see all ideas.
Benefits the group by increasing the ability to learn from each other. Benefits the product by adding context??? Benefits to new users ???
- Class of pages called ideas, specific for a workspace allow ideas to be thrown out.
- Digital libraries of different types of resources that can be restructured for various applications.
Discussion[edit | edit source]
Discussion space (one) http://wiki.esipfed.org/index.php/Talk:Air_Quality/Chemistry_Naming_Conventions#CF_Naming_Extensionsis a place for ideas/issues to be described and resolution to be agreed on. Any thing that might be relevant to the group or benefit the product should go there.
Benefits to group - informed of communication. Benefits to product - discussion about the product is linked to the product providing context, reference. Including the discussion on the workspace allows Benefits to new members - can read the discussion and see another view of the history of the group.
Service: Threaded discussion in central place allows group to keep track of important communication.
Examples of Successful Discussion:
- EECE 449 Class Project Discussion | EECE 449 Class Forum
- NSF Solicitation Discussion
- GEOSS Architecture Barcelona Demo
- AQ/Chemistry Naming Conventions
Get Involved[edit | edit source]
A way to bring others viewing the workspace into the community. Get Involved can include the participant list, links to telecon or meeting information, links to the list-serv. Also could include link to project plan/conventions the group uses/todo items/discussion
How does it benefit: Good for participants already involved because new members may bring new insight, skills, to make the project better. Better for the product because additional members may contribute in ways unforeseen originally. Good for new members because it lowers the barrier to entry to participate.
- listing of telecons
- Collaborative editing/none? just a web page?
- Could have a standard form/template for get involved to be 'standard' on every workspace. Then could include a directory of projects with descriptions and links to their get involved
Product or Object of Workspace[edit | edit source]
The workspace is designed for a particular product, output, goal. If the product or object is a collaboratively written document then that page is connected to the workspace. The product may be a collection (i.e. outcome of EE workspace is list of AQ events analyzed).
- Class Projects
- Scenario development
- Tool development
- Demo preparation
Product important to participants because they need it or can use it. Participants important to product because they provide multiple perspectives that enhance the quality.
What's New[edit | edit source]
Each workspace has a What's New or News section. This section gives group members a way to highlight for each other changes they made to the product or the workspace, resources they've added, events of interest or discussion points that need resolution, new members to the group?.
It also gives newcomers a way to catch up on the happenings of this group. What's new also increases visibility to key content.
Who is it for: What's new is for both people new to the space as well as group members.
Needs to have a way to archive the news. Need a way to create automatically so that top few show up - One solution is through transcluding top 5 items from the Workspace News page.
- collaborative editing
- standard 'news' page with transcluding built in?
Needs a method - how to move transclude up/down to show more or less news.
Tools and Methods[edit | edit source]
These are tools developed for the product. Methods developed as part of the product are also resources. This section of the workspace identifies what those tools and methods are. Identifying the tools and methods separate from the entire product allows for components to be reused. good for future products ....