Time Nick Message 06:51 reiveune hello 07:36 Joubu @later tell dcook answered on the pad about the token passed in the response. 07:36 huginn` Joubu: The operation succeeded. 08:07 cait ping mtj 08:07 cait missed you again, sorry! 08:23 paulderscheid[m] morning #koha 08:23 paulderscheid[m] Just read that catalyst contributed a comprehensive guide to 2FA in the manual. catalyst++ 08:24 paulderscheid[m] But Authy is EOL, we need to change that in the string w/ the recommendations. 08:26 cait submit a patch :) 08:26 paulderscheid[m] Yetp 08:26 paulderscheid[m] yep 09:02 paulderscheid[m] Nevermind, I misread. It's just the desktop app for Authy. 09:02 cait ah 10:37 mtj Hi cait, about now 🍩 10:52 cait mtj: still there? 10:52 cait mtj: I was wondering about your availability for building the release this month - but I think we might still have some missing pieces maybe 10:52 mtj Hiya. yep 10:53 mtj No probs.. I'm about 🙆 10:57 cait what is the best way to reach you? are you following the release-maintainer email threads? 11:01 mtj Signal is good 11:02 mtj And yes, Im following the email threads 11:10 mtj . 11:10 mtj Cait. I messaged you via signal 11:30 mtj The matrix bridge seems to be a bit glitch, lately 11:31 mtj Element app on my fone, seems to miss some alerts 🤔 11:32 mtj Signal seems nice tho.. 🐴 11:34 oleonard-away mtj has all the emojis today 😄⚗️🛶 11:59 cait yeah and my emojis are broken :( 11:59 cait need to finally fix that 11:59 cait mtj: got your message, thx! 11:59 cait we've had other reports aobut the bridge not being reliable... I am still old school IRC 12:01 cait Koha IRC meeting now! :) 12:01 cait https://wiki.koha-community.org/wiki/Development_IRC_meeting_28_February_2024 12:01 thd pauldersheild[m]: Did you configure at least 2 GiB of swap for testing Discourse? Updates are reported to fail without at least 2 GiB of RAM and 2 GiB RAM. 12:02 cait quick heads up, anyone around for he meeting? :) 12:02 thd s/and 2 GiB RAM/and 2 GiB swap/ 12:03 cait I'll give it soem more time, but alone in the jitsi for now 12:07 cait #startmeeting Development IRC meeting 28 February 2024 12:07 huginn` Meeting started Wed Feb 28 12:07:37 2024 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:07 huginn` Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:07 huginn` The meeting name has been set to 'development_irc_meeting_28_february_2024' 12:07 cait #topic Introductions 12:07 cait #info Katrin Fischer, BSZ, Germany 12:08 tcohen Good morning! 12:08 cait come join us on Jitsi please! 12:08 tcohen #info Tomas Cohen Arazi 12:08 kidclamp #info Nick Clemens, ByWater Solutions 12:09 thd #info Thomas Dukleth, Agogme, New York City 12:10 cait so we are only a small group, please feel free to join uns anytime! 12:10 cait #topic Announcements 12:11 kidclamp https://annuel.framapad.org/p/koha_34478_remaining 12:11 cait #info Patches for bug 34478 will be pushed soon - be prepared to have some breakages, report bugs and help with fixing. 12:11 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 is not accessible. 12:12 cait #info Register for hackfest in Marseille if you plan on coming! (second week of April) 12:12 cait #topic Updates from the Release manager (24.05) 12:13 cait #info No big updates apart from bug 34478 12:14 cait #info Updates to Jenkins: including takss for the security branches, cleaned up all users and permissions etc. 12:15 cait #info Jenkins deployment issues with the nodes have been resolved - hopefully giving us less failures 12:16 cait #topic Updates from Release Maintainers 12:16 cait #info We will have a coordinated security release this month, stay tuned 12:16 cait #topic Updates from the QA team 12:16 ashimema sorry.. in another meeting right now 12:17 cait #info QA has been delayed, because of the master freeze and work on the big bug - working to resolve that soon 12:17 cait #topic Status of roadmap proejcts 12:18 cait #info tcohen: work continues on record locking and sources 12:20 cait #info cait: master to main has been discussed and we have a list wit todos - need to agree on a date, lots of scripts will need to be adjusted as well 12:21 cait #info kidclamp: bookings and REST API for item display are next 12:23 cait #info thd/paulderscheid: work on test instances happened 12:26 cait #info paulderscheid: still working on cities on Vue, work on Discourse instance 12:28 cait @action thd to add ask about testing discourse backups to Taiga 12:28 huginn` cait: I've exhausted my database of quotes 12:28 cait #topic Actions from last meeting 12:29 cait #info No actions from last meeting 12:29 paulderscheid[m] #info Paul Derscheid, LMSCloud GmbH, Germany 12:29 cait #topic General development discussion 12:29 cait #info No comments 12:30 cait #topic Review of coding guidelines 12:30 cait #action thd to add task about testing discourse backups to Taiga 12:31 cait #action all add coding guideline for CSRF protection on forms 12:31 cait #topic Set time of next meeting 12:33 cait #info Next meeting: 6 March 2024, 13 UTC 12:34 cait #endmeeting 12:34 huginn` Meeting ended Wed Feb 28 12:34:04 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 12:34 huginn` Minutes: https://meetings.koha-community.org/2024/development_irc_meeting_28_february_2024.2024-02-28-12.07.html 12:34 huginn` Minutes (text): https://meetings.koha-community.org/2024/development_irc_meeting_28_february_2024.2024-02-28-12.07.txt 12:34 huginn` Log: https://meetings.koha-community.org/2024/development_irc_meeting_28_february_2024.2024-02-28-12.07.log.html 12:38 thd tcohen: 12:38 cait Bug 34963 12:42 tcohen thd: hola 12:42 thd tcohen: I still have one significant Traefik question. If you have separate Docker projects, do you give them each an instance of Traefik? 12:42 tcohen o 12:43 tcohen no 12:43 tcohen you have a traefik network in which a single traefik instance is listening on 12:43 tcohen and each project will have it's own (internal) network 12:44 tcohen but the front-end requiring traefik on each project, will also join the traefik network 12:44 tcohen that's what we have in the wiki server 12:44 tcohen a single traefik and two wikis 12:44 tcohen (and jenkins, etc) 12:45 thd tcohen: Do separate networks avoid the error for reusing the same label with separate Docker compose files? 12:45 tcohen I can show you any time 12:45 tcohen no 12:45 tcohen there's no way to avoid that human error 12:46 tcohen each compose file should have it's own router name, middleware name, etc 12:47 thd One seemed fundamental ... [finding it but maybe it could be reidentified checking ] 12:50 thd tcohen: - traefik.enable=true is in every container in the same Docker compose file but if in an additional Docker compose file triggers a duplicate lablel. 12:52 thd tcohen: This label is used universally in examples of using Docker compose for some service with Traefik as a service lablel for the particular container. 12:53 tcohen hmm 12:53 tcohen have you checked how we did it in portainer for the wikis? 12:53 tcohen because it is certainly working 12:55 thd I will check. A permissions problem for my access to that may have developed. You were too busy at the time to check. 12:56 thd My credentials for that have been somewhat disused in consequence. 12:56 tcohen I can check of course 12:56 tcohen gimme a minute 12:56 tcohen can you zoom or smth? 12:56 tcohen are you you 12:57 thd My camera crashes but I may have microphone without rebooting. 12:59 thd Changing the kernal did nothing for the problem it seems to be a poorly supported chipset issue in several old Dell Lattitude models which I like for being highly repairable and very low priced second hand. 13:00 thd M icrophone may work though. 13:22 Joubu kidclamp, cait: https://wiki.koha-community.org/wiki/Coding_Guidelines#Security 13:22 cait in meeting, will check in a bit! 13:31 paulderscheid[m] Hey thd, you were right to point that out! W/ the current specs of the instance this could have led to a problem. Please add it to taiga anyway. 14:06 Joubu saving wiki page I am getting: "The server did not respond within the expected time." 14:08 Joubu thd, tcohen: $wgMainCacheType = CACHE_NONE; 14:08 Joubu https://www.mediawiki.org/wiki/Topic:Wxox117jvgchxhah 14:08 Joubu why CACHE_NONE? 14:12 Joubu thd, tcohen: opened https://tree.taiga.io/project/koha-ils/us/250 14:14 thd Maybe the container just needs a restart. How slow is slow? 14:15 Joubu 30s-1min then it timeouts 14:16 Joubu I don't know but CACHE_NONE vs CACHE_ACCEL... Why do we have NONE? 14:25 thd Lack of cache could be a config issue remaining from migration to avoid the risk of serving the previous content state where the cache might not been updated soon enough. If caching was not used, then caching problems could not be the source of previous content persisting. Code for what is updated in the cache seemed to be aimed at keeping Wikipedia served quickly not ensuring the latest changes are displayed. The container is supposed to ma 14:25 thd nage the caching automatically. Formerly caching was run directly on the VPS explicitly.. 14:26 * thd will check the config. 14:46 Joubu @later tell tcohen can you have a look at 36177#c4 please? 14:46 huginn` Joubu: The operation succeeded. 15:11 Joubu mtj: did you actually roll another release for stables with 36034 2 weeks ago? 15:12 lukeg hi 15:12 Joubu ...or are all the servers of the world running an "up-to-date" version of Koha have their disks full of silly row in the sessions table...? 15:35 cait Joubu: I think it's a great start, thank you (wiki). Maybe we could add some code snippes, like a cud example so people don't have to look throught he huge bug once we have pushed the code 15:36 cait Joubu: maybe most people not using binlogs or so? 15:36 cait I was wondering too 15:37 * oleonard imagines binlogs are logs that go straight into the bin 15:42 Joubu it's not related to binlog 15:42 Joubu it's the sessions table full of DBIC schema object 15:45 cait ah ok; i misread that 15:45 cait Iam not sure really, my inner fear is that people have not updated to security release 15:52 reiveune bye 16:02 thd tcohen: Prior to migration, running MediaWiki directly on the host system we would have had in current syntax $wgMemCachedServers = [ 'localhost' ] . 16:08 thd tcohen: I am not certain that localhost will resolve to the container. We could use the container IP address but I do not see that it is currently persistent. 16:17 thd tcohen: Nevermind, I seem to now understand that localhost will point to the container itself. I know that it does not point to the host system localhost outside the container. 17:24 caroline Is it possible to get this "charge" amount in the ISSUESLIP with TT? https://snipboard.io/BHP6j1.jpg 17:24 caroline It's the item's itemtype's rentalcharge minus the discount? 18:13 tcohen thd: I think canasta runs a memcached server, locally inside the container 18:14 tcohen the syntax change is part of the upgrade I think, we had to change some bits until we got rid of all the errors 18:15 thd Yes, MediaWiki still needs to access it. I think that localhost works fine as a value. 18:16 thd The current syntax was there. During the migration testing old syntax had been replaced or commented out. 18:17 thd We still had configuration errors but not generally over syntax. 18:18 thd I had $wgMemCachedServers = [ ] for disabling MediaWiki use of MemCacheD. 18:19 thd Old syntax was array ( 'array_value1', 'array value2', 'etc') 18:20 thd new syntax is [ 'array_value1', 'array_value2', 'etc' ] 18:21 thd My concern had been about localhost as a value in the container to ensure that it was pointing at the container. 18:26 thd All the caching for MediaWiki for which MemCacheD is merely a component is now turned on for the wiki. It had always been on before migration. The disadvantage is that the cache may be behind actual changes and may not have the current state. I had turned off caching for debugging purposes during migration testing and it did not seem slow to me. 18:53 thd Joubu, tcohen: I cannot post the LocalSettings.php values which I changed to Taiga. Is that because my user is not currently in the koha-ils team? 18:58 aude_c[m] Documentation meeting starting in 2min https://wiki.koha-community.org/wiki/Documentation_meeting_28_February_2024 19:01 davidnind #startmeeting Documentation IRC meeting 28 February 2024 19:01 huginn` Meeting started Wed Feb 28 19:01:24 2024 UTC. The chair is davidnind. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01 huginn` Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01 huginn` The meeting name has been set to 'documentation_irc_meeting_28_february_2024' 19:01 davidnind #chair aude_c 19:01 huginn` Warning: Nick not in channel: aude_c 19:01 huginn` Current chairs: aude_c davidnind 19:03 davidnind #chair aude_c 19:03 huginn` Current chairs: aude_c davidnind 19:03 aude_c[m] #chair marie-luce 19:04 davidnind #chair marie-luce 19:04 huginn` Current chairs: aude_c davidnind marie-luce 19:04 davidnind #info Agenda https://wiki.koha-community.org/wiki/Documentation_meeting_28_February_2024 19:04 marie-luce #topic Introductions 19:04 davidnind #topic Introductions 19:04 aude_c[m] #info Aude Charillon, PTFS Europe, UK 19:04 marie-luce #info Marie-Luce Laflamme, inlibro, Montreal, Québecc, Canada 19:04 davidnind #info David Nind, New Zealand 19:05 krimsonkharne[m] #info Philip Orr, LMSCloud, Germany 19:07 thd #info Thomas Dukleth, Agogme, New York City 19:07 caroline #info Caroline Cyr La Rose, inlibro, Québec, Canada 19:08 marie-luce the current meeting is also in a virtual meeting 19:08 marie-luce #link https://meet.jit.si/KohaDocumentationMeeting 19:08 davidnind #topic Review of action points 19:16 davidnind #infor Philip to set dates and times for workshop session https://wiki.koha-community.org/wiki/Documentation_Team_-_Drop-in_sessions 19:18 marie-luce #topic Automated screenshots (Caroline, Aude) 19:18 davidnind #info Automated screenshot project guidelines - still to be done 19:18 marie-luce #link https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34076 19:18 huginn` 04Bug 34076: enhancement, P5 - low, ---, jonathan.druart+koha, In Discussion , [ALTERNATE] [DOCS] Automated screenshots using Cypress.io testing framework 19:19 marie-luce #info This project is still ongoing, but there is not much so say at the moment. 19:20 marie-luce #topic Re-organising the manual (David Nind) 19:20 marie-luce #link https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32391 19:20 huginn` 04Bug 32391: enhancement, P1 - high, ---, david, ASSIGNED , [DOCS] Reorganise the manual contents 19:24 davidnind #info davidnind hopes to make the merge request with the changes by the end of the week 19:29 davidnind #info Google developer documentation style guide https://developers.google.com/style 19:35 davidnind #agreed Use the Google developer documentation style guide as a preference, with differences discussed and agreed at the documentation meeting 19:38 marie-luce #info We consider an accessibility guidelines to improve readability (e.g. background colour and text contrast). 19:39 davidnind #info WAVE Web Accessibility Evaluation Tools https://wave.webaim.org/ 19:40 krimsonkharne[m] #action Philip to check the Koha Manual with accessibility in mind (screenreaders, contrast ratios... etc.) 19:43 marie-luce #topic FAQ page 19:44 marie-luce #info The whole page seems updated 19:57 davidnind #action davidnind to add section to content development guide about approach for FAQs: incorporate into manual sections, update with date last reviewed, add bug to review and update, link to manual sections, use Wiki for configuration examples such as printers 19:57 davidnind #topic Next meeting 19:58 davidnind #agreed to move next meeting 27 March 2024 14:00 UTC 19:59 davidnind #nextmeeting Next meeting: 27 March 2024, 14:00 UTC 19:59 davidnind #info Next meeting: 27 March 2024, 14:00 UTC 19:59 davidnind #endmeeting 19:59 huginn` Meeting ended Wed Feb 28 19:59:49 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 19:59 huginn` Minutes: https://meetings.koha-community.org/2024/documentation_irc_meeting_28_february_2024.2024-02-28-19.01.html 19:59 huginn` Minutes (text): https://meetings.koha-community.org/2024/documentation_irc_meeting_28_february_2024.2024-02-28-19.01.txt 19:59 huginn` Log: https://meetings.koha-community.org/2024/documentation_irc_meeting_28_february_2024.2024-02-28-19.01.log.html 20:01 aude_c[m] davidnind++ 20:01 aude_c[m] marie-luce++ 20:01 marie-luce davidnind++ 20:01 caroline aude_c++ davidnind++ marie-luce++ krimsonkharne++ 20:01 krimsonkharne[m] aude_c++ :) 20:01 davidnind caroline++ 20:02 marie-luce aude_c++ krimsonkharne++ 20:02 caroline any MARC nerds around? h2h2 maybe? 20:03 caroline I'm wondering if biblio 654 should be linked to an authority record 20:12 thd caroline: Yes, 654 $0 should link to an authority record or multiple authority records for the same topic with as $0 is repeatable with the Subject thesaurus code, such as FAST, given in 654 $2. 20:13 hammat Hello everyone, 20:13 hammat I'm currently facing an issue with a new Z3950 authority server integrated with ElasticSearch that I'm trying to set up. My basic searches are functioning properly, but when I attempt to use @attr attributes, it doesn't seem to work. Interestingly, attribute 1=1 (personal name) works fine. I've attempted to address this by adding the attributes in the /etc/z3950/attribute_mappings.yaml file, but unfortunately, that hasn't resolved the issue. 20:13 hammat This situation has led me to question whether it's possible, with ElasticSearch for authorities, to perform a search on a specific field, such as a title by adding @attr 1=4 on yaz-client command line. In contrast, I haven't encountered this problem with an authority server under ZEBRA. For example, when I use @attr 1=4, it works seamlessly, but with ElasticSearch, it's not functioning as expected. 20:13 caroline thanks thd! 20:15 thd I am not certain of actual practise for repeating subfield $0 in this case. It has been a point of a little controversy where some preferred to use an additional 654 for the same topic, which may be DNB practise. 20:18 thd hammat: The Elastic Search implementation has not had extensive review from a library cataloguing perspective. It will probably need to be extensively revised over time. 20:23 thd YAZ has had extensive exposure to library systems over decades. Koha's own ElasticSearch implementation is something new from a small community of developers who generally do not have an expert cataloguer critique available for development. Given a somewhat working implementation bugs in implementation can be fixed over time. Sometimes a very long time for very obvious bugs. 20:25 thd Yet libraries are pleased to adopt systems which have the library science completely wrong but which help with discovery. We can have both good library science and good discovery with much extra work. 20:37 thd caroline: To avoid breaking some system somewhere, FAST is lowercase fast when used in $2 for Subject Heading and Term Source Code. We may normalise everthing in uppercase on the backend. Computer cataloguing practise starts with lower case norms perhaps because they are easier to type. 20:57 caroline link_bibs_to_authorities.pl doesn't seem to link 654 21:09 JasonGreene[m] how can we add Salutation to the dropdown when creating patrons 21:09 caroline JasonGreene[m], in the system preference BorrowersTitles 21:11 JasonGreene[m] found it.. thanks 21:30 thd caroline: Previously, I had been answering for standard MARC 21 cataloguing practise. link_bibs_to_authorities.pl creates Koha specific makeshift authority records from a subset of authority controlled fields where normative authority records are not present if I understand correctly or certainly that was past behaviour. Such makeshift records allow normative searches by authority controlled strings but do not have all the value of full autho 21:30 thd rity records. 21:32 thd caroline: If you supply the argument -g 654 to link_bibs_to_authorities.pl what happens? 21:33 caroline I'll try 21:33 caroline it does nothing it seems 21:57 thd caroline: I interpreted too much into a recent bug fix. When you build the Koha something like authority records using link_bibs_to_authorities.pl for 650 it should also build them for all related 6XX including 654. 21:58 cait It looks like we hardcode the headings, I tracked it through the code a bit and ended here: https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/Heading/MARC21.pm#L49 22:02 cait 654 is not in the list, I tihnk that's why it's failing 22:02 cait adding it for a test might work 22:03 thd I may be responsible for this bug. 22:08 thd When asked long ago, I may have said that link_bibs_to_authorities.pl is the wrong way to build pre-coordinated authority records such as Library of Congress Subject Headings. However, link_bibs_to_authorities.pl is the extra wrong way to build faceted subject headings and then 654 was not added in consequence of my statement. Having 654 there would be helpful but link_bibs_to_authorities.pl generated authority records are never proper author 22:08 thd ity records. 22:09 caroline I didn't know link_bibs_to_authorities created authorities. I thought it only linked them 22:09 thd Currently, it is much easier to acquire real authority records than it had been in the past. 22:09 thd caroline You are right. 22:10 caroline Ok I added a line for 654 in C4/Heading/MARC21.pm and it worked 22:10 caroline So that is where it comes from. I still don't know if it SHOULD, but it CAN 22:10 thd I may be conflating a different script build_marc_authorities.pl or some such script. 22:12 caroline not sure which one that is. We have an in-house one that I use for migrations 22:13 * dcook looks at scrollback 22:14 thd Still, the config file which cait identified shows how only very partially informed by library standards Koha is. 22:15 thd A proper script for 654 faceted subject heading should use only authority records from an authority database matching the thesaurus specified in 654 $2. 22:16 thd FAST is popular and derived from LCSH but OCLC charges real money for FAST records. 22:17 caroline I think there was a fix for the $2 thesaurus recently (it broke things catastrophically, but they fixed it) 22:18 caroline not sure if it applies to 654 22:18 caroline syspref LinkerConsiderThesaurus 22:19 thd LCSH records can be obtained without charge for a complete set a few years old and then updated or added to with some consortium contacts. 22:20 thd FAST records are presumably controlled by distribution contacts and more difficult to obtain. 22:25 caroline good night everyone! 22:27 thd caroline: I see that there is some code in MARC21.pm for doing something with $2 but maybe not enough. 22:27 thd caroline: good night 23:02 JasonGreene[m] I imported 250 users , is there a way I can remove all of them in one action? 23:03 JasonGreene[m] actually, I did it 3 times so I need to remove 750 23:03 JasonGreene[m] opps 23:07 thd JasonGreene[m]: I only know about reverting to a previous database backup for such cases. I do not have relevant expertise on patron management. You could write an SQL script to revert things but you would need to know which tables are affected by importing users to avoid partially removing them and creating problems for inconsistencies between tables. 23:08 JasonGreene[m] i found this Batch patron deletion and anonymization 23:09 JasonGreene[m] i'll try it 23:09 thd JasonGreene[m]: Presumably that will correct all the relevant tables and relations. 23:11 dcook @later tell Joubu I've replied on the pad, and realized that the Vue.js apps might experience issues with token expiry over time 23:11 huginn` dcook: The operation succeeded. 23:12 JasonGreene[m] Not sure what anonymization means 23:13 thd Anonymization is intended to disguise the true origin of the data but preserve things like circulation statistics without identifying who the borrower is for example. 23:14 JasonGreene[m] ok 23:15 thd Anonymization can be a weak disguise because if in your community you know that only person X would have an interest in borrowing Y to your knowledge. There is a good chance that you can identify person X and everything else which person X borrowed. 23:18 JasonGreene[m] The Batch patron deletion won't remove the koha.admin" account will it? 23:18 thd For anonymization to really work well against behavioral data inspection more would need to be done than what Koha probably does to merely remove identifying information. 23:19 JasonGreene[m] I just want to remove my mistake of 3xuser acconts 23:19 JasonGreene[m] without getting into the sql 23:20 thd I assume that the admin is more than a super patron. However, I do not know how the admin is defined. 23:21 thd You should read the script documentation for how it is intended to work so that you do not remove more than intended. 23:22 thd For example, perhaps it removes all patron IDs between a particular set of values. 23:23 thd You should discover what patron IDs you just imported in that case and start from the first mistakenly imported ID. 23:24 JasonGreene[m] it is a new system and the IDs are the "stock" ones that came with the install and mine... all the other were just added 23:25 thd I do not know that the batch processing script takes a parameter for patron IDs, but if it does then using them may be helpful. 23:27 JasonGreene[m] it has this option ... whose patron category is (drop-down) this looks good 23:28 thd That should help you exclude the admin account ;) 23:29 JasonGreene[m] yes 23:31 thd There is also a wiki page with example SQL queries for the reports function which could help you discover something about existing and recently added patrons, https://wiki.koha-community.org/wiki/SQL_Reports_Patrons . 23:32 JasonGreene[m] thanks 23:38 JasonGreene[m] Batch patron deletion and anonymization and whose patron category worked 23:42 JasonGreene[m] Is there a Batch card creator for patrons with no card number?