Re: [Koha-devel] generic Koha data export format?
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 format would probably be used. Then a seperate button to generate a csv of the borrower information. This could be amended easily to be imported into different version of Koha by adding or removing columns in a spreadsheet application. Finially, another botton to generate a csv/xml/yaml file with issues, reserves, fines, serials. Maybe even split those to seperate buttons/files too. That's just one idea. And one of those features is already in place in the biblio exports. It would just need to be expanded to handle copy information. On Wed, 2010-06-02 at 13:49 +1200, Reed Wade wrote: 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 reason) - portable backups - a stable interchange format when migrating between Koha and other ILSs - the case where some library is running v2 and it's really, really finally time for them to move to v12 and they now have the resources to do it -reed ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
Re: [Koha-devel] generic Koha data export format?
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 xml) without the need of extra tags (required in xml) - it's human readable/editable Which is better on the above two points are debatable: YAML doesn't need closing tags (which are often better for clarity, like comments next to /TMPL_IF tags), but I think it has meaningful whitespace which I don't like because humans are poor at seeing whitespace. - it supports pointed structures Do we need them? - it's now supported everywhere Not everywhere, but probably comparable with XML. Does MySQL handle it now? I'm inclined towards XML because I know its tools better and my experience is that XML tools are more widely available, although I guess Koha requires both YAML and XML tools to be available. Hope that helps, -- MJ Ray (slef) Webmaster and LMS developer at | software www.software.coop http://mjr.towers.org.uk| co IMO only: see http://mjr.towers.org.uk/email.html | op ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
[Koha-devel] generic Koha data export format?
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 reason) - portable backups - a stable interchange format when migrating between Koha and other ILSs - the case where some library is running v2 and it's really, really finally time for them to move to v12 and they now have the resources to do it -reed ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
