| Time |
Nick |
Message |
| 07:00 |
|
collum joined #evergreen |
| 08:38 |
|
sleary joined #evergreen |
| 08:43 |
|
redavis joined #evergreen |
| 08:46 |
|
mantis1 joined #evergreen |
| 08:50 |
|
dguarrac joined #evergreen |
| 09:02 |
|
kmlussier joined #evergreen |
| 09:55 |
eeevil |
scottangel: re the font question from last week, it's based on a (IIRC) freetype font, but then hand-customized for the logo. unfortunately (fortunately?) you can't just select an installed font and recreate the logo in-line in text. the font was documented when it was proposed, I believe, and may be somewhere on the logos+trademarks page of the wiki? |
| 09:57 |
|
sleary joined #evergreen |
| 09:59 |
kmlussier |
I remember the specialness of the font was one of the reasons we looked into changing the logo years ago, but we ended up just changing the small logo. |
| 10:07 |
sleary |
I have some SVG versions of it that I need to finish cleaning up so I can replace the fuzzy versions in the staff screens |
| 10:16 |
kmlussier |
If I reading the release schedule correctly, 3.9 should be taken down from the main downloads page and 3.10 should be updated to security only. Am I correct? If so, I can try to carve out some time today to make the update. |
| 10:17 |
kmlussier |
If I reading...yeah, I speak English good. |
| 10:28 |
|
sandbergja joined #evergreen |
| 10:58 |
|
kmlussier1 joined #evergreen |
| 11:02 |
|
Christineb joined #evergreen |
| 11:16 |
|
briank joined #evergreen |
| 12:03 |
scottangel |
eeevil++ |
| 12:04 |
scottangel |
sleary++ |
| 12:06 |
scottangel |
I had a feeling it was a custom font and not something I could find with a quick google search. I just think it would be cool to have that font for headers and such. sleary, can I get a copy of those svg's whenever you get a chance? |
| 12:30 |
|
Dyrcona joined #evergreen |
| 13:54 |
|
jblyberg73 joined #evergreen |
| 13:57 |
|
sleary joined #evergreen |
| 14:00 |
Dyrcona |
Sometimes its not so easy to figure out where a method/function belongs in a class hierarchy. |
| 14:01 |
Dyrcona |
Maybe it would be easier to think with some nice music playing? |
| 14:07 |
kmlussier |
If you get confused, listen to the music play. |
| 14:08 |
Dyrcona |
The music is telling me, "I'm a fool to do your dirty work." Does that mean I should drop it? :) |
| 14:08 |
kmlussier |
lol |
| 14:12 |
Dyrcona |
So, I think I've figured it out. I have two classes Evergreen\ObjectClass and Evergreen\ObjectInstance. The first is metadata describing a Class and the latter is an instance and contains a reference back to the class. |
| 14:13 |
Dyrcona |
What I want to do is implement a method in ObjectInstance that "defleshes" fleshed fields. I'm going to call it ObjectInstance::flatten. |
| 14:15 |
Dyrcona |
I can query the class of an instance, so I'm going to implement ObjectClass::flattenInstance($obj) that takes an instance and returns the value of the identity/primary field..... Hm... Maybe ti would be better to just implement that on the Instance instead.... yeah, that would be a cleaner interface. |
| 14:21 |
|
Christineb joined #evergreen |
| 14:42 |
Dyrcona |
Hm.. I'm not sure that "flatten" or "flattenFields" is all that obvious. Flatten usually means to flatten a multidimensional array into a single dimension. I don't want to call it "deflesh" or "defleshFieds" because they sound icky and are too Evergreen-specific, though this code is pretty much only useful with Evergreen. |
| 14:42 |
Dyrcona |
I considered 'flay' for a hot minute, but that's too clever and even more ambiguous than "flatten." |
| 14:44 |
Dyrcona |
Think I'll go with "flattenFields" until something better comes along. |
| 15:07 |
|
b_bonner joined #evergreen |
| 15:37 |
Bmagic |
anyone else using the new queued ingest feature? |
| 15:40 |
|
mantis1 left #evergreen |
| 15:52 |
* Dyrcona |
does the bug wrangling after the releases last week. |
| 15:52 |
Dyrcona |
Bmagic: To answer your question, I'm not using it yet. |
| 15:57 |
|
Stompro joined #evergreen |
| 16:05 |
Bmagic |
we went live with it, and we're seeing "missing" title phrases in several interfaces. So I took one example, and pingested it, and that still doesn't produce a title in the grid. Only when I manually edit the marc and save it does it do the thing to make the title show up in the grid (item status for example) |
| 16:06 |
Bmagic |
I always assumed that pingest did all the same things as saving the record in the marc edit interface |
| 16:10 |
Dyrcona |
Bmagic: Depends. pingest runs the database functions. It may also be out of date for newer ingest requirements. |
| 16:12 |
Bmagic |
there is some magic that the interface is doing |
| 16:13 |
Dyrcona |
No. It's all done in the database. Updating the marc runs a trigger in the database. There may be new parts of that which pingest doesn't know about. |
| 16:13 |
Bmagic |
I have rows for this record in metabib.title_field_entry, as well as reporter.materialized_simple_record |
| 16:14 |
Bmagic |
so, it looks good from the database side, but the item status still doesn't show the title. It must be getting it from some other table |
| 16:14 |
Dyrcona |
Well, the new OPAC, staff client, etc. don't always use the same fields. |
| 16:18 |
Bmagic |
once I figure out which table the item status grid is using for the title, I should be able to walk backwards |
| 16:19 |
Dyrcona |
It may not be. it could be doing some transformation in code, too. There were things like that in TPAC. |
| 16:25 |
Bmagic |
it's the AngularJS grid. Whatever "Title" in the column picker does |
| 16:26 |
Bmagic |
I'm swimming in code trying to figure that one out |
| 16:29 |
Bmagic |
I think it's .factory('itemSvc', ['egCore','$q', |
| 16:34 |
jeffdavis |
at a very quick glance, looks to me like AngJS itemSvc uses simple_record |
| 16:34 |
Bmagic |
reporter.materialized_simple_record ? |
| 16:35 |
Bmagic |
up closer look, there is a row in that table for my record, but the title column is null. Bingo |
| 16:36 |
Bmagic |
I passed --rebuild-rmsr into pingest |
| 16:37 |
Bmagic |
and magically, it's fixed |
| 16:37 |
Bmagic |
Dyrcona++ |
| 16:40 |
Dyrcona |
jeffdavis++ |
| 16:49 |
Dyrcona |
Here's another hurdle to doing releases: bugmaster duties. |
| 16:54 |
Dyrcona |
I'm still working on the summary of the conversation from last Tuesday about releases. I have a narrative written up, but I want to condense it to just the important points. |
| 16:56 |
sandbergja |
because I can't resist: it's hurdles all the way down! |
| 16:57 |
kmlussier |
sandbergja++ |
| 16:57 |
sleary |
sandbergja++ |
| 17:06 |
kmlussier |
OK, 3.9 has been removed from the downloads page and 3.10 updated to security only. |
| 17:08 |
kmlussier |
And it looks like we no longer post links to tarballs on the code museum page? |
| 17:09 |
Bmagic |
kmlussier: I think the code museum should have them |
| 17:10 |
kmlussier |
Bmagic: OK, that looks like a bigger project. The last one is from 2.12. Maybe I'll tackle it when I get tuits. |
| 17:10 |
kmlussier |
Too bad I can't make tuit cookies anymore. |
| 17:10 |
Bmagic |
:) |
| 17:10 |
Bmagic |
I didn't realize it had been that* long, maybe it doesn't matter :) |
| 17:11 |
kmlussier |
2.12 was my release! :) It's irrelevant to the discussion, but it always gives me a warm fuzzy feeling when I see it. |
| 17:12 |
Bmagic |
it was a good one! |
| 17:12 |
kmlussier |
They're all good ones! Every release gets us closer to finishing Evergreen. |
| 17:13 |
Bmagic |
lol, oh yeah, I forgot! |
| 17:20 |
|
kmlussier left #evergreen |
| 22:31 |
|
jblyberg73 joined #evergreen |
| 22:32 |
|
jblyberg73 joined #evergreen |
