Evergreen ILS Website

IRC log for #evergreen, 2022-03-23

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:53 bshum joined #evergreen
03:48 Keith-isl joined #evergreen
05:22 JBoyer joined #evergreen
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:26 rjackson_isl_hom joined #evergreen
07:57 rfrasur joined #evergreen
08:29 stephengwills joined #evergreen
08:32 mantis joined #evergreen
08:37 mmorgan joined #evergreen
08:48 Keith-isl joined #evergreen
08:54 Dyrcona joined #evergreen
09:06 Keith-isl joined #evergreen
09:12 derekz joined #evergreen
09:28 derekz A library in our consortium isn't able to get their board to approve a patron privilege expiration of 2 years, as the consortium wants. The library insists that their patrons expire at 1 year. Since the expiration interval for permission groups is configured at the consortial-level, I'm trying to any major reconfiguration/data projects.
09:29 derekz At the moment, I'm thinking that I could write a script to review the previous day's activity in the actor.usr table for the target org unit/s. If a new patron record was created with the target home_ou, truncate the expire_date to the create_date + 365 days. If a patron record was updated during the previous day, ensure the interval between the last_update and expire_date is at most 365 days, else truncate.
09:29 derekz Had anyone else encountered this issue? Any thoughts on this approach? Better approaches?
09:35 mmorgan derekz: Could a separate permission group be configured for this library's use with the different expiration interval?
09:41 derekz It could, and that would be ideal, but I'd need to reconfigure circulation policies, hold policies, update patron records, etc... It would create the reconfiguration/data project that I'd prefer to avoid, if possible.
09:42 derekz In theory, yes. In practice, I don't have the time or the funds to hire someone else to do the work. I'm looking for a hack, basically
09:52 Dyrcona derekz: Adding a patron group for this library is the better solution. It seems to me that your circulation rules are too specific if you have to do all that work. The hold and circ rules cascade much like CSS, so simpler is better.
09:53 Dyrcona Philosphy: IMNSHO, it's better to have a bunch of generic rules that apply to the majority of cases at the largest number of org units, then you make specific exceptions from there.
09:54 Dyrcona Avoid using permission groups if possible.
09:55 Dyrcona Unrelated: "Vendor MARC records" seems to be a synonym for "garbage."
09:57 derekz Dunking on "Vendor MARC records" is a perfect distraction and apropos for March
09:58 Dyrcona Well, I just got a batch to load that produce character warnings regardless if I process them as UTF-8 or MARC-8, so they're likely in some other character set.
10:01 Dyrcona derekz: Writing a script as a QND solution is ... viable(?). In the long run, you'll want to eventually do the work with the circ and hold matrices. Unfortunately, there's nothing more permanent than a temporary solution.
10:01 stephengwills perfect segway.  I have a new school library that just started importing vendor records and, during this same few days postgres just started getting goosed by oom-killer.  Any chance that not a coincidence?  is vandelay known to consume lots of postgres memory?
10:02 Dyrcona stephengwills: I don't use vandelay much. I'm just throwing garba... ahem.. MARC at the database via DBI.
10:03 stephengwills I have a time/funding issue and am too paranoid to allow anyone else to touch the database directly. ;)
10:03 Dyrcona Why do I suspect that this batch of records is a mix of UTF-8 and some Windows code page or 3?
10:05 stephengwills they started using vandelay instead of having to wait for me.  which, in theory, isn’t unreasonable.
10:05 Dyrcona stephengwills: Understood. I wasn't critiquing the use of Vandelay for its intended purpose. Just sayin' that I don't use it much, so I'm not sure if it leads to memory issues with Pg.
10:06 Dyrcona I forget the exact sauce, but I did configure OOM Killer to be less likely to kill postgres, which doesn't help much when you've finally run out of RAM and swap. At that point, it's going down.
10:10 Dyrcona I will add that our cataloging staff use Vandelay a good bit and we've not had any memory issues that I can trace to Vandely.
10:11 Dyrcona When Pg has memory issues it's usually an insane report with the pivot table option or a nasty OPAC search.
10:12 Dyrcona Oh, and multiple dozens of the OPAC search are all running at the same time.
10:18 derekz Appreciate your thoughts and suggestions. Thank you
10:19 derekz mmorgan++, Dyrcona++
10:32 Dyrcona Does anyone else load records from Kanopy? If so, what do you to fix the records? I was given a batch of 379 records and 87 of them won't load because of character issues: "\x9D" does not map to Unicode at /usr/lib/x86_64-linux-gnu/perl/5.26/Encode.pm line 212, <GEN1> chunk 16.
10:35 Dyrcona *mumbles* Google...useless...
10:40 Dyrcona Thank you, chardet! Windows-1254 with confidence 0.51855302355
10:40 Dyrcona Now, can yaz-iconv convert that to UTF-8?
10:42 Dyrcona Argh! Somethng's wrong with my processor... I get "utf-8 with confidence 0.99" on the original. I swear I worked that all out a couple of weeks ago!
10:43 Dyrcona marc--
10:43 Dyrcona @blame MARC
10:43 pinesol Dyrcona: It's all MARC's fault!
10:59 Dyrcona The real issue isn't MARC so much. It's how Perl handles character sets and "binary" data.
11:00 Dyrcona My other prep program doesn't seem to have this problem.
11:01 Dyrcona Also, it would help if vendors would set the leader properly.
11:02 Dyrcona Maybe it's time for lunch?
11:08 mmorgan Dyrcona: My colleague loads Kanopy records, she says she often uses MarcEdit to search and replace or strip out characters.
11:09 mmorgan She loads using Vandelay.
11:10 Dyrcona mmorgan: Yes. I'm replacing the search and replace that was done in MarcEdit with a Perl program.
11:10 Dyrcona They're UTF-8 records. Perl is just mangling them on me, but I've got it sorted for now.
11:12 Dyrcona I should probably just go ahead and output MARCXML in the preprocessor program.
11:12 Dyrcona Or even make the preprocessor part of the loader.
11:15 Dyrcona Or, maybe just switch to Bmagic's loader that i've been meaning to test.
11:18 Dyrcona This is still too "hands on" for my taste.
11:28 Dyrcona @marc 022
11:28 pinesol Dyrcona: The ISSN, a unique identification number assigned to a continuing resource. (Repeatable) [a,y,z,2,6,8]
11:28 Dyrcona @marc 028
11:28 pinesol Dyrcona: The formatted number used for sound recordings, printed music, and videorecordings. Publisher's numbers that are given in an unformatted form are recorded in field 500 (General Note). A print constant identifying the kind of publisher number may be generated based on the value in the first indicator position. (Repeatable) [a,b,6,8]
11:28 Dyrcona @marc 024
11:28 pinesol Dyrcona: A standard number or code published on an item which cannot be accommodated in another field (e.g., field 020 (International Standard Book Number), 022 (International Standard Serial Number) , and 027 (Standard Technical Report Number)). The type of standard number or code is identified in the first indicator position or in subfield $2 (Source of number or code). (Repeatable) [a,c,d,z,2,6,8]
11:29 Dyrcona Anyone know where UPCs usually show up?
11:29 Dyrcona @marc 026
11:29 pinesol Dyrcona: Used to assist in the identification of antiquarian books by recording information comprising groups of characters taken from specified positions on specified pages of the book, in accordance with the principles laid down in various published guidelines. (Repeatable) []
11:29 Dyrcona @marc 025
11:29 pinesol Dyrcona: A number assigned by the Library of Congress to an item that was acquired through one of its overseas acquisition programs. (Repeatable) []
11:39 Dyrcona Looks like 024.
11:46 rhamby yeah, should be 024s though the indicator for it is rarely set in my expeirence
11:48 stephengwills joined #evergreen
11:55 Dyrcona rhamby++
11:56 Dyrcona My character set issues stem from using print with binary data. I should probably switch so syswrite.
11:56 rhamby don't you know marc is dead adn everything is pure utf compliant linked data now.  standards have made everything easy.
11:57 rhamby I'll just see myself out before the rotten fruit heads this way....
11:57 Dyrcona :)
12:02 Dyrcona UTF-32: Because RAM is cheap! :)
12:05 jihpringle joined #evergreen
12:16 * Dyrcona sighs after reading perldoc -f syswrite
13:02 JBoyer Does anyone here know who has admin access to github.com/evergreen-library-system/ ? I can throw a Q to the dev list but thought I'd check here first.
13:16 JBoyer joined #evergreen
13:26 Keith_isl joined #evergreen
13:30 JBoyer Never mind! I have found what I need.
14:07 mantis Question for DIGGERS: what's the difference between Tip and Note in the docs?
14:07 mantis Sometimes I have a hard time deciding
14:07 mantis And if this is addressed in a style guide already, apologies in advance
14:12 jihpringle mantis: I don't think we have anything about tip versus note
14:13 jihpringle in our own docs we generally use a tip if it's something about how to do whatever is being described, whereas a note is slightly more generic useful to know info
14:13 mantis jihpringle++
14:14 mantis I see some times when I could differ between the two; others is uh
14:14 mantis kind of harder
14:14 jihpringle like with patron search we have recommendations of what to use as defaults and put those as tips
14:15 jihpringle ya, I think sometimes either would work and then you just have to pick one :)
14:16 jihpringle it would be good to have something in the style guide about when to use tip, note, caution
14:42 mantis jihpringle: I'll be sure to bring this up the next time we meet
14:56 jihpringle joined #evergreen
16:54 rfrasur joined #evergreen
17:10 mmorgan left #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:14 Keith__isl joined #evergreen
18:47 miker grabbing 1314 for upgrade goodness
19:07 Keith_isl joined #evergreen
19:16 pinesol News from commits: Stamping PG10+ upgrade script <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=28d181​46ce075bc6f2ff015e9efd032dfbe9b746>
19:17 pinesol News from commits: LP1937294: Fix another invalid XPath expression error <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=7d2793​f82e21747ef0af9ad94e41c770d319e435>
19:17 pinesol News from commits: LP1937294: Fix XPath invalid XPath expression Error <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=bd487d​3003cc4bb99ec51ea94db8df38ef299287>
19:17 pinesol News from commits: LP1937294: Update Installation Documentation <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=5a4891​4ad9d915975fbd3b08a40151542f7d8a8f>
19:17 pinesol News from commits: LP1937294: Update Prerequisite Installation for PostgreSQL Server <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=09d021​bc336b18799968313f79d4c22371e577ed>
19:17 pinesol News from commits: LP1937294: Fix the unaccent and squash tests <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=a75d7a​34ee5fd4b3bb5f32c7a36b9a131913c016>
19:17 pinesol News from commits: LP1937294: Fix metarecord master record choice predictability issue <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=b035da​7435ced7f7beca36a742fa9a80b62ac410>
19:17 pinesol News from commits: LP1937294: Fix Functions for XML/XPath changes <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=171f87​3a72275bfb554f03e9ccd27d38b4326982>
19:17 pinesol News from commits: LP1937294: Fix Sample Data Load Predictability Issue <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=0ab42b​1702ae0797dc9247b5a4258edbe27d6c74>
19:17 pinesol News from commits: LP1937294: Add FTS Config for PostgreSQL 11 - 14 <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=c7d525​f4a5b7839b1ce13457184359e27430596e>
20:48 Keith__isl joined #evergreen
21:59 stephengwills left #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat