Hello DSpace Community, Recently our our wiki tech support worked to put in place more security on the wiki to reduce the amount of spam. Two solutions were initially proposed by Larry Stone and myself to assist in this endeavor. Initial work was done, going ahead with what probably appears to be the simplest solution. I'd like to give the community a little more power in the decision making on this subject so I am proposing that we take a brief survey of what the community would like to see and go forward from there.
Our current wiki implementation is Mediawiki (www.mediawiki.org). And our current issue is that we get occasional users registered in the system who are spammers and alter pages. When this happens one of us SysOp users has to go in and clean out the page and ban the user. While a nuisance, this happens only occasionally, once a week or less. Recently the configuration was lost in an upgrade and even "non- registered users" could edit pages. We recently went in to correct this issue again. The two solutions proposed are as follows: 1.) Gated Editor community: The solution put in place yesterday now requires all new users to request to be added to a special group to actually edit a page. Adding some to this group requires someone in the group to hand the users request to be added (as you have just recently seen a request on the dspace-tech). 2.) Leave the community editing open to registered users, who will have rights to edit certain pages. Install a spam blacklist extension that exists for media wiki that stops know spammers from being allowed to access the wiki. (http://meta.wikimedia.org/wiki/ SpamBlacklist_extension) While I have strong opinions about these solutions I would like to see what the community itself would like to see put in place. Please remember, that individuals who are currently maintain the wiki already have very limited schedules to do so and we are trying to balance their dedication and time as editors and maintainers of content. As well, please keep in mind that MIT has recently hired a temporary contractor to fix up much of the main static html site (www.dspace.org) which is sorely out of date, and bring a significant chunk of that content into the wiki space for us. Currently we do already restrict edit access on a number of important high visibility pages in the wiki and that much of this migrated content will only be editable by a limited number of SysOp users. Cheers, Mark Mark R. Diggory ~~~~~~~~~~~~~ DSpace Systems Manager MIT Libraries, Systems and Technology Services Massachusetts Institute of Technology ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
