← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
02:57 | aleisha joined #koha | |
02:57 | aleisha | hello a;; |
02:57 | hello all | |
02:58 | i got this error when running `ktd pull`: "Error response from daemon: toomanyrequests: You have reached your pull rate limit." has anyone seen and fixed this before? | |
06:12 | jpahd[m] | It’s a docker hub thing |
06:13 | https://www.docker.com/increase-rate-limits/#:~:text=Anonymous%20and%20Free%20Docker%20Hub,pull%20requests%20per%20six%20hours. | |
06:42 | cait joined #koha | |
06:45 | cait1 joined #koha | |
07:12 | alex__ joined #koha | |
07:46 | thibaud_g joined #koha | |
07:48 | thibaud_g joined #koha | |
07:59 | Krel joined #koha | |
07:59 | Krel | Dear koha software developer |
08:00 | May you guide me how to migrate data from Newgenlib to Koha? | |
08:03 | jpahd[m] | We use Pentaho to write the migrations but you‘ll most likely need a contract or do it yourself as this is very resource intensive. As a high level approach: Look at the koha schema, try to map your schema to it and write the migrations. |
08:04 | cait1 | it also depends on what you want to migrate... for records and items you need to convert to MARC - there are some hints on how to do a CSV to MARC in the Koha manual |
08:04 | easier if your system can export MARC | |
08:05 | jpahd[m] | This 👆 |
08:07 | Krel | May you show me how to export data from newgenlib |
08:08 | jpahd[m] | If there is documentation you should reference that. Don't know the system, unfortunately. |
08:08 | I found this, maybe you can adjust the format | |
08:08 | http://ngl.70.s1.nabble.com/Ex[…]el-td7573115.html | |
08:13 | Krel | Thanks |
08:13 | dcook_ joined #koha | |
08:20 | PedroAmorim[m] | o/ |
08:34 | cait1 | \o |
08:51 | thibaud_g joined #koha | |
08:56 | AlexanderBlanchard[m] joined #koha | |
08:57 | ashimema | \0/ |
09:01 | AlexanderBlanchard[m] | Hi All, |
09:01 | I am new to the Koha Community, just popping in to introduce myself | |
09:02 | jpahd[m] | Hi |
09:02 | wahanui | bonjour, jpahd[m] |
09:05 | ashimema | Alexander is a new addition to the development team at ptfs-e. |
09:05 | jpahd[m] | Very cool, have fun Alex |
09:07 | AlexanderBlanchard[m] | Thank you! |
09:17 | cait1 | hi AlexanderBlanchard[m] :) |
09:18 | cait | IRC regulars? |
09:18 | wahanui | it has been said that IRC regulars is https://wiki.koha-community.org/wiki/IRC_Regulars |
09:18 | cait | If you want to know who is behind the nicks |
09:19 | alex__ joined #koha | |
09:24 | ashimema | we have all the cait's again 😜 |
09:44 | AlexanderBlanchard[m] | Hi cait1 ! |
10:04 | cait1 joined #koha | |
10:12 | dcook | This regular turning up at an irregular time for a few minutes... |
10:17 | cait1 | ? |
10:17 | ah :) | |
10:18 | dcook | And I'm off again hehe |
10:18 | Have a good daaaaay | |
10:18 | cait1 | bye dcook |
10:32 | ashimema | anyone know if frido is back from all his travels yet? |
10:32 | bit concerned that 23.05 really hasn't seen any love.. 22.11 is waiting on quite a pile of bugs to go through 23.05 now.. | |
10:40 | cait1 joined #koha | |
10:42 | cait1 | t |
10:45 | * cait1 | thinks cait is a zombie from lost network connection |
11:09 | oleonard | o/ |
11:09 | kidclamp joined #koha | |
11:11 | cait1 | hi oleonard and kidclamp |
11:26 | oleonard | A zombie!! |
11:29 | cait | lol |
11:30 | * kidclamp | waves |
11:40 | * cait | is scared to wave in case she is a zombie |
12:13 | tcohen | hola #koha o/ slow start this monday |
12:16 | PedroAmorim[m] | o/ |
12:17 | ashimema | morning tcohen: |
12:20 | alex__ joined #koha | |
12:49 | tcohen | PedroAmorim[m], ashimema Joubu |
12:49 | See bug 34233 | |
12:49 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34233 major, P5 - low, ---, lucas, Needs Signoff , Pickup location pulldowns in request.pl are blank |
12:49 | tcohen | caused by 28726 |
12:50 | can we think for a bit about Joubu's discussion on how we split and reuse the files | |
12:50 | I'm not saying we should revert, but we need to agree on the way to do it | |
12:50 | and in the meantime, we need lucas' patch to fix select2 dropdowns | |
12:51 | khall joined #koha | |
13:01 | Dyrcona joined #koha | |
13:12 | PedroAmorim[m] | <tcohen> "can we think for a bit about..." <- the patron-autocomplete.js vs staff-global.js? |
13:12 | sorry I'm confused! | |
13:13 | tcohen | yes |
13:16 | AnkeB joined #koha | |
13:26 | tcohen | but also that Lucas' patch needs urgent attention |
13:33 | * oleonard | signed off |
13:41 | tcohen | oleonardd++ |
14:10 | cait | QA Team: that one is now added to your todo list! |
14:10 | (wished it worked as simple as that) | |
14:11 | oleonard | Threaten to eat their brains |
14:13 | cait | lol |
14:16 | PedroAmorim[m] | about how we split and reuse files, I think having a 'staff-global.js' sort of implies that every JS that is used in Staff globally should be there, meaning we don't have the need for specific files addressing stuff that's used globally. I don't have a personal preference on the matter though! |
14:17 | about 34233 I can have a look but I'm not the best qualified person (never looked at select2 or holds for that matter) | |
14:30 | Dyrcona joined #koha | |
14:33 | Dyrcona joined #koha | |
14:41 | cait | re staff-global: you coudl also argue that everything that is needed everywhere shoudlgo there |
14:42 | ... but that might appyl to patron search not sure, big files get harder to manage, maybe some splittig makes sense | |
14:43 | PedroAmorim[m] | I agree, some splitting may make sense, it may be a matter of finding rule? i.e. when do we split vs when do we add to staff-global.js? I don't know |
14:44 | cait: I don't understand bug 34246 =DD | |
14:44 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34246 enhancement, P5 - low, ---, koha-bugs, NEW , Add search filter for library backend |
14:44 | cait | maybe it's our 22.11 |
14:44 | I wanted to filter by backend with the filters on the left side? | |
14:44 | you can do a keyword search... but that's a little annoying if you need to do it often for a backend name | |
14:44 | PedroAmorim[m] | there is a backend filter on the left-side |
14:45 | cait | so... there is not in 22.11 heh |
14:45 | PedroAmorim[m] | it's on 22.11.06 onward |
14:45 | cait | oooh |
14:45 | PedroAmorim[m] | where bug 22440 exists |
14:45 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=22440 normal, P4, ---, tomascohen, RESOLVED FIXED, Improve ILL page performance by moving to server side filtering |
14:45 | cait | I was looking at a 22.11.05! |
14:45 | PedroAmorim[m] | nice |
14:45 | cait | waiting for my coworker to update our demo to .07 |
14:56 | caroline | cait, oleonard, or anyone else, do you have an opinion on bug 33510? |
14:56 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=33510 enhancement, P5 - low, ---, koha-bugs, NEW , Add context to "New" as a status |
14:57 | caroline | We sometimes use "New" as an action button to "Add" something, and sometimes we use "Add" |
14:57 | I was wondering if Add should be used systematically to mean "Add a new thing", and "New" only be used as a status "this is a new thing" | |
15:00 | bag joined #koha | |
15:06 | khall_ joined #koha | |
15:51 | oleonard | caroline: There was a time when we were trying to standardize on New and Edit (rather than, say, Add and Modify) |
15:51 | That was a long time ago and it's gotten loose. | |
15:52 | caroline | That was another question davidnind raised, about Edit vs Modify |
15:58 | oleonard | Oh, looking at the files in the bug report I remember more... |
15:59 | "Add" was to be used when one is adding *to* something, e.g. "Add to cart" | |
16:00 | caroline | makes sense |
16:01 | oleonard | tcohen: Compiled CSS not in master? |
16:01 | caroline | SO I'll just add context to distinguish verb vs adjective |
16:04 | cait | caroline: usually what works better for you does work better for us as well :) |
16:04 | It's way too warm here... time to go | |
16:04 | bye #koha | |
16:08 | cait left #koha | |
16:22 | khall joined #koha | |
16:51 | caroline joined #koha | |
16:57 | cait joined #koha | |
17:04 | cait | yeah it's a problem if you pick newest release... everyone else is depending on you :( |
17:05 | oleonard | I am once again wondering why authorities isn't finding duplicate records when added manually |
17:09 | I suppose I should check with sample data and bisect... | |
17:10 | tcohen | oleonard: we don't commit compiled CSS anymore |
17:10 | you need to run yarn build yourself | |
17:11 | oleonard | Have we gone back and forth on that? I thought we were back to "on" :D |
17:15 | cait | i think koha-testing-docker is supposed to do it in the up step, right? |
17:15 | otherwise i might have missed doing so too :) | |
17:16 | oleonard | Anyway, all that matters is that I know how it's supposed to be! |
17:17 | tcohen | cait: KTD does it on startup and also on reset_all |
17:18 | but, overall, we decided not to include compiled assets in the code repo | |
17:18 | starting 22.11 | |
17:18 | things are built on packaging time | |
17:18 | cait | phew, ok |
19:47 | IGS joined #koha | |
19:53 | caroline joined #koha | |
19:55 | IGS | I have a question. I have two audiences for my catalog. Those who are here in the library, and those who might see it from outside. We are not a circulating library. I mark items as Not for Loan so people from outside know they have to come in to the library. This has the effect that people who are here in the library are confused by the items showing as "unavailable." They think the item is missing or we deaccessioned it or something. |
19:55 | Can anyone suggest a better way to do this? | |
19:56 | caroline | You could rename Not for loan to something more obvious to users, like 'In house use only' or something like that? |
19:57 | IGS | Is there an easy way to do that so I don't have to touch every item? |
19:57 | caroline | Go in Administration > Authorized values > NOT_LOAN, edit the value for Not For Loan and change the 'Text for librarian' and/or 'Text for OPAC' |
19:58 | cait | hm there is also a system preference to not show them as unavailable in results list |
19:58 | caroline | NFL something |
19:58 | cait | and the text in details page you can change as you want |
19:58 | Reference_NFL_Statuses | |
19:59 | caroline | Yes! Football status :) |
19:59 | It's how I remember that pref lol | |
19:59 | cait | heh |
20:02 | IGS | I'm looking for that, but my system is going really slow at the moment. Is that under Authorized values? |
20:02 | cait | system preferences |
20:02 | wahanui | system preferences are in the systempreferences table, other settings like circ rules have their own table(s) |
20:04 | caroline | IGS, you'll need to do both 1) Change the 'Text for ...' in Administration > Authorised_values > NOT_LOAN; this will change the value in the record details page; and 2) Add the value of the status (usually 1) in Administration > System preferences > Reference_NFL_Statuses so that the resultst list will show as reference rather than unavailable |
20:05 | IGS | It says, "No system preferences matched your search for: Reference_NFL_Statuses" |
20:05 | caroline | IGS what version of Koha are you using? |
20:06 | it's a newish preference | |
20:06 | IGS | Oh. We're behind. We're using version 19.11.00.000 |
20:07 | caroline | ooh... yes, the pref was added in 21.05 |
20:07 | cait | oleonard++ # improving the translations :) |
20:09 | caroline | IGS, what value is your Not For Loan? Is it 1? I think the defalut pre-21.05 was that 1 was considered for reference use only, so it might still be ok in 19.11 if Not For Loan is 1 |
20:20 | aleisha | hello |
20:20 | wahanui | salut, aleisha |
20:20 | IGS | NOT_LOAN the value is 3 |
22:50 | khall joined #koha | |
23:39 | khall joined #koha |
← Previous day | Today | Next day → | Search | Index