Agreed, +1. I could see a situation where a library takes a new picture
every year, and Koha just uses the newest one as the default.
Kyle
http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federa
+1 from me to.. initially I couldn't see a reason for multiple pictures,
but then it occured to me that a history could well be useful in some
instances.
Martin Renvoize
Software Engineer, PTFS Europe Ltd
Content Management and Library Solutions
Skype:
Landline: 0203 286 8685
Mobile: 07725985636
Greetings,
> Should I consider the use case where the library/user
> might want to attach more than one picture to a patron
> and choose a default?
Yes. This will allow for flexibility in the future.
GPML,
Mark Tompsett___
Koha-devel mailing list
Koha-
On Jul 15, 2014 3:39 PM, "Chris Cormack" wrote:
>
>
> I think that building it so more than one can be saved (in the future) is
a good idea.
>
+1
Chris N
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cg
On 16/07/2014 6:02 am, "Tomas Cohen Arazi" wrote:
>
> Hi, for bug 12578 [1] I was thinking of adding a 'timestamp' field to the
'patronimages' table. And got into the task of rewriting the CRUD methods
for patron pictures into the Koha namespace, as an excercise for using DBIx
in a real life examp
Hi, for bug 12578 [1] I was thinking of adding a 'timestamp' field to the
'patronimages' table. And got into the task of rewriting the CRUD methods
for patron pictures into the Koha namespace, as an excercise for using DBIx
in a real life example.
Should I consider the use case where the library/u
