Loading Profile...
How to handle simultaneous edits on a small office wiki?
Hi. We are trying to create a wiki-newsletter for our office. Content will be provided by 50-60 people and it will be self-edited as well as edited by an administrator. The only problem with this idea is allowing multiple people to access the wiki at the same time, and enter information. When we send out an email letting people know it's ready to launch, there will be 10+ people trying to add information at the same time. I've noticed the system "locks" when more than one person is editing. How can I get around this? If pbworks / pbwiki can't help, is there a program that can? I read a thread here about MediaWiki but this seems too complicated for the small scale we are thinking - I don't have a tech background. Thank you!
I’m annoyed
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Jon,
The problem with concurrent editing is that it causes overlaps on who made the most recent data. You have a few options here. The first is to give each user their own workspace page, and then compile the pages together at a later date.
A second option is more fun, but a little tricky! You give each user their own workspace page, and then create a compilation page. Using the include plugin (From the PBwiki magic menu) you can include each user page on the compilation page. While each user works on their own page, other users can view the compilation page to see what's occurring and what changes they need to make.
I hope this helps!
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
Rachel,
Thanks ever so much for the advice. Your options seem like they might be difficult for a 50-person office - 50 pages.... yikes! I will give it a whirl and see how it works. Thanks again.
jon
