Another possibility would be to create a branch for the sip machines that
had different issuing rules.
On Wed, Apr 10, 2019 at 10:03 PM Mason James wrote:
> hi folks
>
> does anyone have any advice for restricting some Koha item-types from
> being circulated (issued/returned) via a 3M self-check
ubuntu)
> But the plan is to fix them, when we have time of course. We could
> maybe make that a push at the hackfest, or kohacon :)
>
> Chris
>
> On Wed, 20 Mar 2019 at 12:14, Barton Chittenden
> wrote:
> >
> > Explainshell.com is a very nifty site that will
Explainshell.com is a very nifty site that will parse the man pages that
they know about, and then tell you what a given command line does.
For example, given the command line
yaz-marcdump -i marc -o marc -f utf-8 -t marc8 -l 9=20 filenametoconvert.mrc
Explainshell will tell you what the -i, -o,
On Mon, Feb 25, 2019 at 6:51 AM Chris Cormack
wrote:
>
> Whatever they are changed to needs to be translatable.
>
Agreed. I suspect that the trade-offs between 'We would like this to be
translatable' and 'we need these values to be un-editable' (I.e. not
authorized values) are probably what's ke
The accounts system uses the following codes to show what kind of fee or
credit has been issued:
A = Account management fee
C = Credit
F = Overdue fine
FOR = Forgiven
FU = Overdue, still accruing
L = Lost item
LR = Lost item returned/refunded
M = Sundry
N = New card
PAY = Payment
W = Writeoff
The
I will, forever after, congratulate the release manager on every release,
having seen the process (at least second hand).
Awesome job.
--Barton
On Wed, Nov 28, 2018 at 8:31 AM Amit Gupta wrote:
> Congrats Nick.
>
> On Wed 28 Nov, 2018, 6:51 PM Tomas Cohen Arazi wrote:
>
>> Congrats Nick and a
Is there any way to change the default statuses on the bugzilla advanced
search page? https://bugs.koha-community.org/bugzilla3/query.cgi
The default statuses searched are NEW, REOPENED and ASSIGNED... which skips
bugs that are 'In Discussion', 'Needs Signoff', 'Signed off', 'Passed QA',
'Pushed f
uot;
> cataloguing.
> >>It has been removed in Koha ??? (2.2 or 3.0 ?), only MARC cataloguing
> >>remained.
> >>At this time biblioitems table became useless/should have been
> merged,
> >>but no one coded/hacked it. But yes, it can be remov
Nov 2018 at 15:22, Katrin Fischer
> wrote:
>
>> Hi,
>>
>> I feel if we want one source of truth besides the source code, it would
>> make sense to submit patches to the manual directly instead of adding more
>> documentation outside of it. Adding a POD file wi
The field guide is based on the wiki page, which I maintained... but I
think that developers should be documenting any notices they add, which is
why I've added this to the agenda for Wednesday's dev meeting:
*Review of coding guidelines*
- Proposed coding guideline DOC2: Entries in the *lette
Koha doesn't currently have a single point of truth for documentation of
notices and slips, which has lead to a proliferation of markup syntaxes,
especially in regard to repeating detail, e.g.
DUEDGST/PREDUEDGST:
<>
ODUE*
<>
or
CHECKOUT/CHECKIN/RENEWAL
Detail here
---
Just out of curiosity, why does biblioitemnumber exist? There should be a
one-to-one relationship between biblio records and biblioitem records ...
so why not use biblionumber as the primary key for biblioitems?
--Barton
___
Koha-devel mailing list
Koha-
I'm guessing that this could be fixed using template toolkit in the notice,
but I don't know the syntax off hand.
On Wed, Oct 24, 2018, 6:38 AM Holger Meissner <
holger.meiss...@hs-gesundheit.de> wrote:
> Dear koha devs,
>
> when we send an order by email <> is formatted with
> decimal point and
I'm not a big fan of items.onloan... If you want to check item
availability, use the checkouts API.
...and then I realized that there's no route for items in the checkouts API.
On Tue, Oct 23, 2018, 6:07 AM Josef Moravec wrote:
> Hello developers,
>
> Me and Michal Denar were thinking a bit abo
On Mon, Oct 22, 2018 at 3:39 PM Liz Rea wrote:
> The term bibliographic number is easily confused with "inventory number"
> and any local or old internal record numbers that migrated MARC may have.
>
Agreed, bibliographic number is confusing.
>
> I think the most accurate long form representa
On Mon, Oct 22, 2018 at 10:14 AM Owen Leonard wrote:
> > I'm starting with looking for instances of 'biblio', which should be
> 'Bibliographic record'.
>
> Hopefully Bug 19833 took care of (most of?) them.
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19833
I found a dozen or so i
I've been looking at the Koha terminology page (
https://wiki.koha-community.org/wiki/Terminology). There are still a
handful of occurrences of incorrect terminology throughout the '.tt' files.
I'm starting with looking for instances of 'biblio', which should be
'Bibliographic record'.
I'm wonder
; Bug 21150 - Data inconsistencies - item types
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21150
>
> It can also check for false authority types, and missing holdingbranch and
> homebranch in items. More could be added to it.
>
> Hope this helps,
>
> K
When ByWater started upgrading our partners to 17.11 last spring, I noticed
that we were getting a lot of errors of the form
"can't call method * on an undefined value at ..."
We're starting to see these errors because more and more of our code uses
Koha objects, and these will fail if a method i
11:49 AM, Tomas Cohen Arazi
wrote:
> It seems 18.04 includes 2.0.59:
>
> https://packages.ubuntu.com/bionic/idzebra-2.0
>
> It requires the 'universe' repo active.
>
> El mar., 28 ago. 2018 a las 12:44, Barton Chittenden (<
> bar...@bywatersolutions.com>) escr
As of debian jessie / Ubuntu 16.04 (xenial), I think idzebra-2.0 should be
at 2.0.62 or 2.0.63.
There are known bugs in 2.0.59 which is the default for debian jessie
and Ubuntu 16.04, so you'll need to use indexdata's repos for those.
I don't know what the version is for Ubuntu 18.04, but 2.0.44
soon that incorporates this.
On Sat, May 26, 2018 at 4:58 AM, Katrin Fischer
wrote:
> I don't know about other sources, but in Germany I've never encountered
> data where the numbers in $w minus MarcOrgCode don't match the one in 001.
> Maybe this problem is just specific to
I agree entirely about the duplication, I'm not a fan.
I think that someone had filled in the template with a real report; I
edited it and made it generic:
https://wiki.koha-community.org/wiki/SQL_Reports_Library#SQL_Report_Template
On Sat, Jul 21, 2018 at 2:19 PM, Cab Vinton wrote:
> > If you
On Fri, Jul 20, 2018 at 4:21 PM, Cab Vinton wrote:
> Hi, All --
>
> All Holds, Patrons, & Circulation reports have been copied over from
> the main wiki reports page to the appropriate dedicated page.
>
> I believe it should now be safe to delete these sections from the main
> page (sections 2, 3
te ...
>
> So my initial thought is to just proceed w/ these relatively trivial
> edits to the wiki. Will certainly hold off, though, if there's
> consensus that it's a waste of time :-)
>
> Cheers,
>
> Cab
>
>
> On Thu, Jul 19, 2018 at 9:56 AM, Ba
On Fri, Jul 20, 2018 at 8:07 AM, Tomas Cohen Arazi
wrote:
> Maybe run the QA script should be one of them?
+1
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website :
Cab,
the reports wiki is in a state of benign neglect, because of development of
_mana_, which will create a way for reports to be shared to and imported
from a central server.
See
https://wiki.koha-community.org/wiki/Recommendation_engine_integrated_with_Mana_project_RFC
https://wiki.koha-comm
Congratulations!
I have to say, I got goosebumps when I saw
Results of search for 'juggling' with limit(s): 'suppress:0'
rather than
Results of search for 'kw,wrdl: juggling'
Cheers,
--Barton
On Fri, Jun 29, 2018 at 3:16 PM, Nicolas Legrand
wrote:
> thank you Tomas ^^
>
> 2018-06-29 17:42
It would be useful for Koha to have a 'Deprecated' function, which would
send a warning about the caller() function and the version of Koha where
the function will be deprecated, and what it will be replaced by... so
let's say that C4::Adequate::DoEET() is being replaced by
Koha::Awesome->sauce().
tatus : NEW
On Sat, Jun 16, 2018 at 3:32 PM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> Very interesting!
>
> Thanks for the link.
>
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koh
Very interesting!
Thanks for the link.
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs
On Sat, Jun 16, 2018 at 2:37 AM, Michael Kuhn wrote:
>
> Dewey Decimal Classification uses characters that indeed do look like
> Arabic numbers (standing for classes, divisions, sections), but these
> characters do not behave like numbers, so the correct sorting is actually
> not as you would exp
The documentation for GetClassSortKey says
* Concatenates class and item part.
* Converts to uppercase.
* Removes leading and trailing whitespace and '/'
* Separates alphabetic prefix from the rest of the call number
* Splits into tokens on whitespaces and periods.
* Leaves first digit group as is
This is an old issue that's never really been addressed. As I understand
it, at one time, we had a tool that used the unix 'at' scheduler to run
requested reports. This was a huge security hole, and we disabled it
and it's never worked since.
As such, those who host servers must add calls to r
On Wed, Jun 13, 2018 at 3:07 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi Barton,
>
> Yes, and no. It depends.
>
... the dark side of TMTOWTDI ;-)
I read through your examples, they all made good sense.
Basically, we should avoid indentation blocks (if ( defined $i
Calling a method or accessing a member of an undefined object will throw a
fatal error that looks like this: "can't call method * on an undefined
value at ..."
For example, this code will cause a software error if $data->{itemnumber}
exists, but the item doesn't exist (maybe it's been deleted?):
+1
On Mon, Jun 4, 2018 at 2:20 PM, Katrin Fischer
wrote:
> +1 !
>
> :)
>
>
> On 04.06.2018 18:27, Séverine Queune wrote:
>
> I like that one !
>
> 2018-06-04 18:10 GMT+02:00 Owen Leonard :
>
>> If there is consensus that the add/edit buttons should be in line with
>> the section headings:
>>
>>
I like screenshot #2; It manages to be more compact *and* it feels less
cluttered, which is all win as far as I'm concerned.
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-de
On Thu, May 24, 2018 at 3:34 PM, Katrin Fischer
wrote:
> Hi Barton,
>
> Control-number is the index on 001. 001 should have the number and 003 the
> MarcOrgCode, that's why it's stripped from $w for search. I don't know
> about OCLCs practices, so can't tell how numbers are handled there. The
> e
I'm working on generating links for 7XX linking fields in XSLT, a-la Bug
15140 - Add MARC21 776 to OPAC and staff display (
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15140).
This Takes the 773$w, and uses the XSLT template 'extractControlNumber'
which strips the leading MARCOrgCode
On Sat, May 19, 2018 at 6:20 PM, Katrin Fischer
wrote:
> Hi Manos,
>
> it's an item field, so it's added for every item in 952/955.
>
> As the complete items information is added on time of indexing, I think
> what Barton suggests is already the case?
>
That's my understanding.
For background:
One of my first trouble-shooting experiences with Koha involved a report of
search results where an item was showing as 'available', but the detail
showed it checked out to a patron. Some helpful bywaterian pointed me to
items.onloan, and issues.date_due, and showed me that they didn't match. A
dat
I've looked at a lot of fines, I've never seen this used...
On Thu, May 17, 2018 at 9:57 AM, Tomas Cohen Arazi
wrote:
> I've filed bug 20777 [1] removing that column. If you are familiar with
> that pre-3.0 column and its usage, please speak up on the bug!
>
> Thanks!
>
> [1] https://bugs.koha-c
On Thu, Apr 26, 2018 at 9:43 AM, Tomas Cohen Arazi
wrote:
> I'm sure Jonathan would raise funds to put one of those on each of our
> desktops :-D
>
... or maybe one of these?
https://www.youtube.com/watch?v=9YoZGXU6Nk0
___
Koha-devel mailing list
Koha
10:10 AM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> Just to see what happens, I enabled warnings in C4/Reserves.pm. All of the
> warnings were of the form
>
> Subroutine * redefined at C4/Reserves.pm line *.
>
> This is happening because of circular depen
Just to see what happens, I enabled warnings in C4/Reserves.pm. All of the
warnings were of the form
Subroutine * redefined at C4/Reserves.pm line *.
This is happening because of circular dependencies, e.g.
C4/Reserves.pm
uses
C4::Members
C4::Circulation
Those modules in turn use
I'm trying to use template toolkit for notices, as illustrated on
https://wiki.koha-community.org/wiki/Notices_and_Slips_Library#Notices_and_slips_using_template_toolkit
This uses the syntax
[% USE Branches %]
or
[%- USE date -%]
to import ... something.
The wiki page says 'See Koha/Template/
Great write-up Paul!
--Barton
On Fri, Mar 16, 2018 at 11:33 AM, Tomas Cohen Arazi
wrote:
> Julian and Alex unveiled an OAuth2 IdP to be backed into Koha!
>
> El vie., 16 mar. 2018 a las 12:30, Paul Poulain (<
> paul.poul...@biblibre.com>) escribió:
>
>> Hello all,
>>
>> So the 2018 hackfest in
Huzzah!
On Mon, Mar 12, 2018 at 11:02 AM, Fridolin SOMERS <
fridolin.som...@biblibre.com> wrote:
> Hi,
>
> I'm please to announce we have build sandboxes with Zebra and
> ElasticSearch.
> See https://wiki.koha-community.org/wiki/Sandboxes#BibLibre
>
> If help needed please use sandbo...@biblibre.
On Feb 5, 2018 08:41, "Fridolin SOMERS"
wrote:
Thanks,
Where do I live BTW ?
LOL
Directly above the center of the Earth. :-D
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha
David,
Books might or might not be listed with a UPC in the U.S. I think the
de-facto standard is to use EAN(ISBN-10 or ISBN-13), and *possibly* UPC as
well. Things like mass market paperbacks are more likely to have UPC, a
quality paperback book is less likely to have UPC. ... but magazines, CDs
I've been trying to find out whether pulling cover images via Universal
Product Code would be possible from Amazon and Google.
I did some digging; we're doing this via Syndetics and Baker & Taylor
already, so the groundwork is already partially laid:
Bug 14607 : Make Baker & Taylor cover images
Ah, sweet. Thanks for taking care of that!
--Barton
On Mon, Jan 29, 2018 at 5:34 PM, Chris Cormack
wrote:
> * Barton Chittenden (bar...@bywatersolutions.com) wrote:
>
>> https://bugs.koha-community.org/bugzilla3/rest/ is also giving me the
>> message
>> The REST
https://bugs.koha-community.org/bugzilla3/rest/ is also giving me the
message
The REST Interface feature is not available in this Bugzilla.
--Barton
On Mon, Jan 29, 2018 at 4:25 PM, Chris Cormack
wrote:
> Bugzilla and the OS have both been upgraded which appears to have
> removed those links
>
o2709, and not
> USMARC. It applies to any MARC flavour, and is only related to the file
> format, not the file content.
>
> HTH
>
> Le 17/01/2018 à 19:46, Barton Chittenden a écrit :
>
> The documentation for
>
> misc/cronjobs/build_browser_and_cloud.pl
>
> Sta
The documentation for
misc/cronjobs/build_browser_and_cloud.pl
States
> *Important*
> This preference and cron job should only be used on French systems.
(see
https://koha-community.org/manual/18.05/en/html/16_cron_jobs.html?highlight=cronjobs#authorities-browser
)
The associated OpacBrow
Tomas,
Thank you for putting the REST api RFCs page together; having a series of
pages that document the routes was sorely needed.
One question -- the RFCs lists the route for borrowers as '/patrons'.
However https://wiki.koha-community.org/wiki/Coding_
Guidelines_-_API#SWAGGER1.2:_Resource_names
Can confirm. Still down.
On Fri, Dec 1, 2017 at 1:22 PM, Joy Nelson wrote:
> Galen,
> Are you also working on the wiki.koha-community.org site? This is still
> down.
>
> -Joy
>
> On Fri, Dec 1, 2017 at 8:43 AM, Galen Charlton
> wrote:
>
>> Hi,
>>
>> It is now back up.
>>
>> Regards,
>>
>> Gale
Alex,
A borrower should not be allowed to cancel a waiting hold; that would leave
items orphaned on the holds shelf.
Cancelling waiting holds was removed from the OPAC, but the button was
not. See discussion in
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18856
On Tue, Nov 7, 2017
>From the "Summary" section of the bug reporting guidelines:
Also keep in mind that the summary is what people will see when bugs are
listed in the search -- it's a good place to put keywords like which page
the error occurs on, or specifics about where a problem occurs. The summary
Times are for
\"echo -n \\\"[SIGNED-OFF] \\\" && cat && echo \\\"\nSigned-off-by: Barton
Chittenden \\\"\" HEAD~$c^..; }; f"
On Fri, Aug 25, 2017 at 6:17 AM, Tomas Cohen Arazi
wrote:
> +1
>
> On vie., 25 de ago. de 2017 4:07 AM Marc Véron wr
On Jul 10, 2017 17:39, "Tomas Cohen Arazi" wrote:
An 'introduction'?
Well, technically there's already an introduction, but yes, that's exactly
where I'm headed. :-)
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-comm
b the barrier should be
> much easier, Im hoping the doc manager role is more and more that,
> managing, not authoring.
>
> https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual
>
> Chris
>
> On 11/07/17 08:49, Barton Chittenden wrote:
>
> I've been wondering
I've been wondering for a while if it would be a good idea to move the
administration section farther back in the manual. As it stands, a new
user, first reading through the manual will read through a page or two of
introduction, and then get thrown straight into 600+ system preferences.
I'm coming
IP address is also written to (intranet|opac)-access.log. There is no user
information logged, but there might be enough URL and browser information
logged to leak the user's identity, especially in combination with
information in the database.
On Sun, Jun 25, 2017 at 4:45 PM, Chris Cormack
wrote
Oooh. Very nice idea, Tomas!
On Tue, May 23, 2017 at 3:25 PM, Tomas Cohen Arazi
wrote:
> Has anyone considered the option to use UUIDs for our PK? I'm pretty sure
> DBIx::Class supports them. I'm not sure how SQL::Abstract handles them, but
> I know MySQL provides the uuid() function.
>
> This w
Just in case anyone is late catching up on email, bug 17898 was pushed to
master on 2017-05-22... so we're all set here.
On Fri, May 19, 2017 at 2:41 PM, Marc Véron wrote:
> +1 for this, even if we are in string freeze
>
> We will have a mix between translations and English anyway in the more
>
I'd like to add that if anybody would like help in the next few days with a
testing environment, whether it's a guided tour of the koha-sandboxes, or
help setting up kohadevbox (see https://github.com/digibib/kohadevbox ),
feel free to ask me (barton) in IRC. Just mention my name in #koha, and
I'll
Do we have any conventions for snake_case vs. notsnakecase?
I don't see that in https://wiki.koha-community.org/wiki/Terminology,
although it may be somewhere else in the coding guidelines.
[This is probably bike-shedding that's been discussed elsewhere; please
don't let me derail the discussion]
Excellent catch, David!
Please file a bug for that, if you haven't already, the use of MARC 880 for
CJK languages is quite common in US libraries.
Does Zebra handle 4 byte characters correctly?
--Barton
On Fri, Mar 24, 2017 at 2:08 AM, David Cook
wrote:
> Hi all,
>
>
>
> I ran into a problem
On Mar 18, 2017 14:20, "Mark Tompsett" wrote:
Greetings,
KohaDevBox may be putting the messages into plack error logs, not the
standard staff and opac ones.
GPML,
Mark Tompsett
... Those will be in /var/log/koha/kohadev/
___
Koha-devel mailing list
Welcome to Koha-devel, jukka!
Sounds like you're doing interesting stuff. Tomas (aka tcohen in #koha) has
done a lot of good work with ansible in kohadevbox; I think that he's
looking at re-tooling some of the koha deployment scripts to make them work
better in an ansible environment.
Cheers,
Ba
I've got an issue that we've seen periodically at ByWater; I want to file a
bug, but I don't have a clear idea of how to replicate the issue, so I'm
trying to solicit information from the community on how to narrow the scope
of the problem and/or measure the performance problems that I'm seeing.
T
Gaetan,
I've added your entry here:
https://wiki.koha-community.org/wiki/ICU_Chains_Library#Swedish
Please let me know if I've made any copy/paste errors.
Thanks,
--Barton
On Wed, Feb 1, 2017 at 9:18 AM, Gaetan Boisson
wrote:
> Digging this back up as we finally found a solution. And by "we
This was discussed at the last IRC developer meeting.
See
http://meetings.koha-community.org/2017/development_irc_meeting_11_january_2017.2017-01-11-20.01.log.html
Discussion starts at 20:40:47
There are a little over 100 reports in the SQL Library that will need to be
updated, most of which wil
On Tue, Jan 10, 2017 at 5:33 PM, David Cook
wrote:
> I've received a reply from Adam at IndexData. He's looked into the problem
> and has added a fix as part of YAZ 5.20.0.
>
Nice.
Does IndexData have a public bug tracker? If so, is there a bug number or
URL?
--Barton
_
On Tue, Dec 20, 2016 at 10:15 AM, MHE I.T. Admin (DRR)
wrote:
> 15:58:14-20/12 zebraidx(9140) [warn] default.idx:13: Could not load
> icuchain config 'words-icu.xml'
>
I see two unrelated issues in your logs. The most crucial was
Could not load icuchain config 'words-icu.xml'
This is what's c
Marcel,
I like the idea of having the scripts available via a git install for a
couple of reasons:
1) I'm a command line weeny, and hate losing my tools when I'm working in a
git environment
2) Just out of principle, I think that paths should not be hard coded... it
makes it needlessly hard to ru
Pardon my ignorance, but I'd like to add a topic for discussion in the next
dev meeting, and I can't quite figure out where that should go -- the last
dev meeting has come and gone:
https://wiki.koha-community.org/wiki/Development_IRC_meeting_19_October_2016,
but there's not another meeting schedul
After some conversations on the Koha mailing list, I re-factored some of
the language specific ICU chains pages and created
https://wiki.koha-community.org/wiki/ICU_Chains_Library
Which documents language specific modifications to words-icu.xml (and, at
least theoretically, phrases-icu.xml).
If
Also, if you can run tail -f /var/log/koha//plack-error.log
when the error occurs, that should give us a better idea of what's timing
out.
On Mon, Oct 3, 2016 at 7:19 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi Paul,
>
> What's the frequency of your plack errors (1/
On Thu, Sep 29, 2016 at 10:26 PM, David Cook
wrote:
> That’s awesome to hear, Tomas. I suppose I’d like to brainstorm more about
> the schema changes that would be required to support a more useful API.
>
>
>
> I figure if we collect a number of use cases, we can create a general
> approach to co
I recently created a patch for bug 12374 'Add koha-mqsqldump script,
analagous to koha-mysql'.
This prompted discussion in the ticket, as well as in IRC; Katrin requested
a wider discussion:
I'd like to get some more opinions on this as both Magnus and Liz have left
> notes that this might be bet
On Wed, Aug 31, 2016 at 8:17 AM, Philippe Blouin <
philippe.blo...@inlibro.com> wrote:
> Now, may I suggest something? Documentation. Not user friendly, but at
> least dev-enlightening.
>
> "You" guys put time in there, as with plack and memcache and whatnot, but
> if you're on the outside, you
+1
On Wed, Aug 24, 2016 at 5:40 PM, Chris Cormack
wrote:
> Done
>
> http://schema.koha-community.org/master/
> and
> http://schema.koha-community.org/16_05/
>
> Chris
>
> On 23 August 2016 at 14:30, Chris Cormack wrote:
> >
> >
> > On 23/08/16 13:50, Mark Tompsett wrote:
> >> Greetings,
> >>
>
and why and when use_zebra_facet=1 is slow
>
> 2016-08-22 21:31 GMT+01:00 Barton Chittenden >:
> > I haven't run into the issue with the dashes in idzebra-2.0 2.0.59, but I
> > have run into this, when using ICU-Chains:
> >
> > Bug 16581 : ICU toke
I haven't run into the issue with the dashes in idzebra-2.0 2.0.59, but I
have run into this, when using ICU-Chains:
Bug 16581 : ICU tokenization bug in idzebra-2.0 2.0.59-1
URL : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16581
Priority : P5 - low
Urgency : enhancement
Sta
ly in some corner of C4/Search.pm where angels fear to
tread, but those should at least be the candidates...
On Wed, Aug 17, 2016 at 2:55 PM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> If you do a keyword search using
> itemnumber:
>
> That will take you to the i
If you do a keyword search using
itemnumber:
That will take you to the item record.
E.g.
Log in to http://intranet.bywatersolutions.com/ (user:pass is
bywater:bywater)
Then click 'Search the catalog' and type
itemnumber:37771
This will take you to the record for *Juggling for the complete klu
On Fri, Jul 22, 2016 at 8:23 AM, Christopher Davis
wrote:
> Jesse,
>
> Best of luck to you and thank you for your work on Koha.
>
I'll second that in spades!
--Barton
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-co
On Jul 12, 2016 11:47 PM, "David Cook" wrote:
>
> In regards to XSLTs, I’d love some sort of registry where you could add
XSLTs and then reference them elsewhere from a dropdown.
>
>
>
> As for https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16648,
I’m curious why we’d have XSLTs publicl
I like that idea.
On Tue, Jun 28, 2016 at 1:37 PM, Tomas Cohen Arazi
wrote:
> Hi everyone, I started to work on logging Holds actions (Bug 14642). One
> of the interesting things to log is the context in which those actions take
> place (OPAC, staff, CLI scripts).
>
> Do u have any opinion on th
Owen,
I've been wrestling with the issue of CSS and XSLT as well, my proposed
solution is
Add Content system preferences for all CSS and XSLT sysprefs that accept a
URL. ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16648 )
that should be relatively easy to implement, simply becaus
On Wed, May 4, 2016 at 10:28 PM, David Cook
wrote:
> Hi all,
>
>
>
> I thought I was going crazy(er) last night when search wasn’t working for
> me in my Koha dev install...
>
>
>
> I kept seeing this message in yaz-client:
>
> [120] Unsupported Truncation attribute -- v2 addinfo '103'
>
>
>
> I
Nuts. accidentally hit send too soon.
>
>
> Koha is supposed to be a general purpose ILS, and I don't think that
> limiting it to a
>
>
... and I don't think that limiting it to a single timezone is in keeping
with that idea.
___
Koha-devel mailing list
don't think that
limiting it to a
> GPML,
> Mark Tompsett
>
> P.S. Back to your regularly scheduled Y2038 doomsday discussion.
>
> *From:* David Cook
> *Sent:* Wednesday, May 04, 2016 8:23 PM
> *To:* 'Barton Chittenden'
> *Cc:* koha-devel@lists.koha-comm
On Wed, May 4, 2016 at 8:23 PM, David Cook wrote:
> Hey Barton,
>
>
> ...
>
>
> Also, I’d never heard of date_t before your email, and the only references
> I can see to it are for specific projects which have implemented it as a
> new data structure themselves. I think time_t is the standard an
Agreed.
There is a 'Documentation' category in bugzilla. The documentation is in
docbook format; I'm sure that you could supply patches, or I'm sure that
Nicole would be happy to make edits if you supply the text.
--Barton
On Wed, Apr 20, 2016 at 8:59 AM, Tomas Cohen Arazi
wrote:
> I think it
Just because I remembered this conversation, and ended up looking this up,
Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15714
enhancement, P5 - low, ---, m.de.rooy, Pushed to Master , Remove zebra.log
from debian scripts and add optional log levels
This should be released in 16.05,
Leading in to the testing -- is there any documentation on
* Adding indexes for ES?
* Support for unicode/i18n in ES?
* Understanding how ES handles relevance (and how this is configured in
Koha)
On Sun, Apr 10, 2016 at 5:58 AM, Katrin Fischer
wrote:
> Hi Brendan,
>
> could you share some link
1 - 100 of 136 matches
Mail list logo
