http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10306
Galen Charlton <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Galen Charlton <[email protected]> --- To outline a way of dealing with this: One way of looking at the problem is that RDA and the 260/264 forces us to deal with the fact that some attributes that we might want to stick in a column in biblio or biblioitems needs to draw from multiple MARC fields. XSLT and XPath give ways to do that sort of parsing... so we can add it to Koha something like this: - Create a new table to store XSLT stylesheets. This could be a combination of standard stylesheets (e.g., the MARC21 to MODS transforming) and local ones. - Create a new table to specify mappings to columns, something like this: koha_attribute_map kohafield # name of table and column to store the results xslt # reference to the XSLT to use, if need be xpath # what to use to extract the value The process would then be, when saving a bib record, that for each attribute specified in koha_attribute_map, the XSLT (if specified) would be applied to the MARCXML, then the XPath used to extract a result, which is then placed in the column specified by kohafield. This process could be used to supplemnt the one-subfield-to-one-column mapping that the MARC frameworks already specify, or with a bit more work, replace it. I should note that this general idea is inspired largely by similar mechanisms in Evergreen. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
