Time |
Nick |
Message |
06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
07:24 |
|
rjackson_isl_hom joined #evergreen |
07:52 |
|
mantis joined #evergreen |
08:38 |
|
mmorgan joined #evergreen |
09:16 |
|
rfrasur joined #evergreen |
09:19 |
|
derekz joined #evergreen |
09:21 |
|
Dyrcona joined #evergreen |
10:24 |
derekz |
In SVF Record Attribute ... , what does 'SVF' stand for? |
10:38 |
Bmagic |
derikz: it comes out of table config.record_attr_definition |
10:38 |
* csharp_ |
glance in miker 's direction |
10:39 |
Bmagic |
derekz* (fingers, you know) |
10:39 |
mmorgan |
Something Very Fishy? |
10:40 |
csharp_ |
I guess I read it internally as "single value field" - not sure if that's from a long forgotten conversation with someone who knows or not :-/ |
10:40 |
csharp_ |
seems like we'd want it defined explicitly somewhere |
10:40 |
Bmagic |
maybe the "V" is "vocabulary"? (I see that mentioned on the table) |
10:40 |
csharp_ |
derekz: apparently NO ONE KNOWS |
10:41 |
derekz |
lol |
10:41 |
csharp_ |
grepping the code was no help - I was hoping an inline comment would explain, but NO |
10:41 |
JBoyer |
I'm relatively sure it's Single Value Field, because theres also MVF which I'm also thinking is Multi-Valued Field. |
10:41 |
* mmorgan |
thinks csharp_ is on the right track with single valued fields |
10:41 |
csharp_ |
JBoyer: that's what I was remembering |
10:41 |
JBoyer |
It's either in IRC logs or LP, pretty sure it's never spelled out in code. |
10:42 |
csharp_ |
page DIG, stat! |
10:42 |
mmorgan |
Multi Valued Fields is spelled out in the documentation. |
10:42 |
csharp_ |
(sorry, binge-watching Grey's Anatomy) |
10:43 |
mmorgan |
https://docs.evergreen-ils.org/eg/docs/latest/admin/MARC_RAD_MVF_CRA.html |
10:43 |
csharp_ |
mmorgan++ # R-ing TFM |
10:45 |
derekz |
Wow! This new documentation format is nice |
10:47 |
derekz |
Once you've created a definition to target a new icon, one that's not already defined in the stock Evergreen icon_formats, where do you tell Evergreen that this new OPAC Icon Format should target newiconfile.png? |
10:48 |
Dyrcona |
You have to do what we call a reingest. |
10:48 |
Dyrcona |
Let me check something, and I can tell what database function you need to run. |
10:51 |
derekz |
I may be misunderstanding or missing a step, too. For example: if I create an new icon_format in the SVF Record Attributes Coded Value Map Config, with the following definition: {"0":{"_attr":"marc21_biblio_347_sub_b","_val":"CD audio"},"1":[{"_attr":"item_type","_val":"a"},{"_attr":"item_type","_val":"t"}],"2":{"_not":[{"_attr":"item_form","_val":"a"},{"_attr":"item_form","_val":"b"},{"_attr":"item_form","_val":"c"},{" |
10:51 |
derekz |
_attr":"item_form","_val":"o"},{"_attr":"item_form","_val":"q"},{"_attr":"item_form","_val":"s"}]}} |
10:52 |
derekz |
Where do I tell Evergreen: "When a record matches that above definition, display newiconfile.png"? |
10:57 |
derekz |
Or maybe, where to make the connection/reference to the new icon in /openils/var/web/images/format_icons/icon_format/newiconformat.png |
11:00 |
rhamby |
derekz I'm blanking on which table it is but it looks for a png with the same name as a value in one of the tables, ctype in config.coded_value_map when it is icon_format maybe |
11:00 |
JBoyer |
derekz, the code field of config.coded_value_map where ctype=icon_format is the filename of the icon. I don't recall if it requires .png (may as well) or just looks for whatever images in that dir. |
11:01 |
JBoyer |
rhamby++ |
11:02 |
derekz |
Awesome! Thanks! I've give that a try |
11:04 |
JBoyer |
(to be clear, I believe .png is added to the code field; don't put .png in the code field or you'll need to use iconname.png.png :) ) |
11:04 |
rhamby |
that is my memory as well |
11:05 |
Dyrcona |
Yeah. I used to just *know* that but was looking it up. :) |
11:05 |
|
jihpringle joined #evergreen |
11:06 |
Dyrcona |
derekz: You'll want to run metabib.reingest_record_attributes (rid BIGINT, pattr_list TEXT[] DEFAULT NULL, prmarc TEXT DEFAULT NULL, rdeleted BOOL DEFAULT TRUE) on the affected bib records for this to show up. |
11:08 |
rhamby |
yeah, definitely target the affected bibs, reingesting the whole db for a small subset is no bueno |
11:10 |
pastebot |
"Dyrcona" at 168.25.130.30 pasted "This will ingest icon_format for all not delted bib records" (3 lines) at http://paste.evergreen-ils.org/14430 |
11:18 |
derekz |
JBoyer++ |
11:18 |
derekz |
rhamby++ |
11:18 |
derekz |
Dyrcona++ |
11:19 |
derekz |
And for now, I'll think "Single Value Field" :) |
11:21 |
Dyrcona |
That's my understanding: SVF = Single Value Field and MVF = Multiple Value Field. I figured it was covered earlier, so didn't say anything then. |
11:23 |
Dyrcona |
Also as rhamby suggests, if you can find a way to narrow the list of bib records to only those that have the new attribute, it will save you a lot of time on the reingest call. You could try joining to metabib.real_full_rec where the tag is 347 and subfield is b, etc. |
11:24 |
rhamby |
yeah even if you can't target the exact subset (though you probably can) if you can at least narrow out the vast majority it'll save time and db activity |
11:25 |
derekz |
For sure. To test, I'll just make a simple edit and save a record via the web client. If all is good, I'll collect the bib IDs that need reingest. I definitely don't want to hit the db with unnecessary activity. |
12:53 |
|
jvwoolf joined #evergreen |
16:39 |
Bmagic |
miker: let's say I wanted an authority "110" heading to apply to the "subject" axis. It seems* like all I need to do is insert the glue in authority.browse_axis_authority_field_map. Which I've done on a test machine. It's not working immediately, so I need to reingest? |
16:49 |
|
jihpringle joined #evergreen |
16:51 |
Dyrcona |
Bmagic: You'll most likely want to run the authority linking programs. Otherwise, you can wait for the changes to take effect as bibs and authorities are updated. |
16:54 |
|
gsams joined #evergreen |
16:54 |
Bmagic |
This is where I get broke down. authority.indexing_ingest_or_delete inserts rows into metabib.browse_entry_simple_heading_map based on the output from authority.simple_heading_set |
16:56 |
Dyrcona |
Bmagic: These are support scripts. |
16:56 |
Bmagic |
right, I'm using those too |
16:57 |
Dyrcona |
I'm not an expert on authority linking, but those should cover it if everything is set up correctly. |
16:59 |
Dyrcona |
Bmagic: You might need to do a browse ingest, too. I"m not 100% on any of this, though. |
17:00 |
Bmagic |
authority_authority_linker.pl would "link" two authority records together. Which doesn't address this browse index thing (I don't think) |
17:01 |
Bmagic |
the browse reingest function is for bibs right? This is something I need the database to do for the authority record. Now that I've indicated that I want the 110 field to apply to the subject index |
17:02 |
Dyrcona |
authority_control_fileds.pl links bibs to authorities. |
17:02 |
Bmagic |
yep, that's my understanding of the code as well |
17:03 |
Dyrcona |
I'd run that then do the browse ingest see if that works. |
17:06 |
Bmagic |
what I think I need is the equivalent authority ingest (not bib ingest) |
17:06 |
Bmagic |
I ran this function authority.propagate_changes(aid) - which took a long time and felt satisfying |
17:07 |
Dyrcona |
Well, that might be it. I'm signing out, now. Good luck! |
17:07 |
Bmagic |
later! |
17:09 |
|
mmorgan left #evergreen |
17:30 |
|
jvwoolf joined #evergreen |
18:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
21:15 |
|
jvwoolf joined #evergreen |