Evergreen ILS Website

IRC log for #evergreen, 2014-07-03

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

All times shown according to the server's local time.

Time Nick Message
02:10 dcook__ joined #evergreen
05:40 mrpeters joined #evergreen
07:23 mrpeters joined #evergreen
07:27 mrpeters joined #evergreen
07:58 csharp @blame add $who wants the TRUTH?!  $who CAN'T HANDLE THE TRUTH!!
07:58 pinesol_green csharp: The operation succeeded.  Blame #16 added.
08:25 akilsdonk joined #evergreen
08:38 mmorgan joined #evergreen
08:38 akilsdonk joined #evergreen
08:57 kbeswick joined #evergreen
09:24 yboston joined #evergreen
10:21 mllewellyn joined #evergreen
10:36 mrpeters morning guys -- i'm fighting with the fop utility and generating some PDF's for notices.  From what I can tell, the template in Evergreen (at.event_definition.template) looks good, and the resulting XML passes xmllint --noout.  I get the error pasted at http://pastie.org/9350586 when I attempt to convert the .fo to PDF and I'm a bit puzzled about what the "fo:root" is missing child elements error is indicating.
10:37 mrpeters ew, that pasted fo got truncated....1 sec
10:38 mrpeters fixed at http://pastie.org/9350602
10:46 jwoodard joined #evergreen
10:55 jboyer-isl It wants to see <fo:page-sequence> or <fox:external-document> tags
10:56 mrpeters so the problem is likely at the template level
10:57 jboyer-isl The .xsl transform step is missing something.
10:57 jboyer-isl (At least that's how they're run here)
10:59 jboyer-isl OH. I just noticed the template you posted. That A/T event is for email notices. The A/T output for generating .pdfs usually output xml and a lot more complicated looking.
11:05 bshum Yeah I think jboyer-isl is right.  There's probably some .xsl file that controls what attributes are set for a given template converting from .xml to .fo and whatever server you're trying this on is stricter about the syntax than past versions.
11:07 bmills joined #evergreen
11:14 dcook joined #evergreen
11:14 mrpeters yeah, im confused at what they're trying to do here heh, why would an email need to go to a PDF
11:23 pinesol_green [evergreen|Robert Soulliere] Documentation: Add the authentication proxy chapter - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ae0a652>
11:53 ldw joined #evergreen
12:59 tspindler joined #evergreen
13:06 hbrennan joined #evergreen
13:25 afterl joined #evergreen
14:18 csharp bshum: if you're around, I may want to bug you about how you hid due dates from patrons in the OPAC
14:23 bshum Did we?
14:23 * bshum checks his customizations branch....
14:26 bshum csharp: Which part of the catalog are we talking about?  rec display or something in myopac?
14:26 csharp I may be misremembering that it was you :-/
14:26 csharp record display
14:26 bshum Yeah I don't think we've altered ours to not show
14:26 csharp ok
14:26 bshum Seems simple enough though
14:26 bshum I would just wrap the block in an is_staff check :)
14:27 csharp yeah - that's a good idea
14:27 csharp thanks ;-)
14:29 bshum I think the only thing we touched on record display was to remove the column for age hold protection, since we don't employ that in our consortium.
14:32 bshum csharp: Looks like there's three places that due_date is defined in copy_table.tt2.  Should be simple like putting [% - IF ctx.is_staff %] and [%- END %] around the places it gets noted.
14:32 bshum Guessing, without trying it directly.
14:37 remingtron berick: do you have a minute to talk about documenting the web staff client? DIG is trying to formulate a plan
14:39 csharp bshum: excellent - thank you
14:40 * csharp is already in holiday mode
14:41 berick remingtron: i do
14:42 remingtron berick: thanks. we're hoping to start drafting docs for the web staff UIs as development continues
14:43 remingtron any comments on which UIs are most "stable" at this point?
14:43 remingtron or ones to wait on?
14:43 berick remingtron: this is the best general source -> http://evergreen-ils.org/dokuwiki/doku.​php?id=dev:browser_staff:dev_sprints:1 -- however, given that none of these have been thorougly tested, "stable" is a relative term
14:44 berick anything marked through is feature complete within the realm of the current "sprint" -- that is, there are missing features, but they will be done later
14:46 berick documenting basic stuff, like login, the splash page, the nav bar, etc. is a good start.  then moving on to simpler interfaces -- ones that are less likely to change -- is a good next step
14:47 berick having said that, though, I have a hard time thinking of tnese UIS will change *drastically* regardless of bugs or missing features
14:47 berick since they all mimic the XUL client very closely
14:48 berick hmm, smells like hurricane outside
14:48 csharp berick: are you in the storm's path?
14:49 remingtron berick: thanks for the advice, feel free to run and board up the windows if needed
14:49 berick csharp: just the outer swirly bits.  we'll get rain and modest wind.
14:49 * csharp sometimes wishes he lived on a coast, other times, not so much :-/
14:49 berick a big gust just came from nowehere
14:49 csharp berick: good
14:49 berick remingtron: heh, no prom
14:49 berick er, prob
14:49 csharp s/good/as good as can be/ ;-)
14:50 berick also, no prom for me tonight
14:50 remingtron heh
15:01 berick BTW, this will be the browser client Bootstrap theme: https://kristopolous.github​.io/BOOTSTRA.386/index.html
15:02 jeff berick: that was proposed here earlier today. glad to hear you're on board with it!
15:02 jeff er, "here" in a physical sense, not this irc channel.
15:02 berick jeff: haha.  done and done.
15:03 dbs AngularJS is so six months ago. Now it's all about Polymer, man
15:03 * dbs jests!
15:04 dbs bshum: I noticed a markup issue with your production instance that does funny things to the RDFa
15:04 bshum dbs: Yikes, entirely possible.  Our production is a bit wacky in places.
15:04 berick dbs: I read your /me as "jets!", as in, I'll just leave this mischief here and run
15:05 dbs bshum: line 712 of http://acorn.biblio.org/eg/opac/record/1816597 opens a div, but line 722 closes with a span
15:05 * berick has a feeling 100 new hotnesses will show up before the browser client sees daylight
15:05 bshum Hmm
15:05 dbs Of course you can use Polymer in AngularJS. Pack in all the heat
15:05 berick indeed
15:07 jeff jets to me says less about running and more about the sounds of my workday today.
15:08 dbs Imagine the org-unit selector behaviour and appearance all wrapped up into a single Polymer <org-unit-selector> element. Mmm, so clean and relocatable.
15:08 jeff constantly being overflown by some USN F/A-18 Hornets for some reason
15:08 jeff (the Blue Angels are in town)
15:09 bshum Oh, strange
15:09 bshum dbs: The ending </div> seems to be at the end of the include block for the copy_table.tt2
15:09 bshum I have to move around some stuff.
15:10 dbs wouldn't surprise me if that's a problem in master / released versions too
15:10 bshum I was just checking up on that myself
15:10 berick dbs: see line 13 http://git.evergreen-ils.org/?p=working/Ever​green.git;a=blob;f=Open-ILS/src/templates/st​aff/circ/share/t_hold_edit_pickup_lib.tt2;h=​895cda0a573356026e7fe74b5479f4bb6abdae26;hb=​refs/heads/collab/berick/web-staff-proto
15:10 bshum I do notice that we comment out the hold copy counts block there in summary.tt2
15:10 bshum But I don't think we moved around that much stuff.
15:11 jeff berick: nice :-)
15:11 jeff berick: angular directive, or actually polymer / web component?
15:12 berick angular directive
15:12 jeff k.
15:13 dbs bshum: then again, could be some other random thing throwing off RDFa extraction. I shall play a bit more.
15:13 bshum dbs: Yeah, looking at record/summary.tt2 in master and it's got the same issue.  <div id="copy_hold_counts"> at line 130 and ending div at 152
15:13 dbs berick: nice :)
15:14 bshum I wonder if we need them actually... or if they ought to be removed if we intend for the includes to handle the contents.
15:14 bshum Oh, you know
15:14 bshum I see now
15:14 bshum Yeah it's weird.
15:18 yboston @marc 740
15:18 pinesol_green yboston: Contains related or analytical titles that are not controlled through an authority file or list. (If related or analytical titles are controlled by an authority file, use field 730 (Added entry - uniform title)). (Repeatable) [a,h,n,p,5,6,8]
15:19 dbs bshum: so on the bright side, linter.structured-data.org is fine with our markup. It's just RDFa Play that gets angry and sulky.
15:19 csharp bshum++ # your suggestion worked for me - thanks
15:19 csharp my patch http://git.evergreen-ils.org/?p=evergreen/pines.gi​t;a=blobdiff;f=Open-ILS/src/templates/opac/parts/r​ecord/copy_table.tt2;h=c0fbbd2c98b08ca26cd9537b42e​21584e464dc80;hp=c29a0171f94c3f4e526dae5cfd651a65d​5de9d1d;hb=af5b18ef988dfe2b21f536dd963737a03080189​9;hpb=c5ee6b43f566ea65b3361cc8a4056edc1c32bbd8
15:19 dbs So it could be a bug in RDFa Play
15:19 csharp oops - dead link
15:19 bshum dbs: My quick googling finds me the LP bug where we chatted about the testing tool and its quirks :)
15:19 csharp http://git.evergreen-ils.org/?p=eve​rgreen/pines.git;a=commit;h=af5b18e​f988dfe2b21f536dd963737a030801899 - this works
15:19 csharp (for the logs)
15:20 dbs bshum: Well, there are different testing tools, each with their own quirks
15:20 bshum No doubt.
15:22 dbs yeah, nevermind. As weird as that markup is (really? a div for hold counts that wraps the copy table?) that's not the issue with RDFa Play
15:22 dbs RDFa Play gets sulky about circular references and refuses to play in that case. And we have one of those in standard markup.
15:22 dbs Sorry for the digression / distraction.
15:41 bshum Sigh, anybody have good ideas about checking in all the items that belong to a particular lib and getting rid of any associated fines?  I have two libraries that are withdrawing from the consortium (sad face) and we need to clear patron records of stuff that "no longer exists"
15:41 csharp ugh
15:42 * dbs will submit a patch to remove that, along with the addition of the price="0.00" markup to make the Google Rich Snippets tool happy, and remove the AggregateOffers bit altogether (because hey, we have the complete set of Offers on the same page)
15:43 csharp bshum: for batch voiding fines, we use this for inclement weather days: http://git.evergreen-ils.org/?p=contrib/pin​es.git;a=blob;f=batch_void_fines.sh;h=eb84c​27b09b03e92275c1447e765d4ad93e4cb8e;hb=HEAD
15:44 csharp it's not elegant, but it is effective ;-)
15:49 bshum Heh
15:49 bshum Thanks csharp.  I'll tinker and ponder.
15:53 hopkinsju Maybe I'm missing something/doing it wrong, but when I try to 'Edit Activation Date' for items on the hold shelf I get a message "Number of holds not updated: {X}"
15:53 hopkinsju Same happens when trying to suspend the hold.
15:54 hopkinsju Is it possible to do this for holds that have been captured?
15:55 csharp hopkinsju: I think not, but I don't know for sure
15:56 hopkinsju If a patron has holds on the hold shelf, but due to circ limits can't check the item(s) out, the library would like to pass the item on to whoever is next in line and set an active date for the patron at the desk.
15:56 hopkinsju Is there any sort of shortcut that wouldn't require an entirely new hold to be placed?
16:04 afterl left #evergreen
16:07 DPearl left #evergreen
16:13 ningalls joined #evergreen
16:18 ningalls1 joined #evergreen
16:23 jeff hopkinsju: only shortcut i'm aware of is to cancel the hold then un-cancel the hold.
16:23 jeff hopkinsju: (then set the activation date)
16:24 jeff hopkinsju: and that's going to depend on some org unit settings, if the patron is last in line or next in line when the hold is uncancelled, etc.
16:24 hopkinsju jeff: How do you uncancel a hold?
16:25 jeff from the patron's account, in their Holds display, there's an option to view cancelled holds.
16:26 jeff what you're looking for is a way to "snooze" a hold, while keeping the patron's place in line, but letting the hold be captured for the next person, etc?
16:26 hopkinsju Oh, I see it now. That option is available in the browse hold shelf display
16:26 hopkinsju jeff: Yes, that's correct. Snooze is a good analogy.
16:27 hopkinsju I think Cancel/Uncancel is a good work around.
16:28 jeff if you are closely monitoring statistics on holds, keep in mind that the "uncancel" process changes fields that normally are never changed on holds.
16:29 jeff there may be permissions required and there's certainly at least one org unit setting that you'll want to verify for this use case -- reset request time on hold uncancellation or somesuch.
16:30 tspindler left #evergreen
16:50 ningalls joined #evergreen
17:11 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:16 yboston @marc 024
17:16 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]
17:19 hopkinsju Thanks jeff++
17:30 mmorgan left #evergreen
19:54 gsams joined #evergreen
20:28 dcook__ joined #evergreen
23:58 zerick joined #evergreen

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