| Time |
Nick |
Message |
| 08:36 |
|
dguarrac joined #evergreen |
| 08:39 |
|
mantis1 joined #evergreen |
| 09:21 |
|
Dyrcona joined #evergreen |
| 09:26 |
|
mmorgan joined #evergreen |
| 09:52 |
|
sandbergja joined #evergreen |
| 10:08 |
eeevil |
grabbing 1471 |
| 10:27 |
Bmagic |
is it possible to add audience as a facet in the OPAC search? |
| 10:28 |
Bmagic |
I've tried {facet_class => 'audience', facet_order => ['name']} no joy |
| 10:34 |
pinesol |
News from commits: Stamping upgrade script <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=6de207dc74e5cf85cf05870308cbeafd2808fca7> |
| 10:34 |
pinesol |
News from commits: LP#2112412: Adding a live pgTAP test for oils_xpath_string <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=d7fece855f2feff317def06edd2a4184b9941b90> |
| 10:34 |
pinesol |
News from commits: LP#2112412: oils_xpath_string is too strict <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=e78a4721c79be022bcbd625ca7afb14ffa7c0202> |
| 10:46 |
Bmagic |
walking the source code, I think* the facets are restricted to what's in config.metabib_field.field_class |
| 10:58 |
Bmagic |
maybe I can add a row to config.metabib_field to gather "audience" out of the 521? and reingest |
| 11:06 |
Dyrcona |
Bmagic: I was going to suggest trying that. |
| 11:06 |
Bmagic |
Dyrcona++ |
| 11:09 |
|
Christineb joined #evergreen |
| 11:45 |
|
jihpringle joined #evergreen |
| 12:12 |
|
jihpringle joined #evergreen |
| 13:02 |
* Dyrcona |
"wrote" 122,376 lines of SQL code this morning. Thanks, GNU Emacs! |
| 13:03 |
Dyrcona |
Of course, most of those lines are copy barcodes exported from spreadsheets, but I did have to use regex replace to quote them and add the comma after each one. |
| 13:04 |
eeevil |
Bmagic: is the point to get the audience and a count of records using it into the left hand sidebar? IOW, is this a UI issue? because ... it's already a filter for searching |
| 13:05 |
eeevil |
put another way, perhaps duplicating the data by extracting it again isn't the way, maybe we just need to show what's already there in a different manner |
| 13:07 |
eeevil |
(bonus to exposing config.record_attr_definition where filter=true in the "facet" sidebar: all the other crad filters are available, too, no just audience) |
| 14:54 |
Bmagic |
eeevil: it's two things: they want the audience as defined by the 521 field instead of leader/006/008, and they want it to be represented in the facets as you say. But let's pretend we don't want to include non-indexed marc fields and go with what is already defined as "audience" - what changes do I make to config.tt2 to include those in the facets? |
| 15:09 |
|
redavis joined #evergreen |
| 15:28 |
|
mantis1 left #evergreen |
| 16:21 |
eeevil |
Bmagic: you don't, today ... there's some dev. but if they want to replace AACR2 fixed field audience with RDA arbitrary-value audience, then you'll have to reconfigure stuff anyway. exactly how comes down to what you want to display -- the raw marc value from 521, or a translatable value from coded value map. but, with that, I have to run away for the day :( |
| 16:22 |
Bmagic |
ty! |
| 16:22 |
Bmagic |
eeevil++ |
| 16:23 |
Bmagic |
here's a fun one: https://bugsquash.mobiusconsortium.org/eg/opac/record/218 versus: https://bugsquash.mobiusconsortium.org/eg/opac/record/218?query=coraline;qtype=keyword;locg=1;detail_record_view=0 |
| 16:23 |
Bmagic |
notice the lack of 505 fields in the OPAC display when the record is shown via search query? |
| 16:24 |
Bmagic |
Uhhh.... that's confusing me, what's the thinking on this? Why is it programmed to not* show the 505 fields in the OPAC when there's a search query involved? |
| 16:24 |
eeevil |
that's just "with query CGI param we use display fields, without we parse the marc in-page" |
| 16:25 |
eeevil |
that's been the case since highlighting became a thing (that's when display fields entered the opac) |
| 16:25 |
Bmagic |
It's what we want? |
| 16:26 |
eeevil |
we want to only use display fields |
| 16:26 |
eeevil |
ideally |
| 16:26 |
Bmagic |
hmmm, fields that are flagged as display in config.metabib_field is what you mean? |
| 16:26 |
eeevil |
then it's configuration (of display fields) rather than hard-coded marc parsing in the templates |
| 16:26 |
eeevil |
that's part of it, yes |
| 16:27 |
eeevil |
not all. but now I do have to run |
| 16:27 |
Bmagic |
I've been tasked with getting all of the 505's to show all the time, not just sometimes |
| 16:27 |
Bmagic |
lata! |
| 16:44 |
Dyrcona |
Is it time for an Angular OPAC? (Asks one who has long argued that the OPAC should work without JavaScript.) |
| 16:44 |
Dyrcona |
Related, tangentially, to the above discussion.... |
| 16:45 |
mmorgan |
Bmagic: Bug 1822875 is rearing it's head. |
| 16:45 |
pinesol |
Launchpad bug 1822875 in Evergreen "OPAC titles are truncated when query string present" [Undecided,Confirmed] https://launchpad.net/bugs/1822875 |
| 16:45 |
Bmagic |
mmorgan++ |
| 16:46 |
Bmagic |
I was wondering if there was a report for it |
| 16:46 |
Bmagic |
hahaha! and I wrote it |
| 16:51 |
Bmagic |
Dyrcona: yeah, I long assumed that OPAC was going to be Angularized when we moved to the web based staff client in 3.0 |
| 17:07 |
|
mmorgan left #evergreen |
| 17:13 |
|
jihpringle joined #evergreen |
