http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14201
Marcel de Rooy <m.de.r...@rijksmuseum.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |http://bugs.koha-community.
| |org/bugzilla3/show_bug.cgi?
| |id=14815
--- Comment #13 from Marcel de Rooy <m.de.r...@rijksmuseum.nl> ---
(In reply to Héctor Eduardo Castro Avalos from comment #9)
> Hi Marcel you're right, the three perl scripts/templates do nothing or do
> the same thing, but the magic of having too many plugins perhaps is for
> filling different data in the frameworks. i.e., books only uses "06 - Type
> of record: a - Language material" but computer files uses "m - Computer
> file" and videos uses "g - Projected medium"
>
> With this you save time for experimented catalogers. The data in the leader
> is predefined and she or he doesn't need to fill at all. Just by the fact to
> choose the proper framework is enough.
>
> Maybe you can do a trick in your plugin to catch the framework code and
> redefine the leader for the type of resource/material.
Yes, you are right that this would be handy. And it probably was the idea when
these files came up. But it did not work.
Note that this report does not change behavior.
So I am opening a new report to collect some ideas how to improve the default
leader. Since we have the framework code already, we could pass that one to the
plugin. When we add a preference, we could add leaders there per framework
code. I would not favor hardcoding BKS BOOKS etc. in the plugin..
See bug 14815.
--
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/
