quire going through a lot of code that uses
format_date(), of course. Also, I think we should remove usage of
"-00-00" to signify a unset date; this should be NULL in database
columns and undef in code.
Regards,
Galen
--
Galen Charlton
Koha Application Devel
Hi,
On Wed, Apr 2, 2008 at 10:20 AM, Joshua Ferraro <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 9:54 AM, Galen Charlton
> > Doing this would require going through a lot of code that uses
> > format_date(), of course. Also, I think we should remove usage of
ibliographic/bdapp-e.html.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
view at
http://manage-gmc.dev.kohalibrary.com/patches/granular/.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
[EMAIL PROTECTED
w_XXX = view record type XXX
* edit_XXX = edit record type XXX
* first word or word group in the code is a verb
* don't put in a negative, e.g., don't have something like
'cannot_edit_orders'. A permission should be a positive grant of a
privilege.
Regards
o translation for the staff interface. You
could install Koha using one of the languages for which a staff
translation is available, then enable Portuguese for the OPAC.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTEC
b browsers can render NFD strings without any
difficulty, while other ones seem to work better if NFC is used.
Right now Koha passes UTF-8 strings to the browser without
renormalizing them, but perhaps we should be automatically converting
them to NFC?
Regards,
Galen
--
Galen Charlton
Koha Applica
be returned by a specific time the following
morning. That's not the same as supporting short loans via a separate
reserves module, but there are enough commonalities that I wonder if
(and hope) that we can use the same issues table for both "normal" and
hourly loans.
Regards,
Galen
--
s syspref.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
+
For the first, try running 'cpan Net::Z3950::ZOOM' as root - that will
also install ZOOM. For the second, try 'cpan Net::LDAP' as root.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
_
tied to the project root so
that a Makefile in a project subdirectory is not ignored by default.
*.patch
/t/run
/t/test-config.txt
/blib
/Makefile
/Makefile.old
/pm_to_blib
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
_
improve multimarc support.
I agree that USEMARCON would be nice to have. However, its license
(http://www.bl.uk/services/bibliographic/uselic.html) is neither BSD
nor GPL. We would need to look at it carefully.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAI
able to create a valid
MARC::Record object. I suggest adding code to check for that
condition - hopefully only a few of your bib records have that
problem.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
e 3.0.
5. Plan 3.2. As far as I know, we're using even revision numbers for
release intended for production, so the 3.1 line of development would
end up becoming 3.2 at some point.
Step 3 will need to be planned in more detail, of course, and tied to
specific dates.
Regards,
Galen
--
ional IDs would display in the Administration
menu, the patron editor, or the OPAC.
I would appreciate comments on this proposed functionality, the
proposed implementation, and whether or not this would be of use to
others.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PRO
f public Z39.50 targets at
http://irspy.indexdata.com/.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
t work for a production system. Koha using MySQL on Debian Etch
does work.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mail
pcoming 3.2 line of development as soon as possible.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
st suite after each commit
> and report the results
Also agreed.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Hi,
On Tue, May 6, 2008 at 3:03 AM, Henri-Damien LAURENT
<[EMAIL PROTECTED]> wrote:
> >> From: [EMAIL PROTECTED] [mailto:koha-devel-
> >> [EMAIL PROTECTED] On Behalf Of Galen Charlton
[snip]
> >>
> lacks 2 fields :
> - authorised_values related to th
ated to do testing and sign off on patches.
Over the next few days, I will start sending out RFCs regarding what
LibLime is working on or plans to work on, particularly with respect
to features to be targeted for 3.2, 3.4, and perhaps 3.6.
Regards,
Galen
--
Galen Charlton
Koha Application Develo
by using rebuild_zebra.pl -a
-b -z in a crontab or by running zebraqueue_daemon.pl?
* if so, are there any interesting messages in the Zebra daemon log?
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
Hi,
On Tue, May 13, 2008 at 3:56 PM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
> Galen Charlton a écrit :
>
> > As Joshua mentioned, I currently work on nothing but Koha, spending
> > perhaps three quarters of my time on development and bugfixing and a
> > quarter
malizations (as ISSNs, LC card numbers, OCLC
numbers, etc. could benefit from this as well), but haven't done
anything yet.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-
-7434-3602-4');
Alternatively, does an OO interface get us anything additional that is useful?
my $isbn = C4::Normalize::ISBN->new('0-7434-3602-4');
print $isbn->search();
print $isbn->display();
Regards,
Galen
--
Galen Charlton
Koha Application Developer
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listinfo/koha-devel
___
K
, $template->output, "404";
or
output_html_with_http_headers $query, $cookie, $template->output, "404
Bibliographic record not found";
Any thoughts or objections to this?
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECT
e
will discard the local changes.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Hi,
On Mon, Jun 2, 2008 at 8:00 AM, Andrew Moore <[EMAIL PROTECTED]> wrote:
> Does that port line mean that the "443" will always be present on
> HTTPS requests since it's not 80? Does that matter at all?
Good point, I'll follow up with another patch.
Regards
dd it to $koha/INSTALL.ubuntu
+1 to translating and adding an INSTALL.ubuntu. Paul, are you willing
to put a translation together? If not, there are enough cognates that
I could throw something together.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROT
ctually to install koha on
> open suse.
By all means, please go ahead - that would be wonderful.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Probably to insert into "Opac" tab.
There is presently no noOPACUserLogin system preference in 3.0, and
there hasn't been for a while - the equivalent syspref is now called
'opacuserlogin'. Are you using a Koha 3 database that has been
upgraded from Koha 2?
Regards,
Ga
713add76e
>
> So I delete it by hand.
Thanks for the information. It looks like a patch to
updatedatabase.pl is in order.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koh
Hi,
On Mon, Jun 9, 2008 at 9:02 AM, Ricardo Dias Marques
<[EMAIL PROTECTED]> wrote:
> Am I misinterpreting the UNIMARC spec?
As with all formats based on ISO 2709, the correct leader length in
UNIMARC is 24 bytes.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLi
f the RFCs are lengthy, I will be mailing only the summaries;
the details will be on the wiki page for each RFC.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
a wiki at
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_system_groups
Thanks in advance for comments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mai
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
infrastructure.
For more information on this proposal, please consult the Koha wiki at
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_email_checkout_slips
Thanks in advance for comments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457
ments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
t the Koha wiki at
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_opening_hours
Thanks in advance for comments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel ma
information on this proposal, please consult the Koha wiki at
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_recalls
Thanks in advance for comments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p:
//wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_holdability_flag
Thanks in advance for comments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@list
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_notifications_and_opac_messaging
Thanks in advance for comments.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
cy settings, own items, and circulate, and have
parents and children.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Hi,
On Tue, Jun 10, 2008 at 8:00 AM, MJ Ray <[EMAIL PROTECTED]> wrote:
> "Galen Charlton" <[EMAIL PROTECTED]> wrote:
>> While we work on bugfixing for 3.0, it is also time to give a concrete
>> thought or two for the future. Today I will start sending LibLi
nd a loan
rule for a given branch, itemtype, and patron category, Koha now
searches for the most specific rule that matches, then looks for less
specific ones.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p:
nd a loan
rule for a given branch, itemtype, and patron category, Koha now
searches for the most specific rule that matches, then looks for less
specific ones.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p:
Hi,
On Fri, Jun 20, 2008 at 8:35 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
> Galen Charlton a écrit :
>>
>> * clarified how issuingrules is searched: when trying to find a loan
>> rule for a given branch, itemtype, and patron category, Koha now
>> searche
branch to another and which would catch
items that haven't arrived in a timely fashion. In its current form,
circ/transferstodo.pl isn't it, but I think such a report should be
considered for 3.2.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p:
Hi,
On Tue, Jul 1, 2008 at 1:06 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
> If you agree with this proposal, i'll add it to RFC for 3.2
I agree with pursuing both memcached and mod_perl for 3.2.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTE
rks would
be a big win. We don't have to think just in terms of caching
individual tables; we can also cache entire data structures and
objects that draw from multiple tables.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-
of course. Even if mod_perl's session and
global variables turn out to be good enough for caching sysprefs,
things like the HTML templates may benefit more readily from memcached
than mod_perl.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTE
gt; on 3.2, can be backported (for the core part only ?) to 3.0 to get speed
> improvement before 3.2 is released. That will be 3.0RM decision, but if
> asked, I would probably vote yes (once memcached stuff has been well
> tested on 3.2 branch)
mod_perl support would be a candidate for such trea
ing up XSLT explicitly, but I've
> certainly had errors about invalid marcxml spat at me.
Right; because all MARC records are processed through MARC::File::XML
at various points, there will be XML parsing going on even if the XSLT
display options are not being used.
Regards,
Galen
--
Gal
keley, ca 94720-6000
__
cell: +1-510-599-5159 | office: +1-510-643-8665
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
erformance should not change
functionality, and ideally a test case should accompany each major
performance fix to verify that functional behavior has not in fact
changed. Perhaps you could take another look at _remove_stopwords()
to see if a faster implementation can be written.
Regards,
Galen
--
em preferences table and the
context.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
l" present in installation pack but not copied to
> /usr/...
> --
I have submitted a patch to correct this in the installer. Thanks for
reporting this.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
__
| kohafield|
+--+-+--+
| RESTRICTED | Use restrictions| items.restricted |
| STACK| Shelving control number | items.stack |
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
___
ame translation management interface can be used for both the HTML
templates and the sysprefs and MARC frameworks, regardless of whether
the translated strings remain in an external file or (for the sake of
speed) get stored in the database.
Regards,
Galen
--
Galen Charlton
Koha Application Devel
n choice in the matter. However, I
think one thing should be added: because laws or policies in some
places may strictly require that circulation history be anonymized,
there should be a setting that controls whether or not the patron is
given the choice to keep their history indefinitely.
Rega
ne utilities', and I consider the test suite to be separate
from installation. IMO, the default assignee should be Andrew Moore.
since he's taken the lead on improving our unit tests.
Regards,
Galen
--
Galen Charlton
Koha Application Developer
LibLime
[EMAIL PRO
od bug description is entered in the
public Bugzilla.
I recognize that you have pressures on your time. I don't think you
necessarily need to spend time translating your bug descriptions by
hand; quick machine translations would be sufficient.
Regards,
Galen
--
Galen Charlton
VP, Res
luck developing Koha to the best free ILS ever.
Sorry to hear about that. Best wishes for the future.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel m
flame you, or are you objecting to any
criticism whatsoever of your patches?
No patch should be above constructive criticism, including any that
LibLime submits.
Regarding your implication that BibLibre is being put off by LibLime's
"flames", are you claiming to speak for them? I'
lines that one only line.
Thanks for the report. It looks this affects many of the help
templates; this also causes a problem for git-send-email and
git-format-patch if a line goes longer than 998 characters.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PRO
Hi,
On Thu, Jul 31, 2008 at 9:53 AM, Galen Charlton
<[EMAIL PROTECTED]> wrote:
> On Thu, Jul 31, 2008 at 9:33 AM, Zeno Tajoli <[EMAIL PROTECTED]> wrote:
>> working on translation I have found templase with very few returns
>> For the transator is better more lines tha
Hi,
On Thu, Jul 31, 2008 at 10:52 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
> Galen Charlton a écrit :
>> This will build upon the existing C4::Letters infrastructure.
>
> C4::Letters should be renamed to something like C4::MailNotifications or
> something like that I
, then it would be easier for the RM to apply n+1 to git first,
then n a couple days later. Ideally we'd structure things in such a
way that git merge conflicts are minimized, possibly by putting the
SQL for each DB rev in a separate file.
Regards,
Galen
--
Galen Charlton
VP, Research
nal Z39.50 servers -
Koha's current use of Pazpar2 is for an experimental workset grouping
feature.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing lis
koha.org/doku.php?id=en:development:rfcs3.2:rfc32_turn_on_warnings
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
mechanism.
Since a stable 3.2 will be months away, for current work I suggest we
stick with using 3.1 as the version number, following the Linux kernel
convention that an odd subrevision number signifies an unstable
development version.
Regards,
Galen
--
Galen Charlton
VP, Research & Develop
ks 28 to 31).
At the end of this period I will release 3.2-rc1.
[10] Final release (weeks 32 and 33)
At the end of this, 3.2-stable. If I'm counting the weeks correctly,
that corresponds to the end of March, 2009.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[E
both, giving proper attention to each. If not, then either the
3.0 RMaint should default to Josh or we should put out another call
for 3.2 QA.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
IT people who are comfortable playing
with and working with the software, the better.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing li
d fetch, create the tracking branch, and check out that branch
BEFORE rebasing and going through the database update. Later tonight
I will be pushing a patch to master's HEAD that updates the version
number to 3.01.00.000.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibL
Hi,
I've added instructions to the wiki about handling the new branch::
http://wiki.koha.org/doku.php?id=en:development:git_usage#create_a_branch_to_work_in
If anybody finds an error or a better way to do it, please update the
wiki or let me know.
Regards,
Galen
--
Galen Charlt
Hi,
On Tue, Aug 5, 2008 at 12:07 PM, Galen Charlton
<[EMAIL PROTECTED]> wrote:
> I propose the following steps to implement this:
...
> 5. Create a standing blocker bug for 3.2 for adding "use warnings".
I have opened bug 2505 for this.
Regards,
Galen
--
Galen
t mistaken, we 'use strict' already.
We do, but this practice is not mentioned in coding guidelines. I
have updated the wiki to promote 'use strict' and 'use warnings':
http://wiki.koha.org/doku.php?id=en:development:codingguidelines#perl
Regards,
Galen
--
Galen Ch
ingness to take this on, and also for providing an
outline of your plan. I support your candidacy.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel
maintainer can push directly to the 3.0.x
branch.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
[EMAIL
he 3.0.x branch.
As 3.1 and 3.0.x diverge, it may necessary at times for the RMaint to
request separate patches for both 3.0 and 3.1. However, I hope that
will be necessary only for the most important bugfixes and security
updates..
Regards,
Galen
--
Galen Charlton
VP, Research & Development,
user documentation in as many languages as possible.
* Maintaining user documentation on the various project websites,
including wiki.koha.org, kohadocs.org, and the forthcoming Plone
version of www.koha.org.
Any volunteers? Comments on the list of responsibilities?
Regards,
Galen
--
Galen Charlt
Hi,
On Tue, Aug 12, 2008 at 9:32 AM, Henri-Damien LAURENT
<[EMAIL PROTECTED]> wrote:
> Galen Charlton a écrit :
>> Joshua may be a volunteer; I'll let him toss his hat in the ring
>> directly if he chooses.
>
> Would Joshua be volunteer both for QA and Release M
e requested versus when they are available to fill hold requests.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
Koha-devel@lists.koha.org
put on the hold shelf or
transfer to other branches.
This mechanism will also be used to minimize the number of transfers
by allocating items located at a branch to fill requests for that same
branch.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p:
Hi,
On Thu, Aug 14, 2008 at 4:00 PM, Galen Charlton
<[EMAIL PROTECTED]> wrote:
> For 3.2, LibLime proposes to add a feature to target specific items to
> fill hold requests. This targeting, which would be done in
> conjunction with use of the holds queue batch job
> (build_h
*lot* of the HTML templates invoke JavaScript
libraries in that fashion, so if the packaging rules allowing setting
up symlinks to the canonical locations of the libraries, that may be
simplest.
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
option to restrict the branches a staff operator is allowed to
set circ rules for
If you decide to apply the patches and test, please note that there
are a couple schema changes, which for now can be installed by running
installer/data/mysqlupdatedb_sysgroups.pl.
Regards,
Galen
--
Galen Charlton
VP
ght translation ?
> (which limit then ?)
I'd prefer packaging as many translations as possible, on the theory
that if there's enough interest for a particular language, an
incomplete translation will eventually be improved.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, Li
Hi,
On Wed, Aug 27, 2008 at 8:41 AM, Rick Welykochy <[EMAIL PROTECTED]> wrote:
> Hey, now that's an idea! pyKoha! Any takers?
Heh. I'm surprised that nobody (that I'm aware of) has started a
Python-based ILS yet.
Regards,
Galen
--
Galen Charlton
VP, Research &
ademic, etc. If
there are any serious objections to this, speak now.
Therefore, I propose to accept Owen's patch. For the convenience of
the translators, I can also prepare a patch to update the existing PO
files.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAI
your case, does it make a
difference whether the search string has a space or not? Are you able
to subscribe using another feed reader?
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
__
bug mode) by warn statements that end up in the error log.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
later.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Hi,
On Wed, Sep 3, 2008 at 3:36 AM, Zeno Tajoli <[EMAIL PROTECTED]> wrote:
> get checkout my3.0.x
You may want to do
git checkout -b my3.0.x
in order to create a new 3.0 working branch, unless my3.0.x exists already.
Regards,
Galen
--
Galen Charlton
VP, Research & Develop
ill finish sending out LibLime's RFCs
and propose a roadmap by next Thursday.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
Koha-devel mailing list
Hi,
On Thu, Sep 4, 2008 at 3:31 PM, Chris Cormack <[EMAIL PROTECTED]>wrote:
> On Fri, Sep 5, 2008 at 4:04 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
> > Galen Charlton a écrit :
> >> Good idea. I suggest Thursday, 11 September or Friday, 12 September
> >
:
Release Manager: Galen Charlton, LibLime
Translation Manager: Chris Cormack, Catalyst
Documentation Manager: Nicole Engard, LibLime,
2. Decide on the release maintainer for Koha 3.0 The two candidates are
currently Joshua Ferraro (LibLime) and Henri-Damien Laurent (BibLibre).
3. Discuss options for
branch (3.0.x) ?
Yes.
> Untin now, no patch was commited for the stable branch, as I see.
>
> Is it so ?
Yes.
Regards,
Galen
--
Galen Charlton
VP, Research & Development, LibLime
[EMAIL PROTECTED]
p: 1-888-564-2457 x709
skype: gmcharlt
___
1 - 100 of 310 matches
Mail list logo