Hi,
In this mail, I want to share with you our situation, our problems, and
our ideas.
You'll be probably surprised by this mail. Please consider it's a good
news. It's not a threat - not my cup of tea (frenchism suspected) - .
But I think things must be done this way, so I share it with you, and
Hi Paul
There is an IRC meeting today, in 3 hours time .. but this topic is
much to big for that, so I propose we leave it off the agenda for
that, and let people think about the ideas raised for a bit, and then
do replies.
Speaking for myself nothing in the email strikes me as bad news, I do
Le 02/06/2010 10:25, Chris Cormack a écrit :
Hi Paul
There is an IRC meeting today, in 3 hours time .. but this topic is
much to big for that, so I propose we leave it off the agenda for
that, and let people think about the ideas raised for a bit, and then
do replies.
Hi chris,
this mail
There are a few possibilities I see here. One is to create an export
tool. Some MARC format would be good for the biblio and copy
information, but there would have to be some framework, similar to that
which is in the works for imports, to map koha fields to MARC fields.
The system prefered MARC
Le 02/06/2010 12:22, Reed Wade a écrit :
Any reason not to move to a 4 week release cycle? With alternate ones
getting better testing.
It would mean automating a lot of things -- but doable and worth it in any
case.
^^The main reason is this one.
and no doubt that it IS BOTH doable AND
Marc Chantreux marc.chantr...@biblibre.com
On Wed, Jun 02, 2010 at 12:18:50PM +1000, Rick Welykochy wrote:
1. CSV, directly importable into spreadsheet and database programmes
2. XML, easily handled by MySQL, more transparent than CSV
I would choose YAML because
- it can store tree (as
See : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3178
this patch was never complete which explains why I don't have the new
preference.
On Tue, Jun 1, 2010 at 3:55 PM, Nicole Engard neng...@gmail.com wrote:
On Tue, Jun 1, 2010 at 3:49 PM, LAURENT Henri-Damien
