| Time |
Nick |
Message |
| 00:03 |
|
dbwells_ joined #evergreen |
| 01:22 |
|
timlaptop joined #evergreen |
| 01:43 |
|
fem joined #evergreen |
| 01:43 |
fem |
hello |
| 01:44 |
fem |
can i ask question? I hope someone will help me.. |
| 05:47 |
|
ktomita_ joined #evergreen |
| 07:33 |
|
rjackson-isl joined #evergreen |
| 07:49 |
|
jboyer-isl joined #evergreen |
| 07:52 |
|
krvmga joined #evergreen |
| 07:54 |
|
kmlussier joined #evergreen |
| 08:06 |
|
collum joined #evergreen |
| 08:18 |
|
akilsdonk joined #evergreen |
| 08:19 |
bshum |
@later tell Dyrcona Well, fwiw, libyaz 4.2.69 works properly with simple2zoom as far as I can tell (so they fixed some broken regressions). Looks like yaz 5.0.0 only works as a client for me right now, don't see it operating as server yet. |
| 08:19 |
pinesol_green |
bshum: The operation succeeded. |
| 08:20 |
|
akilsdonk_ joined #evergreen |
| 08:41 |
|
Shae joined #evergreen |
| 08:41 |
|
kbeswick joined #evergreen |
| 08:45 |
|
mrpeters joined #evergreen |
| 08:50 |
|
mmorgan joined #evergreen |
| 09:08 |
|
mdriscoll joined #evergreen |
| 09:10 |
|
ericar joined #evergreen |
| 09:10 |
|
Dyrcona joined #evergreen |
| 09:36 |
|
yboston joined #evergreen |
| 10:03 |
|
phasefx joined #evergreen |
| 10:11 |
|
dkyle joined #evergreen |
| 10:45 |
|
gsams joined #evergreen |
| 10:51 |
pinesol_green |
[evergreen|Jason Stephenson] Fix an omission in the log redaction configuration. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=f6985d5> |
| 10:51 |
pinesol_green |
[evergreen|Ben Shum] LP#1066141: add authtoken check and related permission for age to lost function - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=adf0af2> |
| 10:51 |
pinesol_green |
[evergreen|Michael Peters] LP#1207281 Prevent download of offline patron list without authentication - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=df6f41a> |
| 10:51 |
pinesol_green |
[evergreen|Galen Charlton] LP#1207281: require SSL when downloading offline patron list - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=82ac0e6> |
| 10:54 |
* phasefx |
still uses squeeze for his dev environment, getting this installing debian-squeeze pre-reqs: E: Package 'libyaz-dev' has no installation candidate |
| 10:55 |
phasefx |
libyaz4-dev or libyaz3-dev |
| 10:56 |
phasefx |
libyaz4 |
| 10:57 |
* Dyrcona |
uses libyaz5 as of the other day. |
| 10:58 |
Dyrcona |
And just got a later from bshum saying it doesn't work with the server. |
| 10:58 |
bshum |
Dyrcona: Well, I didn't try forcing use of libyaz5 now that I think about it. |
| 10:58 |
bshum |
It only just installed the yaz-client one maybe |
| 10:59 |
bshum |
I'm going to give that a try when z39.50 is quieter |
| 11:00 |
bshum |
Well, phasefx, when I try installing libyaz-dev on one of my squeeze boxes, it just spits a "Note, selecting 'libyaz4-dev' instead of 'libyaz-dev'" |
| 11:00 |
bshum |
And carries on |
| 11:01 |
bshum |
Maybe there's a problem with the source, or maybe something weird in the backports |
| 11:01 |
Dyrcona |
bshum: Do you have the index data repo setup on that machine? |
| 11:01 |
bshum |
Dyrcona: Not the squeeze box, it's one of my load balancers. |
| 11:01 |
bshum |
So it doesn't have anything related to this stuff installed on it |
| 11:02 |
phasefx |
bshum: may be lots of cruft with this server. pristine wheezy knows to use libyaz4-dev |
| 11:03 |
Dyrcona |
I'm going to build a new vm from scratch today. |
| 11:03 |
Dyrcona |
Did a database reload yesterday and got tangled up in merge conflicts. |
| 11:04 |
bshum |
Dyrcona: Before you guys upgrade to latest master, we should definitely get bug 1233343 settled. So that you don't have to reingest too many extra times. |
| 11:04 |
pinesol_green |
Launchpad bug 1233343 in Evergreen "alternative title indexing in broken in 2.5" (affected: 1, heat: 6) [Medium,Confirmed] https://launchpad.net/bugs/1233343 |
| 11:07 |
Dyrcona |
I'll add that to my list of things to look at. |
| 11:10 |
|
smyers_ joined #evergreen |
| 11:13 |
bshum |
Dyrcona: So I have to fiddle with simple2zoom, it seems to fall back to yaz4 when setting up the z3950 process. |
| 11:13 |
bshum |
Maybe later tonight or tomorrow |
| 11:13 |
bshum |
Then I can see if yaz5 is fine |
| 11:13 |
bshum |
Or actually, I could setup another VM to look at it... |
| 11:13 |
bshum |
Hmm |
| 11:15 |
|
yboston_ joined #evergreen |
| 11:59 |
|
jdouma joined #evergreen |
| 12:04 |
remingtron |
depesz++ #just found that sqlfiddle.com uses explain.depesz.com |
| 12:16 |
depesz |
nice. wasn't aware |
| 12:21 |
|
CarrieC joined #evergreen |
| 12:24 |
krvmga |
would it be difficult for me to add a Basic Search link to the portal page in the staff client? |
| 12:24 |
krvmga |
i've gotten requests to have the default search open to Basic Search rather than Advanced Search |
| 12:25 |
krvmga |
but there are people who like it opening on Advanced Search, too |
| 12:25 |
krvmga |
i thought maybe a link on the portal page would be a workable compromise |
| 12:25 |
bshum |
krvmga: The portal page is pretty simple html. I wouldn't expect it to be extremely difficult and you've got some examples there to work with. |
| 12:27 |
bshum |
I've found the trick is figuring out how much information is too much information. |
| 12:27 |
krvmga |
the line in index.xhtml that i think sends it to Advanced Search is "try { catalog(false); } catch(E) { alert(E); }" |
| 12:27 |
bshum |
And dealing with the size of the content on that page and the screen size of various folk |
| 12:28 |
bshum |
As a side question though, what's on the basic search that's better than the advanced search? Or is this an asthetics choice? |
| 12:29 |
krvmga |
bshum: since i put in the new format filters, i think most people are preferring basic search to advanced unless they need numeric or expert tabs |
| 12:31 |
krvmga |
the only difference between our basic and advanced searches are in relatively little used features |
| 12:32 |
krvmga |
for most users |
| 12:34 |
krvmga |
difference = differences |
| 12:37 |
|
natschil joined #evergreen |
| 12:46 |
kmlussier |
eeevil: A question about the script you created to generate the release notes file. If I wanted to add a new category (SIP) and just created a new directory in the RELEASE_NOTES_NEXT directory, would it automatically pick up on that new directory? |
| 12:54 |
|
rfrasur joined #evergreen |
| 12:54 |
|
rfrasur_ joined #evergreen |
| 12:54 |
|
rfrasur_ joined #evergreen |
| 13:05 |
rfrasur_ |
does anyone, offhand, know/remember the name of an OS image management system? |
| 13:06 |
Dyrcona |
ghost |
| 13:06 |
rfrasur_ |
diff kinda image, I think. I mean just digital pictures. |
| 13:07 |
rfrasur_ |
It's Greenstone. I didn't describe it well. Sorry. |
| 13:09 |
|
remingtron joined #evergreen |
| 13:10 |
|
dbwells joined #evergreen |
| 13:12 |
|
Michal_ joined #evergreen |
| 13:13 |
eeevil |
kmlussier: I shall look ... unsure |
| 13:14 |
Michal_ |
hello all, |
| 13:14 |
Michal_ |
I have a problem with Evergreen VirtualBox Appliances. Shown on the login / password do not match egsa. How to connect with client staff? |
| 13:15 |
Dyrcona |
rfrasur_: ok. I was thinking of disk/operating system images, obviously. |
| 13:15 |
Dyrcona |
There's one for the Linux/Gnome environment called ShotWell. |
| 13:15 |
rfrasur_ |
No worries. I didn't think multiple meaning of images til you responded. |
| 13:16 |
rfrasur_ |
Hmm, I might have to try to get a linux machine running again....as in try again....not as in get it running again. |
| 13:17 |
* rfrasur_ |
has never succeeded. |
| 13:17 |
Michal_ |
The root account in gentoo you can get. But I can not connect to client staff. Wrong password / login |
| 13:18 |
bshum |
Michal_: I think edoceo is managing that server, I don't see him in channel at the moment. |
| 13:18 |
bshum |
Presumably someone might have changed it wrongly or it needs to be reset again. |
| 13:19 |
bshum |
Or wait, you say virtualbox appliances? |
| 13:19 |
eeevil |
kmlussier: yes, looks like a new directory name will create a new section and heading |
| 13:19 |
bshum |
Oh... gah, I thought we removed all of them. |
| 13:19 |
* bshum |
doesn't know anything about that one edoceo linked to |
| 13:20 |
Michal_ |
And will someone Evergreen VirtualBox Appliances |
| 13:20 |
eeevil |
kmlussier: and any .txt files that remain in the top of RELEASE_NOTES_NEXT get tossed in a "Miscellaneous" section at the end |
| 13:21 |
eeevil |
kmlussier: also, that script is still just on offer in working/collab/miker/release-notes-proposal AFAIK |
| 13:21 |
eeevil |
kmlussier: oh! no, I see I'm wrong, it's in master. cool! |
| 13:22 |
Michal_ |
And is there any way to change the password and username? |
| 13:23 |
senator |
Michal_: where did you get this evergreen virtualbox appliance? unfortunately, it's likely you're using something that is very old and/or unsupported |
| 13:23 |
bshum |
senator: It looks like there's still VM links on the http://evergreen-ils.org/dokuwiki/doku.php?id=community_servers |
| 13:24 |
bshum |
I'd consider those unsupported |
| 13:24 |
* bshum |
thought we had removed all of them |
| 13:25 |
Michal_ |
senator: http://evergreen-ils.org/dokuwiki/doku.php?id=community_servers |
| 13:25 |
bshum |
My gut feeling is that maybe the password isn't wrong but it's something else. Like the startup doesn't actually bring up Evergreen fully. Or it's a certificate error of some kind. |
| 13:26 |
senator |
Michal_: i'm afraid that's our mistake for having that on our wiki without a clear disclaimer saying it's unsupported by the wider community |
| 13:26 |
senator |
only edoceo can help you with that |
| 13:27 |
Michal_ |
how to catch them on this channel? |
| 13:28 |
bshum |
@seen edoceo |
| 13:28 |
pinesol_green |
bshum: edoceo was last seen in #evergreen 1 week, 0 days, 20 hours, 43 minutes, and 51 seconds ago: <edoceo> will do |
| 13:28 |
bshum |
Michal_: I'm not sure when edoceo will show up next. IRC users all keep to their own schedules I've gathered. |
| 13:28 |
Michal_ |
Does anyone else have them e-mail because the site can not find? |
| 13:29 |
Michal_ |
@seen edoceo |
| 13:29 |
pinesol_green |
Michal_: edoceo was last seen in #evergreen 1 week, 0 days, 20 hours, 44 minutes, and 56 seconds ago: <edoceo> will do |
| 13:29 |
Michal_ |
ok |
| 13:30 |
bshum |
senator++ #thanks, I was about to go edit the page and see you've done so |
| 13:33 |
bshum |
Oh man, that virtual is all sorts of borked |
| 13:33 |
* bshum |
just downloaded a copy and imported into his virtualbox |
| 13:33 |
senator |
yeah, my disclaimer may be too mild |
| 13:33 |
senator |
i would back you up if you feel like the link should simply be removed |
| 13:34 |
bshum |
Gentoo, so opensrf is complaining pretty loudly about errors because of the PID issues |
| 13:34 |
bshum |
From a bad reset |
| 13:34 |
moodaepo |
bshum++ senator++ |
| 13:35 |
bshum |
Well, it just spits alot of noise, but I guess it's "working" |
| 13:35 |
Michal_ |
after running a gentoo enters root login root password to enter. But what's next? |
| 13:36 |
bshum |
Michal_: Well, I'm not edoceo, but I'd say he needs to give better instructions about how to start up Evergreen properly. |
| 13:36 |
bshum |
Michal_: If you switch over to the opensrf user, and then issue "osrf_ctl.sh -l -a start_all" it'll do a proper startup of the Evergreen services. |
| 13:36 |
bshum |
And restart apache for good measure |
| 13:36 |
bshum |
But personally, I'm not sure I'd really recommend using this virtual image. |
| 13:37 |
bshum |
It's not very helpful as a demonstration tool in this state. |
| 13:38 |
bshum |
senator: I'm going to remove the link until edoceo can do some better explanation of the virtual image / update it. It's old and not helpful at this point. |
| 13:38 |
senator |
bshum++ |
| 13:40 |
* bshum |
needs more hours in his life. |
| 13:40 |
kmlussier |
eeevil: Thanks! :) |
| 13:40 |
Michal_ |
And if someone could do the image on virtualbox and put on the evergreen-ils?\ |
| 13:41 |
rfrasur_ |
bshum_cloning++ |
| 13:46 |
mrpeters |
Michal_: its far easier to install evergreen yourself at this point than it is for someone to build you a virtualbox |
| 13:46 |
mrpeters |
the instructions these days are very detailed and clear, first install OpenSRF then install your chosen Evergreen version. Both have really good documentation for installation. |
| 13:47 |
|
rsoulliere joined #evergreen |
| 13:48 |
rfrasur_ |
kmlussier: yboston: just calendar clarification. DIG meeting today at 2:00 p.m. EST, right? |
| 13:48 |
kmlussier |
yup |
| 13:48 |
rfrasur_ |
rock on |
| 13:49 |
* rfrasur_ |
might be a few minutes late but will be here |
| 13:50 |
yboston |
rfrasur: yes, the monthly DIG meeting starts at 2 PM EST |
| 14:00 |
yboston |
#startmeeting 2013-09-05 - DIG Monthly Meeting Evergreen Documentation Interest Group (DIG) Monthly Meeting. |
| 14:00 |
pinesol_green |
Meeting started Thu Oct 3 14:00:29 2013 US/Eastern. The chair is yboston. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 14:00 |
pinesol_green |
The meeting name has been set to '2013_09_05___dig_monthly_meeting_evergreen_documentation_interest_group__dig__monthly_meeting_' |
| 14:00 |
yboston |
The agenda can be found here http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meeting_20131003-agenda |
| 14:01 |
yboston |
#topic Introductions |
| 14:01 |
yboston |
Please feel free to start introducing yourselves... |
| 14:01 |
* yboston |
is Yamil Suarez @ Berklee college of Music - DIG meetings facilitator |
| 14:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:01 |
* rsoulliere |
is Robert Soulliere, Mohawk College |
| 14:01 |
remingtron |
#info remingtron is Remington Steed, Hekman Library, Calvin College |
| 14:02 |
|
ElliotFriend joined #evergreen |
| 14:02 |
rfrasur_ |
#info rfrasur is Ruth Frasur, Hagerstown Library, Evergreen Indiana |
| 14:02 |
ElliotFriend |
#info ElliotFriend is Elliot Voris, McCaslin Library, St. Louis Christian College |
| 14:03 |
bshum |
#info bshum is Ben Shum, Bibliomation |
| 14:04 |
Michal_ |
Or maybe you think of Everegreen Live CD as in KOHA Live CD |
| 14:04 |
yboston |
We can move on (my timer finished), late comers can introduce themselves as they arrive |
| 14:04 |
yboston |
#topic Updates from Content Coordinators |
| 14:05 |
yboston |
I see that we have both Robert and Kathy here, do you guys happen to have something to share? |
| 14:05 |
kmlussier |
I've got a report. |
| 14:05 |
yboston |
no worries id you don't |
| 14:05 |
yboston |
go ahead kathy |
| 14:05 |
kmlussier |
#topic Release Coordinator Report |
| 14:06 |
kmlussier |
#info I have been reviewing the 2.5 release notes for content and completeness |
| 14:06 |
kmlussier |
#info There are a number of new features that do not have release note entries. I have created release notes for some and plan to finish the rest by the end of the day tomorrow. |
| 14:06 |
kmlussier |
#info Once the release notes are complete, I plan to identify features that need new documentation by submitting the doc needs in Launchpad. |
| 14:06 |
kmlussier |
Just a note that, for now, I don't plan to do any LP entries for new features that came from Equinox since they already have people who are working on that documentation. |
| 14:07 |
kmlussier |
Any questions? |
| 14:07 |
yboston |
kmlussier++ |
| 14:08 |
bshum |
kmlussier++ |
| 14:08 |
yboston |
those items you add to LP could be stuff we could work on during the DIG hack-a-way |
| 14:08 |
kmlussier |
Yes, I think that would be a great idea. |
| 14:09 |
* kmlussier |
still has some things she needs to get in from 2.4. :P |
| 14:10 |
remingtron |
kmlussier++ |
| 14:10 |
yboston |
if there are no question or comments at this point, we can consider moving on. |
| 14:11 |
yboston |
OK, Robert did you have something to say talk about today? |
| 14:11 |
rsoulliere |
I have a few items. |
| 14:11 |
rsoulliere |
#topic Conversion Coordinator Report |
| 14:11 |
rsoulliere |
#info A recent discussion on the general list made me wonder if I should convert and move these migrating patron documentation forward from 2.1: |
| 14:11 |
rsoulliere |
#link http://docs.evergreen-ils.org/2.1/html/migratingpatrons.html |
| 14:12 |
yboston |
(you read my mind) |
| 14:12 |
rsoulliere |
I wrote this up a long time ago. Is it still useful? |
| 14:12 |
kmlussier |
+1 |
| 14:12 |
rsoulliere |
I converted it today but just wanted to verify its usefulness before getting it into the repository. |
| 14:12 |
rfrasur_ |
+1 |
| 14:12 |
ElliotFriend |
I found it incredibly useful for our library |
| 14:12 |
yboston |
I want to look at it and test it our, also good to know the author! |
| 14:13 |
rsoulliere |
Another question... |
| 14:13 |
ElliotFriend |
it was exactly what I needed to do, but I was focusing on the 2.4 docs |
| 14:13 |
rsoulliere |
#help Is there an inventory of files needing conversion from docbook available somewhere and being maintained? I remember an inventory was created a while back at a DIG gathering. |
| 14:13 |
rsoulliere |
remington brought this to my attention. |
| 14:14 |
yboston |
I am running behind, one thing you/DIG could try about the patron stuff, is to post your converted version (or the old one) to the dev list to see if they have some additions they would like to add that DIG could add for them |
| 14:14 |
yboston |
(you = Robert) |
| 14:15 |
yboston |
but i think it is probably fine as it is already, but that is the approach I had been taking when I was moving stuff from docbook to asciidoc (by checking with the debs before I converted to see if they had comments) |
| 14:15 |
yboston |
about a list of what need to be converted |
| 14:16 |
yboston |
I worked with an intern to look at conversions |
| 14:16 |
yboston |
the spreadsheet we did at last years DIG hack-a-way confused me a bit |
| 14:16 |
yboston |
so I ended up making a much more detail spreadsheet with the intern |
| 14:17 |
yboston |
it is large and confusing and I have only shared it with two DIG people so far |
| 14:18 |
yboston |
my list has some very useful information, but a lot of my observations of what has/has not been converted to asciidoc is focused on the "Section" levee and not necessary at the chapter level |
| 14:18 |
yboston |
(I'll shut up for now so others can comment) |
| 14:19 |
remingtron |
it seems like we basically need to look over the 2.1 docs online to see if anything valuable has been left out of the current docs, right? |
| 14:19 |
* rfrasur |
is listening more than anything today. |
| 14:20 |
yboston |
yes and no, I want to look at all version, not just 2.1 |
| 14:20 |
kmlussier |
remingtron: When we looked at it during last year's DIG hack-a-way, we went all the way back to 1.6 |
| 14:20 |
kmlussier |
Because there was a decent set of docs for 1.6, and there are several pieces that still haven't been moved up. |
| 14:20 |
remingtron |
sure, that makes sense |
| 14:20 |
kmlussier |
yboston: I think it would be useful to share that spreadsheet with everyone, even if it is somewhat confusing. |
| 14:21 |
yboston |
with my intern I tried to move as much as aI could form 1.6 |
| 14:21 |
remingtron |
I think it would be best to set this project up in a way that we can collaborate |
| 14:21 |
yboston |
since people found it so frustrating to have to look that far back for useful stuff |
| 14:21 |
remingtron |
split up the docs versions and sections, and we can chip away at it until it's done |
| 14:21 |
yboston |
remingtron: that sound fine to me |
| 14:22 |
yboston |
I can share the spreadsheet with everyone as read only for now, and I can take time explaining my terminology at the hack-a-way or online/email |
| 14:23 |
remingtron |
sounds like a good start |
| 14:23 |
kmlussier |
yboston: Did everything your intern did make it into the doc repository? |
| 14:23 |
rsoulliere |
yboston++ |
| 14:23 |
yboston |
sadly, nothing the intern did has made it in yet |
| 14:23 |
yboston |
I wanted to do some basic proofreading first and have to volunteers that have been waiting for me to give them the files |
| 14:24 |
yboston |
I've been too slammed, and I wanted to provide the original source of the converted documents for their comparison |
| 14:24 |
rsoulliere |
Is what is being worked on documented in the outline online: eg. http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.4:outline |
| 14:24 |
yboston |
since some content comes from 1.6 others from 2.1, etc |
| 14:25 |
yboston |
the intern stopped working fro me in June |
| 14:25 |
yboston |
all her work was listed in the one link |
| 14:26 |
yboston |
you posted |
| 14:28 |
kmlussier |
yboston: If you want any help from any of us in getting those files out for review, just let us know. Even if you don't get the original source out there, other people might be able to do that for you. Because I know you're really busy. :) |
| 14:29 |
yboston |
thanks, I had a chat with remingtron today and at the dev hack-a-way about it, so I think he can help me push this forward, and with the help of others |
| 14:30 |
kmlussier |
yboston++ remingtron++ |
| 14:30 |
rsoulliere |
yboston++ remington++ |
| 14:30 |
remingtron |
yboston++ |
| 14:31 |
yboston |
this reminds me that I wanted to start an email thread to have DIG members start finding old stuff to convert to 2.5 at the DIG hack-a-way. though having access to my massive/confusing spreadsheet could help in this |
| 14:32 |
|
rfrasur joined #evergreen |
| 14:33 |
yboston |
any other comments on this or Robert, do you want to mansion other points? |
| 14:33 |
yboston |
(mention) |
| 14:34 |
rsoulliere |
No, that is all for my report. |
| 14:34 |
yboston |
rsoulliere++ |
| 14:34 |
yboston |
any other comments on what we were just discussing? |
| 14:34 |
kmlussier |
rsoulliere++ |
| 14:35 |
remingtron |
rsoulliere++ |
| 14:35 |
yboston |
#action yboston ail share his spreadsheet with an inventory of documentation that needs to be moved to asciidoc |
| 14:35 |
kmlussier |
yboston: Just wondering. Would it be easier to track those needs in Launchpad rather than doing it in the confusing spreadsheet? Since we've talked about adding other doc needs there. |
| 14:36 |
yboston |
#action yboston will start an email thread about finding asciidoc conversion target for DIG hack-a-way |
| 14:36 |
yboston |
the spreadsheet was for me to keep track of how the "prominence" of individual chunks of documentation |
| 14:37 |
yboston |
For example, I used it to track each section of 1.6 to see if it moved to 2.0 |
| 14:38 |
remingtron |
I think whenever we discover a section of docs that went missing, we could document it with a launchpad bug |
| 14:38 |
yboston |
and I checked each section of 2.0 to see if it moved to 2.4, etc |
| 14:38 |
yboston |
remingtron: exactly |
| 14:38 |
kmlussier |
Yes, that makes sense. Thanks! |
| 14:38 |
yboston |
the spreadsheet s for low level research, LP can be used for aissignments |
| 14:39 |
rfrasur |
yboston: yes |
| 14:40 |
rsoulliere |
I had a question about how to ensure new features in release notes make it into the docs going forward? |
| 14:40 |
rsoulliere |
E.g. LDAP configuration is covered in the 2.2 release notes... but never again. |
| 14:40 |
yboston |
I never thought of that |
| 14:40 |
yboston |
I smell another spreadhseet |
| 14:40 |
kmlussier |
I thought everything was automatically moving up now that the docs live with the rest of the code. |
| 14:40 |
|
GeoffSams joined #evergreen |
| 14:41 |
ElliotFriend |
I've run into that issue a few times, for various features |
| 14:41 |
rfrasur |
yboston, are you able to upload that spreadsheet into gdrive so we can take a quick look? |
| 14:42 |
kmlussier |
Or are these things that are mentioned in Release Notes, but never get put into the core documentation? |
| 14:42 |
yboston |
it is already a gdrive spreadsheet, I will share it after the meeting |
| 14:42 |
rsoulliere |
I thought release notes were different since they are new features and should not be repeated in later version? They become old news ;-) |
| 14:42 |
rfrasur |
okay |
| 14:42 |
kmlussier |
rsoulliere: Sure, I think I was misunderstanding your initial question. |
| 14:43 |
* rfrasur |
must be misunderstanding as well. |
| 14:43 |
|
gsams joined #evergreen |
| 14:43 |
yboston |
this could be another parallel fast for the DIG hack-a-way |
| 14:44 |
remingtron |
it sounds like some things from release notes should also be added to the main docs |
| 14:44 |
yboston |
to inventory what has or has not been documented form the older release notes |
| 14:44 |
kmlussier |
rsoulliere: It's a good question. I tried to more clearly identify those doc needs during the last release by doing this - http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:2.4_needs. But, as you can see, not everything got a volunteer to work on docs. |
| 14:44 |
yboston |
(task not fast) |
| 14:44 |
rfrasur |
remingtron, if the new feature is going to impact how people use EG, it'll live on and should have updated documentation, yeah? |
| 14:45 |
ElliotFriend |
rfrasur++ |
| 14:45 |
remingtron |
rfrasur: that's my opinion, yes |
| 14:45 |
rfrasur |
it's one thing if it's a security fix or something...but another if it changes how people interact with the software |
| 14:45 |
remingtron |
right |
| 14:45 |
kmlussier |
But, as I was going through the 2.5 release notes, I was trying to identify features that were already more fully documented as part of the release notes. There were a couple of things I was planning to move into the core docs. |
| 14:45 |
rfrasur |
kmlussier++ |
| 14:46 |
* rfrasur |
is back on the rails |
| 14:46 |
kmlussier |
For example, Dyrcona had good release notes for his PhoneList work and tsbere has basic docs for his floating work. It should probably just go in as is and then a DIG person can improve upon it if they think it's needed. |
| 14:47 |
remingtron |
kmlussier: I think your "2.4 needs" wiki page is a good method and should be repeated for 2.5 |
| 14:47 |
yboston |
that sounds reasonable to me |
| 14:47 |
yboston |
I like those wiki pages, even if we shift some of the info to LP too |
| 14:47 |
kmlussier |
remingtron: Do you think the wiki page is a good method or Launchpad? I was thinking it might be more easily tracked in Launchpad. |
| 14:47 |
kmlussier |
Or, as yboston, just said, I can hit both. |
| 14:48 |
remingtron |
kmlussier: right, just realised that |
| 14:48 |
remingtron |
let's try launchpad |
| 14:48 |
remingtron |
sure, or both while we transition |
| 14:48 |
yboston |
BTW, me and remingtron recently updated the info on the DIG wikipages, and now there is an empty page for the 2.5 release |
| 14:49 |
yboston |
I just like having high level info on the wiki, then maybe the more specific stuff can go on LP |
| 14:49 |
remingtron |
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.5:outline |
| 14:49 |
rfrasur |
I think there's value in both the wiki and LP. The wiki is a good overview document. |
| 14:50 |
rsoulliere |
I like the wiki as well, especially for reviewing documentation structure and organization. |
| 14:50 |
yboston |
BTW, we are at the 50 minute mark |
| 14:51 |
yboston |
I wanted to talk about the DIG hack-a-way nefpre we wrap up, if that is OK |
| 14:51 |
yboston |
? |
| 14:52 |
yboston |
before we wrap up, sorry for my spelling |
| 14:52 |
rfrasur |
I have a question after you yboston...just a short one |
| 14:53 |
yboston |
go ahead |
| 14:54 |
rfrasur |
well, I'm on the front page of the dokuwiki where the roadmap links are located. I personally like how the different EG versions are linked right there. |
| 14:55 |
rfrasur |
Under the documentation & resources heading, would it possible to have the documentation for the various versions listed in a similar way? Including that needs list? |
| 14:55 |
rfrasur |
or not...or are those things compiled in some place that I'm just not finding in a timely manner? |
| 14:55 |
yboston |
it was down in the past, i thought |
| 14:56 |
rfrasur |
What was down? Down as in not working? |
| 14:57 |
yboston |
sorry "done in the past" |
| 14:58 |
remingtron |
currently, there's a section called "Documentation & Resources" just under the evergreen versions |
| 14:59 |
remingtron |
most of those docs links are very old |
| 15:00 |
rfrasur |
right |
| 15:00 |
rfrasur |
in my mind, that'd be the place to put links to the documentation wiki page(s) |
| 15:01 |
rfrasur |
(this is a longer question than I'd anticipated) |
| 15:01 |
kmlussier |
rfrasur: Sorry, just catching up. You're talking about the links on the wiki page? http://wiki.evergreen-ils.org/doku.php |
| 15:01 |
remingtron |
rfrasur: good thought, I'll put some thought into that section |
| 15:01 |
yboston |
we should probably continue this topic on the mailing list, since we just hit the hour mark, and I wanted to talk briefly about the DIG hack-a-way |
| 15:01 |
rfrasur |
kmlussier: yes remingtron++ |
| 15:02 |
* rfrasur |
listens to yboston |
| 15:02 |
yboston |
#topic DIG hack-a-way |
| 15:02 |
yboston |
any comments or questions about locations? so far I can host a dozen folks at Berklee, and ESI can host too |
| 15:03 |
rfrasur |
I'm going to be talking with our state library as a possible host site for a satellite group |
| 15:03 |
yboston |
start could be at 9:30 AM EST, to give us time to settle in. Some of us can host google hang outs for those working from afar |
| 15:03 |
yboston |
feel free to add ideas to the DIG hack-a-way wiki page, or bring stuff up on the list |
| 15:03 |
ElliotFriend |
I'd likely not be able to get away, I'm assuming participating online is viable? |
| 15:03 |
yboston |
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_hack-a-way |
| 15:03 |
rfrasur |
ElliotFriend: yes. |
| 15:03 |
kmlussier |
ElliotFriend: Yes, we used Google Hangouts last time. |
| 15:04 |
ElliotFriend |
rfrasur: kmlussier thanks |
| 15:04 |
rfrasur |
yboston: do you have a better idea of when to do asciidoc tutorial session? |
| 15:04 |
yboston |
for example, doing an inventory of what documentation from older release notes that has not made it in to the docs could be good to be done form afar |
| 15:05 |
yboston |
about asciidoc training... |
| 15:05 |
yboston |
I will host a Google hangout for asciidoc trainign (unless the techonlogy does not work for me). I will do a doodle poll to find a good date |
| 15:05 |
rfrasur |
yboston++ |
| 15:05 |
yboston |
if it does not work on Google hang out, I wilt try to record the training and then post it to YOutube, I can then host a Q and A session on google hang out before the DIG hack-a-way |
| 15:06 |
* rfrasur |
needs to go help a young lady w/ a research project. |
| 15:06 |
yboston |
rough agenda for asciidoc session woudld be |
| 15:06 |
yboston |
- FAQ about DIG |
| 15:06 |
yboston |
- Asciidoc training |
| 15:06 |
yboston |
- walk through on converting a MS word document into asciidoc |
| 15:06 |
kmlussier |
yboston: If possible, I think it would be best if we could try to do any kind of inventories before the hack-a-way so that we can focus on creating documentation during the actual event. |
| 15:06 |
ElliotFriend |
kmlussier++ |
| 15:06 |
remingtron |
+1 |
| 15:07 |
yboston |
that is why I wanted to start an email thead about finding documentation targets this week |
| 15:07 |
kmlussier |
I would be willing to take on going through old Release Notes. |
| 15:07 |
yboston |
I can add a read only link to my huge spreadsheet |
| 15:08 |
remingtron |
we have some good action items forming here |
| 15:09 |
yboston |
#action yamil will post a doodle poll for finding a date for asciidoc training |
| 15:09 |
yboston |
#action yboston will post a doodle poll for finding a date for asciidoc training |
| 15:09 |
yboston |
any other final comments (I don't want to go too past the hour mark) |
| 15:11 |
yboston |
anything else for now? |
| 15:11 |
kmlussier |
Nothing from me. |
| 15:11 |
ElliotFriend |
none here |
| 15:11 |
remingtron |
one question |
| 15:12 |
yboston |
go ahead |
| 15:12 |
remingtron |
we will try to have the already-converted but not yet proofread docs for the hackaway, yes? |
| 15:13 |
remingtron |
like, made available for people to help with by the hackaway? |
| 15:13 |
yboston |
the ones my intern worked on? |
| 15:13 |
remingtron |
yes |
| 15:13 |
yboston |
yes |
| 15:13 |
remingtron |
cool, thanks, that's it from me |
| 15:14 |
yboston |
BTW, one thing that need to be done is that I pull together a huge amount of docs about cataloging that is in no particular order. someone at the hack a away can come up with a smarter order of the sections |
| 15:14 |
yboston |
unless there ano other questions I will close out the meeting |
| 15:15 |
yboston |
#endmeeting |
| 15:15 |
pinesol_green |
Meeting ended Thu Oct 3 15:15:48 2013 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:15 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-10-03-14.00.html |
| 15:15 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-10-03-14.00.txt |
| 15:15 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-10-03-14.00.log.html |
| 15:15 |
remingtron |
yboston++ |
| 15:16 |
kmlussier |
yboston++ |
| 15:16 |
rsoulliere |
yboston++ |
| 15:16 |
ElliotFriend |
yboston++ |
| 15:16 |
yboston |
muchas gracias amigos |
| 15:28 |
remingtron |
yboston and all: next DIG meeting? just the hackaway? |
| 15:29 |
yboston |
it is not for me to decide, this usually get brought up on the list. this happens when there is a conference coming up too |
| 15:29 |
yboston |
I ca send an email to see what folks think. good question |
| 15:29 |
remingtron |
cool, thanks |
| 15:40 |
|
CarrieC left #evergreen |
| 15:52 |
pinesol_green |
[evergreen|Robert Soulliere] Documentation: Add migrating patron data from 2.1 docs. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ba74324> |
| 16:32 |
|
moodaepo joined #evergreen |
| 16:32 |
|
moodaepo joined #evergreen |
| 16:47 |
|
smyers_ joined #evergreen |
| 17:18 |
|
mmorgan left #evergreen |
| 17:37 |
gsams |
Staff member noticed curious behavior with hold slips just now, didn't see a bug and though I'd ask on it |
| 17:37 |
gsams |
when placing a hold on an item from the item status screen, right click and select request item |
| 17:37 |
gsams |
when checking the item in to print the slip it does't print contact information |
| 17:44 |
bshum |
gsams: Could be a problem with the templates, meaning that the notify_by_* variables aren't set in the body and it doesn't print because of that. |
| 17:44 |
bshum |
Could also be the patron itself, not having proper email info |
| 17:44 |
bshum |
Or could be the patron's selected hold options |
| 17:44 |
bshum |
Meaning, they deselected the option for notify by phone and didn't fill anything in |
| 17:44 |
bshum |
So it didn't print anything |
| 17:46 |
gsams |
Template would explain my computer, but it was correct at the front desk |
| 17:46 |
gsams |
he also ruled out notify settings and details |
| 17:46 |
gsams |
but I'm going to double check right quick |
| 17:48 |
gsams |
yeah, settings are in place, no contact info printed |
| 17:50 |
bshum |
And you checked the hold you're checking in to make sure there's a phone associated with the hold? |
| 17:54 |
* bshum |
wanders off to dinner first. |
| 17:57 |
gsams |
bshum: no worries, not serious anyway, just curious. |
| 17:58 |
gsams |
I don't see a number associated with the hold itself, though I don't know why it wouldn't |
| 18:02 |
bshum |
gsams: If you don't see a hold number that would print with no contact info then. That's what drives the hold slip. |
| 18:02 |
* bshum |
is going to wander, just picking what's a good place to get food on the way home. :) |
| 18:03 |
bshum |
gsams: That can happen if the patron doesn't input something or they don't have a phone associated with them by default, or they deliberately erased the field. |
| 18:03 |
bshum |
Or if the person who placed the hold didn't put in that information. |
| 18:03 |
bshum |
On older versions I don't think it defaults to the user's day phone or whatnot. |
| 18:03 |
bshum |
So it's entirely possible for that to end up blank and confusing for everyone involved. |
| 18:06 |
gsams |
hmm, this particular interface only asks for the barcode and pickup library, it's rather odd compared to other interfaces for placing holds |
| 18:06 |
dbwells |
bshum: I am heading home, but I just posted a branch for bug #1233340 |
| 18:06 |
pinesol_green |
Launchpad bug 1233340 in Evergreen "2.5 serials receiving error" (affected: 2, heat: 12) [Medium,Triaged] https://launchpad.net/bugs/1233340 - Assigned to Dan Wells (dbw2) |
| 18:07 |
dbwells |
bshum: One part of the branch prevents the 'a's from being created, and the other should allow you to receive even if you have the extra 'a's hanging around. |
| 18:07 |
gsams |
bshum: the interface is Item Hold?Recall/Force instead of via the TPAC like I'm used to seeing |
| 18:08 |
bshum |
dbwells: "If going by the book..." I love this commit message already. |
| 18:08 |
bshum |
dbwells: Thanks, I'll be sure to take a look at it. |
| 18:09 |
gsams |
bshum: 'm about to head out, so I'll take a look at it again tomorrow |
| 18:09 |
bshum |
gsams: Alright, good luck till then, but maybe that GUI isn't very good at making holds. Or rather, you shouldn't use it to create holds for regular patron use. |
| 18:09 |
bshum |
Recall/force holds are for staff-only |
| 18:09 |
bshum |
Or normally are used just for staff |
| 18:10 |
bshum |
To like force items back for cataloging purposes |
| 18:10 |
gsams |
yeah, I wasn't even aware of its existance until he brought it up |
| 18:10 |
gsams |
I generally ask them to place holds through the patrons account |
| 18:10 |
bshum |
dbwells++ # we'll toss the thing into production and try receiving stuff and generating new issuances too. |
| 18:10 |
gsams |
AH! He uses that interface to place ILLs on hold |
| 18:11 |
bshum |
(well, testing first, then production if it works) |
| 18:11 |
gsams |
bshum: not going to worry about it, since its only for that purpose and not meant for this sort of process. |
| 19:20 |
|
hbrennan joined #evergreen |
| 19:23 |
gmcharlt |
http://www.loc.gov/today/pr/2013/13-A07.html <-- we haz LC website happiness again |
| 19:23 |
kmlussier |
Yay! :) |
| 19:24 |
hbrennan |
yay! |
| 19:26 |
|
zamboli joined #evergreen |
| 19:30 |
hbrennan |
Hey gmcharlt or bshum, or another website superpower.... is the overall Evergreen website search box missing, or can I just not find it? |
| 19:31 |
hbrennan |
I know that technically I should be able to find something just on Google, but it's not working as nicely |
| 19:31 |
kmlussier |
hbrennan: There's the magnifying glass in the upper right corner, but I'm not sure what it's searching right now. |
| 19:32 |
kmlussier |
I just tried finding something on the wiki there, but didn't have any luck. So It may just be searching the WordPress content. |
| 19:33 |
hbrennan |
Oh gosh, I can't even see the hourglass.... |
| 19:33 |
gmcharlt |
kmlussier: I think the one you're referring to is WP-only (and it shows up only if one is logged into the website) |
| 19:33 |
hbrennan |
Yeah, I used the wiki search too.. but that's definitely not grabbing from all the sources |
| 19:34 |
kmlussier |
Oops. Okay, I'm obviously logged in. :) |
| 19:34 |
hbrennan |
Well at least gmcharlt makes me not look crazy, or blind |
| 19:37 |
kmlussier |
hbrennan: Just looking at the minutes from the last web team meeting. bshum mentioned it as one of the things he still needed to do. |
| 19:37 |
gmcharlt |
yeah |
| 19:38 |
hbrennan |
No worries then. Shoot, I think I missed that meeting. |
| 19:38 |
kmlussier |
No worries. But we handed of downloads page to somebody else because I kept procrastinating. :P |
| 19:38 |
kmlussier |
handed off, not of. |
| 19:39 |
gmcharlt |
hbrennan: are you sure you missed that meeting? I don't recall you having 10 tasks suddenly assigned to you ;) |
| 19:39 |
hbrennan |
Yeah, things have just been nuts here since May. Director had person health crisis, and now we're dealing with a retirement. |
| 19:40 |
hbrennan |
Ahh, is that how it works? I better show up so I don't have to do anything |
| 19:40 |
hbrennan |
and now I'm dealing with a position change. Thanks to our switch to Evergreen I'm becoming "Library Technical Specialist" and working towards my CCNA |
| 19:42 |
gmcharlt |
cool |
| 19:42 |
hbrennan |
Yeah, it really is. I thought I was tech savvy before, just knowing a little HTML and CSS! |
| 19:43 |
hbrennan |
Learning how the internet works it terrifying. I have no clue how things turn out okay so often. |
| 19:43 |
hbrennan |
But now I know why IT people are so calm in disasters |
| 19:45 |
kmlussier |
IT people are calm? :) |
| 19:46 |
hbrennan |
Haha. Calmer than I am when everything breaks! |
| 19:47 |
hbrennan |
So what I'm tasked to do (and why I jumped on here today) is to create a way to feature everything in the location of "New Books" |
| 19:48 |
hbrennan |
I have New Books as a Copy Location Group, so it can be searched |
| 19:49 |
hbrennan |
But Evergreen won't let me hit Search without a keyword/author/etc |
| 19:50 |
hbrennan |
Can I trick it, by creating a link to search results for Search All Formats for (blank) Keyword in New? |
| 19:50 |
kmlussier |
Can you search it with an asterisk? |
| 19:51 |
hbrennan |
Oh yes, and now I have 5,000 results.. |
| 19:51 |
kmlussier |
hbrennan: I know some of our consortia have also used the RSS feed to grab new books. |
| 19:51 |
hbrennan |
That is an amazing trick |
| 19:52 |
hbrennan |
Yeah, that's what I would like to do because we have this fancy Library Thing widget that displays them nicely, as long as we supply a link or RSS |
| 19:52 |
kmlussier |
They then use a script to republish it on their web sites to highlight new books on their web site. |
| 19:52 |
hbrennan |
I've done it plenty of times with booklists staff have created, but never with a whole location |
| 19:54 |
kmlussier |
Using the MVLC catalog, this is the feed for most-recently added bib records. The same format should work for your catalog - http://catalog.mvlc.org/opac/extras/opensearch/1.1/MVLC/rss2-full?searchTerms=sort%28create_date%29%23descending |
| 19:54 |
hbrennan |
Oh awesome |
| 19:54 |
kmlussier |
However, since we're in a consortium, that one isn't very useful for us. An alternative is to use something like: |
| 19:54 |
kmlussier |
http://catalog.mvlc.org/opac/extras/browse/rss2-full/item-age/MCD/ |
| 19:54 |
hbrennan |
that's one thing I love about Evergreen.. the search links are stable! |
| 19:55 |
kmlussier |
MCD identifies one of their branches. The feed should then be looking at the age of MCD's copy instead of the bib record. |
| 19:55 |
hbrennan |
Thanks! Between my search results and those links I should be able to come up with something... we just don't have staff time anymore to keep up with blogging, so we need something that updates itself |
| 19:56 |
hbrennan |
kmlussier++ |
| 19:56 |
kmlussier |
No problem. Good luck! :) |
| 19:57 |
hbrennan |
Thank you! |
