| Time |
Nick |
Message |
| 01:03 |
|
Mark__T joined #evergreen |
| 02:25 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 03:57 |
|
gsams joined #evergreen |
| 04:11 |
|
eady joined #evergreen |
| 05:12 |
|
gsams joined #evergreen |
| 07:13 |
|
TaraC joined #evergreen |
| 07:45 |
|
rjackson_isl joined #evergreen |
| 07:46 |
|
rlefaive joined #evergreen |
| 07:59 |
|
ericar joined #evergreen |
| 08:00 |
|
jboyer-isl joined #evergreen |
| 08:15 |
|
wlayton joined #evergreen |
| 08:32 |
|
akilsdonk joined #evergreen |
| 08:36 |
|
mrpeters joined #evergreen |
| 08:39 |
|
mmorgan joined #evergreen |
| 08:44 |
|
Dyrcona joined #evergreen |
| 08:46 |
|
yboston joined #evergreen |
| 08:51 |
|
maryj joined #evergreen |
| 09:03 |
|
jwoodard joined #evergreen |
| 09:04 |
|
Shae joined #evergreen |
| 09:05 |
|
collum joined #evergreen |
| 09:19 |
remingtron |
yboston / kmlussier: today is 2.9 Docs Hack-fest, right? |
| 09:19 |
remingtron |
I can't get in to the Google Hangout (via link sent to DIG list) |
| 09:22 |
remingtron |
...but for anyone interested in helping document 2.9 new features: |
| 09:22 |
remingtron |
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.9_needs |
| 09:23 |
yboston |
remingtron: can you try joining again https://plus.google.com/hangouts/_/berklee.edu/dig-eg-2-9-new |
| 09:23 |
yboston |
remingtron: maybe I had to open the hangout first? |
| 09:23 |
remingtron |
yboston: okay, trying again |
| 09:24 |
remingtron |
looks good! |
| 09:24 |
|
maryj joined #evergreen |
| 09:24 |
remingtron |
yboston++ |
| 09:24 |
yboston |
remingtron: I had set it to allow non Berklee folks when I first created it, bu it got reset |
| 09:31 |
kmlussier |
I won't be in the hangout, but I'll be documenting and I'll be here. |
| 09:33 |
|
sarabee joined #evergreen |
| 09:34 |
yboston |
kmlussier++ |
| 09:42 |
remingtron |
Docs opinion question: Now that JSPAC is officially removed in 2.9, how should we refer to the TPAC in the docs? |
| 09:43 |
yboston |
good question |
| 09:43 |
yboston |
SHould we say just "PAC"? |
| 09:43 |
remingtron |
OPAC/catalog? the Only-PAC? |
| 09:44 |
kmlussier |
I like public catalog. |
| 09:44 |
kmlussier |
Or catalog, if we are referring to its use in the staff client. |
| 09:46 |
mmorgan |
possibly "public catalog" and "staff catalog" depending upon the context? |
| 09:47 |
remingtron |
mmorgan: good thought. I think there are some cases where the staff catalog displays differently |
| 09:47 |
remingtron |
good to be clear in those cases |
| 09:47 |
remingtron |
kmlussier: I agree, public catalog sounds the most clear |
| 09:47 |
kmlussier |
I always have found PAC to be jargony |
| 09:48 |
kmlussier |
Even though I use the word all the time. |
| 09:48 |
remingtron |
agreed, not nice for outsiders or newcomers |
| 09:57 |
|
rfrasur joined #evergreen |
| 09:58 |
|
alynn26 joined #evergreen |
| 10:03 |
Stompro |
I hate pac-- and opac-- also. |
| 10:06 |
rfrasur |
In general? or specifically EG? |
| 10:06 |
Stompro |
I think we should use "Discovery Layer" instead, much clearer. |
| 10:07 |
kmlussier |
rfrasur: In my case, I don't like it in general. |
| 10:08 |
csharp |
opac-- |
| 10:08 |
Stompro |
rfrasur, just the terms, since patrons have no idea what you are talking about when those terms get used. |
| 10:08 |
rfrasur |
kmlussier: me either. But I'm without capability to change much at this point. It's a cluster... (in general) |
| 10:09 |
rfrasur |
Stompro - ah yes...jargon. I <3 (hate) jargon. |
| 10:10 |
alynn26 |
jargon is fine based on your readers. |
| 10:10 |
rfrasur |
Aye. But with an OPAC, we want everybody to be our reader. |
| 10:10 |
kmlussier |
Yes, we were talking about the jargon. Sorry, I just realized you weren't here for the beginning of the conversation. I do like the ability for users to find materials in the library, so I have no problem with the existence of the catalog. ;) |
| 10:11 |
rfrasur |
I wasn't here, but it's a pretty common issue. |
| 10:16 |
jeff |
in general, I try to refer to "the catalog" |
| 10:17 |
rfrasur |
Same here, Jeff. |
| 10:18 |
jeff |
and even then i wonder if there's a better term. |
| 10:18 |
jeff |
*shrug* |
| 10:18 |
* jeff |
scrolls back for context |
| 10:18 |
jeff |
ah. |
| 10:18 |
rfrasur |
Is there? I'd like to call it a resource database...but I'm pretty sure that our public wouldn't be going for it. |
| 10:18 |
rfrasur |
Or my staff |
| 10:19 |
kmlussier |
I agree there probably is a better term; not sure what it is. Finder? |
| 10:20 |
kmlussier |
Not that I would ever use 'finder' in our docs. Our libararians need to know what we're talking about. |
| 10:20 |
jeff |
that's on my Mac, right? |
| 10:24 |
jboyer-isl |
Everyone gets the concept of a catalog (think Sears), I think Amazon may even use that term somewhere. I dig it. |
| 10:25 |
alynn26 |
I like catalog also. I like the idea of staff catalog and public catalog, especially dealing with Evergreen. As there are things that you can do in the staff catalog, that you cannot do in the public catalog. |
| 10:31 |
Bmagic |
kmlussier: the vendcode in the EDI invoice from BT ? |
| 10:32 |
kmlussier |
Bmagic: Yes, the vendcode is in the EDI invoice from BT. |
| 10:33 |
Bmagic |
I explored that with BT, and funny enough, they said they would do it. My data doesnt show it, I will open that conversation again! It is odd that it's only happening with 3 of the 9 BT accounts though |
| 10:36 |
|
jvwoolf joined #evergreen |
| 10:38 |
|
dMiller_ joined #evergreen |
| 10:38 |
|
RoganH joined #evergreen |
| 10:38 |
maryj |
kmlussier: Trying to set things up in the staff client so aspects of the OPAC can be tested for documentation purposes. Is it okay if I modify barcodes for items within the mnlc 2.9.rc test server? |
| 10:39 |
kmlussier |
maryj: That's not a problem. It |
| 10:39 |
kmlussier |
It's there to be used and abused however you see fit. |
| 10:40 |
maryj |
Whoooo! I mean - with great power comes great responsibility. ;) Thanks, kmussier |
| 10:40 |
|
Christineb joined #evergreen |
| 10:43 |
maryj |
** kmlussier ^ |
| 10:43 |
kmlussier |
Heh...I didn't even notice the typo on my first read. |
| 10:47 |
|
jwoodard_tablet joined #evergreen |
| 10:58 |
yboston |
miker: I have a quick question about removing JSPAC only documentation; I plan to delete the JSPAC "Search for Authorities" section; what about the "Create a new Browse Axis" section, should it be removed? |
| 10:58 |
yboston |
miker: http://docs.evergreen-ils.org/dev/_browse_axes.html |
| 10:59 |
* miker |
looks |
| 10:59 |
miker |
yboston: nope, don't remove that |
| 10:59 |
gmcharlt |
yeah, it also affects stasff-side auth browsing |
| 11:00 |
yboston |
miker: good to know, I suspected it should stay, but can I remove the "Search for Authorities" section |
| 11:00 |
yboston |
? |
| 11:01 |
miker |
I don't see that section in the TOC |
| 11:01 |
miker |
ah, found it. opac searching for authoritie |
| 11:02 |
miker |
that looks dead |
| 11:05 |
yboston |
miker: that is what I thought, folks were confusing that section for "borwse the catalog" section, so I wanted to remove it |
| 11:06 |
miker |
+1 |
| 11:07 |
yboston |
miker & gmcharlt: thanks for confriming that "Create a new Browse Axis" is still being used. Shoud I make a note about any code related to "Search for Authorities" that we want to remove to clean things up |
| 11:08 |
yboston |
miker & gmcharlt: then agian we might want to keep code in to allow for reviing related fucntionality later on |
| 11:08 |
yboston |
s/reviing/reviving/ |
| 11:09 |
gmcharlt |
yboston: in a word... no, I don't think there's any code left that should be specifically targeted for removal |
| 11:10 |
yboston |
gmcharlt: I had a feeling htere might not be anything left, just wanted to make note if there was code we could shed, like JS circs stuff |
| 11:12 |
gsams |
I'm looking at making a report/query for the amount of money saved for patrons by checking materials out from the library. I was wondering if anyone had cause to do something similar? |
| 11:13 |
Dyrcona |
gsams: ldw did something to count cost per circulation for his various member libraries. That might be useful to find out how that worked. |
| 11:14 |
RoganH |
gsams: I've done that. we use circ mods related to type of item, e.g. BOOK and LEASE, etc... so I do the math making assumptions based on those |
| 11:14 |
gsams |
Dyrcona: I will definitely check with ldw then, thanks for pointing me that way. |
| 11:15 |
mmorgan |
gsams: Some libraries put a total value of the items borrowed on their checkout receipts. |
| 11:15 |
gsams |
RoganH: That might be a good way for me to go, because some of our item prices are combined prices on all the parts. |
| 11:15 |
gsams |
otherwise I'd need to figure in some sort of error margin there. |
| 11:16 |
RoganH |
gsams: my libraries are all over the board about entering item prices and making sure they're in the bib, in the end averaging it out seemed a better idea |
| 11:16 |
jeff |
yup. phasefx helped us hack together a way to do that back in 2009. it was something patrons actually missed. |
| 11:16 |
jeff |
i don't recall if we came up with that idea or stole it from someone else in library land. |
| 11:16 |
gsams |
mmorgan: I'll probably want to do that as well at some point |
| 11:16 |
RoganH |
gsams: I went down the road of using the bib / item / default price and in the end it wasn't worth the headache |
| 11:17 |
kmlussier |
gsams: When you get to that point, there's some info on it here - http://www.swissarmylibrarian.net/2012/05/08/highlighting-the-value-of-library-use/ |
| 11:17 |
gsams |
RoganH: So basically, go with an assumption on average price point for a particular type of item, and work it that way? |
| 11:18 |
gsams |
kmlussier++ #That's fantastic |
| 11:18 |
RoganH |
gsams: if your libraries are like mine it provides better numbers because the data isn't always there. I have libraries that don't use a default replacement cost, don't put item prices in, etc... so their numbers were horribly low |
| 11:19 |
RoganH |
gsams: I used this for prices: http://www.swissarmylibrarian.net/librarycalculator/valuecalc_costs.html |
| 11:19 |
jeff |
we use tables based on shelving location that were at one time or are occasionally "re-calculated" (in the case of new shelving locations to be the average of items in those locations (that HAVE price data). |
| 11:19 |
jeff |
most items have price data. |
| 11:19 |
jeff |
(in our catalog) |
| 11:20 |
gsams |
RoganH++ #Thanks for the info, will look into that more for sure |
| 11:21 |
gsams |
jeff: I think my group is generally good about price information, I'd really have to do a bit more digging to be completely sure. |
| 11:21 |
kmlussier |
Those values were pulled together years ago (before I was an Evergreener). They probably could use some updating. |
| 11:22 |
gsams |
jeff++ Dyrcona++ mmorgan++ #Thanks everyone! |
| 11:22 |
gsams |
kmlussier: Would be interesting to see what has changed. |
| 11:23 |
gsams |
Looks like I have my work cut out for me one way or another! |
| 11:25 |
kmlussier |
Yes, it would. I know the Massachusetts Library Association. When Maine adopted the calculator, they adapted the pricing a bit http://www.maine.gov/msl/services/calexplantion.htm . |
| 11:25 |
kmlussier |
Sorry, I should re-read what I'm posting before I hit send. |
| 11:31 |
|
rfrasur joined #evergreen |
| 11:33 |
Stompro |
A/T question, is the event definition owning library only honored if there is an associated filter that adds the '"context_org":"home_ou"' comparison? So if I trigger events using --hooks=blah, without using a filter, the events won't be limited to the owning library? |
| 11:37 |
pinesol_green |
[evergreen|Yamil Suarez] Docs: add more details about displaying authority subject heading thesaurus value - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6289cc0> |
| 11:37 |
mmorgan |
Stompro: I have pondered the same question at times. I am not positive of the answer, and hope someone else will jump in, but I think you always need the filter. |
| 11:38 |
Stompro |
mmorgan, you mean that no events will get created unless you have the filter, or that you need the filter for the ownling library to have any effect? |
| 11:38 |
mmorgan |
I have suspicions that the owning library of the event definition just serves to limit which org units can view/edit the definition. |
| 11:40 |
mmorgan |
Stompro: Sorry, I meant the latter. Events will get created without the filter, but won't be limited to the owning library. |
| 11:41 |
* mmorgan |
is hoping someone will correct any misconceptions. |
| 11:41 |
pinesol_green |
[evergreen|Yamil Suarez] Docs: remove TPAC based Searching of Authorities section - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=2392315> |
| 11:44 |
Stompro |
mmorgan++ thanks, I'll test it out, eventually, and let you know if that isn't how it works. |
| 11:46 |
mmorgan |
Stompro++ |
| 11:46 |
* mmorgan |
also planned to test it out eventually. Unfortunately, "eventually" hasn't happened yet ;-) |
| 12:04 |
|
jihpringle joined #evergreen |
| 12:21 |
pinesol_green |
[evergreen|Yamil Suarez] Docs: add info on disabled Google Analytics in staff client - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=cae3146> |
| 12:23 |
|
gdunbar joined #evergreen |
| 12:23 |
jvwoolf |
Hey DIG folks - anybody working on OPAC documentation? |
| 12:24 |
alynn26 |
jvwoolf: most of us have marked what we are currently working on. |
| 12:24 |
yboston |
jvwoolf: so far I only see remingtron as being marked as working on that area |
| 12:25 |
Stompro |
Does anyone have a helper script that they use with cron that queries the closed days table, so you can skip running some cron jobs on holidays? |
| 12:25 |
yboston |
jvwoolf: Is there something you would like to work on? |
| 12:25 |
alynn26 |
yboston: the Clear cache documentation is done, I've linked to my GIST. |
| 12:26 |
Stompro |
alynn26++ |
| 12:26 |
jvwoolf |
yboston: Was thinking about snagging the "Account Expiration Date in My Account" |
| 12:26 |
remingtron |
jvwoolf: FYI, http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.9_needs |
| 12:27 |
yboston |
jvwoolf: would you like me to wark you down for that section? |
| 12:27 |
yboston |
*mark |
| 12:27 |
* jvwoolf |
is Jessica Venturo from Bibliomation, BTW. Now Jessica Woolford. |
| 12:27 |
jvwoolf |
yboston: Thanks, I can do it. |
| 12:27 |
yboston |
jvwoolf: ahhh |
| 12:27 |
remingtron |
jvwoolf: ahhh |
| 12:28 |
jvwoolf |
Shiney new IRC handle to go with my shiney new last name :) |
| 12:28 |
yboston |
alynn26: I am grabbing your content now |
| 12:28 |
yboston |
jvwoolf: :) |
| 12:29 |
alynn26 |
jvwoolf: Congrats on the new last name. |
| 12:30 |
yboston |
alynn26: do you have a suggestion where I sould palce that content, sorry if you explained this somewhere already |
| 12:30 |
alynn26 |
yboston: I was thinking about that. I'm not sure |
| 12:31 |
yboston |
alynn26: OK, will think about it too |
| 12:32 |
alynn26 |
yboston: I was thinking the part XIII Some where in there. |
| 12:32 |
alynn26 |
But, as it is just for staff use??? |
| 12:33 |
yboston |
alynn26: to be clear; this can only be done by staff on the client? (Link in catalog to clear Added Content cache) |
| 12:33 |
jvwoolf |
alynn26: Thanks! |
| 12:34 |
alynn26 |
Yea, its just in the staff client. hmmm |
| 12:34 |
yboston |
we couls place it in the area where added content set up is covered |
| 12:34 |
yboston |
*could |
| 12:34 |
alynn26 |
that would work |
| 12:38 |
yboston |
I am thinking of putting it near here? what do you think? |
| 12:38 |
yboston |
http://docs.evergreen-ils.org/dev/_including_external_content_in_your_public_interface.html |
| 12:39 |
alynn26 |
That works. |
| 12:39 |
yboston |
this area first covers "Including External Content in Your Public Interface" |
| 12:39 |
yboston |
then it covers "Including Locally Hosted Content in Your Public Interface" |
| 12:39 |
yboston |
not sure if your section shoudl go in between the two sections or after those two? |
| 12:40 |
yboston |
does anyone know if the "Including Locally Hosted Content in Your Public Interface" woudl also benefit from the cache clearing feature we are trying to document? |
| 12:40 |
alynn26 |
From reading the code, I do not think so. |
| 12:42 |
|
RoganH joined #evergreen |
| 12:42 |
yboston |
alynn26: is this the file you are looking at? perlmods/lib/OpenILS/WWW/AddedContent.pm |
| 12:44 |
|
rlefaive joined #evergreen |
| 12:47 |
jeff |
yboston: the local override overrides, and is unaffected by the cache clearing feature. |
| 12:47 |
|
maryj joined #evergreen |
| 12:48 |
yboston |
jeff: thanks for the confirmation |
| 12:49 |
yboston |
alynn26: then I will place that section of docs between those two section; i.e. after "Including External Content in Your Public Interface" |
| 12:49 |
alynn26 |
Ok |
| 12:49 |
jeff |
i think alynn26 confirmed, i was just double-confirming :-) |
| 12:49 |
* jeff |
chases encoding issues similar to (or perhaps identical to) bug 1442276 |
| 12:50 |
pinesol_green |
Launchpad bug 1442276 in Evergreen "Supercat encoding problems with MODS output (Zotero)" (affected: 2, heat: 10) [Undecided,New] https://launchpad.net/bugs/1442276 |
| 12:55 |
jvwoolf |
Just noticed somebody marked "Account Expiration Date in My Account" as "no change required," but I know it's not in the 2.8 docs. Am I missing something? |
| 12:56 |
yboston |
I did not make that chnge, but maybe someone felt that the curretn screen shot showed that feature already? |
| 12:56 |
alynn26 |
I was wondering about that also, It's actually a new feature in 2.9 |
| 12:56 |
yboston |
let me check the wiki page logs |
| 12:57 |
yboston |
today I did label some things as "no change required" because they were either a bug fix or soemthing that was very tiny and in the back end |
| 12:58 |
yboston |
remingtron: are you around? |
| 13:00 |
remingtron |
yboston: mostly, yes |
| 13:01 |
yboston |
remingtron: jvwoolf asked a question earlier about "Account Expiration Date in My Account" being labeled as "no change required" |
| 13:01 |
yboston |
remingtron: in case that was you, shoudl she work on it? |
| 13:03 |
yboston |
jvwoolf: it might have been akilsdonk |
| 13:03 |
remingtron |
yboston: I don't think I labeled that as "no change required" |
| 13:04 |
maryj |
That would be because of me |
| 13:04 |
remingtron |
I was looking at things that have been removed in 2.9 |
| 13:04 |
akilsdonk |
jvwoolf, yboston: I did do that at the request of maryj. |
| 13:05 |
jvwoolf |
maryj: You're working on it? |
| 13:05 |
maryj |
remingtron, yboston, jvwoolf: Do we need screenshots of "Account Expiration Date in my account" then? The explaination seemed straightforward enough. |
| 13:05 |
maryj |
Same for "Column sorting in circulation screens " |
| 13:07 |
yboston |
maryj: when you say the explination is straightforward enough, do you mean in the release or do you mean the part of the offical docs that cover the UI elemnts/fetures of that part of EG? |
| 13:07 |
maryj |
jvwoolf: I looked at it and tested it to see if the written description matched the features on-screen, and if any needed details were needed for the 2.9 documentation. |
| 13:08 |
yboston |
maryj: so far you are mostly making sense to me, specially about "Column sorting in circulation screens", but I want to clear soemthing up |
| 13:08 |
maryj |
What's in the release notes for those two features "Account Expiration Date in My Account" and "Column sorting in circulation screens" would work for documentation for 2.9. I realize my misunderstanding of the linked documents on that wiki page now. |
| 13:08 |
maryj |
yboston: I'm all ears |
| 13:08 |
yboston |
maryj: I think we are now on the same page from your last message |
| 13:09 |
yboston |
maryj: it is funny that when you have been doing something for a while, you take things for granted |
| 13:10 |
yboston |
maryj: you orignal thought was incorrect, but it makes sense if you are not used to our process |
| 13:11 |
yboston |
so I suggest that jvwoolf and maryj get on the same page on working together on that feature; might be a good opportunity for maryj to shadow jvwoolf to learn our typically approaches |
| 13:11 |
yboston |
I can also help |
| 13:11 |
yboston |
*typical |
| 13:12 |
remingtron |
yboston: so, are we using "no change required" to mean "done, and we didn't have to do anything"? that's how I meant it |
| 13:12 |
jvwoolf |
yboston: I still feel like a bit of a newbie myself, but I'm happy to work with maryj |
| 13:12 |
yboston |
I had not noticed that choice until today |
| 13:12 |
yboston |
it might have been around for a while |
| 13:13 |
yboston |
I took it as something that would be good for bux fixes, where the code now behaves like the documentation.users expected |
| 13:14 |
maryj |
yboston: And is the process documented somewhere? I saw your link to the DIG training slides and read them. It was basically a formatting & how do install Asciidoc presentation. |
| 13:14 |
yboston |
maryj: welcome to one of many paradoxes |
| 13:14 |
yboston |
maryj: we need more documentation on how we make documentation |
| 13:15 |
remingtron |
maryj: we have a draft of a style guide, which might help some: |
| 13:15 |
remingtron |
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_style_guide |
| 13:15 |
|
dMiller_ joined #evergreen |
| 13:16 |
yboston |
though we do not have a high level manual for the workflow for working on documenting new features |
| 13:16 |
alynn26 |
Did you know that duplicate search for Patrons during registration is not documented anywhere? I was looking for any current documentation on it, any body have any they want to share? |
| 13:17 |
remingtron |
alynn26: try Sitka... |
| 13:17 |
remingtron |
http://docs.sitka.bclibraries.ca/Sitka/current/html/ |
| 13:17 |
alynn26 |
They have it on registration, but not the duplicate searching that happens. |
| 13:18 |
jvwoolf |
Since we're talking about workflow, I have been wondering about something... |
| 13:18 |
yboston |
maryj: for the most part, 1) we look at the new feature docs to do list 2) we look over the release notes entry 3) determine if the feature warrants a new section in manual or just a bit of new content in an exisitng section; maybe just replacing an existing screenshot in the docs with a new er screenshot |
| 13:19 |
remingtron |
maryj: and half the time we discover a totally missing section, which makes that little job into a big job |
| 13:19 |
maryj |
yboston: Is this the point where I ask for a wiki account? :) |
| 13:19 |
remingtron |
that's when you email the list and ask for help :) |
| 13:19 |
maryj |
remingtron: It is happens |
| 13:20 |
maryj |
*It happens often enough |
| 13:21 |
jvwoolf |
I had gone to the GITHUB source to copy the original documentation for My Account in the OPAC with the ASCIIDoc formatting |
| 13:21 |
jvwoolf |
It's a big document |
| 13:22 |
maryj |
remingtron: and thank you for the style guide link |
| 13:22 |
remingtron |
maryj: you're welcome! |
| 13:22 |
kmlussier |
yboston: You should copy and paste those steps into a wiki page so that we have the starter page for documentation on how we document. |
| 13:23 |
maryj |
we're getting very meta here ;) |
| 13:23 |
kmlussier |
maryj: I can set you up with a wiki account if yboston doesn't beat me to it. Just send me your email in a pm. |
| 13:23 |
yboston |
:) |
| 13:23 |
maryj |
kmlussier: perfect. Thank you! |
| 13:23 |
* kmlussier |
thought she had already done this for maryj, but must be thinking of wordpress |
| 13:23 |
jvwoolf |
Would you prefer that I copy and make changes to a small section of that document and tell you where to insert it in the file, or does it make sense to copy the whole thing and submit it to someone with commit priveleges after I've made my changes? |
| 13:23 |
maryj |
You are thinking of wordpress, kmlussier :) |
| 13:23 |
yboston |
kmlussier: can you do it this time, so I can finsish pushing somehting from soem volunteers |
| 13:24 |
kmlussier |
yboston: Yes I can! |
| 13:24 |
kmlussier |
Anything to distract myself from billing documentation. :P |
| 13:25 |
remingtron |
jvwoolf: if you have a github account, you can make your changes directly to the file on github, then submit a pull request |
| 13:26 |
remingtron |
jvwoolf: otherwise, whichever way is easier for you. |
| 13:26 |
jvwoolf |
Oh, good deal! |
| 13:26 |
jvwoolf |
remingtron: Thank you. |
| 13:26 |
remingtron |
jvwoolf: you're welcome |
| 13:28 |
remingtron |
yboston / kmlussier : for the record: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:how-to-contribute-documentation |
| 13:29 |
kmlussier |
remingtron: Yeah, that's a page I refer too often. Thanks for the reminder. |
| 13:29 |
kmlussier |
I wish I had gone there earlier today when trying to remember how to convert my asciidoc file. |
| 13:36 |
yboston |
I just added my version of the high-level workflow for docuemnting new features to this page http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.9_needs&#high_level_workflow_for_documenting_new_eg_features |
| 13:36 |
yboston |
maryj: check out my edit here to help guide you http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.9_needs&#high_level_workflow_for_documenting_new_eg_features |
| 13:37 |
kmlussier |
yboston++ |
| 13:37 |
yboston |
near the end I referenced remingtron link: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:how-to-contribute-documentation |
| 13:37 |
maryj |
yboston++ |
| 13:38 |
yboston |
folks, feel free to make edits to what I wrote |
| 13:41 |
kmlussier |
Not only is DIG hack-a-way day a great way to get new docs, but it's also a good opportunity to get another round of bug checking done before the full release is out. |
| 13:41 |
* kmlussier |
just found a bug. :) |
| 13:53 |
* maryj |
may have just found a bug also |
| 13:55 |
bshum |
Nobody seems to kick the tires on the alpha/beta/rc testing like we used to. |
| 13:55 |
kmlussier |
bshum: Speak for yourself. I still kick tires. :) |
| 13:56 |
maryj |
kmlussier: there isn't a library setting for the test server to activate the holds, is there? Inability to place holds in staff client and in OPAC. No error messages, just reloads the screen. |
| 13:56 |
maryj |
*reloads the holds screen |
| 13:56 |
bshum |
maryj: Make sure you have a good pickup location selected |
| 13:56 |
kmlussier |
Are you logged in as admin? |
| 13:57 |
bshum |
That's a common bug that happens with the admin account. |
| 13:57 |
maryj |
kmlussier: yes |
| 13:57 |
kmlussier |
Yeah, pickup location was where I was going with that question. It defaults to consortium for the admin login. |
| 13:57 |
maryj |
and bshum is correct |
| 13:57 |
maryj |
Consortium is automatically selected rather than a branch |
| 13:57 |
maryj |
D'oh! Live and learn |
| 13:57 |
maryj |
I feel (slightly) more sane. Thank you. |
| 13:57 |
kmlussier |
maryj: When you start making that mistake on a weekly basis, as I do, you learn to recognize the signs. :) |
| 13:58 |
maryj |
I'm too used to my fake patrons, obviously, kmlussier. ^_^ |
| 14:01 |
kmlussier |
This might be helpful for the DIG people using the demo server. We do have a list of Concerto logins available at http://evergreen-ils.org/dokuwiki/doku.php?id=qa:concerto_logins that will work on the server. |
| 14:01 |
maryj |
kmlussier++ |
| 14:17 |
pinesol_green |
[evergreen|Lynn Floyd] Docs: Link in catalog to clear Added Content cache - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8626fb0> |
| 14:22 |
* jeff |
eyes OpenILS::SIP::clean_text |
| 14:24 |
kmlussier |
Huh...when I tested the last piece of the negative billing code, I could have sworn that "Adjust to zero" option replaced the void option. But the void option is still there. |
| 14:24 |
kmlussier |
And is producing negative balances when I said to prohibit them. :( |
| 14:26 |
kmlussier |
I must have been in a rush that day. |
| 14:27 |
|
akilsdonk_ joined #evergreen |
| 14:27 |
remingtron |
kmlussier: seems like it's not working right? you could try running the tests |
| 14:27 |
kmlussier |
remingtron: No, I don't think it would be picked up by the tests. It was a UI element that was going to be removed, but was not removed. |
| 14:28 |
kmlussier |
It's something I should be able to fix. |
| 14:28 |
remingtron |
kmlussier: ah, I see |
| 14:32 |
maryj |
another new question: Is there a location off of github where the official manual for 2.9 is? Or are we waiting for after this hackfest to publish it? (I ask because of the High Level Workflow 2.a. mentions "the official manual" & I wanted to include a correct link.) |
| 14:33 |
remingtron |
maryj: the official docs are built from the master code repository every night, and they end up here: http://docs.evergreen-ils.org/ |
| 14:37 |
maryj |
remingtron: And there is no link for 2.9 at http://docs.evergreen-ils.org/ |
| 14:37 |
remingtron |
maryj: right, currently we are using the "dev" link |
| 14:37 |
remingtron |
that will be copied into 2.9 when it is released |
| 14:37 |
maryj |
remningtron: I know there's several ways to skin a rabbit (or to link to documents) so I wanted to be sure. |
| 14:39 |
remingtron |
maryj: hmm, I guess I should ask more about what you are doing |
| 14:40 |
remingtron |
maryj: are you linking from a doc to another doc? If so, there's a simple way to do internal links |
| 14:40 |
remingtron |
well, kinda simple |
| 14:40 |
maryj |
remingtron: I don't even know where the doc is to begin with. |
| 14:41 |
maryj |
remingtron: I am looking for the 'dev' link you're referring to, but I don't know if it is on git, if it is in the wiki, if it is elsewhere |
| 14:41 |
maryj |
I'm looking for context |
| 14:41 |
kmlussier |
maryj: http://docs.evergreen-ils.org/dev/ |
| 14:42 |
remingtron |
maryj: right, sorry for not explaining more |
| 14:42 |
remingtron |
github has the code, and docs.evergreen-ils.org has the HTML version that is generated from the code every night. |
| 14:43 |
maryj |
remingtron: no worries. I appreciate you interacting with me in the first place. |
| 14:43 |
maryj |
thank you kmlussier |
| 14:44 |
remingtron |
maryj: I'm glad to help. Let me know if you have other questions. |
| 14:44 |
maryj |
remingtron: which is a really nice automated set-up. |
| 14:44 |
kmlussier |
Heh...I think I found the commit that created the refund error. I think I can fix that one too. :) |
| 14:44 |
maryj |
will do |
| 14:45 |
remingtron |
I usually search on http://docs.evergreen-ils.org/ for the content I'm looking for, then guess at the file name and location in the code. |
| 14:51 |
|
Shae joined #evergreen |
| 14:52 |
|
sandbergja joined #evergreen |
| 15:10 |
|
akilsdonk joined #evergreen |
| 15:12 |
Stompro |
Is there a keyboard shortcut/hotkey for logging out of the client quickly? |
| 15:14 |
jboyer-isl |
Stompro: Ctrl+Nope. |
| 15:16 |
jboyer-isl |
If I'm in a hurry to close it I'll right click the taskbar icon and choose Close All Windows, but if you just want to log out and back on you have to go to the login window to do it. |
| 15:17 |
jboyer-isl |
Would the Switch User function help? (good for staff taking a break, going to lunch, etc.) or do you mean permanent login changes? |
| 15:27 |
* kmlussier |
hunts around on her keyboard to find the Nope key. |
| 15:28 |
Bmagic |
kmlussier: I believe this issue is due to the vendorcode (or suffix as they call it). kmlussier++ |
| 15:29 |
kmlussier |
Bmagic: Excellent! I'm happy to hear you found a solution. |
| 15:29 |
mmorgan |
@who stole kmlussier's Nope key? |
| 15:29 |
pinesol_green |
mtj_ stole kmlussier's Nope key. |
| 15:30 |
Stompro |
jboyer-isl, I was hoping for something that would quicly log out, so if your walking away from a staff station, you hit the key and log out before you go, so it is ready for someone else to walk up and log in. The switch user only works if the new user is right there. It can be canceled which goes back to the original user that was logged in. |
| 15:31 |
Stompro |
I'm pushing for only having individual logins for our new Evergreen system, no more shared branch logins. |
| 15:32 |
Stompro |
If a grocery store clerk or a bank teller are required only be logged into their stations when they are present, I think that our librarians can be expected to take the same sort of steps to protect patron privacy. |
| 15:33 |
tsbere |
Stompro: Generic "only enough permissions to log in" staff users, switch user to real, switch back to the generic when walking away? |
| 15:35 |
mmorgan |
Stompro: From the login window Alt+f executes Log off, which closes the client window. But users would first have to shift focus to the login window, then execute the keystroke. |
| 15:35 |
jboyer-isl |
Stompro: ++ (and +++++++++++) to the idea of individual logins, but you're right, there's no good way to logout that's not slow on log-in. tsbere's suggestion is a good way to approximate it though. |
| 15:36 |
Stompro |
tsbere, I wanted to avoid to levels of logins also. One way I'm trying to sell this is that the staff will only need to remember their own account, nothing else, even when the sub at another location, they only need to know their own account.) It only takes about 10 seconds for me to log in once the client is running? How long does it take for yours to load? |
| 15:36 |
Stompro |
that second to=two |
| 15:36 |
tsbere |
Stompro: You can skip the need to know the generic account info by embedding it into the shortcuts |
| 15:36 |
alynn26 |
tsbere: that is what we do here. We have Generic logins that are basic staff logins only. Then when the staff member uses the switch user. |
| 15:38 |
Stompro |
tsbere, alynn26 thanks, I'll keep that in mind if we run into a problem with how long logging in takes. |
| 15:38 |
|
dMiller_ joined #evergreen |
| 15:59 |
kmlussier |
OK, I'm going to wrap up documenting for the moment, but I'll continue tomorrow. Need to head home before the traffic to the Patriots game gets too heavy. |
| 15:59 |
kmlussier |
But I think a karma party is in order for all the documentation happening today. |
| 15:59 |
kmlussier |
yboston++ remingtron++ Stompro++ maryj++ akilsdonk++ alynn26++ |
| 16:00 |
kmlussier |
jvwoolf++ |
| 16:00 |
remingtron |
kmlussier++ #and everybody else too |
| 16:00 |
kmlussier |
I wasn't in the Hangout, so I don't know if I'm missing anyone from there. |
| 16:00 |
kmlussier |
DIG++ |
| 16:02 |
|
jlitrell joined #evergreen |
| 16:18 |
yboston |
Dyrcona: I am glad there is no rel_2_9 branch yet, so that the DIG work from today only has to get pushed to master :) |
| 16:25 |
maryj |
yboston: so do you want us to commit directly to the dev docs for today's work? |
| 16:27 |
yboston |
maryj: most DIG volunteers just email the DIG list with their finsished docuemtnation or the works in progress |
| 16:27 |
yboston |
maryj: then one of the few DIG volunteers that has permission to push commits to the repo will push the new content in |
| 16:27 |
yboston |
maryj: lately DIG has been using Gitbub.com's |
| 16:28 |
yboston |
….Gist feature |
| 16:29 |
yboston |
to share AsciiDoc formatted content for easy collaborating and sharing. Also Gists help check your Asciidoc. Though using AsciiDoc is not required |
| 16:30 |
maryj |
yboston: I see. I have everything but the headers formatted via AsciiDoc, and the headers that I have are more contextual for where to put the edited/added content. |
| 16:32 |
|
dMiller_ joined #evergreen |
| 16:34 |
yboston |
maryj: that should eb fine, one of us can look it over and add soem asciidoc where it is needed |
| 16:34 |
yboston |
maryj: just send what ever text content you have and any screenshots tot he EG list; and one of the EG volunteers will get back to you if we have any questions |
| 16:35 |
yboston |
maryj: BTW, have we met yet? |
| 16:35 |
maryj |
We may have, yboston, if you were in Vancouver during the Evergreen conference then. |
| 16:36 |
yboston |
maryj: I was defiently there. What system are you with? |
| 16:36 |
yboston |
maryj: Also, thanks for helping out and for explaining to us what you did not understand from our process |
| 16:38 |
maryj |
yboston: back then, I was one of the student notetakers. I worked for the BC Coop doing not-so-EG-related things before ending up at Equinox. :) |
| 16:39 |
maryj |
yboston: my pleasure! I'm looking forward to contributing more in the future. |
| 16:40 |
|
ericar joined #evergreen |
| 16:52 |
yboston |
maryj: congrats on the move to ESI |
| 16:54 |
maryj |
yboston: Thanks! |
| 16:55 |
maryj |
okay y'all - I'll have my one remaining piece of acq documentation in tomorrow. Have a good evening! |
| 16:57 |
yboston |
you too |
| 16:59 |
gmcharlt |
@coin |
| 16:59 |
pinesol_green |
gmcharlt: heads |
| 17:07 |
|
mmorgan left #evergreen |
| 17:14 |
|
dMiller_ joined #evergreen |
| 17:18 |
pinesol_green |
[evergreen|Christine Burns] Docs: New link to My Lists - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=805d4d6> |
| 17:28 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:30 |
|
rlefaive joined #evergreen |
| 17:31 |
|
dMiller_ joined #evergreen |
| 17:45 |
Bmagic |
does evergreen record user logins paired with actor.workstation ? |
| 17:45 |
Bmagic |
actor.usr_activity connected to actor.workstation ? |
| 17:48 |
Bmagic |
I have a theory that a workstation somewhere is registered to the wrong branch and I was going to find logins to a workstation that doesn't belong to the user's home_ou |
| 18:12 |
gsams |
Bmagic: not sure this is helpful, but you could cross reference the usr_activity table with your activity log, which should contain the workstation name, complete with OU. Not sure that helps much, but it is something. |
| 18:13 |
gsams |
That's the only connecting place I could find both the login username and the workstation, but it doesn't contain home ou. |
| 18:36 |
jeffdavis |
miker: really dumb question: after applying the changes from bug 1485374 (and the corresponding OpenSRF stuff), I should expect to see timestamps saved in the database with the client timezone? |
| 18:36 |
pinesol_green |
Launchpad bug 1485374 in Evergreen "Use client TZ in the database when supplied to the server" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1485374 |
| 18:37 |
jeffdavis |
i.e. if the db uses America/New York by default and my computer is using America/Vancouver as its timezone, any timestamps I enter or generate should be saved as 2015-01-01 12:00:00-07 rather than 14:00:00-04 or whatever? |
| 18:40 |
miker |
jeffdavis: nope. display tz is /always/ the client tz |
| 18:41 |
miker |
time should be shifted the the real world time of the event regardless of tz, though |
| 18:42 |
miker |
make sense? |
| 18:53 |
jeffdavis |
I think so. Thanks. |
| 19:03 |
|
dMiller_ joined #evergreen |
| 19:20 |
|
jwoodard_tablet joined #evergreen |
| 19:29 |
|
bmills joined #evergreen |
| 19:38 |
|
jwoodard_tablet joined #evergreen |
| 20:43 |
|
gdunbar joined #evergreen |
| 20:53 |
kmlussier |
@sortinghat |
| 20:53 |
pinesol_green |
Hmm... kmlussier... Let me see now... HUFFLEPUFF! |
| 20:53 |
kmlussier |
Figures |
| 21:30 |
kmlussier |
@librarian |
| 21:30 |
pinesol_green |
kmlussier: Management:14, Cataloging:14, Acquisitions:17, Reference:12, Circulation:7, Systems:11, Research:15, Custodial:10 |
| 22:23 |
bshum |
@sortinghat |
| 22:23 |
pinesol_green |
Hmm... bshum... Let me see now... HUFFLEPUFF! |
| 22:23 |
bshum |
Hehe |
| 22:44 |
|
gdunbar joined #evergreen |
