[Edit]Export Functionality Needed

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?

If you're referring to a database export, a DBA should be able to move content fairly easily between databases, and copying the JAMWiki file directories should handle file data. If you're referring to an XML export, technically an XML export is pretty simple to do but the problem comes from determining what the DTD for an export should look like - what author information should be included, how should topic and version information be exported, etc. Backwards compatibility can be a huge PITA, so I'd like to make sure that whatever format we choose is well thought-out. One specific problem is making sure that enough author information is provided with exports to conform to licenses such as the GFDL, which require attribution for redistribution. If you have ideas or suggestions please feel free to discuss them here or on Tech:XML import. -- Ryan 27-Jan-2007 01:40 PST

I think, a proper XML export/import can handle backward compatibility much easier than the database internal structures can do. Imagine a solid update procedure: export your data (optionally incl. changed settings), install the new JAMWiki version and import the exported data. At least this works very smooth since ages with Atlassian JIRA -- Tom 31-Jan-2007 11:53 PST

Sorry, I wasn't clear. My concern about backwards compatibility is that once JAMWiki chooses an XML format, we're pretty much stuck with it. Therefore I'd like to see whatever DTD we use be well thought-out. Exporting content as XML is easy; the hard part is figuring out the best way to structure that content. Mediawiki's DTD formats provide a good starting point if someone wants to work on a proposed JAMWiki DTD format. -- Ryan 31-Jan-2007 12:22 PST

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.

It's definitely climbing up my personal to-do list, although if someone else has the time and motivation to put something together that would be great. Either way, before too long the current XML functionality (discussed on Tech:XML import) will definitely be expanded to allow significantly more functionality. -- Ryan 17-Jul-2007 23:26 PDT