Moved from the Feedback page:
I could really use Export functionality, either for moving between Prod and Dev platforms or for moving out of JamWiki and into another implementation (in case of issues with JamWiki). Can this be moved up on the priority list?
As a user who acknowleges the usability and the value of JAMWiki I think that an easy export mechanism, oriented for non DBAs would be a valuable feature for JAMWiki. It would be very usefull because the export problem does not rise until one needs to move their wiki. If they fail to do so, they might not actually loose data, but they may get such an impression. Not beeing a DBA myself, I find it difficult to access the db where my data is stored when I need to move them. However, if there is no plan to provide such an export functionality, it would be usefull to document the inport/export proceedure for JAMWiki.
Moved from Feature Requests:
The descripton of XML import is arcane and doesn't explain how to use it to generally import a whole mediawiki or use existing online wiki services as a base to import articles/frame pages.
Static import means identifying a mediawiki or its SQL database and sucking it in to jamwiki, choosing manually on a form which namespaces to include. May require dealing with one-time conflicts when names are being overwritten, with policies such as dumping the losing page to the talk/comment/discussion page associated with the winning page.
This is primarily useful for those moving to jamwiki from existing mediawikis.
Dynamic import means identifying which of several mediawikis, jamwikis, or even other wikis supporting XML import, contains an authoritative article on a subject, and instructing jamwiki to import it when there's an open link to it. Wikinfo does this with Wikipedia, importing every page not native to Wikinfo. Tikiwiki has a general facility of this nature.
It's extremely useful for intranets since you don't want to define every damn term in the language, you just want to refer people to relatively standard ones in Wikipedia or some fork of it like Wikinfo, without having them leave your corporate wiki.
Moved from the Feedback page:
Yo, guys. Is there a possibility of dumping my whole wiki in an HTML doc (many HTML pages)? --Zajoman 05-Sep-2007 13:09 PDT
Moved from the Bug Reports page:
Dear Ryan, Thank you for your replay. Jamwiki-0.6.6 allow export internal database data to CSV, that's great! Jamwiki could migrate from an external database of other wiki's,for example,Confluence or Snipsnap? how ?
Moved from the Feature Requests page:
XML import and export is useful for complying with open source licenses such as the GFDL and the CC-SA license, as it allows the full history of an article to be downloaded and credited. However, while this feature may be implemented in some form to allow for testing using data from other wikis, it will probably not be implemented as a fully supported feature for a while.
The extremely strategic and useful feature of Getwiki (a mediawiki fork) is that it draws in an entire wiki and populates all pages that are populated in that other wiki, and then lets users merely specialize and customize the pages. This is how Wikinfo works and it's how most organizations SHOULD use wiki content. That is, NOT write most of it themslves but rather import and specialize. Getwiki/Wikinfo uses some color coding to tell users which articles have been imported and which not.
Being able to nest wikis in a multiple-wiki cascade would make jamwiki extremely useful for projects that, like most in a private corporation, have multiple layers of security.