There are a few possibilities I see here. One is to create an export
tool. Some MARC format would be good for the biblio and copy
information, but there would have to be some framework, similar to that
which is in the works for imports, to map koha fields to MARC fields.
The system prefered MARC
Marc Chantreux marc.chantr...@biblibre.com
On Wed, Jun 02, 2010 at 12:18:50PM +1000, Rick Welykochy wrote:
1. CSV, directly importable into spreadsheet and database programmes
2. XML, easily handled by MySQL, more transparent than CSV
I would choose YAML because
- it can store tree (as
Maybe this is already solved but--
It seems like it would be fun if there was a nicely generic format
defined for Koha data dumps. Is it correct that right now this is a DB
specific task?
I'm thinking some format that would be good for--
- working across different versions of Koha (within
