Evergreen ILS Website

IRC log for #evergreen, 2018-11-28

| 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:45 sandbergja joined #evergreen
03:11 * dbs wonders how many people are watching the SWIB livestream today: http://swib.org/swib18/livestream.html
07:07 JBoyer joined #evergreen
07:14 rjackson_isl joined #evergreen
08:15 bos20k joined #evergreen
08:39 mmorgan joined #evergreen
08:55 Dyrcona joined #evergreen
08:57 Dyrcona I think a lot of the weird "bugs" that happen with the web staff client have to do with the browser/PC running out of resources.
08:57 Dyrcona A lot of them stop happening for a while after the user quits the browser and restarts it.
08:57 Dyrcona Just throwing that out there.
09:04 rhamby Dyrcona: but I only forty tabs including seven paused youtube videos going, I don't see how that could be true
09:05 Dyrcona :)
09:05 mmorgan Dyrcona: What sort of weird "bugs" are you seeing?
09:06 Dyrcona I'm thinking mainly of the "copy templates sometimes don't apply all fields" types of bugs. We've had it reported where the user specifically said it works again if they quit the browser and then go back in.
09:06 Dyrcona Could be because of bugs in Chrome, too....
09:08 * mmorgan nods
09:11 aabbee joined #evergreen
09:13 bdljohn joined #evergreen
09:15 pinesol [evergreen|Cesar Velez] LP#1746769 - add item tag owner OU to label in volcopy editor - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=611a34b>
09:23 JBoyer Dyrcona, I would also add potential issues with understanding promises (leading to occasional race conditions) depending on the experience spread of the community with them.
09:27 JBoyer (I say that because I had a rough start with them, and a mix of cargo culting patterns and reading, especially articles about the way things can go wrong helped me a bit.)
09:36 yboston joined #evergreen
09:43 collum joined #evergreen
10:01 mmorgan1 joined #evergreen
10:06 jvwoolf joined #evergreen
10:06 Dyrcona Anyone using the Hold Expires from Shelf Soon email notice care to discuss how you run it?
10:07 Dyrcona We're running it daily with a delay of -2 days and finding that they usually go out for the next day, not two days ahead.
10:08 Dyrcona I think that's because the shelf expire time is not 23:59:59 but the actual time the item went on the shelf + our 7 day interval.
10:08 Dyrcona If I run it later in the day on a test VM, I get more that are 2 days out but still get some that are for 1 day.
10:12 * Dyrcona is considering changing the delay to -3 days, but wonders if running it hourly would make a difference.
10:15 JBoyer We don't use it here (probably should consider it) but if there's a preference for 2 days it might help to add an additional 12 hours, so 60 hours rather than 2 days? Depending on how things line up that should fairly well cover the second day without creeping into the third or leaving many behine.
10:17 kmlussier joined #evergreen
10:24 Dyrcona Another, longer term option, would be to she shelf_expire_time to use 23:59:59 like due dates, but dunno if anyone uses hourly hold shelf intervals.
10:24 Dyrcona JBoyer: -60 hours seems plausible.
10:26 JBoyer That would make the most sense long term, yeah, as I imagine most places only want to clear their shelf once a day. (unless they have absolutely bonkers hold shelves, who knows.)
10:41 khuckins joined #evergreen
10:42 Dyrcona Yeah, I was going to experiment with setting the time to 23:59:59 a bit later before opening a Lp bug about it.
10:44 Dyrcona I think some discussion would be warranted about that before making changes for similar reasons.
11:00 remingtron joined #evergreen
11:03 jeff_ another option would be to teach A/T about how to have an interval that's day-granular.
11:04 jeff can you do that already in this case with a max validity interval?
11:11 kmlussier jeffdavis: While updating contact information here - https://wiki.evergreen-ils.org/dok​u.php?id=faqs:evergreen_companies - I noticed that the Sitka info could also use an update.
11:14 sandbergja joined #evergreen
11:25 mmorgan joined #evergreen
11:41 beanjammin joined #evergreen
11:55 jeffdavis yes indeed, thanks kmlussier
11:56 kmlussier Gah! I just noticed that the MassLNC listing has been saying "Membership is open to any..." since May due to an edit made by somebody else.
12:06 sandbergja joined #evergreen
12:15 jihpringle joined #evergreen
12:17 miker Dyrcona: benefit of running that hourly would be less of a chance of looking like a spammer to MTAs... I don't see a downside to hourly, if you really want as close to 48 hours as you can get
12:32 nfBurton joined #evergreen
12:38 nfBurton Does anyone have documentation or links on possible Call Number w/ Prefix and Suffix standards? We are cleaning out our old usage and trying to start fresh but need to do some research to find some options
12:38 khuckins joined #evergreen
12:42 Dyrcona miker: Thanks. I may try that as an option instead.
12:43 jeff miker++ i like that option better.
12:48 Dyrcona miker++
12:48 Dyrcona If I set the max delay to -1 days, we shouldn't miss any notices either.
12:50 Christineb joined #evergreen
12:55 jeffdavis nfBurton: do you mean standard prefixes/suffixes?
12:56 nfBurton Yeah. Our standard got lost in the ether and I am trying to help them come up with a new one
12:56 nfBurton Also they are used to free text which led to a lot of issues as you can imagine
12:57 yboston joined #evergreen
12:57 nfBurton I know it differs but I want to show them what some other libraries on the system are doing
12:58 Dyrcona Well, I don't think the actual content of the prefixes matters so much as long as each library is consistent in using them. We have some libraries that use prefixes on some call numbers and some other of the same library's call number have the prefix embedded in the label.
12:59 Dyrcona The latter are a mess to fix.
12:59 Dyrcona Ditto for suffixes.
13:03 nfBurton Ugh it becomes a mess. After migration I had around 15 000 suffixes. I have been cleaning it up slowly and need to help them come up with a standard to prevent the high numbers
13:03 nfBurton Not being a Librarian though, I have presented what the data shows but am not really deep in the pains of cataloging
13:07 hbrennan joined #evergreen
13:12 jeffdavis nfBurton: do your call numbers use the Dewey Decimal System?
13:12 Dyrcona I have less experience and fewer thoughts on suffixes. They tend to be more free form. Prefixes tend to "obvious" things like YA, DVD, etc.
13:13 nfBurton Yes. The call numbers we can at least agree on. Those use Dewey.
13:13 Dyrcona We have mostly Dewey, some LC, but we're a multi-type library consortium. The LC libraries tend not to use prefixes and suffixes.
13:27 sandbergja nfBurton: fwiw, our prefixes (at a LC library): are REF, OVERSIZE, and four that are related to unusual shelving locations
13:28 sandbergja And our suffixes are a lot of v.1, v.2, v.3 etc.
13:29 sandbergja The dewey libraries in our consortium don't use prefixes and suffixes at all (at least not the formal ones in Evergreen)
13:30 nfBurton Hmm. Okay. I am trying to get away from volume/series indication and move that to copy part instead. It flooded us in our old system with it being inputted so many different ways
13:33 sandbergja That makes sense.  I'm not sure how we came to the decision to use suffixes for volume indications; it was before my time
13:36 Dyrcona I think added the volume to the end of call numbers is a fairly common thing in libraryland.
13:50 Dyrcona Back to my hold expires from shelf soon thing: I just noticed that the 2 day courtesy notice that we use has a delay of -3 days and a max delay of -2 days. I'm going to use those settings.
13:56 * Dyrcona tests it, first.
14:58 yboston joined #evergreen
15:04 mmorgan Dyrcona: FWIW, our 2 day courtesy notices have those same settings.
15:04 Dyrcona mmorgan: -3 days, -2 days, daily granularity?
15:05 Dyrcona It's looking like that would work, but I'm testing -2 days, -1 days, hourly granularity.
15:05 mmorgan Dyrcona: Yes, daily
15:12 JBoyer A late in the day thought re: acp.alert_message in a post 3.1/3.2 world, is there any reason for it to even be in the IDL at all? After running the upgrade script and updating the copy editor there's really no way to use it anymore, and it's displayed by default in a few grids...
15:13 JBoyer I don't think it's worth altering the db tables just yet, but if it can't be set and can't be changed, maybe it's time it can't be seen.
15:13 JBoyer (Unless I'm missing something, hence my bringing it up.)
15:33 mmorgan JBoyer: I would say the alert_message fields certainly should not display by default in the web client. I also want to say the alert_message field should remain in the IDL until the xul client is actually removed.
15:43 * kmlussier yawns.
15:43 kmlussier @coffee
15:43 * pinesol brews and pours a cup of El Salvador Finca Siberia Pacamara, and sends it sliding down the bar to kmlussier
15:43 mmorgan @dessert kmlussier
15:43 * pinesol grabs some candy from krvmga's desk for kmlussier
15:43 kmlussier Ha! I really did eat candy from krvmga's desk today. :D
15:44 mmorgan :)
15:44 kmlussier Caramel bullseye!
15:44 mmorgan I remember those!
15:47 mmorgan I had caramel apple bullseyes once. They were surprisingly not bad.
15:51 kmlussier I don't think I would like that.
16:20 Dyrcona Jabber disconnects....
16:21 Dyrcona On a test server but sure is making testing rather difficult.
16:23 khuckins_ joined #evergreen
16:34 nfburton joined #evergreen
17:08 mmorgan left #evergreen
17:18 jvwoolf left #evergreen
17:52 khuckins joined #evergreen
20:05 sandbergja joined #evergreen
21:07 kmlussier joined #evergreen
22:53 kmlussier joined #evergreen

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