Hello,
I have just posted a related question, but to keep it simpler I post a
new message for this one.
I wanted to show the field 17$a in the "normal" view of a biblio. I
think I could do something like searching in the $record->fields
structure until I found the desired 17$a field and then
Hello,
We are using Koha 3.00.04.
In the intranet "normal" view of a biblio we needed to differentiate the
additional authors whether they are personal, corporate or conference
ones (Marc 700, 710 or 711). To achieve this I had to include this
information in the structure returned by the method
On 10 February 2010 11:17, Darrell Ulm wrote:
> Hello All,
>
> The following is not a positive or negative observation of the Koha 3.4
> release
> as I think the goals set for Koha 3.4 are obviously very positive.
>
> I am just stating the obvious technical implications to any who may not know:
>
Hello All,
The following is not a positive or negative observation of the Koha 3.4 release
as I think the goals set for Koha 3.4 are obviously very positive.
I am just stating the obvious technical implications to any who may not know:
I just wanted to state that with the goals of the 3.4 prop
2010/2/9 MJ Ray
> Darrell Ulm
> > If a button were made to set a cookie on the Opac labeled "Kid's OPAC"
> then
> > feasibly the CSS included could be switched on the fly with the user
> controlled
> > switch.
> >
> > This would allow all the existing code for the OPAC to work by just
> setting
On 09/02/10 15:47, Paul Poulain wrote:
> Galen Charlton a écrit :
>> Hi,
>>
>> The current list of default assignees for bug categories is here:
>>
>> http://wiki.koha.org/doku.php?id=en:development:bug_default_assignees
>>
> Note to all : i've nothing against "loosing" default assignment: I don't
Galen Charlton a écrit :
> Hi,
>
> The current list of default assignees for bug categories is here:
>
> http://wiki.koha.org/doku.php?id=en:development:bug_default_assignees
>
Note to all : i've nothing against "loosing" default assignment: I don't
have time anymore to be a good bug wrangler.
I'll step up the plate and be added to the default CC list for the following
areas:
Cataloging
MARC Authority data support
MARC Bibliographic data support
MARC Bibliographic record staging/import
They all seem pretty related, and I've had to spend a lot of time face-down in
MARC during my insti
On Tue, Feb 9, 2010 at 8:12 AM, Chris Nighswonger
wrote:
> On Tue, Feb 9, 2010 at 7:40 AM, Galen Charlton wrote:
>>By the time of
>> the next general meeting (3 March 2010 at 19:00 UTC+0), please reply
>> to this thread and signal if:
>>
>> * you want to be or remain as assignee for a component
>
I would be willing to take "Circulation", "Hold requests", and
"Patrons". Of the list of components still in your name, these are the
3 I feel most experienced with.
Kyle
http://www.kylehall.info
Information Technology
Crawford County Federated Library System ( http://www.ccfls.org )
On Tue,
Hi to all,
this is a bug that need a preliminary discussion.
'popularity' is a way to sort bibliographic results of a search.
In the Zebra setup this sort is based on a value, the value of all loans done
with all items/copies of a specific bibliographic record.
In NoZebra setup the valuse is cal
> * you want to be or remain as assignee for a component
I'm happy to remain assigned to:
Browser compatibility
Online Public Access Catalog (patron-facing interface)
Templates
-- Owen
--
Web Developer
Athens County Public Libraries
http://www.myacpl.org
__
Darrell Ulm
> If a button were made to set a cookie on the Opac labeled "Kid's OPAC" then
> feasibly the CSS included could be switched on the fly with the user
> controlled
> switch.
>
> This would allow all the existing code for the OPAC to work by just setting
> up a
> new CSS (for Kid's fo
Darrell Ulm
> I would like to add a cookie to Koha to add sound (it is working on
> my test Koha instance). Should I just set the cookie or does the
> Koha source have an existing javascript (or otherwise) function to
> do this?
Does it have to be its own cookie, or could it be added to the
sessi
Hi,
The full log of the meeting today can be found at
http://stats.workbuffer.org/irclog/koha/2010-02-09#i_387991.
Significant news and updates:
* Koha 3.2 beta will be targeted for release around 1 March. There is
a bug squashing session tomorrow all day, all time zones in the #koha
IRC channel
On Tue, Feb 9, 2010 at 7:40 AM, Galen Charlton wrote:
>By the time of
> the next general meeting (3 March 2010 at 19:00 UTC+0), please reply
> to this thread and signal if:
>
> * you want to be or remain as assignee for a component
> * you no longer want to be an assignee
> * you want to be added
Hi,
The next general IRC meeting will be held on Wednesday, 3 March 2010
at 19:00 UTC+0 in the #koha IRC channel (server irc.katipo.co.nz).
The agenda is currently"
1. Update on Roadmap to 3.2.
2. Update on Koha 3.0 Roadmap.
3. Follow-up on actions from General IRC Meeting, 9 February 2010.
4. Di
Hi,
During the general IRC meeting today, we decided to hold the vote for
the 3.4 Translation Manager tomorrow, 10 February 2010, at 19:00 UTC+0
on the #koha IRC channel. Two people have expressed interest,
Frédéric Demians and Brendan Gallagher, but we're awaiting a proposal
from Brendan.
Brend
Hi,
The current list of default assignees for bug categories is here:
http://wiki.koha.org/doku.php?id=en:development:bug_default_assignees
I am issuing a call for module experts to volunteer to be default
assignees, and for existing assignees to confirm their willingness and
availability to inv
19 matches
Mail list logo
