I have not seen this in use in any library so far, and think this would be better if superseded by xslt, or extra columns in the biblio table.
Fridolyn also mentions that this leads to performance issues.
Would we benefit from dropping it?
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 ***
Thanks a lot to Ere for working on Bug 11529 that removes keywords to marc mapping.