This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".

The branch, new/enh/bug_5478 has been created
        at  689bc191540e6d55dcf98046c2225691ce4233c0 (commit)

- Log -----------------------------------------------------------------
commit 689bc191540e6d55dcf98046c2225691ce4233c0
Author: Salvador Zaragoza Rubio <[email protected]>
Date:   Fri Mar 4 10:05:34 2011 +0100

    Bug 5478 - Automate MARC framework import/export
    
        Module to Import/Export a Framework structure to CSV/Excel-xml/ODS/SQL 
in Intranet Administration - MARC Frameworks section.
        There are two new links: "Export" to export to a format; and "Import" 
to import from a file.
        The data exported/imported is the one stored in the MySQL tables 
marc_tag_structure, marc_subfield_structure.
    
        Exported works as follows:
        1) CSV: As this format only allows one worksheet, the data from the 
tables is splitted with a row with #-# cells or with the
        names of the fields of the next MySQL table. Each row has as much cells 
as fields has the MySQL table. The first row contains the
        field names, the remaining holds the data.
        2) Excel: Excel xml 2003 format. Each MySQL table has its own worksheet 
in the spreadsheet. Rows and cells data as CSV.
        3) ODS: OpenDocument Spreadsheet compressed format, creates a temporary 
directory to generate the files needed to create the zip file.
        Each MySQL table has its own worksheet in the spreadsheet. Rows and 
cells data as CSV.
        4) SQL: Text file, the first row for each table is a delete and the 
remaining are inserts.
    
        Importing reads the rows from the spreadsheet/text-file as follows:
        1) CSV: Each row inserts or updates the associated MySQL table for this 
framework. At the end of the importing for a MySQL table, deletes the rows in 
the database that don't possess a correspondence with the spreadsheet.
        2) Excel: Imports each worksheet to the associated MySQL table. Works 
as the CSV for each worksheet.
        3) ODS: Creates a temporary directory to decompress and read the 
content.xml. This file has the data needed to import.
        Works as the CSV for each worksheet.
        4) Executes the SQL file.
        If the file imported has a different frameworkcode that the framework 
importing, the framecode is changed along the process.
    
        The Csv format will be the default.
        It uses perl module Archive::Zip or zip/unzip system command to process 
ODS files.
        To parse the sql files when importing it uses SQL::Statement or 
homemade parsing.
    
    Signed-off-by: Nicole C. Engard <[email protected]>
    Signed-off-by: Chris Cormack <[email protected]>

-----------------------------------------------------------------------


hooks/post-receive
-- 
main Koha release repository
_______________________________________________
koha-commits mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-commits

Reply via email to