Summary: | Refactor "Keywords to marc mapping" | ||
---|---|---|---|
Product: | Koha | Reporter: | Gaetan Boisson <gaetan.boisson> |
Component: | Staff interface | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | fridolin.somers, gmcharlt |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | |||
Bug Blocks: | 20396 |
Description
Gaetan Boisson
2018-03-14 14:00:08 UTC
I feel strongly that we cannot consider dropping keywords to MARC mapping until we have a good way to handle subtitle in place to replace it. As far as I know the feature could be renamed "subtitle configuration" since that's the only thing it's used for. However, it is used in a lot of places. Because multiple subfields can be configured at a time, a single subfield column in the biblio table would probably not be an adequate solution. I renamed this to "refactor" instead of "remove" since it is in fact used. We do need to find a way to solve the performance issue, and have an interface that makes more sense than the current one. I am in favor of adding columns to the biblio table, but it wouldn't be possible to have more than one field in one column. We use this for displaying 245 $b $n $p in a lot of places. It's really needed still. I think we should provide an XSLT transformation for all compact display of a biblio record. I think it could be a performance issue. *** This bug has been marked as a duplicate of bug 11529 *** |