reindexing data.
But it is a desirable feature.
--
Henri-Damien LAURENT
2009/3/4 Joe Atzberger
> Should be doable.
> --joe
>
> On Mar 3, 2009 11:04 PM, "Eric Bégin" wrote:
>
> Hi,
>
> In the authority search, is there a way to sort the result of the
> auth
u have a dev install, all you have to do is a
git fetch
git rebase remotes/origin/3.0.x 3.00.01-stable_update
and then login to staff interface and some needed system preferences will be
added.
--
Henri-Damien LAURENT
BibLibre SARL
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-do
Joe Atzberger a écrit :
> Nahuel's recent patch for "no title" reminded me of something. I
> don't think there is any problem with the patch, but I wanted to bring
> up the use of TMPL_VAR DEFAULT attribute, like:
>
>
>
> I like the way that looks. But am I remembering correctly that there
> is
Zeno Tajoli a écrit :
> Hi to all,
>
> At 22.55 24/11/2008, Henri-Damien LAURENT wrote:
>> Hi,
>> I am glad to announce String Freeze for 3.0.1.
>
> we are starting to update our transaltion with the present
> version of 3.0.x
> The git web repository is
> http
Vincent Danjean a écrit :
> Frederic Demians wrote:
>
And if we know where the XML parser is called (directly or indirectly),
we can set in the koha file(s) the global variable
>> $XML::SAX::ParserPackage = "XML::LibXML::SAX";
>>
in order to forc
.
Let me know if you encounter any problem.
Hopefully, christmas will bring us 3.0.1 release. ;)
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
BI, which is still 8 times faster (according to
the tests http://code.google.com/p/rose/wiki/RDBOBenchmarksWithDBI )
than DBIC for circulation which is a critical part in Koha ?
I donot want to slow down things. But I want to be sure that what we
choose is the best alte
mallikarjun dora a écrit :
> Greeting
>
>
> can u tell me what will be the new feature going to add in new version
> of koha.
No brand new feature in 3.0.1.
It will only contain bug fixes.
Nevertheless, some new system preferences (RenewallAllowOverride) are
being ported from 3.2 to 3.0.
Hopes tha
Hi,
I am writing to announce a little delay in 3.0.1
I propose to freeze patches on November, 21st.
Then let 1 month for translations, if any one is OK.
And 3.0.1 would be hopefully out on the 21st december.
Sorry for cross posting.
--
Henri-Damien LAURENT
Chris Cormack a écrit :
> Hi all
>
> Just wanted to bring to the community's attention the fact that
> Rosalie Blake (the Head librarian at Horowhenua Library trust, and a
> massive reason why Koha exists) was just awarded a lianza fellowship.
>
> Lianza is the Library and Information association o
Hi andrew.
Thanks for your hard work.
I will try and test this.
I hope that Marc will have some time to this too.
let's stay tuned.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo
.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Joe Atzberger a écrit :
> Marc --
>
I think you meant Marc++ ;)
> Looks cool. We have been talking about consolidating all the
> repetitive table operations in similar ways. I have an experimental
> implementation as "C4::Table" that also tries to provide baseline
> SELECT, UPDATE and eventually
to do it.
gitosis was meant to be installed in order to allow me to push directly
on that branch.
At the moment, maintenance is stalled. And I donot think it is a good thing.
Is there a way we could solve this situation ?
Friendly.
--
Henri-Damien LAURENT
8, it will probably finish at may 2009
> The instrument used will be OpenOfficeOrg Calc.
>
You may also want to use that tool :
http://schemaspy.sourceforge.net/
Maybe adding some descriptions to fields.
Thanks a lot.
Hopes that helps.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
erator was rather a burden than a good thing.
I donot think that using $_ will really ease the process.
Maybe only with maps and greps, but in for/foreach/while loops, I donot
see any good in this.
My 2 cts.
--
Henri-Damien LAURENT
___
Koha-d
Jesse Weaver a écrit :
> I have a small favor to ask of any french-speaker on the list; could
> you translate the following syspref description?
>
> "If ON, allows renewal limits to be overridden on the circulation screen"
>
Si activé, permet de redéfinir les limites de renouvellement dans les
rè
gt;
This seems to be owed to the fact that you donot have any database
structure in your database
consider loading /installer/data/mysql/kohastructure.sql in your koha
database.
For zebra problem, feel free to mail your edited koha-conf.xml.
We cannot guess where "include" is
Joe Atzberger a écrit :
>
> My question is: Which is the problem? Should I change the
> DBD::mysql configuration to enable utf-8?
>
> Your mysqld setup appears correct. I am curious about your desktop OS
> and language settings.
>
> Are you using Windows? What keyboard do you have setup
Rick Welykochy a écrit :
> Henri-Damien LAURENT wrote:
>
>> But paul also spoke about zebra queries and they are not logged nor
>> saved into the database at the moment
>> which could be good for storing user queries history but is an other
>> point.
>
>
for storing user queries history but is an other point.
And they are not mysql, and sometimes needs to be viewed in order to
find what the problem is.
Friendly.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
that you expect kohaversion to be a minimum requirement and not ==). But
then it would require a good way to import them into the base.
By the way, is that way to note SQL variable a standard that exists. Or
is there already one that exists somewhere ?
--
Henri-Damien LAURENT
Joe Atzberger a écrit :
> Vincent --
>
> Thanks for your work on this. I think I can answer a couple of your
> questions.
>
> Do you think that these duplicate files in language directory are here
> by intend (ie you think that one day JQuery, TinyMCE, YUI, ... will be
> different, d
rog/es/modules/admin/systempreferences.tmpl:2
> #, fuzzy
> msgid "System Preferences › Data Added"
> msgstr "Administración de Preferencias del Sistema"
>
>
> Intranet BBVA Infoblue › Administration › System Preferences › Modify system preference ''Añ
g should be discussed along.
And Translation Manager and Doc manager should work hands in hands.
> Would you consider tackling that type of
> problems too (inconsistencies in the use of certain terms, etc.)? Or
> do you think it's too far from what "documentation" should be
m
Galen Charlton a écrit :
> Hi,
>
> On Tue, Aug 12, 2008 at 4:19 AM, Henri-Damien LAURENT
> <[EMAIL PROTECTED]> wrote:
>
>> As far as we (BibLibre) are concerned, even though it was talked about
>> a while back, we are in fact not candidate for the QA mana
r 3.0,
Translation) should have ssh access to the git repository via a key so
that they can do what their position requires them to do, with
sign-off of their commits so that RM can be informed in real time of
what has been done.
--
Henri-Damien LAUR
t is safe.
> Is there any field (tag / subfield) in UNIMARC / MARC 21 for storing
> information about who created and/or "last modified" a bibliographic
> record?
>
/me doesnot know for USMARC Sorry.
But as far as UNIMARC is concerned, this (Who/When/Where) information
has sometimes been stored in 801 tag or 809 if you want to use a local tag.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
Josh++,
It also could be part of the SQL files we could propose at install time,
imho, click to select a report, with a txt file to describe it, maybe
with a sample.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
if i don't mind.)
But then there would still be the problem of template separation.
This raises also the problem of features : for instance, basket is not
provided at intranet, but is really useful also for staff members.
Should we change and unify Koha's scripts and naming ?
Should this
Galen Charlton a écrit :
> 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
>
yes it is .
It is a three dimensional type of authorised_values with crossing.
you have an insight of what a MACLE is here
:http://frantiq.mom.fr/html/macles/macles.html
It used well structured authorised_values.
and adds them to biblios.
HTH.
--
Henri-Damien LAURENT
__
.
Imho, this type of things should eventually be possible via a
virtualshelf, just need to be quite general on what a virtual shelf
contains and display actions depending on elements type (It would just
need to add a type of element to virtualshelves.)
But maybe i am daydreaming.
--
Henri-Damien
Chris Nighswonger a écrit :
> Can anyone comment on whether serials/serials-recieve.pl is being used?
>
> If not, any objections to its removal?
>
> Kind Regards,
No objection.
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/ma
ses
which could be sent.
process_report table;
processid; timestamplaunched; datefinished;status;results
This may allow more portability on Windows.
And would be much more in a OOP point of view, which is to my mind more
scalable and sustainable.
With
he
authoritative ones.
So would it be for simple result display, we silently use XML::LibXML
my 2 cts
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
modules. If not, then error 500 would come out.
I havenot investigated. But maybe we should be aware of the fact that
adding a new dependency, should be done quite conciously and cautiously.
And if dependency is not require, try and test on a fresh build bot so
that it is proven that it is not gen
a HUGE work, maybe highly valuable but I think that
having too many objects without good documentation and entry points
would really be a waste of time and strength.
Let's have this release out and document features and functions.
Then time for OO Programming will come at his own pace.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
uded in koha3-beta3
Looks OK for me.
But before committing, please test how good is interaction with
IndependantBranches system preference.
Will this only be allowed with Galen subpermission system or for any
Koha setting ?
Cheers.
--
Henri-Damien LAURENT
_
reciated in that purpose too.
(We could also try and use virtualization to install and maybe automate
installs on different Linux flavours later.)
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
-- NOT OK
>
> Running make test
>
> Can't test without successful make
>
> Running make install
>
> make had returned bad status, install seems impossible
>
>
>
> cpan> DBD::mysql
>
>
>
> Any ideas?
>
>
>
> Thanks,
>
>
different informations and both can be interesting ?
We should choose one way to display and stick to it and allow the same
functions OR have only one page to edit circulation information and fines.
What should we do about that ?
--
Henri-Damien LAURENT
t;>
>> "INSTID:12345, MAJOR:Physics, ADDLOGIN:abcdef/passwd"
>>
>> The new feature would be guarded by a syspref - if the preference is
>> off, no sign of the additional IDs would display in the Administration
>> menu, the patron edito
some ways in order to improve multimarc support.
--
Henri-Damien LAURENT
BibLibre SARL
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
tel : +33 4 67 65 75 50
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koh
orcing conventions is
important, all the more than we are providing 2 MARC standards and may
be willing to open Koha to other standards. For instance, it could
prevent us to use in our code $record->title() for a MARC record, since
this is not MARC-flavo
, 1st and 3rd day of month, depending on frequency.
Irregularities would be optional and display in a window the expected
issues periods based on frequency and one could check the periods an
issue is not published.
--
Henri-Damien LAURENT
___
Koha
n
ODLIS or any dictionary. I favour ODLIS that seems to be good, but I
think anyway sometimes we may have to make choices between two
synonyms.), updating and keeping translation up will be a nightmare.
I am sure his point was : let us not spread out forces, but let us join
and disam
But would require QUITE changes in our templates and codes.
And I have a big trouble :
Who, when, how will be maintained the list of all the permissions ?
My proposition is that mysql/en/permissions.sql should be authoritative.
But it should be accounted that it HAS to be translated.
And somehow it
hen passing it via a sed command over the po file...
--
Henri-Damien LAURENT
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
it is in a TMPL_ELSE which is not parsed because
condition is right.
But maybe it is because of bad habbits.
Hope that helps.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
[EMAIL PROTECTED]
http://list
Ignacio Javier a écrit :
> Hi all:
>
Hi alone
> I'm trying to undo changes I've made on a lot (70) files in my kohaclone
> directory, so trash them and revert all since the last commit I've made to
> the origin branch, anyone has idea how using a git command or commands
> sequence?
>
> I've trie
Now Move from nonGnu.org to Lists.koha.org is complete.
--
Henri-Damien LAURENT
___
Koha-devel mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listinfo/koha-devel
___
Koha-devel mailing
--- Begin Message ---
I have to add a Library name to the Main logon screen of KOHA. (2.2.9)
I am not sure what is the standard way of doing it.
Can anyone please help?___
Koha-devel mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listin
--- Begin Message ---
[EMAIL PROTECTED] wrote:
I am looking at doing this to load some records into a "test" setup, but was wondering if
there is a document that tells me what all the "flags" for running this option are, and
how to run this .pl file.
Run the script without any arguments, e.
54 matches
Mail list logo
