| Time |
Nick |
Message |
| 02:44 |
|
book` joined #evergreen |
| 05:31 |
|
rjackson_isl_hom joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Failed Installing Angular web client <http://testing.evergreen-ils.org/~live//archive/2022-03/2022-03-18_04:00:02/test.29.html> |
| 06:09 |
|
JBoyer joined #evergreen |
| 07:50 |
|
CBrown joined #evergreen |
| 07:54 |
|
rjackson_isl_hom joined #evergreen |
| 07:57 |
|
rfrasur joined #evergreen |
| 07:58 |
|
rjackson_isl_hom joined #evergreen |
| 08:22 |
|
mantis1 joined #evergreen |
| 08:59 |
csharp_ |
@blame npm |
| 08:59 |
pinesol |
csharp_: npm is why we can never have nice things! |
| 08:59 |
|
Dyrcona joined #evergreen |
| 09:04 |
|
Keith-isl joined #evergreen |
| 09:06 |
|
Keith_isl joined #evergreen |
| 09:30 |
|
jvwoolf joined #evergreen |
| 10:15 |
|
terranm joined #evergreen |
| 10:29 |
Dyrcona |
If I want to find a record in the database that has a MARC tag with two particular subfield values, there doesn't seem to be a quick way to do that with a double join on metabib.real_full_rec and even then, I'm not guaranteed that they're in the same tag. Am I missing something? |
| 10:36 |
Dyrcona |
I could probably add a "search" index using xpath or something, but I always get lost in a maze of twisty config and metabib tables when I do that. |
| 10:43 |
|
rjackson_isl_hom joined #evergreen |
| 10:45 |
Dyrcona |
Thought I had an example of that in my old code, but I can't find it. I know that I created such things in the database in the past. |
| 10:47 |
berick |
along the lines of this, maybe? https://gist.github.com/berick/40d3c555e43ba42fd99707055ddff4c1 |
| 10:54 |
Dyrcona |
berick: Yeah, but I'm trying to avoid a join like that. |
| 10:55 |
Dyrcona |
I'd probably have to join mravl and crad anyway. |
| 10:57 |
Dyrcona |
I don't even need a join, yet. There won't be any other records that would match this tag and a particular subfield value, but I can't guarantee that will always be the case (though it very likely will be). |
| 10:58 |
Dyrcona |
Plus, the field will have dates in it, and I should also use those dates in my query.... This is MARC tag 583 for anyone who is curious. |
| 11:02 |
Dyrcona |
I'm trying to come up with a query to get bre ids to pipe into marc_export. If I end up having to deal with dates, then I may just have to write a custom export to pick the marc apart in Perl. |
| 11:03 |
Dyrcona |
I don't even need the query today. I'm trying to figure out something that might work, so I can estimate how long it will take to implement. |
| 11:04 |
Dyrcona |
@marc 583 |
| 11:04 |
pinesol |
Dyrcona: Contains information about processing, reference, and preservation actions. (Repeatable) [a,b,c,d,e,f,h,i,j,k,l,n,o,u,x,z,2,3,5,6,8] |
| 11:08 |
Dyrcona |
I basically want to be able to find records where a single 583 has $f = some value $5 = someother value $c < today's date and $d > today's date (if $d is even there) |
| 11:09 |
Dyrcona |
Oh, and a bunch of other criteria, like a certain member library has a non-deleted asset.copy entry with a specific circ modifier... |
| 11:25 |
Dyrcona |
Poking around our database, I found some views with "materialized_" in the name. I think whoever created these views didn't understand the meaning of materialized. |
| 11:26 |
Dyrcona |
Also, I would not be surprised if we don't use them. They're in extend_reporter. |
| 11:28 |
Dyrcona |
Anyway, I want to match records based on the criteria that I mentioned earlier and I don't want to join mrfr 4 times.... |
| 11:32 |
jeff |
related: when you issue a command like "REFRESH MATERIALIZED VIEW foo" and "foo" is not a PostgreSQL materialized view, the error message says: ERROR: "foo" is not a table or materialized view |
| 11:32 |
jeff |
I'm not sure what that command would do if the target was a table... |
| 11:33 |
jeff |
hah, when it's a table you get: ERROR: "foo" is not a materialized view |
| 11:33 |
jeff |
(which is better than the alternative of "now foo is empty" or something) |
| 11:33 |
Dyrcona |
Well, maybe they are actually materialized views... :) |
| 11:33 |
Dyrcona |
I didn't look up the definitions, just the names. |
| 11:34 |
jeff |
\dv shows views, \dm shows materialized views. (i had to look) |
| 11:35 |
jeff |
but yeah, that's possible! :-) |
| 11:37 |
Dyrcona |
Yeah, these are not materialized views, just plain views. |
| 11:39 |
Dyrcona |
It looks like my options are make a record attribute with xpath and build a search for that or I could try making a custom index on biblio.record_entry using xpath. I fear the latter would be very slow to use. |
| 11:42 |
Dyrcona |
Could I specify a tag, sf_list, and a joiner? |
| 11:50 |
Dyrcona |
Hm... I may be over thinking this. :) |
| 11:54 |
Dyrcona |
I suppose that if I add something to config.metabib_field, it will become usable in the OPAC? I basically just want an index that I can use from SQL. |
| 12:13 |
|
jihpringle joined #evergreen |
| 12:23 |
miker |
Dyrcona: IIRC there have been (pre CREATE MATERIALIZED VIEW) "materialized" views that were either trigger or function maintained that were later replaced by a view over /another/ "materialized" view (perhaps at multiple levels). the old names were almost certainly used for the new views to reduce code churn of things that want to look using the "old" format |
| 13:45 |
|
Keith__isl joined #evergreen |
| 14:00 |
Dyrcona |
miker: Makes sense, that's likely what I've got here. |
| 14:00 |
* Dyrcona |
returns to being "off" for the rest of the day. |
| 14:01 |
Dyrcona |
Just got back from walking the dog. |
| 14:43 |
jvwoolf |
mmorgan++ |
| 14:43 |
jvwoolf |
Because your action trigger program just helped us with something |
| 15:11 |
terranm |
I found at least one reason why our Stripe payments have been occasionally failing since the upgrade - https://bugs.launchpad.net/evergreen/+bug/1965579 |
| 15:12 |
pinesol |
Launchpad bug 1965579 in Evergreen "Stripe Payment Intents and Negative Bills" [Critical,New] |
| 15:13 |
terranm |
Marked it critical since it is causing patrons to get billed without their accounts getting credited |
| 15:15 |
csharp_ |
terranm++ |
| 16:20 |
|
jvwoolf left #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:42 |
|
jihpringle joined #evergreen |
| 18:44 |
|
jihpringle84 joined #evergreen |
| 20:30 |
|
JBoyer joined #evergreen |
| 20:42 |
|
rjackson_isl_hom joined #evergreen |
| 20:57 |
|
rfrasur joined #evergreen |
| 22:13 |
|
Keith-isl joined #evergreen |
