[Koha-bugs] [Bug 23073] wiki.koha-community.org needs updating to a later version

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Jul 11 03:18:32 CEST 2019


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23073

Thomas Dukleth <td-koha-bugs at agogme.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |td-koha-bugs at agogme.com

--- Comment #3 from Thomas Dukleth <td-koha-bugs at agogme.com> ---
Perhaps the trend of consensus may point to starting over with a new instance
of MediaWiki or Dokuwiki which may simplify the problem even if the choice
would be an unfortunate consequence of my time having become less available for
Koha in recent years.

Updating the Koha instance of MediaWiki version while retaining the current
Postgres database implementation may prevent the best improvements to the Koha
MediaWiki implementation as too many extensions, scripts, etc. do not work
properly with Postgres.  If MediaWiki is updated and new content is added,
there may be no good way to migrate to MySQL from that point.  See
https://wiki.koha-community.org/wiki/Proposal_for_Wiki_Curator_17.05_Thomas_Dukleth#Migrating_to_MySQL
.   

I only ever found one set of scripts for migrating a MediaWiki instance from
Postgres to MySQL,
http://www.winterrodeln.org/trac/wiki/MediaWikiPostgresqlToMysql . 

First migrating to MySQL and then updating MediaWiki would allow using many
advantages of extensions such as SemanticMediaWiki which do not work properly
and are not supported in Postgres even if has been possible to install the
extension at one point.  We could have a good system of faceted categories
which would be easier and more useful than the currently implemented more
hierarchical categories modelled on what was implemented in the finding aid in
Docuwiki which only supported hierarchical namespaces in browsable manner and
thus lacked the flexibility provided by an extension such as SemanticMediaWiki.

Possibly breaking some installed extensions which can happen with any update is
not a significant issue holding back upgrading but merely a reason to test
updates before putting them into production.  The Koha MediaWiki instance did
become briefly broken in the past by installed extensions when it was updated
without testing and required some testing and modification of extensions which
are not necessarily at issue going forward presently.  However, anything not
core to the base software might lead to breakage in untested updates.

[While the details of issues relating to Dokuwiki should be out of scope for
this bug, it is worthwhile noting the importance of not allowing an historical
mistake in MediaWiki database choice and the subsequent neglect of the Koha
MediaWiki instance to become a permanent mistake preventing the use of features
dependent on MySQL.  In the practise of users on the previous Koha Wiki
implemented in Dokuwiki, most pages seemed to be frustratingly lost to anything
but guessing query terms in a search.  People did not have the habit of tagging
pages at all when created and when people did tag them it was too often in a
manner which did not aid findability.  Dokuwiki also did not provide any easy
means for a wiki maintainer to find untagged pages and then add a tag or tags
for findability, although, some people in the Dokuwiki community have been
raising the issue for a while.  See
https://github.com/dokufreaks/plugin-tag/issues/77 and
https://forum.dokuwiki.org/thread/9473 .]

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list