http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #9 from Jesse Weaver ---
I've stolen this development from Kyle, and I have an idea for implementing it
that could get us other benefits down the road. Instead of shoving this new
status
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #10 from Kyle M Hall ---
I'm for this idea. I think a path to z39.50 without Zebra is very good and
useful, aside from the benefit of simplifying the feature in a way, and having
it be always up
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #12 from Heather Braum ---
And all is good now -- Jesse has said that the MARC subfield creation is still
possible with the procedure of what he's suggesting. So my concerns are
satisfied.
--
You are
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #11 from Heather Braum ---
I added a version of this comment privately where we're tracking the
development, but I'll go ahead and add it here publicly.
As one of the development sponsors, if this
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Nicole Engard (ByWater) nic...@bywatersolutions.com changed:
What|Removed |Added
CC|
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Nicole C. Engard neng...@gmail.com changed:
What|Removed |Added
Assignee|k...@bywatersolutions.com
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #8 from Kyle M Hall k...@bywatersolutions.com ---
Thanks Galen! That's a capital idea! I imagine then I would need to add a
system preference to decide which field/subfield that status value should go
into, right?
(In
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #7 from Heather Braum hbr...@nekls.org ---
I'm not quite following the comments being made here -- forgive my ignorance on
how MARC works with the Koha items table.
TLDR version: Regardless of how this is developed and
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Heather Braum hbr...@nekls.org changed:
What|Removed |Added
CC|
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Kyle M Hall k...@bywatersolutions.com changed:
What|Removed |Added
Assignee|gmcha...@gmail.com
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Katrin Fischer katrin.fisc...@bsz-bw.de changed:
What|Removed |Added
CC|
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #3 from Kyle M Hall k...@bywatersolutions.com ---
I would also like the emphasize that this will be a completely optional
component and will not be a required feature in Koha. As I wrote, we *could*
use this feature within
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #2 from Kyle M Hall k...@bywatersolutions.com ---
(In reply to Katrin Fischer from comment #1)
I am not sure about this idea - do we really need to store it in the
database as it is a calculated value? Or could it be
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Galen Charlton gmcha...@gmail.com changed:
What|Removed |Added
CC|
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
--- Comment #5 from Katrin Fischer katrin.fisc...@bsz-bw.de ---
Hm, it would also be very annoying to correct in case of changing the logic or
adding to it. Calculating on the fly might allow for more flexibility and
configuration
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13937
Chris Cormack ch...@bigballofwax.co.nz changed:
What|Removed |Added
CC|
16 matches
Mail list logo