← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
00:07 | mbridge joined #koha | |
01:07 | mbridge joined #koha | |
02:07 | mbridge joined #koha | |
03:07 | mbridge joined #koha | |
04:07 | mbridge joined #koha | |
05:07 | mbridge joined #koha | |
06:07 | mbridge joined #koha | |
07:07 | mbridge joined #koha | |
07:14 | mbridge | [mattermost] <dilipkumar> @paulderscheid I asked one of the programmers to change the command below, and after that, the update worked. |
07:14 | [mattermost] <dilipkumar> sudo apt update | |
07:14 | [mattermost] <dilipkumar> sudo apt install sudo apt-transport-https ca-certificates curl | |
07:14 | [mattermost] <dilipkumar> sudo mkdir -p --mode=0755 /etc/apt/keyrings | |
07:14 | [mattermost] <dilipkumar> sudo curl -fsSL https://debian.koha-community.org/koha/gpg.asc -o /etc/apt/keyrings/koha.asc | |
07:14 | [mattermost] <dilipkumar> sudo apt update | |
07:14 | [mattermost] <dilipkumar> sudo apt upgrade | |
07:30 | thibaud_g joined #koha | |
07:39 | mbridge | [mattermost] <forehead> Hello |
07:40 | reiveune joined #koha | |
07:41 | mbridge | [mattermost] <forehead> I am currently working with the Koha API, specifically on adding patrons. Is the API designed for bulk patron insertion. May I also ask what is the best way to efficiently add multiple patrons at once? |
07:42 | alex_a joined #koha | |
08:02 | lds joined #koha | |
08:07 | mbridge joined #koha | |
09:07 | mbridge joined #koha | |
10:07 | mbridge joined #koha | |
11:07 | mbridge joined #koha | |
12:07 | mbridge joined #koha | |
12:18 | mbridge | [mattermost] <rudy.hinojosa> I have a specific use case that may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. At 3:15 am everyday, I have a cron job that pr |
12:19 | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. At 3:15 am everyday, I have a cron job tha | |
12:20 | [mattermost] <rudy.hinojosa> But having said all that, the Koha Patron importer works perfect for file loads too. You'll find that in Tools->Import Patrons. The Koha front end for this handles patron attributes as well. | |
12:22 | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. I don't delete an records for the record. | |
12:23 | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. I don't delete an records for the record. | |
12:25 | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. I don't delete an records for the record. | |
12:26 | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. I don't delete an records for the record. | |
12:46 | alex_a joined #koha | |
12:46 | thibaud_g joined #koha | |
12:52 | lds joined #koha | |
12:59 | alex_a joined #koha | |
13:07 | mbridge joined #koha | |
14:07 | mbridge joined #koha | |
14:30 | alex_a joined #koha | |
15:02 | alex_a joined #koha | |
15:07 | mbridge joined #koha | |
16:00 | reiveune left #koha | |
16:07 | mbridge joined #koha | |
17:07 | mbridge joined #koha | |
17:20 | blahdeblah joined #koha | |
18:07 | mbridge joined #koha | |
19:07 | mbridge joined #koha | |
20:07 | mbridge joined #koha | |
21:07 | mbridge joined #koha | |
22:07 | mbridge joined #koha | |
23:04 | mbridge | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. I don't delete any records by the way. At |
23:06 | [mattermost] <rudy.hinojosa> I have a specific use case that you may find useful. I have clients that interact with the Texas Educational Agencies that provide the patron and faculty rosters electronically via SFTP pushes to the Koha server on a nightly basis. The files are full file loads. Any faculty or staff patron rows that are not in this file should be considered deleted or retired. I don't delete any records by the way. At | |
23:07 | mbridge joined #koha |
← Previous day | Today | Next day → | Search | Index