Project

General

Profile

Spent time

Filters

Apply Clear

Hours: 344.53

Created Date User Activity Issue Comment Hours
17.02.2022 20:24 16.02.2022 Lari Taskula Development Feature #786: Cron script reminder for unretrieved material Last fixes. illrequests.date_due was not updating so investigating the issue and sending a new commit to PR. 0.50 Actions
15.02.2022 19:48 15.02.2022 Lari Taskula Development Feature #786: Cron script reminder for unretrieved material Making fixes according to Magnus's feedback. Removed faulty logic that message transport types would be based on the messages sent at receival step. Changed it so that now we attempt to find all transport types defined for that specific letter code and send notifications to all of them. Pushing changes to GitHub PR. 1.50 Actions
14.02.2022 10:47 14.02.2022 Lari Taskula Documenting Feature #786: Cron script reminder for unretrieved material Improving documentation. Adding pod2usage and author & license. 0.25 Actions
14.02.2022 10:34 14.02.2022 Lari Taskula Development Feature #786: Cron script reminder for unretrieved material Some fixes were required after Magnus's reviewing. Removed useless query, removed a statement that overrided a configuration variable that eventually led into a bug on further iterations of the reminder loop, added some print statements for better logging, and fixed a bug in array size comparison that made the lastly configured letter to be skipped. 1.00 Actions
09.02.2022 22:59 10.02.2022 Lari Taskula Development Feature #786: Cron script reminder for unretrieved material Making improvements according to author's feedback. 0.75 Actions
03.02.2022 08:59 03.02.2022 Lari Taskula Development Feature #786: Cron script reminder for unretrieved material Studying module's already existing cronjob. Designing a flexible config.yaml configuration for this feature. Developing the feature and sending a PR to upstream repository. 6.00 Actions
09.02.2022 23:54 10.02.2022 Lari Taskula Development Support #780: Charge patron a fee at receive Noticed a bug that causes logs to get spammed by a warning. Fixing it and sending a PR. 0.50 Actions
02.02.2022 01:45 02.02.2022 Lari Taskula Development Support #780: Charge patron a fee at receive Reading specification for step b. Implementing changes. 1.25 Actions
20.04.2022 14:37 20.04.2022 Lari Taskula Maintenance Support #779: Bug 24239 - Let the ILL module set ad hoc hard due dates Rebasing 0.25 Actions
09.02.2022 23:56 10.02.2022 Lari Taskula Development Support #779: Bug 24239 - Let the ILL module set ad hoc hard due dates Reading Magnus's response. Creating a configuration variable that allows configuring which field will be used for due date. Adding business logic behind it. Testing. Creating a pull request. 1.25 Actions
02.02.2022 00:21 02.02.2022 Lari Taskula Development Support #779: Bug 24239 - Let the ILL module set ad hoc hard due dates Studying the specification doc for task a. Checking Bugzilla Bug 24239 and studying Magnus's patch. Reading discussion related to the bug. It was suggested that instead of custom attribute, a date_due column could be added to illrequests table. Implementing this and writing tests for this. 3.50 Actions
11.02.2022 13:11 11.02.2022 Lari Taskula Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Continuing where Samu left off. Reading specification description, observing Koha's current capabilities for displaying item type, adding item type as new column, creating a new Bug, translating item type code to item type description and sending a new patch to Bugzilla. 1.00 Actions
10.02.2022 06:27 10.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Trying to figure out how to use KohaTable instead of just dataTable in Holds-tab 2.00 Actions
09.02.2022 23:30 10.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations I have studied the Koha-database tables and the way to access the homebranch-information of items. 1.00 Actions
09.02.2022 01:24 09.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Studying those javascript-files again with better understanding of the language syntax. Now I understand a whole lot better. 2.00 Actions
07.02.2022 08:06 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations And in fact it's not a calling object but oObj is as a parameter 0.10 Actions
07.02.2022 07:53 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations The main problem is that I know so little about javascript. I really have to study javascript syntax to get this to work. And, maybe the calling object in the holds-table is biblio after all, because oObj.title is a biblio name :) 1.00 Actions
07.02.2022 06:51 07.02.2022 Samu Heiskanen Design Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Argh! The setting: Default checkout, hold and return policy - Hold policy: was in value home library so I couldn't make interlibrary loans which tricked me to believe thet Holds-tab couldn't handle interlibrary loans. Wasted time making new Interlibrary tab and it'as functionality. Now back to designing the Holds-tab to show Holds' home library. 2.00 Actions
07.02.2022 04:43 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Ok, now I have replaced the checkouts-tab functionality temporarily with interlibrary-tab just for testing. And now changing the functionality of the interlibrary-tab towards its real purpose. 1.00 Actions
07.02.2022 03:35 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Working so hard that I almost forgot to report. Copy-pasting so much code as possible from checkouts. When I get it to work similarly then reducing the code gradually. 2.00 Actions
07.02.2022 01:34 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Now the task goes forward: I have made the Interlibrary Holds-tab and copied functionality from checkouts 1.00 Actions
07.02.2022 00:39 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations On the positive side now I now how to implement this task because I have learned a lot about the way these tabs are made 0.50 Actions
07.02.2022 00:00 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Ok now I get it. I have to make new tab for interlibrary loans. Wasn't I been stupid! 0.05 Actions
06.02.2022 23:57 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations Now I realized that there can't be interlibrary holds under holds-tab: it is only for home library holds. That's why there isn't homebranch for that because those holds are always from homebranch 1.00 Actions
06.02.2022 23:07 07.02.2022 Samu Heiskanen Development Support #776: “Details” under patrons in the staff interface a way to separate ordinary reservations from inter library loan reservations I guess holds-table oObj is Hold, not Item. Maybe I can reference straight to the Item with Hold-object. 1.00 Actions
(76-100/182) Per page: 25, 50, 100, 500

Also available in: Atom CSV