Time |
Nick |
Message |
02:08 |
|
Mark__Tr joined #evergreen |
02:16 |
|
Mark__Tr joined #evergreen |
02:17 |
|
Mark__Tr left #evergreen |
02:18 |
|
Mark__T joined #evergreen |
02:18 |
|
Mark__T joined #evergreen |
03:45 |
|
Mark__T joined #evergreen |
06:40 |
|
rlefaive joined #evergreen |
07:52 |
|
rjackson_isl joined #evergreen |
07:58 |
|
rlefaive joined #evergreen |
08:00 |
|
jboyer-isl joined #evergreen |
08:23 |
|
ericar joined #evergreen |
08:30 |
|
Newziky joined #evergreen |
08:33 |
|
mrpeters joined #evergreen |
08:34 |
|
mmorgan joined #evergreen |
08:37 |
|
TaraC joined #evergreen |
08:42 |
|
Stompro joined #evergreen |
08:49 |
Stompro |
Good Moorning Evergreeners, What workstation/OU are offline transactions associated with, the workstation where they occur or the workstaton that processes the transactions? |
08:52 |
mmorgan |
Stompro: Good Morning! Interesting question. I believe it's the workstation that processes. The actual workstation where the transaction occurs doesn't appear to be recorded in the offline file. |
08:56 |
Stompro |
mmorgan: Thanks, we are just trying to figure out how it is going to work for migration. We currently handle offline processing centrally, looks like that is going to be more difficult with EG. |
09:02 |
mmorgan |
Stompro: So you plan to process offline files from migration centrally? You'd need to login with a workstation registered for each library, but it could be done. |
09:07 |
Stompro |
mmorgan, That is our current method, but I think it may not be the best method going forward. I don't really want to setup 30 staff client profiles on my machine to handle every location. |
09:09 |
Stompro |
We don't have "local system administrators" at our sites, we are a pair of consolidated systems, so If I can figure out what permissions are needed to create the offline session and process the transactions so our regular circ users can do that, then that is a better method. |
09:11 |
mmorgan |
We also used to process offline centrally, but it's nice that libraries can process their own, on their own schedules. |
09:13 |
mmorgan |
We currently give the permissions OFFLINE_VIEW and OFFLINE_UPLOAD to our regular circ users. Our higher level circ users have OFFLINE_EXECUTE. |
09:15 |
mmorgan |
So our regular circ users can upload but the Process button is greyed out for them. |
09:17 |
mmorgan |
One thing that has confused users that process the transactions is that the screen doesn't refresh and they think the process is hung. They have to manually hit the Refresh button to see that processing is complete. |
09:18 |
mmorgan |
We also ran into this bug: lp 1174970 |
09:18 |
pinesol_green |
Launchpad bug 1174970 in Evergreen "logging out of the staff client while offline transactions are being processed will cause NO_SESSION exceptions for the remaining transactions" (affected: 1, heat: 6) [Medium,Triaged] https://launchpad.net/bugs/1174970 |
09:19 |
Stompro |
Thank you for listing those out for me, I appreciate it. I think I'll add those the the offline circ docs. |
09:21 |
mmorgan |
Stompro: NP. Another offline related thing: For some reason, when uploading, some users think they need to click the Export button, and when prompted to delete the file, they say yes. |
09:22 |
mmorgan |
They then need to find the exported file and reimport it to process it. |
09:22 |
Stompro |
Thanks, we will watch out for that. |
09:23 |
mmorgan |
We've had a little experience with offline processing ;-) |
09:37 |
|
yboston joined #evergreen |
09:43 |
Stompro |
mmorgan++, thanks for all the info. |
09:46 |
mmorgan |
NP :) |
10:02 |
|
collum joined #evergreen |
10:31 |
csharp |
Stompro: this PINES documentation may be a good reference for you: http://pines.georgialibraries.org/sites/default/files/files/Evergreen%20Standalone%20Procedures%20v2.5.pdf |
10:33 |
|
mllewellyn joined #evergreen |
10:44 |
mmorgan |
csharp++ |
11:09 |
|
Newziky1 joined #evergreen |
11:09 |
Stompro |
csharp++, thanks for the manual link. |
11:14 |
|
krvmga joined #evergreen |
11:54 |
|
jihpringle joined #evergreen |
12:01 |
Bmagic |
csharp: nice doc! Gonna keep that around for a rainy day! |
12:21 |
gsams |
csharp: Thanks for posting that doc, I'm going to share that with my group! |
12:21 |
gsams |
csharp++ |
12:24 |
gsams |
mmorgan++ #I must enjoy learning the hard way because I've been through most of that as well. |
12:26 |
* mmorgan |
thinks that must be true of most of us ;-) |
12:35 |
|
edoceo joined #evergreen |
12:42 |
csharp |
terran++ # the doc's author ;-) |
12:45 |
mmorgan |
terran++ |
12:52 |
|
Dyrcona joined #evergreen |
13:18 |
|
buzzy joined #evergreen |
13:40 |
|
Callender joined #evergreen |
13:49 |
gsams |
terran++ #I'll pile some more karma on this train too |
14:42 |
|
rlefaive joined #evergreen |
15:03 |
Dyrcona |
@seen bshum |
15:03 |
pinesol_green |
Dyrcona: bshum was last seen in #evergreen 3 days, 23 hours, 52 minutes, and 18 seconds ago: <bshum> Before we run make_release script |
15:04 |
bshum |
Dyrcona: So, how was the move? |
15:04 |
bshum |
:) |
15:04 |
* bshum |
is still in SF |
15:04 |
csharp |
@seen bshum |
15:04 |
pinesol_green |
csharp: bshum was last seen in #evergreen 3 seconds ago: * bshum is still in SF |
15:04 |
Dyrcona |
Others are still unpacking. |
15:04 |
Dyrcona |
It went smoothly enough. |
15:05 |
Dyrcona |
It took all day Saturday to move the servers and have them set up again. |
15:05 |
Dyrcona |
We need the filter changed on the a/c in this part of the offices, though. |
15:05 |
Dyrcona |
bshum: How was ALA? |
15:06 |
bshum |
Dyrcona: It |
15:06 |
bshum |
*It's been good |
15:06 |
Dyrcona |
Still going on? |
15:06 |
bshum |
I spent some time at the Evergreen booth |
15:06 |
bshum |
Today is the last day. |
15:06 |
bshum |
But I'm taking it easy for a moment, and spending quality time with my laptop... |
15:06 |
Dyrcona |
heh |
15:07 |
Dyrcona |
I don't have wifi problems in the new offices. |
15:07 |
Dyrcona |
And, if I plug in, I've got gigabit to the servers down the hall. |
15:08 |
Dyrcona |
We tested that this morning because the building people wanted to make sure that the fiber was working properly. |
15:16 |
jeff |
that's somewhat troubling. |
15:16 |
Dyrcona |
What's somewhat troubling? |
15:17 |
jeff |
though in one scenario could be encouraging (this run tests clean, can you verify?) |
15:17 |
Dyrcona |
Well, yeah, we actually tested it last week. |
15:17 |
jeff |
it would be troubling if they were relying on your test as the only diagnostic. :-) |
15:18 |
Dyrcona |
tsbere came over and they tested it Thursday, but didn't do any speed tests. |
15:18 |
Dyrcona |
The building's engineer wanted us to do a speed test Saturday, but he had to leave before we had the right servers up. |
15:31 |
Dyrcona |
Does NO_CHANGE mean that the copy check in failed? |
15:31 |
jeff |
i believe it can mean that the copy was already checked in. |
15:32 |
jeff |
SIP checkin considers SUCCESS and NO_CHANGE to be acceptable, and anything else is a failure. |
15:32 |
Dyrcona |
It seems to come from two places. |
15:33 |
Dyrcona |
One after checking for holds and the other does appear to happen if it is already checked in. |
15:34 |
Dyrcona |
Some asked about this event 'cause they got it when processing offline circulations and it wasn't on the list of events that they were given. |
15:48 |
jeff |
hrm. i thought we had taught offline mode to do no-op checkins. now i'm not seeing it in a quick glance. |
15:49 |
jeff |
but even if it were there, i think it might be possible that a noop checkin will still complete a transit, even if it won't start one. |
15:51 |
jeff |
(untested thought) |
15:52 |
jeff |
(not even quite a theory) :-) |
16:03 |
|
Newziky left #evergreen |
16:31 |
|
jboyer-isl left #evergreen |
16:51 |
|
mrpeters left #evergreen |
17:11 |
|
mmorgan left #evergreen |
17:17 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
21:48 |
|
dcook joined #evergreen |