Re: [Koha-devel] Authentication field on borrower.

> I'm trying to figure out where the field authentication of the borrowers > table is used? I don't see borrowers.authentication in the schema: http://schema.koha-community.org/tables/borrowers.html -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org _

Re: [Koha-devel] Authentication field on borrower.

Then I have a legacy application customization that the upgrade22to30.pl didn't find out. Is there any possible way to add different authentication per user? Say use LDAP on one user, DBI on another? Thanks for the help! Regards On Wed, Sep 21, 2016 at 8:54 AM, Owen Leonard wrote: > > I'm try

Re: [Koha-devel] To React or not to React

David Cook schrieb am 21.09.2016 > The updated licence isn’t without controversy: > > https://discuss.reactjs.org/t/legal-department-did-not-allow-use-of-react/3309/4 > > That said, I think the issue is that Facebook

[Koha-devel] Customize debian scripts.

Hi, I'm looking at the Debian scripts and I'm finding out that all the paths are hard coded. This is not really useful when installing the development version. Is worthy to change them to relatives paths? Or have it to take the enviroment variable to build the paths? Or is a waste of time? Regar

Re: [Koha-devel] To React or not to React

Yes, I've done as thorough a review on the issue as I've been able to. Basically, Koha is never in any danger. But if say, *I* sued Facebook, I could possibly lose my patent grants and wouldn't be able to distribute software that uses React. Everyone else would continue on using Koha as usual. Many

Re: [Koha-devel] To React or not to React

Yes, I'll definitely need to make it translatable! I'll do that along with building out the backend to make it a complete fully functioning feature. Kyle

Re: [Koha-devel] To React or not to React

You are looking at a POC, that doesn't have the endpoints it need to hit against, so it has some sample values in plain english. But a real implementation would of course use the usual _("blah") stuff, and have the strings defined in a translatable file/directory. El mar., 20 sept. 2016 a las 21:1

Re: [Koha-devel] To React or not to React

El mié., 21 sept. 2016 a las 11:17, Kyle Hall () escribió: > Yes, I've done as thorough a review on the issue as I've been able to. > Basically, Koha is never in any danger. But if say, *I* sued Facebook, I > could possibly lose my patent grants and wouldn't be able to distribute > software that u

Re: [Koha-devel] Customize debian scripts.

Rodrigo, take a look at koha-gitify, or even to kohadevbox. El mié., 21 sept. 2016 a las 10:19, Rodrigo Santellan () escribió: > Hi, > > I'm looking at the Debian scripts and I'm finding out that all the paths > are hard coded. This is not really useful when installing the development > version.

Re: [Koha-devel] Authentication field on borrower.

There's LDAP with fallback to local user. That's the default behaviour. El mié., 21 sept. 2016 a las 9:04, Rodrigo Santellan () escribió: > Then I have a legacy application customization that the upgrade22to30.pl > didn't find out. > > Is there any possible way to add different authentication per

Re: [Koha-devel] To React or not to React

On Tue, Sep 20, 2016 at 6:29 PM, David Cook wrote: > I think it differs in that a search engine and a RESTful API adds core > functionality. Without them, we can’t really search or expose services. We > already have a JS UI toolkit, which seems to be working fine. > Yes, jQuery UI does work just

Re: [Koha-devel] To React or not to React

Mirko, you would have no worries. The license basically means that an entity that sues facebook may lose the patent grants facebook has. So if I sue Facebook, I might lose my patent grant to distribute React based software, but you would not be affected in any way. The license cannot be revoked. K

Re: [Koha-devel] To React or not to React

At 02:14 PM 9/21/2016 +0200, Mirko Tietgen wrote: David Cook schrieb am 21.09.2016 > The updated licence isn’t without controversy: > > https://discuss.reactjs.org/t/legal-department-did-not-allow-use-of-react/

Re: [Koha-devel] To React or not to React

Paul, that's not how it works. As I wrote earlier, if *I* sue Facebook I could potentially lose my right to distribute software using React, but you would be unaffected. Kyle

Re: [Koha-devel] To React or not to React

I suppose that is the most prudent thing to do Tomas. We do have a access to a lawyer so I'll talk to her and let you know her thoughts! Kyle h

Re: [Koha-devel] To React or not to React

I'm still going to run this past our lawyer, but I think it's even less of a concern then before. Not only would I need to sue Facebook, I would need to sue Facebook *for infringing on my own patents*. Kyle

Re: [Koha-devel] To React or not to React

At 08:34 AM 9/21/2016 -0600, Kyle Hall wrote: Paul, that's not how it works. As I wrote earlier, if *I* sue Facebook I could potentially lose my right to distribute software using React, but you would be unaffected. Kyle -- not wanting to flog a dead horse (and as I wrote IANAL), but Koha is

Re: [Koha-devel] To React or not to React

Hi there! I don't know how I intercepted this email since I never read my email, but... "In all seriousness, I just want Koha to be the fastest, slickest most useful ILS in the world. I want it to be an absolute pleasure to use. And I think this is a necessary milestone to achieving that goal."

Re: [Koha-devel] To React or not to React

Kyle Hall schrieb am 21.09.2016 > I suppose that is the most prudent thing to do Tomas. We do have a access > to a lawyer so I'll talk to her and let you know her thoughts! Excellent, thank you Kyle. And to Tomas for bringing lawyers into the discussion. In the end nobody cares what we thought was

Re: [Koha-devel] Customize debian scripts.

I'm looking to kohadevbox for how to use that for my scripts. On Wed, Sep 21, 2016 at 11:23 AM, Tomas Cohen Arazi wrote: > Rodrigo, take a look at koha-gitify, or even to kohadevbox. > > El mié., 21 sept. 2016 a las 10:19, Rodrigo Santellan (< > rsantel...@gmail.com>) escribió: > >> Hi, >> >> I'

Re: [Koha-devel] Customize debian scripts.

Tomas, just to clarify, even on a gitified install using koha-gitify, the koha-* scripts are still the version from the package install, and *not* the versions that would be in the git install, correct? Kyle

Re: [Koha-devel] To React or not to React

With some snipping, please see interspersed text below At 03:03 PM 9/21/2016 +, Kivilahti Olli-Antti wrote: Hi there! I don't know how I intercepted this email since I never read my email, but... Well, you've been subscribed for many years, have occasionally written, but I would agree tha

Re: [Koha-devel] To React or not to React

Tomas: Fair enough about it being a POC so not showing how to translate it. I was just concerned that it would make translation more difficult, but it looks like that concern was baseless : ). Kyle: Well, I think I’m mostly persuaded. That said, I think it’s a shame that Koha has no prio

[Koha-devel] Improving the API for record imports

Hi all, I want to improve the API(s) for importing (bibliographic) records. But I'm not 100% sure how to go about what criteria to use to gauge "improvement". Here are some ideas: * I think the REST API offers up one obvious addition and that's DELETE. It would be great to delet