\"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
>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
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
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
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
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
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
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
>
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
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
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
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
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.
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
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/
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
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
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
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
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
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:
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 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 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
+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:
>>
>>
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?):
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
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
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
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
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
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
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().
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
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
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 :
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 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
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
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
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
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
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
; 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
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
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
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
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
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
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-
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
---
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
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
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
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
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
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
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
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,
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
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
>
> Mark,
You were spot on when you said "there must be some side-effect obscuring
the code"
$upcoming_digest is set on line 281:
http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/advance_notices.pl;h=62e36e4a92920b2bafc67c79043bf0a197491842;hb=HEAD#l281
Here's the code sn
On Wed, Nov 26, 2014 at 4:25 PM, Robin Sheat wrote:
> Mark Tompsett schreef op wo 26-11-2014 om 15:49 [-0500]:
> > QUESTION: Do all the koha command scripts need to be only sh?
> >
> For debian/ubuntu, except init scripts, bash is fine as it's required to
> be installed.
>
My personal preference
Pablo,
I'll second Tomas' sentiment -- I refer to the reports library on a regular
basis. I ran across your SQL Reports Library in templates last week, and it
caught my interest. I would be willing to spend some time working on
converting the old SQL Reports Library.
Thanks,
--Barton
On Mon, M
I mentioned this in #koha a few weeks ago, but this seems like a perfect
place to bring it up again:
http://devblog.nestoria.com/post/115930183873/tombstones-for-dead-code
Essentially, this is a method for adding executable markers near code that
you want to remove. If you look for the results of
I dunno, C4::Auth doesn't seem right to me, from the standpoint of
separation of concerns. I seems more natural to me in C4::Members.
On Wed, Jun 3, 2015 at 3:11 PM, Tomas Cohen Arazi
wrote:
> I'd say it could belong to C4::Auth.
>
>
> 2015-06-03 13:07 GMT-03:00 Mark Tompsett :
>
>> Greetings,
Noice!
I use a slightly different coding style -- here's mine, but I don't make
anyone drink my kool aid... I prefer $() to back-ticks -- they're easier to
distinguish from other quotes and far easier to nest.
I *think* that you could replace
for i in $(echo $BUGS); do
...
with
for i in $BUGS;
+1. Would definitely recommend to a friend.
--Barton
On Fri, Jun 19, 2015 at 11:17 AM, Jesse wrote:
> Definite +1 to this.
>
> Should we also discuss adding this to the coding standards at the next
> development meeting?
>
> 2015-06-19 8:43 GMT-06:00 Jonathan Druart :
>
>> The discussion starte
First, I'm a huge proponent of having a single place to look for command
line scripts... honestly, I wasn't aware of scripts outside of
./debian/command_line/, and I'm someone who actively looks for command line
scripts.
Would it be possible to make the scripts less dependent on being packaged?
My
Chris,
Will this require any changes to be made to the git-bz configuration page
on the wiki?
http://wiki.koha-community.org/wiki/Git_bz_configuration
I've been making small tweaks to that page recently, and I'd be happy to
update it -- I presume that anyone using git-bz will need to do a git pu
Ah, that's what I meant -- sorry, I was being ambiguous.
--Barton
On Mon, Jul 13, 2015 at 10:16 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> No. You just need to update your repo.
> Nothing to do for new installs.
>
> 2015-07-13 15:11 GMT+
Could this be made part of the build process?
On Tue, Aug 25, 2015 at 9:59 AM, Tomas Cohen Arazi
wrote:
> Could we please update the schemaspy files on the site? They have lagged a
> lot. I'm not sure who runs it, just wanted to make him/her notice it needs
> updating.
>
> __
On Tue, Aug 25, 2015 at 9:07 PM, Tomas Cohen Arazi
wrote:
> Thanks Chris! I saw it is already updated!
>
I'd like to echo Tomas' thanks.
--Barton
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/m
String changes can be calculated algorithmically. I suspect that the other
complexities are largely a function of lines of code, number of files
touched, and number of dependencies... but I'm sure that there other
factors. The smaller the patch, the more likely that the complexity could
be determin
I haven't tried this, so take it with a grain of salt... but what about
changing the label template, reversing the page height and width? E.g. for
U.S. Letter size paper, use Page Height 8.5, Page Width 11.
If this causes the page to print off the page, you can change the print
orientation in your
Mea Culpa. Mea maxima culpa.
Thanks for the link, Colin. There are a couple of related issues that I had
noticed along the way:
1) Convention (and possibly some koha programming standard) says that the
bug number be included in the summary line of the commit message. Somewhere
along the line, I a
That's really going to make my life easier.
galen++
Thanks,
--Barton
On Wed, Sep 23, 2015 at 9:54 AM, Galen Charlton wrote:
> Hi,
>
> On Wed, Sep 23, 2015 at 9:13 AM, Galen Charlton
> wrote:
> > I'm not sure that there's automation for putting the bug number in the
> > subject line of the c
On Thu, Sep 24, 2015 at 2:16 AM, akafortes wrote:
> Hi barton,
> thank you for your answer, I thought of that method as well and my guess is
> that it'll work just fine if I print just a single label. I'm afraid though
> that this can't work if you want to print more than one labels at the same
>
On Wed, Sep 30, 2015 at 10:18 AM, Tomas Cohen Arazi
wrote:
>
> 2015-09-30 9:20 GMT-03:00 Philippe Blouin :
>
>> Because the code would be extremely specific to a specific functionality,
>> whereas the code in the libraries is there to be reused.
>> And let not go overboard with OO.
>>
>
> We embr
25006: nekls: longoverdue.pl development request -- changing overdue items
to lost status, with patron category restrictions
After bug was pushed to master, Heather and I had the following
conversation:
> Hooray! Now, comes the big logistical question -- what's the process
> > to get this ad
Sorry all,
This was meant for the bywater developers email list. Please disregard.
Thanks,
--Barton
On Thu, Oct 22, 2015 at 8:55 PM, Barton Chittenden <
bar...@bywatersolutions.com> wrote:
> 25006: nekls: longoverdue.pl development request -- changing overdue
> items to lost
On Mon, Nov 2, 2015 at 5:00 PM, Robin Sheat wrote:
> Tomas Cohen Arazi schreef op ma 02-11-2015 om 14:55 [-0300]:
> > To enable it you need to
> > - Comment the rebuild_zebra.pl line in /etc/cron.d/koha-common
> > - Enable the indexer daemon in /etc/default/koha-common
> > - Restart Koha's daemon
I am working on searching lexile number ranges.
ccl.properties shows
lex 1=9903 r=r
The 'r=r' bit means that I should be able to search using a numeric range
separated by a dash, e.g.
500-600
Should return any numeric results from 500 to 600.
The following query works:
cgi-bin/koha
I added this to the agenda:
http://wiki.koha-community.org/wiki/General_IRC_meeting_2_December_2015#Agenda
I would like to add that there is, at this point, no up-to-date
documentation for doing a git install of Koha. Yes, the packages are far
easier to deal with than the git installs, and yes, mo
:
> On 17 November 2015 at 09:48, Barton Chittenden
> wrote:
> > I added this to the agenda:
> >
> http://wiki.koha-community.org/wiki/General_IRC_meeting_2_December_2015#Agenda
> >
> > I would like to add that there is, at this point, no up-to-date
> > docume
>
>
>
>
> Of course, off the top of my head, I don’t know how you’d store indicators
> and subfields in an extensible way. I suppose indicators are attributes and
> subfields are child elements...
>
>
>
> I suppose DSpace actually does a “element” and “qualifier” approach for
> DC. So you’d have a
Hi, has anyone gotten debugging to work in vim, using the instructions here?
http://wiki.koha-community.org/wiki/Debugging_in_VIM
I tried it, and ran into dependency hell... If I remember
correctly, Komodo-PerlRemoteDebugging-4.4.1 didn't play nicely with
https://github.com/joonty/vdebug.
If som
The rfc made sense to me; I think that it is the right approach. Here are a
few things to consider:
1/ There are a *lot* of reports written that use items.itype. I don't like
the fact that this isn't called items.itemtype, but unless we have a
seamless and foolproof transition, this will cause mas
Nice work.
On Mon, Jan 11, 2016 at 9:57 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> Hi devs,
>
> I have played with NYTProf at the end of the last week, here is my
> loosely structured notes:
> https://joubu.github.io/koha/nytprof/dbic/index.html
>
> I have not found b
On Fri, Jan 15, 2016 at 8:53 AM, Kyle Hall wrote:
> I'm am totally in favor of merging borrowers and deletedborrowers! I think
> the same could be said for most if not all of the deleted/old tables.
>
I couldn't +1 this more vigorously if I tried... I write a lot of reports
for libraries, and I
Yes, it's possible
Here's what I use:
so = "!f() { c=`expr $1 - 1`; git filter-branch -f --msg-filter \"echo -n
\\\"[SIGNED-OFF] \\\" && cat && echo \\\"\nSigned-off-by: Barton Chittenden
\\\"\" HEAD~$c^..; }; f"
... I'm
On Mon, Feb 1, 2016 at 5:54 PM, David Cook wrote:
> Hi Nicole,
>
> I keep meaning to look over and revise the search documentation, but I
> always seem preoccupied with other work.
>
> I'm not sure whether or not the list at
> http://manual.koha-community.org/3.24/en/kohasearchindexes.html is
> c
I think that a flag may not even be necessary -- the TT syntax won't
conflict with the current letter formats, and is unlikely to be entered
accidentally. I think that we could simply silently start to support TT,
and no one would be the wiser, except for those who want to use it.
This also addres
I'm in much the same boat as Mirko -- the mailing list fits my existing
workflow.
Discourse, to my mind, fills a niche between IRC and a mailing list. I
wouldn't want to try to replace either of those with Discourse, but I think
that it might be helpful for certain kinds of discussion like RFCs or
Owen,
I'm really glad that you re-posted this -- it's a page that I wish that I
had seen two years ago -- it gives me names for things that I've had to
muddle through describing.
I've added a link to this page at the end of the terminology page on the
wiki: https://wiki.koha-community.org/wiki/Te
Hi,
We just upgraded a library from Koha 3.0 to 3.22. After the upgrade, the
library complained that the title "Golden Age" was at the bottom of their
OPAC search results.
I checked the obvious first:
OPACdefaultSortField had been set to 'relevance' with OPACdefaultSortOrder
set to 'ascending',
You can create a report with the following query:
select * from accountlines
Running the report will allow you to export as CSV which you can easily
import into excel.
On Thu, Mar 31, 2016 at 3:29 PM, yash verma wrote:
> is there anyway to export the fine data along with some user info in an
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
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,
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
1 - 100 of 136 matches
Mail list logo
