OpenWetWare:Software/Extensions

From OpenWetWare
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Back to Community Portal

Installed Extensions

Go to Special:Version to see the definitive list of installed extensions and their versions. See OpenWetWare:Feature test to check that the extensions are working. If you wish to discuss extensions on openwetware, sign up for the mailing list.

The following extensions are installed on OpenWetware:

Critical Extensions

Critical extensions are either those which if they break would cause many pages to "break" and as such, these extensions should be considered as important to support (for upgrades, etc). Another way to look at this: if we aren't willing to support these, then we shouldn't encourage people to use these. The known dependencies of these are listed to help in smooth upgrades.

  • Biblio: for citing from PubMed. (Requires php w/ builtin curl support)
  • Calendar: extension for fancy calendars
  • Dewikify: for helping with dewikifying (The mediawiki 'extension' itself only provides the wikionly tags. The dewikify script itself relies on the default format of the monobook skin. If that changes, the script is likely to break.)
  • Recentchangesfilter: extension that augments the recent changes list with the ability for complex filtering (depends quite heavily on the internal structure of MediaWiki so extension likely to break on all major version upgrades, although it is also quite easy to update the extension to match the MediaWiki version)
    • Jasonk 22:44, 12 March 2006 (EST): I think this extension may end up being critical in order to manage discussions. It will enable each discussion area to have recent changes listed. It also enables users to better manage recent changes in areas important to them, something which will be increasingly important as the site scales up. This may be possible via the watchlist, which is the only reason I wouldn't designate this immediately as critical, but I certainly wouldn't call it non-critical yet.
    • Austin 13:27, 13 March 2006 (EST): Good point, I actually hadn't thought about using this as an includable page rather than just for each user using it to filter their own recent changes.
  • ParserFunctions and StringFunctions: useful for simplifying templates greatly.

Unknown criticality

  • Google Maps Generate google maps
  • Dynamic Page List Can dynamically create lists of pages based on sophisticated selection criteria
  • PartsRegistry: for connecting with the Registry of Standard Biological Parts. Use the bbpart tag such as <bbpart>B0010</bbpart> to get <bbpart>B0010</bbpart>
    • Jasonk 22:44, 12 March 2006 (EST):Is it hard to just link to registry parts via HTML links?
    • Austin 23:17, 12 March 2006 (EST): not really, but you also get the ease of entering it and auto-updating if the link changes (given the URL, this seems likely). This may also be implementable using the interwiki linking feature in the same way we link doi's so we would be able to do something like [[part:B0010]]. The benefit of using an extension is that allows for future more complicated expansion. For example, we could perhaps insert the part description or a part sequence or whatever else we wanted.
    • RS 17:44, 26 May 2006 (EDT): As an example, we may now want to update this extension to point to the "new" registry. (And by we, I mean Austin :) ).
    • Austin 18:03, 26 May 2006 (EDT): right...ok, done.
  • http://meta.wikimedia.org/wiki/Cite/SpecialCite.php: 'Cite this page' support
  • LatexDoc: For writing a LaTeX document on the wiki (see example at OpenWetWare:Feature test/LatexDoc). Now supports images and bibtex!
  • WikiTex: Supports embedding LaTeX objects such as chemical structures with XyMTeX.

Non-critical extensions

Non-critical extensions are defined as those which don't significantly change pages or remove important functionality. Users may use these as they wish and they should be able to easily adapt if we turn them off suddenly.

  • MultiUpload: allow upload of multiple images simultaneously.
  • SyntaxHighlight: syntax highlighting for many languages
  • WikiChat
  • Special:Editcount: Show edit stats for users. Can be linked as [[Special:Editcount/user]] and included {{Special:Editcount/user}}
  • UserDefaultPage: allow users to change their default page in their preferences
  • UserSidebar: allow users to change their sidebar

Deprecated extensions

Do not use these extensions. They may be removed at some point in the future.

  • ShowHide extension to dynamically show/hide sections. Use the more powereful toggle functionality.

Desirable or pending extensions

List extensions you would like to install here and vote or de-vote for ones you'd like. See http://meta.wikimedia.org/wiki/Category:Mediawiki_Extensions for some extensions.

  • Semantic MediaWiki: add semantic data to pages. This is potentially an extremely important extension.
  • ShareThis: add links for many social bookmarking sites to sidebar
  • Dynamic Article List - would allow us to dynamically generate lists of the most popular articles, newest articles etc. Check out the sandbox for a test. (Requires >php5)
  • WikiDrops: Add to the top of pages automatically a 'breadcrumbs' path back to the main page.
  • navimages: for allowing images to link to any URL (was uninstalled as it wasn't working)
  • I'd like to see an extension which treated genbank accession numbers in a way similar to PMIDs. --TK 9 April 2006
Lucks 21:10, 14 April 2006 (EDT): Excellent idea. Perhaps a generalization for any ID numbers in any of the NCBI databases.
Or even citing giving a DOI would be great.Toan 12:07, 20 July 2007 (EDT)
Genbank ids work via interwiki linking. Give examples for other IDs to be added.
  • WikiDB: create arbitrary databases on the wiki, demo site.

Will not be installed

  • MediaWiki extension for R
    • R is an Open Source 'Matlab-like' software (great for statistics, multivariate analysis and ploting]
    • see demos: HTML ouput, Graphics, Interactions.
    • OWW community could benefit from it when it comes to sharing analytical methods.
    • need to investigate further server-side security issues.

Writing new extensions or special pages