> 1: the item-level_itypes system preference be removed.
> 2: biblioitems.itemtype be renamed to biblioitems.default_itemtype
> 3: items.itype be renamed to items.itemtype
> 4: all circulation parameters will be determined by items.itemtype.
> 5: AddItem and ModItem will automatically fill items
On Thu, Oct 9, 2008 at 2:57 PM, Ryan Higgins <[EMAIL PROTECTED]>wrote:
>
> [ this text also available at:
>
> http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_item_level_itemtypes]
>
> RFC: Koha 3.2
>
> Mandate item-level circulation rules.
>
> Currently we use the system preference i
[ this text also available at:
http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_item_level_itemtypes]
RFC: Koha 3.2
Mandate item-level circulation rules.
Currently we use the system preference item-level_itypes to indicate whether
Koha
should use the itemtype stored at the bibliogra
I was reading over the RFC for authority control enhancements in 3.2,
and they look like great changes that we would love to see. I do have
a quick question though. Will there be any provision for preserving
local changes in an authority record when merging the imports. Maybe
something as simple
> After reading the code, only one of the three e-mail adresses asked in
> this form is saved :
> "
> elsif ($newdata{email} =~ /[EMAIL PROTECTED]/) {
> $emailaddr = $newdata{email}
> }
> elsif ($newdata{emailpro} =~ /[EMAIL PROTECTED]/) {
> $emailaddr = $newdata{emailpro}
> }
> elsif ($newdata
Hi,
An user of intranet ask me why there is two "E-mail (home):" input
in /koha/members/memberentry.pl.
After reading the code, only one of the three e-mail adresses asked in
this form is saved :
"
elsif ($newdata{email} =~ /[EMAIL PROTECTED]/) {
$emailaddr = $newdata{email}
}
elsif ($newdata{
