- Koha-devel - lists.koha-community.org

Re: [Koha-devel] Adding Wysiwyg to (HTML) System Preferences
by David Cook 20 Jan '14

20 Jan '14

Great idea, Eric! I've opened bug 11584 for the system preferences and bug 11583 for the notices/letters. At the moment, we're using TinyMCE in other parts of Koha, so I figure it's useful to provide a consistent HTML editor across the board. Martin, I do like the idea of syntax highlighting, indenting, and linting though! MJ: As far as I know, it shouldn't have any problem preserving any hand-coded HTML, but I'll keep that in mind. Perhaps I'll write some bad HTML and see what it does with that. I'm glad to hear positive support! I'll get working on this right away. -David -----Original Message----- Date: Fri, 17 Jan 2014 06:26:15 -0500 From: Eric B?gin <eric.begin(a)inLibro.com> To: Martin Renvoize <martin.renvoize(a)ptfs-europe.com>, Koha Devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Adding Wysiwyg to (HTML) System Preferences Message-ID: <52D91357.1050301(a)inLibro.com> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" I'm thinking about this type of addition for a long time so I'm all for it ! Couldn't we also use a WYSIWYG for editing notifications (when HTML is selected). Cheers, Eric B?gin Solutions inLibro inc. On 2014-01-17 06:14, Martin Renvoize wrote: > I've been thinking of doing something like this for some time, so > would love to see it happen. (and I'm sure our customers would love it) > > I was of two minds whether to implement TinyMCE as wysiwyg, or one of > the code editors out there to do syntax highlighting, indenting and > linting for all code type blocks (css, html, yaml etc), but I think > for your average user the wysiwyg approach is the right one. > > Would be happy to test a patch. > > Martin > > Martin Renvoize > Software Engineer, PTFS Europe Ltd > Content Management and Library Solutions > Skype: > Landline: 0203 286 8685 > Mobile: 07725985636 > > http://www.ptfs-europe.com > > > On 17 January 2014 11:04, MJ Ray <mjr(a)phonecoop.coop > <mailto:mjr@phonecoop.coop>> wrote: > > David Cook wrote: > > What would folks think about adding the tinymce wysiwyg to some > of the > > system preferences that deal with HTML? > > I think it would probably be a useful feature to many libraries and > tinymce seems like the best of the current rather weak bunch. > > A system preference to control it seems like a good thing. > > If you can make tinymce abort if it finds handcoded html that it can't > preserve (I don't know if this is possible), then that would be great. > > Hope that helps, > -- > MJ Ray (slef), member of www.software.coop > <http://www.software.coop>, a for-more-than-profit co-op > http://koha-community.org supporter, web and library systems > developer. > In My Opinion Only: see http://mjr.towers.org.uk/email.html > Available for hire (including development) at > http://www.software.coop/ > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > <mailto:Koha-devel@lists.koha-community.org> > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ ******************************************

2 2

Z39.50 searching by Publisher
by Andrea Furin 20 Jan '14

20 Jan '14

Is it possible to make a searching in Z39.50 mask also by publisher? in file z3950_search.tt I've add a: <li><label for="biblioitems.publishercode">Publisher: </label> <input type="text" id="biblioitems.publishercode" name="biblioitems.publishercode" value="[% biblioitems.publishercode %]" /></li> so the z39.50 mask has a new field, but the results mask doesn't filter with it --

1 0

Hackfest in Marseille, 2014
by Paul Poulain 20 Jan '14

20 Jan '14

Hello Koha & koha-devel mailing lists. I'm happy and proud to announce the 2014 edition of "hackfest in Marseille": http://www.biblibre.com/en/blog/hackfest-marseille-2014 ! Registrations are now open ! just drop me an email ! ( already 12 registrations -not including BibLibre staff- ) -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

1 0

Re: [Koha-devel] Automatic renewal feature
by Holger Meissner 20 Jan '14

20 Jan '14

Galen Charlton wrote: > Yes. Here is how I suggest doing it: > > - add an auto_renew flag to both issuingrules and issues > - when a loan is made, issues.auto_renew is set to the value of issuingrules.auto_renew > from the loan rule that was applied. > - the cronjob checks issues.auto_renew -- in other words, it doesn't go back and check > issuingrules again, it just goes by the value set on the loan itself. Very well. Additionally I suppose to add norenewalbefore to issuingrules. I'm not sure what it should be called? It's about when to renew, X days or hours before due date. This would be checked by CanBookBeRenewed and could be used to control the cronjob as well as solve bug 7413. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7413 May I assign 7413 to myself, or just write a patch without assignment? Updated the RFC: http://wiki.koha-community.org/wiki/Automatic_renewal_RFC Regards Holger

2 1

Re: [Koha-devel] [Koha] VERY URGENT: automatically redirection to searching page
by Owen Leonard 20 Jan '14

20 Jan '14

This is caused by not having updated your templates after the upgrade: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11567 > On Jan 20, 2014, at 7:09 AM, Evan Mungai Njoroge <evan.njoroge(a)gmail.com> wrote: > > This is happening after I updated koha to 3.14.1 on one instance & 3.15 on > another instance. Might be a bug but am sure somebody will pick this up; I > did refresh on the browser & all went well; as for the 3.14.1 instance I > switched browsers, from chrome to Mozilla. > > > > EVAN > NJOROGE *•*+254721375981 *•*+254721375981 *•*about.me/uhusiano *•* > * "Facilitating access to African digital content" * > > > > > On Mon, Jan 20, 2014 at 2:26 PM, Andrea Furin <andrea.furin(a)slacky.it>wrote: > >> After upgrading to koha 3.14.01.1-1 >> >> If I try to add a copy typing something from: >> >> http://localhost:8282/cgi-bin/koha/cataloguing/additem.pl?biblionumber=14#a… >> >> browser goes to advanced search page: >> http://localhost:8282/cgi-bin/koha/catalogue/search.pl >> >> -- >> __________________________________

1 0

VERY URGENT: automatically redirection to searching page
by Andrea Furin 20 Jan '14

20 Jan '14

After upgrading to koha 3.14.01.1-1 If I try to add a copy typing something from: http://localhost:8282/cgi-bin/koha/cataloguing/additem.pl?biblionumber=14#a… browser goes to advanced search page: http://localhost:8282/cgi-bin/koha/catalogue/search.pl --

1 0

Re: [Koha-devel] Automatic renewal feature
by Holger Meissner 17 Jan '14

17 Jan '14

Hi Eric, thanks for your input! I will integrate your idea into the RFC. Eric Bégin wrote: > Instead of implementing this in the issuing rules, I think we could add > an "Automatic renewal" checkbox on the checkout page and adding > this value in the issues table. I think my library needs this as part of the issuing rules, because we have certain patron categories that generally are to be automatically renewed. But other libraries might want to use the feature for individual patrons or even single checkouts. So it might be best to implement it both in the issung rules and on the checkout page? > A syspref could be use for your « Automatically renewal X days before > due date ». Yes. Yet, some libraries might want to use different numbers, depending on how long the renewal period is, which might be days in one case and hours in another case. So I'm not sure.

2 1

Adding Wysiwyg to (HTML) System Preferences
by David Cook 17 Jan '14

17 Jan '14

What would folks think about adding the tinymce wysiwyg to some of the system preferences that deal with HTML? At Prosentient, we've added the "htmlarea" option for local system preferences, and now we're thinking about expanding to include some of the standard system preferences (such as OpacNav, OpacHeader, OpacMainBlock, etc). Many users probably don't know HTML, so it might be useful if they could use a wysiwyg to generate or modify content for these system preferences. That said, maybe not everyone wants to use a wysiwyg. Personally, I rather write HTML by hand. I don't like using wysiwyg editors. Tinymce does have an option where you can hand-edit the HTML source, so that solves that problem, but maybe there should be a system preference that controls whether certain system preferences have the wysiwyg appear or not. Maybe a list style syspref (e.g. OpacNav|OpacHeader) or just a general Yes/No. I would be willing to write the patch, but I want to figure out if there is any interest first. Cheers, David P.S. It's worth mentioning that the "type" stored in the database appears to have *zero* impact on a non-local system preference, and that the ".pref" files are used as the source of truth.

6 5

Automatic renewal feature
by Holger Meissner 17 Jan '14

17 Jan '14

Dear Koha developers, I just created a RFC for a new "automatic renewal" feature in the Koha wiki and would greatly appreciate any feedback on it: http://wiki.koha-community.org/wiki/Automatic_renewal_RFC Especially let me know if you think that I should address bug 7413, before I start working on the new feature. I suppose, that would be the most reasonable approach? Thank you! Holger

2 1

[QA] Description of some patches waiting for QA.
by Jonathan Druart 16 Jan '14

16 Jan '14

Hello QA team (and others)! I realize some of my patches are big and maybe need some explanation. Below is a description of my main patches in the QA queue. === Bug fixes === == Bug 11549: Acquisition module == A major one: Data loss possible! If an order is transferred and you receive/undo the receive, the order is deleted! This patch fixes the issue and add a regression test. === Features/enhancements === == Search history == I provided a lot of patches to improve the search history. The idea is to have a search history at the OPAC and the staff interface. Moreover an authority search history is added. A refactoring has been made and unit tests written. On my side, I have an other pending patch: the ability to merge selected searches. One patch is already passed QA, two need to be signed off and an other one is in the QA queue: Bug 10807 (NQA): OPAC: There is no authority search history This patch adds the authority search history for the OPAC. Bug 10862 (PQA): Add the search history for the staff interface This patch adds the search history for the staff interface (catalogue and authority). Bug 10933 (NSO): PurgeSearchHistory should be merged into the C4::Search::History module => This is a technical one, and I think a developer should do the signoff. These 3 patches should be pushed at the same time I think. Bug 11430 (NSO): Search history: Delete selected lines At this point, it was only possible to delete previous or current search history, not a specific search. This one is a small feature and can be pushed later. == Bug 10212: Columns configuration for tables == This patch was really fun to write and, I think, is a big improvement. It is more than a POC, but it should be validated and pushed to go further. The goal is to provide an admin page to configure all tables into Koha. By configure I mean: "display/hide these columns by default" or "this column could be shown/hidden (or not)". Extending the concept to others tables will be quite easy. == Multi transport types for notices == Hold on to your chair! The goal of these patches is to add the ability to choose the transport type a library want to use for notices. Don't be afraid, it is easy. The entry point is bug 9016: a new field letter.message_transport_type is created. This way it becomes possible to defined several "templates" for a letter_code. It will avoid to have letter codes like HOLD_PRINT, HOLD_PHONE, etc. This patch series adds the first step: the modifications into the DB structure and the interface. The multi transport types support for overdues is added too (interface changes only). A patron could be notified by email and/or sms for a given overdue level. The templates being different, the sent message could be adapted to the transport type. The 3 other patches are based on top of bug 9016. Bug 10832 - Multi transport types for overdue notices Changes for the cronjob script misc/cronjobs/overdue_notices.pl. Bug 10833 - Multi transport types for advanced notices Changes for the cronjob script misc/cronjobs/advance_notices.pl. Bug 10845 - Multi transport types for holds Changes for holds. All these patches are needing QA. == Bug 10363: New package for authorised values == This one needs QA too. I just refactored the authorised values code, put it in a new module and provide unit tests. Even if it does not use DBIC, I think it is useful and with this refactoring, it will be easy to use DBIC later. == Bug 11023: How to manage the newness of items? == This patch allows to manage various use cases for new items (see the commit message for examples). It offers an easy and flexible way to follow news items. It adds a cronjob which automatically remove the new status for items depending from some rules. These rules can be defined easily into a configuration page in the tools area. == Batch modification for records == There are two bugs waiting to be signed off: Bug 11319 - Marc modification templates improvements Bug 11395 - Batch modifications for records The first one fixes some issues with the marc modification templates features (bug 8015). The second one adds an interface to modify records (catalogues or authorities) in a batch using a template previously defined. It is waited for a long time by librarians (see bug 5725 for the history). Extra: bug 11562 (sysprefs.sql is not correctly sorted) should be integrated quickly, if we don't have a sysprefs file sorted, the qa script does not manage to catch non sorted new line (fix is welcomed on the qa tools repo. I don't find how to fix that). Please note that I am still waiting for other feedbacks on bug 8007. I hope this email will be useful to you and make easier the QA step on these patches! Regards, Jonathan

1 0