| Time |
Nick |
Message |
| 01:22 |
paxed |
bshum: i guess you meant bug 1221411 fix |
| 01:22 |
pinesol_green |
Launchpad bug 1221411 in Evergreen "Translating the basic search bar is troublesome" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1221411 |
| 01:26 |
|
Mark__T joined #evergreen |
| 01:35 |
|
stevenyvr2 joined #evergreen |
| 01:36 |
|
stevenyvr2 left #evergreen |
| 01:39 |
|
jcamins joined #evergreen |
| 02:33 |
|
jcamins joined #evergreen |
| 03:01 |
|
zxiiro joined #evergreen |
| 03:16 |
|
misilot joined #evergreen |
| 04:36 |
|
mcooper joined #evergreen |
| 06:01 |
|
dboyle joined #evergreen |
| 07:17 |
|
timlaptop joined #evergreen |
| 07:36 |
|
kmlussier joined #evergreen |
| 07:37 |
|
krvmga joined #evergreen |
| 07:38 |
krvmga |
does anyone know how long the URL in a password reset request remains valid? |
| 07:44 |
phasefx |
krvmga: I believe it's configurable *looks* |
| 07:46 |
phasefx |
krvmga: don't know the default yet, but the library setting for it is Self-serve password reset request time-to-live |
| 07:46 |
phasefx |
krvmga: looks like 24 hours for a default |
| 07:47 |
krvmga |
thx :) |
| 07:47 |
krvmga |
phasefx++ |
| 07:48 |
phasefx |
np |
| 07:55 |
kmlussier |
bshum:#dash_identity a float: left in the media view. I think that will fix our problem with the myopac buttons. |
| 08:03 |
bott_otr |
Arrr… do we have t' latest translation prepared for today? |
| 08:04 |
kmlussier |
bott_otr++ |
| 08:04 |
kmlussier |
Thanks for the reminder - I just switched Facebook over to pirate. |
| 08:16 |
|
kmlussier joined #evergreen |
| 08:18 |
|
akilsdonk_ joined #evergreen |
| 08:38 |
|
kbeswick joined #evergreen |
| 08:40 |
|
mrpeters joined #evergreen |
| 08:45 |
|
Shae joined #evergreen |
| 08:48 |
|
ericar joined #evergreen |
| 08:49 |
|
mmorgan joined #evergreen |
| 08:51 |
|
mtj_ joined #evergreen |
| 08:52 |
* mrpeters |
tries again |
| 08:52 |
mrpeters |
Am I dreaming, or did earlier 2.x versions have a library setting that disallowed a user from placing a hold on a bib record for which they had already checked out a related item on? did this by chance get removed/renamed in later 2.4.x versions? did it never exist and I am mistaken? There is an override for staff. |
| 08:55 |
|
DPearl joined #evergreen |
| 08:55 |
dbs |
mrpeters: sounds like something conifer did, not sure if it got into master |
| 08:55 |
mrpeters |
i swear it was in 2.2....hmm |
| 08:56 |
mrpeters |
wonder why the override permission would be there in 2.4 if it never made it to master |
| 08:56 |
phasefx |
I think it was a one-liner back in circ script days, in one of the permit scripts |
| 08:57 |
mrpeters |
nah there was definetly a YAOUS |
| 08:57 |
mrpeters |
i'd swear to it |
| 08:57 |
mrpeters |
the library thinks they used to have it turned on in 2.2 as well |
| 08:59 |
phasefx |
circ.holds.hold_has_copy_at.alert ? |
| 09:00 |
phasefx |
and circ.holds.hold_has_copy_at.block |
| 09:01 |
phasefx |
not quite the same |
| 09:02 |
mmorgan |
mrpeters: Just tested this on our 2.3.7 system. |
| 09:02 |
DPearl |
Is the hackaway in the same library room today? |
| 09:02 |
mmorgan |
Attempted to place a hold on a bib for a patron who had a copy checked out and it was unsuccessful. Problem HOLD_ITEM_ALREADY_CHECKED_OUT with the option to override. |
| 09:03 |
dbs |
bshum: yeesh, the 800px -> 850px has a very bad smell attached to it (the whole px-width thing); why not just put all of the select boxes on a single "line" and let them wrap to the appropriate width? |
| 09:03 |
* dbs |
will demonstrate |
| 09:06 |
phasefx |
mrpeters: I don't see anything that steps in front of hold_item_is_checked_out in Circ/Holds.pm in 2.2; looks like hard-coded behavior |
| 09:06 |
mrpeters |
hmm |
| 09:07 |
DPearl |
bshum: Is the meeting in the same room today? |
| 09:08 |
DPearl |
bshum: never mind |
| 09:11 |
|
kmlussier joined #evergreen |
| 09:15 |
bshum |
dbs: That sounds much better. My brain wasn't working well last night after a certain point, but I didn't want to forget quirks :( |
| 09:15 |
|
Dyrcona joined #evergreen |
| 09:15 |
dbs |
Could be that I don't understand the rationale behind adv block et aj |
| 09:15 |
|
collum joined #evergreen |
| 09:15 |
mmorgan |
mrpeters: phasefx: If my patron is blocked for something else, I don't get the already checked out block when I override. Just another point of info... |
| 09:18 |
mrpeters |
mmorgan: interesting |
| 09:18 |
|
kmlussier joined #evergreen |
| 09:18 |
mrpeters |
i must be mistaken about it being a YAOUS then |
| 09:19 |
remingtron |
DPearl: it's lonely being the first one to be right. |
| 09:20 |
phasefx |
mmorgan: I think all the events stopping a hold are returned from the server, but I'm not sure how they are presented. A single override would work on all of them at once |
| 09:22 |
mmorgan |
phasefx: OK, thanks. I'm assuming if the staff user didn't have permission to override one of the blocks, the override would be unsuccessful. |
| 09:22 |
jeffdavis |
Dyrcona: https://en.wikipedia.org/wiki/Elinor_Ostrom <- this is the person I mentioned when you were talking about the tragedy of the commons |
| 09:23 |
phasefx |
mmorgan: that should be true |
| 09:24 |
mmorgan |
Oh good :) |
| 09:35 |
dbs |
bshum: Oh, I see, this is all tied up with config.tt2 advanced search interface specialness. Ugh. |
| 09:37 |
|
rfrasur joined #evergreen |
| 09:37 |
dbs |
bshum: I guess we could just take out the width:850px from style.css and the first adv_break from config.tt2; it makes sense to separate the sort/pubdate/search libraries from the rest of the filters |
| 09:38 |
dbs |
but it doesn't make sense to me to set an explicit width by default. if sites want to hang themselves with grouping 2 or 3 filter blocks per line, they can go ahead and customize it that way |
| 09:38 |
bshum |
That makes sense |
| 09:39 |
* paxed |
agrees, explicit width is bad |
| 09:39 |
dbs |
While I'm at it I'll move the inline styles into style.css :) |
| 09:39 |
* rfrasur |
also agrees |
| 09:39 |
rfrasur |
Are we hanging out this morning? "we" referring to the mopac working group. |
| 09:40 |
* dbs |
needs to at least get dressed before hanging out :) |
| 09:40 |
* rfrasur |
agrees with that too |
| 09:41 |
bshum |
dbs++ |
| 09:41 |
rfrasur |
clothes++ |
| 09:42 |
rfrasur |
well, clothes_at_appropriate_times++ |
| 09:46 |
bshum |
berick: Filed https://bugs.launchpad.net/evergreen/+bug/1227667 |
| 09:46 |
pinesol_green |
Launchpad bug 1227667 in Evergreen "MARC batch import/export interface doesn't always load variables" (affected: 1, heat: 6) [Medium,Triaged] |
| 09:46 |
bshum |
berick++ |
| 09:47 |
paxed |
i'd go so far as to say no_clothes++ - with some reservations for place, time, and company. |
| 09:47 |
dbs |
sauna++ |
| 09:48 |
paxed |
yes, that. |
| 09:48 |
rfrasur |
that_whole_idea++ |
| 09:53 |
|
kbutler joined #evergreen |
| 09:58 |
eeevil |
new hangout coming soon? |
| 09:59 |
* rfrasur |
shrugs |
| 10:00 |
|
RoganH joined #evergreen |
| 10:05 |
|
tspindler joined #evergreen |
| 10:05 |
dbs |
bshum: dumped one on for you, I have an idea for making things more accessible too; we'll see how that goes. |
| 10:06 |
* dbs |
looks at "subject" "contains" <input> and realizes that accessibility is a pipe dream in advanced land atm |
| 10:10 |
jeff |
$ svn pull |
| 10:10 |
jeff |
Unknown command: 'pull' |
| 10:10 |
jeff |
Type 'svn help' for usage. |
| 10:11 |
* paxed |
can hardly use svn anymore. |
| 10:12 |
|
dboyle joined #evergreen |
| 10:13 |
Dyrcona |
svn? What's that? ;) |
| 10:15 |
* paxed |
gives sourceforge the evil eye |
| 10:18 |
|
bradl joined #evergreen |
| 10:18 |
|
paxed joined #evergreen |
| 10:18 |
|
paxed joined #evergreen |
| 10:22 |
|
bott_otr joined #evergreen |
| 10:27 |
|
yboston joined #evergreen |
| 10:27 |
yboston |
@marc 028 |
| 10:27 |
pinesol_green |
yboston: The formatted number used for sound recordings, printed music, and videorecordings. Publisher's numbers that are given in an unformatted form are recorded in field 500 (General Note). A print constant identifying the kind of publisher number may be generated based on the value in the first indicator position. (Repeatable) [a,b,6,8] |
| 10:28 |
yboston |
@marc 024 |
| 10:28 |
pinesol_green |
yboston: A standard number or code published on an item which cannot be accommodated in another field (e.g., field 020 (International Standard Book Number), 022 (International Standard Serial Number) , and 027 (Standard Technical Report Number)). The type of standard number or code is identified in the first indicator position or in subfield $2 (Source of number or code). (Repeatable) [a,c,d,z,2,6,8] |
| 10:28 |
bshum |
dbs: Hmm, mixed reactions to the filters stretching across the whole screen here. |
| 10:28 |
dbs |
bshum: I'm hardly surprised at mixed reactions. |
| 10:28 |
yboston |
@marc 022 |
| 10:29 |
pinesol_green |
yboston: The ISSN, a unique identification number assigned to a continuing resource. (Repeatable) [a,y,z,2,6,8] |
| 10:29 |
bshum |
We're pondering the pro's and con's. I think folks just need some time to get used to it :) |
| 10:29 |
dbs |
I mean, we could say "Let's design for a maximum of 1024px wide" but the other half of my screen would get sad. |
| 10:30 |
csharp |
eeevil: rfrasur: RoganH is setting up a cam now for hangout, fyi |
| 10:30 |
dbs |
So then we could wrap it all in a <center> tag! |
| 10:30 |
rfrasur |
cool beans. |
| 10:30 |
* rfrasur |
is talking herself off a librarian cliff right now anyway |
| 10:30 |
csharp |
however, so far this morning it's mostly intense typing and not much conversation |
| 10:30 |
* rfrasur |
understands |
| 10:30 |
csharp |
until right this second |
| 10:30 |
dbs |
But the big problem, really, is arbitrary break points (which was what was prompting the 800 vs. 850 right?) |
| 10:30 |
rfrasur |
it's cool. whenever, whatever |
| 10:31 |
kmlussier |
dbs: Sure, I think the arbitrary break points was my concern. You could have a row with 4 filters and then break down to a row with one. |
| 10:31 |
dbs |
"Keep all four of these things on the same line and scroll if my screen width is < $random pixels" |
| 10:33 |
paxed |
dbs: max-width for the container, maybe? |
| 10:34 |
dbs |
paxed: could do that. I guess I don't know _what_ the design goal is, overall. |
| 10:36 |
bshum |
dbs: I think my thinking was that the adv_break in the config.tt2 would be what controlled whether we'd begin new lines right? (or used to before we went to divs anyways) |
| 10:37 |
bshum |
And so it was easier for folks to decide how many per row and deal with the consequences of the width per site |
| 10:37 |
dbs |
bshum: yeah. so we add "clear: both" to adv_filter_block instead of a width px thing |
| 10:38 |
bshum |
Hmm |
| 10:38 |
RoganH |
I was slow on it this morning, not enough caffeine yet. |
| 10:39 |
|
jboyer-laptaupe joined #evergreen |
| 10:39 |
rfrasur |
RoganH, just got the quote survey. Good choices. |
| 10:39 |
bshum |
Hey paxed, we're exploring using something like the approach described in http://css-tricks.com/responsive-data-tables/ |
| 10:40 |
RoganH |
thanks |
| 10:40 |
bshum |
Curious what implications that might have for i18n |
| 10:40 |
bshum |
The CSS seems to contain strings |
| 10:40 |
bshum |
I have a feeling that might be weird? |
| 10:40 |
dbs |
bshum: pushed the clear:both approach to keep things as they were before. |
| 10:41 |
dbs |
If you _really_ want to use flexible boxes, flexbox would be the right way I suppose. |
| 10:41 |
* bshum |
trying to think of constructive ways of dealing with all the crazy table madness in the my account areas with bott |
| 10:41 |
paxed |
bshum: css content:"text goes here" - yes, those should be translatable... |
| 10:41 |
jeff |
well drat. internal server error with no apparent logs. |
| 10:41 |
bshum |
paxed: We're not doing it yet, just pondering options available. |
| 10:42 |
dbs |
kmlussier: so... what do you want to have happen with a row of 4 filters when someone has a page width that's not wide enough to display all four? |
| 10:42 |
paxed |
bshum: ah. inline css generated by tt2, i'd guess... |
| 10:43 |
dbs |
Is there some need to group these rows with an additional label to give the user a hint as to _why_ they're grouped? |
| 10:43 |
|
jboyer-laptaupe joined #evergreen |
| 10:43 |
dbs |
In which case we could add a label + a border to group them, no matter how they break |
| 10:44 |
paxed |
legend? |
| 10:44 |
dbs |
legend-ary! |
| 10:45 |
* rfrasur |
opens "Evergreen 2.4 Testing Documents" with fear and trepidation. |
| 10:45 |
dbs |
Sorry. What I said was, with the current approach, we can remove the special <600px MOPAC CSS |
| 10:45 |
paxed |
koha seems to use legends all over the place. |
| 10:46 |
dbs |
because it's truly responsive, to whatever size of screen you have. |
| 10:47 |
|
atheos_ joined #evergreen |
| 10:48 |
dbs |
And the commit that I just added keeps the adv_break support, so you start a new row when you have adv_break |
| 10:48 |
dbs |
heh |
| 10:50 |
|
shadowspar joined #evergreen |
| 10:52 |
* dbs |
prepares for the influx |
| 10:53 |
jeff |
dee dah doo dee dah doo... |
| 10:58 |
jeff |
i wonder how long URLs like this have been returning 500 errors: https://catalog.berklee.edu/opac/extras/ac/jacket/small/ |
| 10:58 |
jeff |
http works, but https fails due to lack of "SSLProxyEngine on" |
| 10:58 |
jeff |
the apache docs are annoyingly vague on the implications of SSLProxyEngine |
| 11:00 |
remingtron |
re: release manager discussion yesterday, gmcharlt added some helpful comments to the notes doc: http://goo.gl/oGoSUI |
| 11:01 |
senator |
atheos_: working/collab/senator/opac-stripe |
| 11:05 |
csharp |
@blame everyone |
| 11:05 |
pinesol_green |
csharp: everyone stole csharp's ice cream! |
| 11:05 |
csharp |
@blame git blame |
| 11:05 |
pinesol_green |
csharp: git blame stole csharp's ice cream! |
| 11:07 |
csharp |
@quote random |
| 11:07 |
pinesol_green |
csharp: Quote #24: "<denials> when git doesn't kill you, it makes you smarter" (added by gmcharlt at 03:58 PM, May 03, 2012) |
| 11:10 |
|
zerick joined #evergreen |
| 11:14 |
jeff |
yboston: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jeff/ac_by_record_id_2013 |
| 11:27 |
jeff |
‡aPlatzman, Daniel ‡4prf ‡0(Set cat.marc_control_number_identifier in Library Settings)608493 |
| 11:29 |
yboston |
I would like to update the installation instructions for master/2.5 to use the new "osrf_control --localhost --start-all" command/syntax. Is there a particular developer that wants to give me some feedback before I make the change? |
| 11:30 |
yboston |
I am struggling to find the relevant commit so I can see the code |
| 11:36 |
tsbere |
yboston: "git blame -- filename" and "git show -- filename" are both wonderful ways to determine what commit(s) touched a file. The former gives you a line by line, the latter just shows you them. |
| 11:36 |
yboston |
tsbere: thank you very much |
| 11:40 |
rfrasur |
adbowling-isl_, you around? |
| 11:40 |
rfrasur |
n/m |
| 11:49 |
berick |
yboston: http://git.evergreen-ils.org/?p=OpenSRF.git;a=blob;f=bin/opensrf-perl.pl.in |
| 11:51 |
* tsbere |
supposes that git log -- filename is probably more useful than git show -- filename, but he was in a run of "maybe it was that commit I wanted to look at?" git show statements |
| 11:57 |
rfrasur |
Is there a way for me to run both 2.2 and 2.4 at the same time pointed to diff servers? |
| 11:58 |
rfrasur |
on the same computer, that is. |
| 12:03 |
|
jdouma joined #evergreen |
| 12:06 |
dbs |
rfrasur: with virtual machines I guess |
| 12:06 |
rfrasur |
dbs, but nothing quick? |
| 12:07 |
* rfrasur |
will just use a laptop as well later. |
| 12:09 |
|
smyers_ joined #evergreen |
| 12:14 |
paxed |
dbs: i just finished Fez. took me a bit over 10 hours, and got about 140% of it. |
| 12:15 |
paxed |
dbs: this was the first game in years where i had to use pen and paper to write things down! |
| 12:25 |
|
acoomes joined #evergreen |
| 12:54 |
dbs |
paxed++ # after getting through the tutorial / first level, I took a break :) |
| 12:55 |
* phasefx |
did too |
| 12:55 |
paxed |
i haven't been able to get much work done this week, and all the irritation resulted me in playing the game during evenings. |
| 12:59 |
|
stevenyvr2 joined #evergreen |
| 13:00 |
rfrasur |
Is someone setting up a hangout for the discussion? |
| 13:01 |
|
atheos_ joined #evergreen |
| 13:02 |
phasefx |
rfrasur: I'll invite you to the one I'm on |
| 13:02 |
rfrasur |
got it. muchas gracias |
| 13:06 |
* dbs |
plays with video / audio |
| 13:06 |
* rfrasur |
is looking at berick's head and listening to strange chuckling. |
| 13:07 |
rfrasur |
and writing a grant proposal |
| 13:07 |
* rfrasur |
does work a little |
| 13:12 |
* phasefx |
also managed to crash his Hangouts; chaos powers for the loss |
| 13:12 |
* dbs |
tries to remember - there's an agenda for this afternoon? Wrap-up meeting or something? |
| 13:12 |
rfrasur |
I blame everything on Thursday. We're mortal enemies right now. |
| 13:12 |
bshum |
dbs: Yeah there's a wrap up reports at 1:30 pm EST |
| 13:12 |
dbs |
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:hackfest:hackaway-2013 - oh yeah |
| 13:12 |
bshum |
So in a little bit |
| 13:13 |
csharp |
@blame Thursday |
| 13:13 |
pinesol_green |
csharp: Thursday is NOT CONNECTED TO THE NETWORK!!! |
| 13:13 |
csharp |
pinesol_green: tru dat |
| 13:13 |
pinesol_green |
csharp: MARC still isn't dead yet, alas |
| 13:13 |
bshum |
dbs: We're going to push through a tiny commit to put a hide block around the searchbar elements while on the myopac pages |
| 13:13 |
bshum |
Half the screen being used up by search elements doesn't seem helpful for the time being. |
| 13:13 |
dbs |
bshum: NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO! |
| 13:13 |
dbs |
bshum: I kid. Hide them on all screens except homesearch? |
| 13:13 |
bshum |
Or. :) |
| 13:14 |
kmlussier |
+1 |
| 13:14 |
dbs |
Yeah. Results and all. |
| 13:14 |
rfrasur |
hehe |
| 13:14 |
csharp |
http://www.youtube.com/watch?v=WWaLxFIVX1s |
| 13:15 |
eeevil |
http://www.khaaan.com/ |
| 13:16 |
dbs |
Pop "Another search" above "Advanced search"? |
| 13:16 |
rfrasur |
simultaneous will shatner |
| 13:17 |
bshum |
We're contemplating how the basic search, advanced search, and browse search links will need to work. |
| 13:17 |
bshum |
Since those are all contained within searchbar.tt2 right now |
| 13:18 |
bshum |
Or similar depending on what screen you're on I guess |
| 13:18 |
bshum |
I was thinking about making a new nav bar or something for those |
| 13:18 |
bshum |
But styling them as similar |
| 13:18 |
bshum |
But we're still pondering |
| 13:18 |
bshum |
Just figuring there still does need to be a way back to search from the my account areas |
| 13:18 |
bshum |
Even if we hide the search forms |
| 13:19 |
rfrasur |
and this is a responsive template? or diff template dependent on screen size? or some other mopac mojo that's been created in the wee hours? |
| 13:19 |
bshum |
rfrasur: We've been hacking the existing main template and adding stuff to make it work reasonably in mobile. |
| 13:20 |
rfrasur |
okay |
| 13:20 |
dbs |
bshum: my thought was to stuff it all under the "Refine these results" (or "Refine this search") button for mobile |
| 13:20 |
bshum |
dbs: That works nicely for the results. |
| 13:20 |
dbs |
But yeah, given the current structure that's either going to require restructuring, or DOM surgery via JavaScript |
| 13:21 |
rfrasur |
I feel like I'm at the tail end of the discussion...so...whatever y'all do will be fantastic and I'll concentrate on teaching librarians the difference between a mobile website and an app. |
| 13:21 |
rfrasur |
forever |
| 13:21 |
dbs |
"Refine this search" could become "Search..." on the not-results page... |
| 13:21 |
dbs |
rfrasur++ |
| 13:21 |
rfrasur |
until I fall over...and then it'll be on my headstone "a mobile website/page is not the same as an app" |
| 13:22 |
* rfrasur |
might even get that as a tattoo |
| 13:22 |
dbs |
The http://headstone.app/rfrasur mobile website |
| 13:23 |
rfrasur |
yep |
| 13:26 |
|
Rogan_Ni joined #evergreen |
| 13:28 |
dbs |
theory looks reasonably good on my Android 2.3 with stock browser LG Optimus One |
| 13:31 |
bshum |
Excellent. |
| 13:31 |
kmlussier |
Yay! |
| 13:32 |
dbs |
320x480 3.2" display - feel the power! http://www.lg.com/ca_en/cell-phones/lg-LGP500 |
| 13:33 |
jeff |
hrm. openlibrary api site down. |
| 13:33 |
jeff |
and now it's up. |
| 13:33 |
jeff |
> key can be any one of ISBN, OCLC, LCCN, OLID and ID (case-insensitive) |
| 13:47 |
dbs |
Learning point: design for mobile first! |
| 13:51 |
phasefx |
design for testing first, too, but at least one test tool makes use of accessiblity libraries for working the UI, so you can do both |
| 13:52 |
jeff |
man. i thought isbns were messy. lccns and oclc nums are almost worse. |
| 13:54 |
eeevil |
how upgrade-safe are the changes that have been made thus far? |
| 13:54 |
rfrasur |
thanks bshum |
| 13:54 |
eeevil |
**clap, clap, clap** |
| 13:54 |
dbs |
eeevil: about as safe as any tpac changes |
| 13:54 |
eeevil |
dbs: well, some are very safe |
| 13:54 |
eeevil |
some are foundational, and not so much |
| 13:54 |
dbs |
that is to say, we're changing css and structure |
| 13:54 |
dbs |
so if you override templates, you get to figure out where the diffs are |
| 13:55 |
eeevil |
that clears it up, thanks |
| 13:56 |
dbs |
fwiw - most of the changes we've made improve the main TPAC view, IMO |
| 13:56 |
* eeevil |
pines for a much more granular set of template files, and yet supplies no patches ... |
| 13:56 |
dbs |
(to address dbwells' point) |
| 13:56 |
dbs |
Well, the searchbar changed significantly |
| 13:57 |
eeevil |
but that's pretty safe, I bet |
| 13:57 |
dbs |
but improves i18n and accessibility |
| 13:57 |
eeevil |
that++ |
| 13:57 |
bshum |
Oh right, the searchbar |
| 13:57 |
|
tspindler left #evergreen |
| 13:58 |
paxed |
was bug 1221411 fix included? |
| 13:58 |
pinesol_green |
Launchpad bug 1221411 in Evergreen "Translating the basic search bar is troublesome" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1221411 |
| 13:58 |
dbs |
That's kind of the whole point of a responsive design: it's one design. |
| 13:58 |
rfrasur |
is this referring to font size? sorry...audio is a little hit or miss |
| 13:59 |
dbs |
We were evaluating them on their own merits. And even tested with IE (up to this morning, anyway) |
| 13:59 |
dbs |
rfrasur: all of the changes |
| 13:59 |
rfrasur |
oh...sorry...I meant the 12/14 conversation |
| 13:59 |
|
bott_otr joined #evergreen |
| 14:00 |
dbs |
paxed: nope |
| 14:00 |
dbs |
paxed: but we should definitely take a look at your bug |
| 14:01 |
eeevil |
one-layout-to-rule-them-all++ |
| 14:01 |
dbs |
paxed: we threw out the sentence structure entirely |
| 14:01 |
rfrasur |
eeevil++ |
| 14:01 |
csharp |
hack_prize++ |
| 14:01 |
paxed |
dbs: ahh, i see. |
| 14:03 |
dbs |
wish we had a camera to see! |
| 14:03 |
eeevil |
aye |
| 14:04 |
csharp |
dbs: is the camera not working? |
| 14:04 |
eeevil |
or a url |
| 14:04 |
eeevil |
or branch |
| 14:04 |
eeevil |
csharp: it's washed out .. nature of webcams |
| 14:04 |
dbs |
csharp: hmm, I'm on rogan's hangout and his camera is off |
| 14:04 |
csharp |
https://dev198.esilibrary.com/~berick/egstaff/ang/patron is what's up there |
| 14:05 |
dbs |
Or maybe my hangout is screwed.. |
| 14:05 |
csharp |
better? |
| 14:05 |
phasefx |
still washed out |
| 14:06 |
rfrasur |
it's better, but hard to see. i think other than a screen share, it's going to be like that. |
| 14:06 |
bshum |
Yeah |
| 14:08 |
bshum |
dbs: Hmm, on Chrome, the javascript is a little slow in rendering the facets. |
| 14:08 |
|
fparks joined #evergreen |
| 14:08 |
bshum |
It likes to spin for me a few moments longer before pushing them to their normal place on the left. |
| 14:08 |
bshum |
Maybe it's just my chrome. |
| 14:08 |
bshum |
Just noticed that |
| 14:08 |
bshum |
(for the main catalog) |
| 14:09 |
dbs |
bshum: no, makes sense, because the facets load after the main results, then they get pushed over to the left after the page finishes loading completely |
| 14:09 |
bshum |
dbs: Okay, just checking :) |
| 14:09 |
bshum |
*double checking |
| 14:10 |
dbs |
yet another design approach would be to load them first still, but set them to "display:none" in mobile mode, and then use the javascript "Refine these results" to unhide them |
| 14:10 |
Rogan_Ni |
yeah, the camera is good for people but only so great for little stuff on a screen |
| 14:10 |
bshum |
dbs: I think we talked about hiding facets by default and only having them show if one were using the refine search button. |
| 14:11 |
bshum |
So maybe that would work better. |
| 14:11 |
rfrasur |
dbs and bshum: I think that's a great idea...hiding them |
| 14:11 |
* bshum |
could ponder more after |
| 14:12 |
|
fparks joined #evergreen |
| 14:13 |
csharp |
berick++ |
| 14:13 |
bshum |
berick++ |
| 14:13 |
rfrasur |
berick++ |
| 14:17 |
|
bott_otr joined #evergreen |
| 14:20 |
csharp |
senator++ |
| 14:20 |
csharp |
jboyer++ |
| 14:28 |
rfrasur |
cash is good |
| 14:28 |
remingtron |
jeff++ #syndetic cover image improvements |
| 14:30 |
Rogan_Ni |
google hangouts is not my friend today |
| 14:30 |
Rogan_Ni |
I'm going to look at some new ways to handle remote participation next year that might be a bit slicker since there was high interest this year |
| 14:31 |
remingtron |
puppets++ |
| 14:32 |
csharp |
jeff++ |
| 14:32 |
eeevil |
**clap, clap, clap** |
| 14:33 |
rfrasur |
Rogan_Ni, I know the call went out on Tuesday for people to moderate the community. If that offer is still open, I'd like to experiment with a couple things. |
| 14:33 |
|
GeoffSams joined #evergreen |
| 14:34 |
rfrasur |
If it's not...that's cool, too |
| 14:35 |
|
fparks joined #evergreen |
| 14:35 |
* dbs |
notes that Hangouts worked really well, at least in his opinion |
| 14:36 |
csharp |
dbs++ |
| 14:36 |
csharp |
felt like you were here with us ;-) |
| 14:36 |
rfrasur |
dbs, I agree. fwiw, I think it's good for people like me to NOT be there as a distraction...but hangouts allows us to still know what's going on. |
| 14:36 |
* eeevil |
feels hangouts are 100% better than being completely disconnected |
| 14:37 |
* phasefx |
agrees |
| 14:37 |
|
gsams joined #evergreen |
| 14:39 |
eeevil |
more, smaller rooms for workgroups might make hangouts more workable |
| 14:39 |
eeevil |
avoid cross-talk |
| 14:39 |
eeevil |
he says selfishly |
| 14:39 |
Rogan_Ni |
its a good thought |
| 14:39 |
rfrasur |
eeevil - true, but does the cross-talk provide a benefit for the in-person people? |
| 14:39 |
* phasefx |
really wants floating holographic heads, but can wait for that |
| 14:39 |
rfrasur |
holographic_heads++ |
| 14:40 |
rfrasur |
oh wait....didn't FB try to do that with a mobile overlay? |
| 14:40 |
rfrasur |
(I guess they weren't really holographic...but they're flolating) |
| 14:43 |
|
acoomes joined #evergreen |
| 14:44 |
Dyrcona |
Anyone seen this, and have any idea what I did wrong? |
| 14:44 |
Dyrcona |
Modification of a read-only value attempted at /usr/local/share/perl/5.14.2/OpenILS/Utils/Fieldmapper.pm line 240 |
| 14:44 |
* rfrasur |
thinks Yamil needs to bring a playlist with him next year. |
| 14:45 |
rfrasur |
so people can request music on the piano |
| 14:47 |
jeff |
Dyrcona: i've encountered it in general, and had this in my history, but i do not recall the cause when i dealt with it. i suspect a typo elsewhere. http://www.perlmonks.org/?node_id=570712 |
| 14:48 |
eeevil |
Dyrcona: could it be something like: Fieldmapper::foo->new = $bar; somewhere in the code? |
| 14:50 |
Dyrcona |
Well, I'm actually using $class = Fieldmapper::class_for_hint('are'); $class->new([@data]); |
| 14:50 |
Dyrcona |
That works but not if $class is referenced as a member in an object: $self->{fmClass}->new([@data]) |
| 14:52 |
|
mrpeters left #evergreen |
| 14:53 |
eeevil |
weird ... no use of @_ involved, all shifted ... |
| 14:54 |
Dyrcona |
Ok. I misspoke slightly. |
| 14:55 |
Dyrcona |
I was passing an arrayref $data. |
| 14:55 |
Dyrcona |
when I changed data to an array and use the above syntax, it works. |
| 14:56 |
Dyrcona |
Thanks for the suggestions. |
| 14:57 |
rfrasur |
screenshots are very rarely a bad idea |
| 14:57 |
rfrasur |
in this context, at least |
| 14:57 |
eeevil |
ah .. interesting. are you looping over an array of arrays? like: for $data ($sth->selectall_arrayref) { $foo = $class->new($data); ... } ? |
| 14:57 |
Dyrcona |
eevil: yes. I am |
| 14:58 |
Dyrcona |
I'll push it if you want to look, but switching to $sth->fetchrow_array and using [@data] fixed it. |
| 14:59 |
eeevil |
that's it. it's the same as "common cause 2" |
| 14:59 |
eeevil |
well, just using [@data] should be enough ... but `while(fetchrow_arrayref)` is better anyway, for memory usage reasons |
| 15:00 |
eeevil |
array in hand, use foreach; iterator pattern, use while |
| 15:01 |
eeevil |
Dyrcona: also, switching to while means you can use the variable directly, no need to deref and re-ref |
| 15:01 |
eeevil |
also, \@data will be faster (and less memory hungry) than [@data] ... though that may be a micro-optimization in your use case |
| 15:02 |
Dyrcona |
eevil: I'll give it a try, though testing with ten records it won't be noticeable. |
| 15:02 |
Dyrcona |
eeevil ^ |
| 15:02 |
eeevil |
indeed it wont |
| 15:02 |
eeevil |
but, while++ |
| 15:06 |
dbs |
gah. trying to put facets first again is painful |
| 15:18 |
dbs |
bshum: so... latest commit does good-ish things for mobile show/hide facets and results (although the "Refine results" / "Back to results" links need styling) |
| 15:19 |
dbs |
but the graceful collapsing of place hold / add to my list stopped working. didn't mean to actually _push_ that commit |
| 15:20 |
* eeevil |
's ears are burning |
| 15:26 |
bshum |
dbs: Well I haven't pulled it quite yet |
| 15:26 |
bshum |
Toying with some other things first. |
| 15:28 |
|
depesz joined #evergreen |
| 15:32 |
|
DPearl joined #evergreen |
| 15:36 |
|
DPearl joined #evergreen |
| 15:37 |
remingtron |
now open for editing: http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap:2.6 |
| 15:38 |
remingtron |
it's available from the main roadmap page |
| 15:38 |
remingtron |
http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap |
| 15:48 |
csharp |
remingtron++ |
| 15:51 |
|
DPearl joined #evergreen |
| 15:55 |
|
b_bonner left #evergreen |
| 15:56 |
rfrasur |
thanks hack-away people. have safe journeys home. |
| 15:56 |
csharp |
rfrasur: thanks! |
| 15:58 |
|
kmlussier joined #evergreen |
| 16:07 |
|
yboston_ joined #evergreen |
| 16:10 |
|
dboyle joined #evergreen |
| 16:15 |
|
zerick joined #evergreen |
| 16:29 |
|
roses joined #evergreen |
| 16:36 |
pastebot |
"roses" at 64.57.241.14 pasted "500 fields visability" (5 lines) at http://paste.evergreen-ils.org/13 |
| 16:37 |
roses |
roses: Just pasted a question about 500 field workaround in 2.3.7 and question about 500 fields in 2.4. Thanks. |
| 16:38 |
|
RoganH joined #evergreen |
| 16:40 |
kmlussier |
RoganH: Weren't you supposed to fly out today? |
| 16:40 |
RoganH |
kmlussier: nope, I fly out tomorrow |
| 16:40 |
kmlussier |
Ah, ok. |
| 16:40 |
eeevil |
roses: the 500 field can be made searchable in any version of evergreen. it's a matter of server configuration. |
| 16:40 |
RoganH |
I was confused when we were chatting earlier, I thought you were talking about tomorrow |
| 16:41 |
* RoganH |
is always confused. |
| 16:41 |
kmlussier |
Yeah, me too. |
| 16:41 |
roses |
eeevil: Searchable, but are they visible - ie to the patron who wants to make sure their name is mentioned? |
| 16:42 |
eeevil |
roses: they can be made visible, too. exactly how depends on if you're using the TPAC or the JSPAC (2.3 is the last release that supports the JSPAC), but in either case it comes down to template customization |
| 16:45 |
roses |
eeevil: Are copy notes visible in the TPAC of any version of Evergreen? |
| 16:46 |
eeevil |
they are in the JSPAC, if you drill down to the copy details, I believe |
| 16:47 |
roses |
eeevil: In 2.4 would you still have to drill down to copy details? |
| 16:48 |
eeevil |
no, because the JSPAC is been effectively disabled |
| 16:49 |
eeevil |
s/is/has/ |
| 16:50 |
kmlussier |
roses: In tpac, there is no hidden copy details area. The copy notes will display on the record page without any additional clicks, but public copy notes didn't arrive in tpac until 2.4, I think. |
| 16:50 |
* kmlussier |
tries to find dinner. |
| 16:50 |
roses |
eeevil: So we are just out of luck with the TPAC in 2.3.7 - no workarounds - but it in another field etc. |
| 16:51 |
eeevil |
kmlussier: thanks! I wasn't certain about when that landed in a release, or if it had yet |
| 16:52 |
eeevil |
roses: based on what kmlussier said, I think 2.4 will be your best bet for both copy details and 500 notes |
| 16:52 |
eeevil |
roses: but the 500 notes can be displayed in 2.3 with some template work (JSPAC or TPAC) |
| 16:54 |
roses |
eeevil: Thanks. Any idea of how much customization that would take - or would we just be better off waiting for upgrade? |
| 16:56 |
eeevil |
not much, really. 10 lines or less if you just need it on the record detail page |
| 16:59 |
roses |
eeevil++kmlussier++ Thanks for your help. Much appreciated. |
| 17:04 |
ldwhalen |
senator: I am taking a look at the Stripe work you are doing with jboyer-isl. |
| 17:04 |
ldwhalen |
How is it coming along? |
| 17:04 |
kbutler |
/quit |
| 17:04 |
senator |
ldwhalen: well, but |
| 17:04 |
senator |
for the moment, i've switched tasks |
| 17:04 |
senator |
it really almost works i think |
| 17:05 |
senator |
i'd be interested in any input, esp. suggestions for services that work in the same way as stripe (no payment info need touch the site's servers) that we could think about adding |
| 17:05 |
|
kmlussier joined #evergreen |
| 17:05 |
ldwhalen |
senator: Do you know if Business::Stripe does error checking? Or will that have to be worked into the Evergreen side of things? |
| 17:06 |
|
mmorgan left #evergreen |
| 17:06 |
senator |
what kind of error checking do you mean exactly? it does report to you if stripe declines the charge or doesn't like your input particularly |
| 17:08 |
ldwhalen |
senator: I was wondering if it passes on the Stripe error codes or if it handles them itself. |
| 17:09 |
senator |
ldwhalen: stuff like this so far http://pastie.org/8337096 |
| 17:09 |
senator |
that is, that's the kind of thing i've seen so far |
| 17:09 |
senator |
(sorry, going afk a bit) |
| 17:11 |
ldwhalen |
senator: thanks for that paste. |
| 18:03 |
remingtron |
@later tell yboston: if this is yamil, here's my serials docs: https://bugs.launchpad.net/evergreen/+bug/1207519 |
| 18:03 |
pinesol_green |
remingtron: The operation succeeded. |
| 18:03 |
pinesol_green |
Launchpad bug 1207519 in Evergreen "Serials 2.4 updated documentation needed" (affected: 1, heat: 6) [Undecided,Confirmed] |
| 18:56 |
|
dMiller joined #evergreen |
| 19:28 |
|
dbs_mob joined #evergreen |
| 19:29 |
dbs_mob |
bshum: think I figured it out, now that the facets are back on the left we just need display:inline instead of floats. |
| 19:30 |
dbs_mob |
so we toggle display: none and display: inline. should be easy, in theory |
| 19:37 |
|
dbs_mob left #evergreen |
| 19:45 |
|
stevenyvr2 left #evergreen |
| 20:30 |
|
mrpeters joined #evergreen |
| 20:30 |
dbs |
ahh, true fix coming. |
| 20:30 |
|
mrpeters left #evergreen |
| 21:31 |
|
RoganH joined #evergreen |
| 21:33 |
|
mrpeters joined #evergreen |
| 21:34 |
|
mrpeters left #evergreen |
| 21:51 |
bshum |
dbs++ |
| 22:40 |
|
kmlussier joined #evergreen |
| 23:46 |
|
eby joined #evergreen |
| 23:46 |
|
eby joined #evergreen |
