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 > [email protected] > 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 [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
