https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19360
--- Comment #24 from Katrin Fischer <katrin.fisc...@bsz-bw.de> --- Hi Alex, welcome back! > If so, couldn't I simply remove the $k subfield and store this data value > (with a data delimiter) in the $u subfield, rather than adding a brand new > field url|text? Yes, I think that was the thought, also to keep the last subfield $k free for now. > > I am not familiar with Koha plugins so I've had a look at the kitchen sink > example plugin and it looks like I'd need to make a tool plugin and it would > need to be accessed via a link in the cataloguing/addbiblio.tt file. Sorry, need to clarify. There are different kinds of plugins in Koha :) I was thinking of a value builder that you can link to the subfield via the framework configuration (look for plugin as an option there). It's older and a bit simpler than the new plugins. We use one for dateacccessioned in items, and some others are present in the record, as the helpers for the 00x fields or the authority linker. > The .tt file of this plugin will contain two inputs (url and link text > inputs) which the backend logic concatenates and separates with a delimiter > before this data value is stored in the 952$u database field of > marc_subfield_structure database table. That was the idea - but my initial suggestion of | is not good I think. If you mark $u repeatable in the frameworks, Koha uses | for sorting multiples. Might have to think about something else, that is no tin a URL. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org 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/
