WS Sandbox

A place to experiment with group features and contents

For testing and preparation purposes. Photo credit >>

GROUP DETAILS

Created: Oct 10, 2008

Updated: Aug 28, 2009

Membership: Open

Semi-Private

Created: Dec 25, 2008
Updated: Jan 05, 2009
Viewed: 117 times

Topic: Simplifying and optimizing the co-editing workflow

Posts (1 - 3 of 3)

Sort by: Ascending | Descending
Login to Post a Reply.
Sm_avatar

There has been feedback from Camilla that the workflow is too complex and lengthy:

 

"When I reviewed the template that Bowo kindly set up in this group, the work felt a bit too complex and a bit too lengthy to carry out each time I update an org profile as I have to fill in the detailed chart which is fine if we have 100 entries, but not 110,000 entries.  (I spent 6 months as a volunteer just doing data entry for the WE directory - it does take time to do, so anything to speed things up is great)."

 

Perhaps we should lump the resources, solutions, events, jobs, and wikipages columns into a single "related content" column? Which one gets added is trackable via step 4 of co-editing: "If you add related content (resources, solutions, jobs, events, wikipages) from that organization to WE to the organization entry, add it to this group, and add the o mark."

 

We may also want to add an emphasis that the most important part is to ensure that the Organization Info and Email is accurate, and to send an email inviting staff to join WE and steward the page. Other editing are optional.

 

How does this sound?

Sm_avatar

I think that consolidation has many advantages given the amount of work pending. I do think that consolidating requires the addition of a notes column.

 

Taking advantage of speeding up the process and the addition of a 2nd edit [which seems to be implied by the column titles] seems to be a good way of verification and updating.

 

I do think that clarification of areas of specific importance is in order. I personally would like more info on what it means to network the organization. If networking is not just the automatic addition into the AoF, addition of resources and the like, it really needs more explanation. I have been working on this networking issue and I think I would benefit from the input of seasoned experts!

 

Clear instructions and guides are always good.

 

~h

Sm_avatar

Thanks h!

 

I've just modified the columns and added a notes column. Also modified the column titles (longer but more informative).

 

Networking for me should first mean a mapping of the connection that each organization have to:

  • related people (staff, board, members, volunteers)
  • related organizations (partner, have worked together, close ties)
  • related resources (reports, publications, papers, articles, news, etc.). Resource doesn't have to originate from an organization. It can be other organization's. For example, the wildly popular Story of Stuff video should prove valuable for many organizations, and may actually have been used by them as part of their advocacy / campaign work
  • related solutions (that an organization have come up with, tried, or are being a consultant of, being a funder, etc.)
  • related events (organized, participated in, funded by, etc.)
  • related jobs (jobs, internships, volunteer opportunities from an organization)
  • related wikipages (can be articles, press release, etc.). Wikipages probably won't be used that much by an organization unless an organization is using WE's groupware and then use wikipages for brainstorming, drafting, etc.

Ideally, all of this should be done by the staff of each organization as they know best. Also check out step 4 and step 5 of the Organizations Tutorial.

 

How does this sound? Got ideas on how and where should we include or link to this information?

You do not have access to post to this record
1 to 3 of 3 Posts


Contributors to this Page