Evergreen ILS Website

IRC log for #evergreen, 2016-05-02

| 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
06:31 graced joined #evergreen
07:19 rjackson_isl joined #evergreen
07:52 ericar joined #evergreen
07:58 Evergreen-Mike joined #evergreen
07:59 Evergreen-Mike left #evergreen
07:59 gsams joined #evergreen
08:23 csharp okay - I'm changing cat.maintain_control_numbers in config.internal_flag to 'false' (which is supposed to help with TCN collision detection) - what sort of reingest do I need to do to make that change apply to all existing (non-deleted) records?
08:39 mrpeters joined #evergreen
08:39 tsbere csharp: My understanding is that you can't reingest, the damage is already done.
08:40 mmorgan joined #evergreen
08:42 tsbere csharp: You may be able to do a bulk marc edit though, but that will obviously be harder to work out
08:47 StJoeCONLib joined #evergreen
08:49 StJoeCONLib good morning all, we are going live today with evergreen, and I have a reshelving question after a checkin is processed, we have our setting for 30min to change the status from reshelving to available, but for some reason the status never changes.  Im not sure what Im missing and hope someone can assit.  Thanks!
08:51 bshum StJoeCONLib: Well, there's a script that needs to be run in order to actually move items from reshelving back to available.
08:51 bshum StJoeCONLib: I believe it's installed into /openils/bin by default
08:51 bshum And it's called like reshelving_complete.srfsh or something like that
08:51 * bshum checks
08:51 StJoeCONLib excellent, is this something that can be put on the cron? or scheduled in the evergreen client?
08:52 bshum StJoeCONLib: Exactly, it's supposed to be setup via cron job to run frequently enough to catch the returns
08:52 bshum In the past, I usually set this to run once a day
08:52 StJoeCONLib that is excellent news, thank you so much!
08:52 bshum There should be an example crontab too in the source files
08:52 bshum In Open-ILS/examples/crontab.example
08:53 bshum Which contains many scripts usually set up for an Evergreen instalation
08:53 StJoeCONLib excellent, this Im guessing should be run as the opensrf account?
08:53 bshum Yes.
08:54 bshum StJoeCONLib: Going back to the beginning, huzzah on go-live :)
08:54 StJoeCONLib been smashing my head against the wall for a week trying to figure this out.
08:54 bshum StJoeCONLib++
08:54 StJoeCONLib thanks, we are excited
08:54 bshum Well, once upon a time, I think I volunteered to help write a chapter in the docs about cronjobs.  But then they added the example crontab to the source code, and I got busy.
08:55 csharp tsbere: ewww
08:55 bshum Should probably go back and do that someday.
08:55 jeff csharp: what change were you hoping to make/see in the bibs?
08:56 * bshum has a love/hate with 001 control numbers
08:56 * bshum feels for csharp
08:56 * bshum feels slightly less as he disappears to go to his day job
08:56 StJoeCONLib thanks, we are excited about the go live
08:56 csharp jeff: well, actually, I'm not sure how collision detection works, so, um, I guess I don't really know :-/
08:57 bshum StJoeCONLib: Good luck!  Feel free to bug these other guys if you have more thoughts
08:57 bshum I'm sure they'd be happy to help where they can ;)
08:57 * csharp needs to read the code
08:57 StJoeCONLib will do, I cant believe how massive this system is
08:57 csharp bshum: it was a Bibliomation person who told our person that this was the way to make it work
08:57 phasefx StJoeCONLib++
09:03 csharp okay, I remember now what the issue is... with the "default" MARC21 spec behavior of moving the 001 to the 035 as the record comes in, you can no longer use TCNs as a collision point since there's no way to say "compare the 001 in the incoming record to the 035 in our existing records"
09:04 * csharp may have something backwards there
09:20 Dyrcona joined #evergreen
09:21 jyorio joined #evergreen
09:22 jyorio joined #evergreen
09:24 yboston joined #evergreen
09:26 mdriscoll joined #evergreen
09:28 kmlussier joined #evergreen
09:34 dbwells csharp: That sounds right to me.  We have maintain_control_numbers off, and I think the default should be off for the reasons you are experiencing.  Maybe worth revisiting?  Also, I tried a bit to make a unified attribute for 001/035 for matching purposes, but formatting differences between the two fields is a real drag.
09:36 jeff I've run into frustrations with some records where we'd like to overlay them, but the only reliable match on the source records is the 001. In order to overlay, I think we'd have to modify the incoming records to copy the 001 to the 035 in a way similar to how maintain_control_numbers does it.
09:36 jeff Though there are probably other options.
09:37 Dyrcona LoC recommends moving the 001 to the 035, because 001 is supposed to be unique per database.
09:38 Dyrcona The 001 is also intended to reflect your local database, at least that is how I interpret the recommendation.
09:39 Dyrcona As dbwells and csharp have mentioned that is the default in Evergreen, and I don't think the default should be changed.
09:39 dbwells Does anyone know of benefits to doing this?
09:40 Dyrcona Yes, you can have multiple copies of the same record. :)
09:40 Dyrcona We actually had a lot of records in our previous ILS that were "copy on write" modifications of existing records.
09:41 Dyrcona So, without that setting, we couldn't migrate since the previous ILS did not move 001 to 035.
09:41 Dyrcona I'll see if I can find the link the LoC recommendation.
09:41 dbwells I don't think there is anything in Evergreen to prevent records with the same 001, is there?
09:41 Dyrcona Yes, there is or at least was.
09:44 Dyrcona https://www.loc.gov/marc/bibliographic/bd001.html says "may," but I swear I read something else from LoC that says "recommend."
09:46 dbwells Probably uniqueness was necessary for the "tcn_value" field on bre, but keeping that in lockstep with 001 has never been a serious goal in the code.  It was a Sirsi carry-over, and now holds a lot of different stuff.
09:47 csharp marc--
09:52 dbwells I think that manipulating the 001/035 stuff complicates life without good reason.  We have so many better ways of reliably handling our own identifiers without putting them into the record blob.  In addition, keeping the option off by default is more data conservative, since it is very easy to turn on and do the update, but not easy to go the other way.
09:54 berick joined #evergreen
09:55 dbwells Oh well, I'll try again in another 5 years :)
09:55 Dyrcona I still haven't found the document that said recommends.
09:56 dbwells Does that change your opinion at all?
10:02 mmorgan1 joined #evergreen
10:04 kmlussier joined #evergreen
10:05 jvwoolf joined #evergreen
10:06 kmlussier heh...good to see that paxed's code is still making its way into Evergreen. :)
10:08 dbwells yes, slowly but ... slowly ;)
10:13 mrpeters joined #evergreen
10:17 dbwells Good news everyone, IE has *finally* been dethroned!  https://www.netmarketshare.com/browser-m​arket-share.aspx?qprid=1&qpcustomb=0
10:17 csharp aw yeah
10:20 csharp damn - I shouldn't have bragged about the decreased number of reports tickets after implementing quick reports - my queue is already filling up with them :-/
10:20 csharp @karma reports
10:20 pinesol_green csharp: reports has neutral karma.
10:20 csharp pinesol_green: really?
10:20 pinesol_green Factoid 'really?' not found
10:20 pinesol_green csharp: Have you tried turning it off and back on again?
10:20 berick dbwells++
10:21 berick chrome++
10:26 csharp reports--
10:29 * jeff should write a nagios check for "clark kent is running"
10:33 kmlussier csharp: We still only have one week's worth of karma in here.
10:34 csharp kmlussier: a little bird reminded me of that :-)
10:35 csharp @who is the little bird of which I speak?
10:35 pinesol_green miker is the little bird of which I speak.
10:42 mmorgan joined #evergreen
10:48 dbwells jeff++ I'd use that :)
10:54 jeff dbwells: to be clear, it would alarm if clark was running :-)
10:54 jeff (since we officially buried clark in March)
10:56 Dyrcona dbwells: I had a local meeting, but as for the default of moving 001 to 035, I s'pose I'm not wedded to anything as long as the option is there.
10:56 dbwells jeff: I get jokes!  ;)
10:57 bshum Haha, I got to make a Superman joke with Clark.  Jeff said [10:54:35] <jeff> (since we officially buried clark in March)
10:57 * bshum cracks himself up
10:58 bshum Oops :)
10:58 Dyrcona @eightball Did Clark jump the shark?
10:58 pinesol_green Dyrcona: You're kidding, right?
11:02 mmorgan1 joined #evergreen
11:03 dbwells Dyrcona: good to know, thanks for considering
11:13 tsadok joined #evergreen
11:17 bmills joined #evergreen
11:18 dbs_ joined #evergreen
11:20 bmills1 joined #evergreen
11:21 sard joined #evergreen
11:22 sard joined #evergreen
11:23 _bott_ joined #evergreen
11:35 yboston joined #evergreen
11:42 Christineb joined #evergreen
11:43 sandbergja joined #evergreen
11:58 mmorgan joined #evergreen
12:07 brahmina joined #evergreen
12:11 rlefaive joined #evergreen
12:17 jihpringle joined #evergreen
12:29 hbrennan joined #evergreen
12:46 hbrennan_ joined #evergreen
12:52 hbrennan joined #evergreen
13:14 jeffdavis jeff: "officially buried clark" - you folks aren't using the reporter anymore?
13:16 jeff jeffdavis: correct.
13:16 jeff jeffdavis: I suspect that for a long time before this, the only reports being generated were long-forgotten scheduled reports.
13:21 jeffdavis Interesting, thanks! For a second I was worried that something had changed with the reporter in EG. :)
13:21 jeff Nope! :-)
13:32 sciani joined #evergreen
14:31 rlefaive joined #evergreen
15:02 mmorgan1 joined #evergreen
15:06 geoffsams joined #evergreen
15:11 rlefaive joined #evergreen
16:16 jlitrell joined #evergreen
16:24 mceraso_ joined #evergreen
16:24 bshum_ joined #evergreen
16:25 ldw_ joined #evergreen
16:26 rlefaive joined #evergreen
17:00 yboston joined #evergreen
17:13 brahmina joined #evergreen
17:18 jvwoolf left #evergreen
19:02 rlefaive joined #evergreen
19:33 dcook joined #evergreen
22:27 yboston joined #evergreen

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