| Time |
Nick |
Message |
| 03:38 |
|
snigdha23 joined #evergreen |
| 03:38 |
|
snigdha23 left #evergreen |
| 03:39 |
|
snigdha26 joined #evergreen |
| 03:41 |
|
mmorgan1 joined #evergreen |
| 04:00 |
|
Sato joined #evergreen |
| 05:27 |
|
dbwells_ joined #evergreen |
| 05:30 |
|
remingtron joined #evergreen |
| 05:37 |
|
snigdha26 joined #evergreen |
| 05:42 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 07:49 |
|
collum joined #evergreen |
| 08:00 |
|
akilsdonk joined #evergreen |
| 08:00 |
|
eeevil joined #evergreen |
| 08:35 |
csharp |
so... I'm working on bug 1234927 |
| 08:35 |
pinesol_green |
Launchpad bug 1234927 in Evergreen "Reporter: needs a link Item -> Combined Aged and Active Circulations" (affected: 3, heat: 14) [Wishlist,Triaged] https://launchpad.net/bugs/1234927 - Assigned to Chris Sharp (chrissharp123) |
| 08:36 |
|
Dyrcona joined #evergreen |
| 08:36 |
csharp |
I added <link>'s for the two sources I want to link to the asset.copy source in /openils/var/web/reports/fm_IDL.xml, but they aren't showing up for me |
| 08:37 |
csharp |
I ran autogen.sh after the change, and have cleared the staff client cache - no change |
| 08:37 |
csharp |
any tips on getting those to show? |
| 08:38 |
Dyrcona |
You restarted clark and other services? |
| 08:38 |
csharp |
yes |
| 08:38 |
Dyrcona |
Also, I would change the main IDL in /openils/conf/fm_IDL.xml as well. |
| 08:38 |
csharp |
okay - I was just going to do that for good measure |
| 08:41 |
|
mmorgan1 left #evergreen |
| 08:42 |
|
mmorgan joined #evergreen |
| 08:43 |
csharp |
nope |
| 08:43 |
Dyrcona |
csharp: If that doesn't work, you should check that the other object you're linking to have reporter:core and reporter:label attributes, probably just the latter is necessary, but I don't know the reporter code. |
| 08:43 |
csharp |
damn - I'm sure this is something simple |
| 08:44 |
csharp |
ok - I'll double check |
| 08:45 |
Dyrcona |
I'd also try quitting the staff client completely and starting it up again, if you haven't done that. It may not be sufficient to just clear the cache. |
| 08:46 |
csharp |
yeah - I just tried that too - next step is to create a new profile |
| 08:47 |
csharp |
nope - new profile didn't help |
| 08:48 |
csharp |
I'll triple check the fm_IDL.xml file |
| 09:03 |
mmorgan |
csharp++ |
| 09:03 |
csharp |
okay - found a typo in both files, corrected that, restarted opensrf, ran autogen, still no dice - now I'm back to checking that I have the logic right :-/ |
| 09:04 |
|
nhilton joined #evergreen |
| 09:08 |
|
snigdha26 joined #evergreen |
| 09:09 |
|
dMiller joined #evergreen |
| 09:09 |
|
mrpeters joined #evergreen |
| 09:10 |
mmorgan |
csharp: Did you try validating the xml? Here's a tool: http://www.w3schools.com/xml/xml_validator.asp |
| 09:10 |
Dyrcona |
Well, I'm at the end of my knowledge at this point. I know how the IDL works fairly well, but not how it interacts with the reporter. |
| 09:11 |
Dyrcona |
Also, Emacs' nxml-mode will validate it for you. |
| 09:14 |
dbwells |
csharp: probably a dumb question, but are you restarting Apache as well? Could be part of "restarted opensrf", but thought I'd throw it out anyway. |
| 09:15 |
csharp |
I found the problem - I wasn't defining the field correctly |
| 09:16 |
csharp |
mmorgan: dbwells: Dyrcona: thanks for the support! |
| 09:16 |
csharp |
so... in the reports version of fm_IDL.xml, where are things like '&field.acp.last_captured_hold.label;' defined? |
| 09:16 |
csharp |
I don't see that string when grepping the source tree |
| 09:17 |
Dyrcona |
csharp: That would be in .dtd or similar file somewhere. It would lack the & and ; around it. |
| 09:18 |
Dyrcona |
Summat like so: <!ENTITY nbsp " "> |
| 09:19 |
Dyrcona |
In your case: <!ENTITY field.acp.last_captured_hold.label "Last Captured Hold"> |
| 09:24 |
|
jwoodard joined #evergreen |
| 09:24 |
|
yboston joined #evergreen |
| 09:29 |
csharp |
Dyrcona: thanks |
| 09:31 |
pinesol_green |
[evergreen|Angela Kilsdonk] 2.7 doc asciidoc fix - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6bac28f> |
| 09:32 |
|
kmlussier joined #evergreen |
| 09:39 |
|
kmlussier1 joined #evergreen |
| 09:42 |
|
kmlussier joined #evergreen |
| 09:45 |
csharp |
omg - I didn't think about all the locales |
| 09:45 |
csharp |
so... what is the proper procedure to adding a new entity to the dtd? |
| 09:47 |
csharp |
I'm looking at Open-ILS/build/i18n/po/fm_IDL.dtd/fm_IDL.dtd.pot and it looks scary |
| 09:47 |
dbs |
csharp: if you're en-us only, you can probably just replace the reporter version of fm_IDL.xml with /openils/conf/fm_IDL.xml |
| 09:47 |
csharp |
dbs: yeah, I got the en-US dtd updated, but I was hoping to contribute what I've done as a patch |
| 09:48 |
csharp |
and I figure that needs to factor in i18n |
| 09:48 |
dbs |
Evergreen/build/i18n/scripts/fieldmapper.py generates the entity-ized version of fm_IDL.xml |
| 09:48 |
dbs |
and the corresponding dtd |
| 09:49 |
csharp |
oh ok |
| 09:50 |
csharp |
so if I change the example fm_IDL.xml, is that enough for the translations tools? |
| 09:50 |
dbwells |
yes |
| 09:50 |
csharp |
excellent |
| 09:51 |
* csharp |
sighs in relief ;-) |
| 09:52 |
* tsbere |
stares at an email and wonders what prompted the choice of To: line on the part of the spammer |
| 09:52 |
|
BigRig_ joined #evergreen |
| 09:54 |
csharp |
before I do something I don't fully understand, what is 'oils_persist:virtual="true"'? |
| 09:55 |
csharp |
some fields have it and others don't, so I don't want to add it if my fields shouldn't have it or omit it if my fields need it ;-) |
| 09:55 |
jeff |
"this field does not correspond with an actual database column" |
| 09:55 |
csharp |
gotcah |
| 09:55 |
csharp |
gotcha |
| 09:55 |
csharp |
jeff: thanks |
| 09:56 |
snigdha26 |
yboston, kmlussier: I figured out a way to get around the firewall for github, but not for git. Hence, I still can't commit to the main repository :/ I made changes in the docs on the website though, like I did the last time. If you find time, could you please review and push them? |
| 09:56 |
yboston |
snigdha26: I will look at them in the next hour |
| 09:56 |
|
tspindler joined #evergreen |
| 09:57 |
snigdha26 |
yboston: thank you :) |
| 09:57 |
yboston |
snigdha26: when you can, let me know how you got around the firewall. You can send me the info by email |
| 09:58 |
snigdha26 |
yboston: sure, I'll send you an email |
| 09:59 |
jeff |
csharp: entire classes with oils_persist:virtual set to true are typically views. many (all?) fields of type link are virtual, as are some calculated fields like ahr::status. |
| 09:59 |
csharp |
jeff: excellent information, thank you |
| 10:00 |
jeff |
csharp: I think "this field does not exist in the oils_persist::tablename for this class" is a pretty good description of oils_persist:virtual=true at the field level. |
| 10:00 |
dbs |
yboston: snigdha26: you could always fall back to "git format-patch <commit hash>" and sending the patches to the mailing list via email; then a committer can apply them with "git am" |
| 10:01 |
yboston |
dbs: thanks, cab't beleive I di dnot think of this. |
| 10:01 |
yboston |
*can't |
| 10:02 |
dbs |
yboston: it's easy to get focused on a particular problem, sometimes outside perspective can help :) |
| 10:03 |
csharp |
logolepsy++ |
| 10:04 |
snigdha26 |
dbs: I'll look into that :) |
| 10:05 |
|
athira joined #evergreen |
| 10:06 |
|
Stompro joined #evergreen |
| 10:06 |
jeff |
and now i'm trying to think of where some of those virtual fields like "status" on an ahr get populated. might vary. |
| 10:07 |
jeff |
OpenILS::Application::Circ::Holds::_hold_status in the case of that specific field. |
| 10:08 |
athira |
Hello, I am a beginner and I would like to work on this bug.I don't have any idea about how to start.could someone please help me to proceed this |
| 10:08 |
Stompro |
Anyone know of any III Millennium migration docs/script that have already been developed? I'm just playing around and want to get some data into a test system. |
| 10:08 |
jeff |
athira: Welcome! Which bug are you looking at? |
| 10:09 |
athira |
jeff: https://bugs.launchpad.net/evergreen/+bug/1319964 |
| 10:09 |
pinesol_green |
Launchpad bug 1319964 in Evergreen "double-escaped entity in "Summaries & More" label" (affected: 1, heat: 6) [Low,New] - Assigned to Athira S (athirasnamby) |
| 10:09 |
athira |
jeff: this is my bug |
| 10:11 |
csharp |
Stompro: are you familiar with ESI's migration tools repo? http://git.esilibrary.com/?p=migration-tools.git;a=summary - don't know if that would have anything useful to you, but probably provides examples |
| 10:11 |
athira |
jeff: What am I suppose to do first? |
| 10:12 |
Stompro |
csharp: I did look there, but I didn't see anything III/Millennium specific at first glance. |
| 10:13 |
csharp |
ok |
| 10:15 |
kmlussier |
Stompro: You might want to check with tspindler. |
| 10:16 |
kmlussier |
athira: Have you installed Evergreen? |
| 10:16 |
|
Dyrcona joined #evergreen |
| 10:19 |
Stompro |
kmlussier: Thanks, I'll do that. |
| 10:20 |
athira |
kmlussier: No.I am confused about evergreen version. |
| 10:21 |
athira |
kmlussier: which version? |
| 10:26 |
csharp |
athira: usually with bugfixes you'd want to install the master branch (the current development version), but you could install the current stable version (2.6.X) |
| 10:29 |
kmlussier |
athira: Sorry, I'm juggling a couple of things at once. But, yes, what csharp said. |
| 10:30 |
kmlussier |
Just sending along a note that the MassLNC community demo server will be down for about an hour. |
| 10:41 |
|
evergreenTest joined #evergreen |
| 10:46 |
Dyrcona |
Probably less, we just moved it in the rack. |
| 10:47 |
|
mllewellyn joined #evergreen |
| 10:55 |
csharp |
bshum: is it too late to target bugs to 2.7.0? or should I target 2.next? |
| 10:59 |
dbs |
Bugs can always be targeted to a branch, noÉ |
| 11:00 |
berick |
yeah, target 2.7.0. it will get rolled over to 2.7.1 if/when necessary |
| 11:01 |
bshum |
csharp: dbs is correct, but given I want to cut 2.7.0 today, try to convince a core committer to get it in today if you can ;) |
| 11:01 |
* bshum |
dislikes rollover if he can avoid it. |
| 11:02 |
bshum |
2.next is really supposed to be a stub for new feature targets at this point. |
| 11:02 |
csharp |
ok |
| 11:08 |
kmlussier |
The MassLNC demo server is back up again. |
| 11:13 |
|
vlewis joined #evergreen |
| 11:16 |
|
gmcharlt joined #evergreen |
| 11:25 |
|
ericar joined #evergreen |
| 11:31 |
athira |
csharp: ok thank you |
| 11:34 |
athira |
kmlussier: Sir,I would like to work on the project "Evergreen doc site revamp" for outreach program for women".So I just went through the link about the project ideas.Now only I got to to know that you are the mentor of this project. |
| 11:37 |
athira |
kmlussier: I just started with bite-size documentation bugs |
| 11:37 |
athira |
kmlussier: Is that the right way of approaching the project? |
| 11:42 |
|
sudshekhar joined #evergreen |
| 11:47 |
kmlussier |
athira: Yes, starting with the bitsize-doc bugs is a good start. Make sure you assign yourself to the bug just to avoid two people working on the same bug at the same time. |
| 11:48 |
|
dMiller joined #evergreen |
| 11:57 |
|
jihpringle joined #evergreen |
| 12:23 |
|
buzzy joined #evergreen |
| 12:24 |
Dyrcona |
bshum: If lp 1369128 is too late for 2.7.0, I don't mind it going to 2.next. I should rewrite my code that depends on it to use open-il.cat.asset.copy.fleshed.batch.update. |
| 12:24 |
pinesol_green |
Launchpad bug 1369128 in Evergreen "No Permission in IDL to delete BRE via PCRUD" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1369128 |
| 12:42 |
|
buzzy joined #evergreen |
| 12:45 |
|
snigdha26 joined #evergreen |
| 13:01 |
|
seizonsha joined #evergreen |
| 13:05 |
fjgenus |
hi everyone |
| 13:07 |
fjgenus |
I'm trying to install Evergreen but I've run into an issue. On attempting to run the perl script to set up the database, Evergreen is throwing an error which states that it could not determine which version of postgreSQL I am using. Can someone help me please? |
| 13:12 |
|
dreuther_ joined #evergreen |
| 13:14 |
|
dMiller joined #evergreen |
| 13:16 |
csharp |
fjgenus: did you run the postgresql server install target for your linux distribution from the Makefile install? |
| 13:29 |
csharp |
okay - enriched EDI is not working for us... the copy-level data is coming through in the JEDI Message Body, but isn't present in the EDI Message Body |
| 13:29 |
csharp |
I don't see a way to troubleshoot since logging is pretty minimal |
| 13:31 |
pastebot |
"csharp" at 64.57.241.14 pasted "JEDI and EDI messages not matching" (3 lines) at http://paste.evergreen-ils.org/13 |
| 13:31 |
csharp |
bleh - no formatting |
| 13:32 |
berick |
csharp: that suggests you're not running the right version of the ruby libs |
| 13:32 |
csharp |
aha |
| 13:32 |
|
vlewis_ joined #evergreen |
| 13:34 |
Dyrcona |
csharp: is that on Ubuntu 14.04 or Debian Jessie? |
| 13:34 |
csharp |
it's actually ubuntu 12.04 |
| 13:34 |
berick |
csharp: https://bugs.launchpad.net/evergreen/+bug/1297967 (which you probably already knew about) |
| 13:34 |
pinesol_green |
Launchpad bug 1297967 in Evergreen "document openils-mapper code for enriched EDI" (affected: 1, heat: 6) [Undecided,New] |
| 13:35 |
Dyrcona |
fjgenus: That usually means the script could not talk to the database server. You need to make sure the DB is running and accepting connections from the host where Evergreen is being installed. |
| 13:41 |
fjgenus |
csharp: yes i ran the postgres-server-fedora makefile. akk the dependencies were already installed and the latest version. |
| 13:41 |
dbs |
Ah, fedora! |
| 13:41 |
csharp |
berick: both mapper.rb files are up to date |
| 13:42 |
berick |
csharp: hm, and webrick was restarted after the last update? |
| 13:42 |
csharp |
yeah |
| 13:42 |
dbs |
fjgenus: On Fedora you still need to init the database cluster and, as Dyrcona said, ensure that it is accepting connections |
| 13:42 |
|
vlewis__ joined #evergreen |
| 13:43 |
csharp |
I wonder if eeevil's comment on that bug is relevant /var/lib vs. /usr/lib |
| 13:43 |
dbs |
fjgenus: see http://docs.evergreen-ils.org/dev/_creating_the_evergreen_database.html |
| 13:43 |
csharp |
ruby deps are in /var/lib, but the openils-mapper pieces are in /usr/lib |
| 13:43 |
dbs |
ruby-- |
| 13:43 |
fjgenus |
Dyrcona: the server was running and I edited the pg_hba.conf file as per the installation files |
| 13:44 |
fjgenus |
dbs: i did initialize the database cluster |
| 13:45 |
dbs |
fjgenus: and you can connect using "psql -U <username> -h <hostname> -d <databasename>" |
| 13:46 |
csharp |
berick: checking perms... do the mapper.rb files need the execute bit? |
| 13:47 |
* csharp |
figures more would be obviously broken if so... |
| 13:47 |
dbs |
(I guess the eg_db_blah script is supposed to create the evergreen database for you, actually, but you need to be able to connect using <username> as a superuser account to do that and add extensions, etc) |
| 13:47 |
csharp |
nah, guess that's not it |
| 13:47 |
berick |
csharp: yeah, nothing would work then |
| 13:49 |
berick |
csharp: does "locate openils/mapper.rb" (or similar) show only one version of the file installed? |
| 13:49 |
berick |
IOW, it's not installed in multiple places |
| 13:49 |
csharp |
just installed in one place |
| 13:49 |
csharp |
/usr/lib/ruby/gems/1.8/gems/openils-mapper-0.9.9/lib/edi/mapper.rb |
| 13:49 |
csharp |
/usr/lib/ruby/gems/1.8/gems/openils-mapper-0.9.9/lib/openils/mapper.rb |
| 13:50 |
|
Callender_ joined #evergreen |
| 13:51 |
fjgenus |
@dbs yes. i can connect to the initial postgres database using the evergreen superuser |
| 13:51 |
pinesol_green |
fjgenus: If all else fails, try this: http://en.wikipedia.org/wiki/Rubber_duck_debugging |
| 13:51 |
berick |
csharp: grep GIR /usr/lib/ruby/gems/1.8/gems/openils-mapper-0.9.9/lib/openils/mapper.rb |
| 13:51 |
berick |
(just to be sure) |
| 13:51 |
csharp |
fjgenus: you don't need to prefix with @ when addressing someone @ is the bot trigger (just FYI) |
| 13:51 |
fjgenus |
csharp: it was an accident. too much twitter |
| 13:52 |
csharp |
berick: yep - there are GIR lines |
| 13:52 |
csharp |
fjgenus: no problem ;-) |
| 13:53 |
|
mllewellyn1 joined #evergreen |
| 13:57 |
|
bbqben joined #evergreen |
| 13:57 |
|
kmlussier joined #evergreen |
| 14:00 |
dbs |
fjgenus: what version of evergreen are you trying to install, anyway? |
| 14:00 |
berick |
csharp: Open-ILS/src/edi_translator/test_client.pl would be my next step |
| 14:01 |
csharp |
berick: cool - I'll check it out |
| 14:01 |
dbs |
fjgenus: I would personally recommend the 2.7 preview (or git master) at this point on Fedora. bleeding edge to bleeding edge, best way to heal the wounds |
| 14:04 |
|
mlauter joined #evergreen |
| 14:09 |
fjgenus |
dbs: I had cloned the repo as per the instructions on the dev:git page |
| 14:15 |
* Dyrcona |
catches up on the scroll back. |
| 14:16 |
Dyrcona |
fjgenus: So you can connect to the database server from where you have installed Evergreen, it's just the eg_db_config script that is failing, right? |
| 14:19 |
fjgenus |
Dyrcona: yes |
| 14:20 |
Dyrcona |
fjgenus: OK. So, did you already make an evergreen database? |
| 14:20 |
Dyrcona |
I ask because the eg_db_config script can create the database for you or it can be used to just do the proper configuration if you've already made the database. |
| 14:26 |
fjgenus |
Dyrcona: initially i hadn't, but i created it then tried running the script and it produced the same error |
| 14:28 |
Dyrcona |
fjgenus: What options are you using when you run the script and can you connect to the database named postgres? |
| 14:35 |
fjgenus |
Dyrcona: yes i can connect to the postgres database. options: --user evergreen --password *password i set when i created the evergreen user* --hostname localhost --port 5432 --database Evergreen (also the name of the database i created) --admin-user *admin name i chose* --admin-pass *admin password* |
| 14:39 |
Dyrcona |
fjgenus: Ok. While look something up, can you tell us what version of postgres you are using? |
| 14:41 |
vlewis__ |
How can I add "Actions for this Record" to the (Add Volumes) screen. It doesn't persist the same way it does when I pull the Holdings Maintence screen. Thanks |
| 14:43 |
|
uiuc_pat joined #evergreen |
| 14:44 |
fjgenus |
Dyrcona: PostgreSQL version 9.3.5 on i686-redhat-linux-gnu |
| 14:46 |
|
mlauter left #evergreen |
| 14:47 |
Dyrcona |
fjgenus: What does "psql -U evergreen -h localhost -p 5432 -d Evergreen -qtc 'show server_version;' | xargs | cut -c1,3 " give you? (Don't copy the "" on the outside.) |
| 14:53 |
Dyrcona |
fjgenus: When I have already created the database and extensions, I usually run eg_db-config like the following: |
| 14:53 |
Dyrcona |
eg_db_config --update-config --service=all --create-offline --user=<username> --password=<password> --database=<database> --hostname=localhost --port=5432 |
| 14:53 |
fjgenus |
Dyrcona: you asked for the options i used when i ran the script |
| 14:54 |
Dyrcona |
Yeah, the message you are getting comes from a shell script run by eg_db_config, right after it runs the command I pasted previously. |
| 14:54 |
remingtron |
kmlussier: can you point me to the commit or LP bug for the last unclaimed 2.7 feature? "Support holds targeting and fulfillment of precats for ILL"? |
| 14:54 |
remingtron |
I'm trying to understand what the change was |
| 14:55 |
kmlussier |
Not only can I point you to an LP bug, I could point you to a whole IRC discussion on that feature. :) |
| 14:55 |
kmlussier |
We had a long discussion on it at the DIG hack-a-way |
| 14:56 |
Dyrcona |
fjgenus: I think right now, you've got your password or database name wrong. |
| 14:56 |
kmlussier |
remingtron: bug 1308239 |
| 14:56 |
pinesol_green |
Launchpad bug 1308239 in Evergreen "Support targeting and fulfillment of precat copy holds (for ILL)" (affected: 2, heat: 10) [Wishlist,Fix committed] https://launchpad.net/bugs/1308239 |
| 14:56 |
Dyrcona |
when running eg_db_config. |
| 14:56 |
Dyrcona |
remingtron: changes are actually very small in the code. |
| 14:56 |
kmlussier |
remingtron: One thing that's tricky about that feature is it's used with something that really isn't documented. |
| 14:56 |
fjgenus |
Dyrcona: not likely. i used the same credentials to log into the postgres database |
| 14:57 |
fjgenus |
Drycona: are the equal signs mandatory? they're not present in the installation instructions |
| 14:57 |
kmlussier |
remingtron: It really is only used when Evergreen is working with a third-party ILL system. We weren't sure of the best way to handle it. |
| 14:58 |
Dyrcona |
fjgenus: Well what is happening is the build-db.sh script is failing to find your postgres version. |
| 14:59 |
Dyrcona |
fjgenus: Dunno. I always use them and they work. It uses the perl Getopt::Long module. |
| 14:59 |
kmlussier |
remingtron: There is more explanation on what the feature does at http://irc.evergreen-ils.org/evergreen/2014-06-23#i_107061 |
| 14:59 |
* kmlussier |
fears she won't get her last 2.7 to-do item done by deadline. :( |
| 15:00 |
fjgenus |
dbs: the one i cloned from the git repo |
| 15:01 |
jeff |
kmlussier++ for linking to that conversation. I have been meaning to revisit it. :-) |
| 15:01 |
jeff |
eeevil's comment at http://irc.evergreen-ils.org/evergreen/2014-06-23#i_107078 is relevant to any effort to document: ``berick's code allows holds on precats ... the UI-level popup you're getting would not be gone, IIRC, but automated process that don't use the UI would be allowed to do their thing'' |
| 15:02 |
jeff |
eeevil continues, ``IOW, that change is intended for automated workflows, not human ones'' |
| 15:02 |
fjgenus |
Dyrcona: I just repeated the entire installation process. i think something was wrong with my opensrf_core.xml file. thanks for all your help |
| 15:02 |
jeff |
(heck, just keep reading -- you'll probably get what you need) |
| 15:02 |
Dyrcona |
jeff remingtron berick eeevil: That feature is being used optionally in NCIP::ILS::Evergreen for NCIPServer. It works in testing, so far. |
| 15:02 |
Dyrcona |
fjgenus: OK. Glad you got it resolved. |
| 15:03 |
kmlussier |
fjgenus++ Dyrcona++ |
| 15:03 |
Dyrcona |
Hmm, maybe "testing" should be "development." :) |
| 15:03 |
kmlussier |
@praise Dyrcona |
| 15:03 |
* pinesol_green |
Dyrcona is one of the few who deserves to be praised |
| 15:04 |
* Dyrcona |
blushes. |
| 15:04 |
eeevil |
kmlussier / Dyrcona: that makes FulfILLment happy, as well |
| 15:04 |
Dyrcona |
eeevil: Cool. |
| 15:05 |
Dyrcona |
berick++ # It is a handy feature for ILL. |
| 15:05 |
eeevil |
kmlussier / remingtron: I'm not sure how much "documentation" is needed there ... there shouldn't be any user visible change, just a lifted restriction |
| 15:06 |
eeevil |
lifted coding/automation restriction |
| 15:11 |
kmlussier |
eeevil / remingtron: In the DIG meeting, we were thinking it would be useful to add something if there was documentation on working with ILL systems. Or if we ultimately had some NCIP documentation (once the work is done). |
| 15:15 |
eeevil |
kmlussier: I don't know if Dyrcona's development would benefit from it, but it's a "just works" thing for fulfillment. are you thinking more in terms of documenting a conceptual workflow for other ILL systems (innreach, etc) to make use of? |
| 15:16 |
Dyrcona |
eeevil: It just works for NCIPServer, but I've made it optional since I don't expect everyone to have 2.7 by the time it hits production. |
| 15:17 |
kmlussier |
eeevil: Yes. And I'm not necessarily saying that such documentation will be done anytime soon, but it was just a hypothetical place where we might put it if we wanted to document the removal of the restriction. But now you have me convinced it doesn't need to be documented anywhere. :) |
| 15:18 |
eeevil |
Ha! :) |
| 15:19 |
remingtron |
kmlussier: great! One less thing to document today :) |
| 15:19 |
kmlussier |
yboston / bshum: Do either of you know the status of krvmga's documentation? |
| 15:20 |
yboston |
kmlussier: no |
| 15:20 |
kmlussier |
I thought he had finished it at the hack-a-way, but I don't think I saw a working branch. |
| 15:22 |
kmlussier |
I also thought somebody had claimed the 264 docs (besides yboston). |
| 15:22 |
kmlussier |
Instead of asking questions here, I probably should put out a message to the DIG list. |
| 15:22 |
yboston |
kmlussier: joan help me find a section for me to add the new content |
| 15:22 |
|
bbqben joined #evergreen |
| 15:22 |
yboston |
*helped |
| 15:23 |
yboston |
I am wrong, I did not get help with the RDA thing |
| 15:23 |
yboston |
need to think where to put that |
| 15:23 |
yboston |
kmlussier: joan helped me with the "imported as" fix, I need to set up some imports so I can update a screenshot |
| 15:28 |
kmlussier |
Since the question of RDA support sometimes comes up, and RDA support section of the docs might be worthwhile. Something that outlines the specifics of where evergreen supports RDA. |
| 15:32 |
dbs |
kmlussier++ |
| 15:32 |
jihpringle |
yboston: the 264 RDA thing? I'm converting the Sitka docs on MARC editor to asciidoc so we can put the RDA in there |
| 15:34 |
yboston |
jihpringle: thanks, that makes sense. Let me know if I can help you with that. |
| 15:34 |
bshum |
Hmm |
| 15:35 |
jihpringle |
yboston: will do, thanks |
| 15:35 |
|
StomproJ joined #evergreen |
| 15:35 |
bshum |
Has anyone else started getting notices about changing to SHA-2 SSL certificates instead of SHA-1? |
| 15:35 |
bshum |
The thing I'm seeing is stuff like: http://blog.chromium.org/2014/09/gradually-sunsetting-sha-1.html |
| 15:35 |
yboston |
Not sure what the timieline is for that content to make it in, should I put in a short bit of content to temporarily document that change to make it into 2.7? |
| 15:35 |
yboston |
or just wait until jihpringle to finsish her work? |
| 15:35 |
bshum |
Where new Chrome 39 (expected November 2014) will mark sites with SHA-1 SSL certs beyond 2015 as... well, not great. |
| 15:36 |
yboston |
kmlussier & remingtron: see above, waht do you think? |
| 15:36 |
jeff |
bshum: What is your underlying question? :-) |
| 15:36 |
bshum |
jeff: I guess it's mostly a matter of reissuing and installing new certs. But I figure I was asking if anybody has started doing it yet? :) |
| 15:36 |
jeff |
i have. |
| 15:37 |
jihpringle |
yboston: I have most of it converted and should be able to finish it off tomorrow (I hope) |
| 15:37 |
jeff |
there are a number of issues, depending on your CA and cert provider. |
| 15:37 |
kmlussier |
yboston / remingtron: Well, if you document the short bit, it might seem that the short bit is the only RDA support we have. So I recommend waiting, especially if jihpringle can have it finished by tomorrow. |
| 15:37 |
yboston |
jihpringle: very cool, again let me know if you need help |
| 15:37 |
jeff |
i am somewhat amused to be making the statement that one of the more useful collections of information on the nature of these CA and cert provider specific issues is https://shaaaaaaaaaaaaa.com/ |
| 15:38 |
yboston |
jeff++ |
| 15:38 |
bshum |
jeff++ # Haha! Awesome. |
| 15:38 |
* dbs |
sighs as he recalls trying to get IT Services to approve a cert renewal for this reason back in SEPTEMBER |
| 15:39 |
jeff |
for anyone using RapidSSL, I can say that re-issuing is pretty easy, but you encounter the issue that RapidSSL does not yet make a SHA2 signed intermediate available. They have supposedly given Oct 1 and "mid October" as dates for when those will be available. |
| 15:39 |
dbs |
(has not happened yet of course) |
| 15:39 |
jihpringle |
kmlussier: to clarify the bit I have is info on using the MARC editor and related fields and info on the 264 field - there will need to be more work done on the additional RDA support we have, but there will be a place for it to go |
| 15:40 |
bshum |
jeff: Good to know, that's our provider too. |
| 15:41 |
remingtron |
jihpringle++ #filling in the gaps |
| 15:42 |
remingtron |
kmlussier++ yboston++ #managing docs for 2.7 |
| 15:43 |
kmlussier |
I think bshum's e-mail at http://markmail.org/message/raoie7gog47pvg6q has the general overview for what is available in terms of RDA support. So it sounds like it goes beyond what jihpringle is working on. |
| 15:44 |
bshum |
Dyrcona: I'm playing catch up on things now, but as far as your question regarding bug 1369128, I'm willing to push it in if berick is fine with it, since he was the one who raised the issue. |
| 15:44 |
pinesol_green |
Launchpad bug 1369128 in Evergreen "No Permission in IDL to delete BRE via PCRUD" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1369128 |
| 15:44 |
kmlussier |
Well, maybe not. jihpringle: When you add your info on the 264 field, will it say how it displays in the catalog and how it will be used in the reporter interface? If so, I think thats all that's needed. |
| 15:45 |
berick |
bshum: i have no objections |
| 15:45 |
jihpringle |
it could, but I know there are more RDA fields that I assume we will eventually want to add info on as well |
| 15:45 |
bshum |
berick: Cool, then I'll tap that as one more thing to get in there before I start cutting later, later tonight |
| 15:45 |
Dyrcona |
bshum: That's cool either way. I should probably make the change to my code anyway, since everyone may not be on 2.7 when this goes live for the first time. |
| 15:45 |
Dyrcona |
It would be a handy feature to have for other scripts, though. |
| 15:45 |
berick |
hmm |
| 15:46 |
berick |
the warning is very specific ;) |
| 15:46 |
berick |
there's also holds and potentially other stuff that might not get handled by direct delete |
| 15:46 |
* berick |
is just seeing the warning for the first time |
| 15:46 |
Dyrcona |
Well, I originally thought of just saying, "Don't use this unless you know what you're doing." |
| 15:47 |
berick |
yeah, that's more along the lines of what I was imagining |
| 15:47 |
Dyrcona |
But, there's no warning for cstore delete, and it's just as dangerous, even more so since no perms are required. |
| 15:48 |
eeevil |
jeff: heh ... and https://shaaaaaaaaaaaaa.com/ is using a sha-1 cert :) |
| 15:49 |
kmlussier |
jihpringle: Sure, but those RDA fields aren't supported yet, so this should work for now. :) |
| 15:49 |
jeff |
eeevil: looks SHA2 to me. |
| 15:50 |
jihpringle |
kmlussier: aren't there some 3XX fields that are at least available even if they don't really do anything? |
| 15:50 |
|
dreuther joined #evergreen |
| 15:51 |
eeevil |
jeff: huh... I must be misinterpreting the chrome info. I see its got both sha-1 and sha-256 signatures, though |
| 15:51 |
Dyrcona |
jihpringle kmlussier: MODS 3.5 pulls out some RDA stuff. I've considered looking at it and seeing if it could help our indexing, etc. |
| 15:52 |
kmlussier |
jihpringle: They're available in the MARC record, but I dont' think we're displaying them by default or doing anything else with them yet. |
| 15:57 |
jeff |
eeevil: you might be looking at the fingerprint vs the signature algorithm. |
| 15:58 |
eeevil |
jeff: I was. and also the basic "connection" info, instead of the cert itself |
| 16:03 |
|
kbutler joined #evergreen |
| 16:09 |
pinesol_green |
[evergreen|Chris Sharp] LP#1357364: Allow for sites that may have the intarray extension already installed. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=47f9e39> |
| 16:09 |
pinesol_green |
[evergreen|Chris Sharp] LP#1357364: Explictly create the extension in the "public" schema. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1a1169f> |
| 16:11 |
kmlussier |
@marc 500 |
| 16:11 |
pinesol_green |
kmlussier: General information for which a specialized 5XX note field has not been defined. (Repeatable) [a,3,5,6,8] |
| 16:13 |
pinesol_green |
[evergreen|Jason Boyer] LP#1340947: Finish support in oils_ctl.sh for -y and -z options - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8f4f16b> |
| 16:14 |
bshum |
gmcharlt: Assuming that https://bugs.launchpad.net/evergreen/+bug/1358916 should be backported as well to previous supported versions of EG? |
| 16:14 |
pinesol_green |
Launchpad bug 1358916 in Evergreen "attempting to retrieve an invalid MARC record via Z39.50 can result in unexpected memory consumption" (affected: 1, heat: 6) [Undecided,New] |
| 16:15 |
kmlussier |
Hmmm...so is the 500 tag indexed in Evergreen? The mods-to-marc map I rely on says no. |
| 16:16 |
|
gsams joined #evergreen |
| 16:18 |
* bshum |
decides to call it a "bug fix" and backports |
| 16:21 |
pinesol_green |
[evergreen|Galen Charlton] LP#1358916: refuse to retrieve over-large MARC records via Z39.50 - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1708f88> |
| 16:21 |
gmcharlt |
bshum: yep; no need for you to undo the backporting :) |
| 16:25 |
bshum |
I'm just going through awaiting pullrequests for bug fixes, etc. |
| 16:25 |
pinesol_green |
[evergreen|Jason Stephenson] LP 1350345: marc_export blows up on bad records. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=dce8be1> |
| 16:31 |
pinesol_green |
[evergreen|Steven Callender] LP#1292129: Removed deleted call numbers from the search results to properly show copy count. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=f513ea3> |
| 16:32 |
|
tspindler left #evergreen |
| 16:35 |
pinesol_green |
[evergreen|Bill Erickson] LP#1325720 Repair fund rollover year selector query - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6ad1181> |
| 16:39 |
bshum |
dbs++ # transparency is good :) |
| 16:39 |
pinesol_green |
[evergreen|Kathy Lussier] LP1309131 - Fix series link - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=82b743d> |
| 16:41 |
gmcharlt |
dbs++ |
| 16:42 |
kmlussier |
dbs++ RoganH++ |
| 16:43 |
pinesol_green |
[evergreen|Bill Erickson] LP#1356576 repair sip date_format config typo - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=bdabe1c> |
| 16:54 |
dbwells |
bshum: There are quite a few bugs targetted at 2.6.4 which for some reason aren't targetted at 2.7.0 (some still point to 2.next, others to beta, etc.). Can I point these to 2.7.0, or should they skip to 2.7.1 at this point? |
| 16:55 |
bshum |
dbwells: What status are those bugs? |
| 16:55 |
* bshum |
hasn't looked that far yet |
| 16:55 |
dbwells |
bshum: the majority are simple "new" |
| 16:55 |
dbwells |
https://launchpad.net/evergreen/+milestone/2.6.4 |
| 16:56 |
bshum |
dbwells: Well, if they have actual code to be pulled, I say we can either do last minute pushing (which is what I'm doing now and fixing the 2.7 targets, etc. as I go) |
| 16:57 |
dbwells |
I was just looking at the 2.7.0 list and was wondering where all of our bugs went :) |
| 16:57 |
bshum |
Or we can leave them to point at 2.next or 2.7.1 (whenever we make it) |
| 16:57 |
bshum |
Like https://bugs.launchpad.net/evergreen/+bug/1246859 is pointed at 2.next |
| 16:57 |
pinesol_green |
Launchpad bug 1246859 in Evergreen 2.5 "Loading a staged user can result in a UUID username" (affected: 1, heat: 6) [Medium,Confirmed] |
| 16:57 |
bshum |
But I'm about to point it at 2.7.0 when I push it |
| 16:58 |
dbwells |
I'd think 2.next should be only for features |
| 16:58 |
bshum |
Sounds reasonable to me. |
| 17:00 |
dbwells |
I was looking at bug #1331127, which is what prompted the question. |
| 17:00 |
pinesol_green |
Launchpad bug 1331127 in Evergreen "serials previous issuance copy location randomly fails to apply" (affected: 1, heat: 6) [Undecided,Confirmed] https://launchpad.net/bugs/1331127 |
| 17:01 |
|
kmlussier left #evergreen |
| 17:01 |
bshum |
dbwells: Well, it's not too late to sign and push to 2.7.0 for that one ;) |
| 17:01 |
pinesol_green |
[evergreen|Jeff Godin] LP#1246859: Improve username flow for staged users - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=62b7ae2> |
| 17:02 |
jeff |
yay! \o/ |
| 17:02 |
dbwells |
bshum: I am not sure what the severity of the bugs on the 2.6.4 list are, I just didn't want you to cut 2.7.0 on the false assumption that the 2.7.0 tag was all the bugs :) |
| 17:03 |
bshum |
Hehe |
| 17:06 |
bshum |
dbwells: I'm grabbing things based on what's got a "pullrequest" on them and fixing up targets as I work down the big list. |
| 17:07 |
bshum |
Maybe after I hang up my RM cape, I can put back on my bug wrangler gloves. |
| 17:07 |
|
mmorgan left #evergreen |
| 17:09 |
pinesol_green |
[evergreen|Remington Steed] LP#1361801: Add required fields to serial issuance form - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=3e96e05> |
| 17:14 |
bshum |
Okay, taking a short break now to go run an errand before dinner. |
| 17:14 |
bshum |
I'll poke at things more later tonight. |
| 17:15 |
bshum |
dbwells: Please feel free to fix up any bug targets that seem wrong to you. I'll poke at it more myself later. |
| 17:15 |
pinesol_green |
[evergreen|Galen Charlton] LP#1370630: don't log mod_deflate actions by default - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=7ca67b5> |
| 17:15 |
pinesol_green |
[evergreen|Jason Stephenson] LP 1369128: Add delete permission to fm_IDL.xml for class bre. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d2e7529> |
| 17:25 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 17:34 |
csharp |
@quote add < bshum> Maybe after I hang up my RM cape, I can put back on my bug wrangler gloves. |
| 17:34 |
pinesol_green |
csharp: The operation succeeded. Quote #92 added. |
| 17:34 |
csharp |
@quote random |
| 17:35 |
pinesol_green |
csharp: Quote #53: "<StephenGWills> damn! I love my job :)" (added by Dyrcona at 12:19 PM, April 16, 2013) |
| 17:35 |
csharp |
seen StephenGWills |
| 17:35 |
csharp |
@seen StephenGWills |
| 17:35 |
pinesol_green |
csharp: StephenGWills was last seen in #evergreen 25 weeks, 6 days, 4 hours, 41 minutes, and 4 seconds ago: <StephenGWills> +1 |
| 18:18 |
pinesol_green |
[evergreen|Bill Erickson] LP#1331127 Repair sort logic of previous issuances - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=6dfdbb0> |
| 18:21 |
|
akilsdonk joined #evergreen |
| 18:28 |
|
buzzy joined #evergreen |
| 18:45 |
|
Dyrcona joined #evergreen |
| 19:50 |
bshum |
@later tell eeevil Hmm, it'll be going on a year next month, but curious if you did any further analysis/fixes with https://bugs.launchpad.net/evergreen/+bug/1241024 ? |
| 19:50 |
pinesol_green |
bshum: The operation succeeded. |
| 19:50 |
pinesol_green |
Launchpad bug 1241024 in Evergreen 2.6 "off by one calendar day when using create_date in search" (affected: 1, heat: 8) [Low,Confirmed] |
| 19:51 |
|
remingtron joined #evergreen |
| 19:51 |
|
dbwells joined #evergreen |
| 19:54 |
pinesol_green |
[evergreen|Pasi Kallinen] LP#1231634: Mark Floating Groups Config UI strings translatable. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4dd61e0> |
| 19:54 |
|
kmlussier joined #evergreen |
| 19:54 |
|
sandbergja joined #evergreen |
| 20:04 |
pinesol_green |
[evergreen|Steven Chan] Fix LP904860, Cannot print a patron address label - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ba6a9a9> |
| 20:08 |
bshum |
paxed++ # still pulling in your patches months later, miss you guys! |
| 20:10 |
pinesol_green |
[evergreen|Mike Rylander] LP#1251347: Get the most recent session locale for Event description translation - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=eabce0a> |
| 20:14 |
kmlussier |
Why does git hate me? |
| 20:14 |
kmlussier |
Oh, I know why it hates me. Dumb mistake. |
| 20:15 |
bshum |
kmlussier: It might be hating you because I keep pushing more stuff into master |
| 20:15 |
kmlussier |
bshum: No, I checked for that before whining. |
| 20:15 |
kmlussier |
bshum: I force pushed those updates to http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/kmlussier/more-2_7-release-note-additions |
| 20:16 |
kmlussier |
I still am hoping somebody can review what I wrote for the web client and finish it before it goes in. |
| 20:16 |
pinesol_green |
[evergreen|Jason Stephenson] LP 1319560: Silence template error messages in Apache error log. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1000e74> |
| 20:16 |
pinesol_green |
[evergreen|Jason Stephenson] LP 1319560: Fix the disappearing hold button. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1cb3134> |
| 20:16 |
pinesol_green |
[evergreen|Jason Stephenson] LP 1319560: Another fix for summary.tt2. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=3a01aa7> |
| 20:16 |
bshum |
kmlussier: I'm reading it right now |
| 20:18 |
bshum |
kmlussier: I like it! |
| 20:18 |
bshum |
We just have to end the ... there at the end |
| 20:18 |
bshum |
:) |
| 20:18 |
kmlussier |
Yes, well I don't know what to put there. That's where your contribution comes in. :) |
| 20:18 |
bshum |
Yeah I'll do what I can on that. |
| 20:18 |
bshum |
I haven't had a chance to write through the web client steps into the main README yet. |
| 20:18 |
kmlussier |
I figured you would just link to whatever you've been working on. |
| 20:19 |
kmlussier |
Ah, well. Maybe we can say "coming soon: README instructions on how to implement this." |
| 20:19 |
bshum |
We could do that. |
| 20:19 |
bshum |
The instructions need more polish I think than what's in the existing directory |
| 20:24 |
* kmlussier |
needs to scoot for now. |
| 20:40 |
pinesol_green |
[evergreen|Kathy Lussier] lp1271198 Strip browse and facet parameters from links - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=995b6c4> |
| 20:40 |
fjgenus |
quit Leaving. |
| 20:46 |
pinesol_green |
[evergreen|Kathy Lussier] More additions to 2.7 Release Notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d44c97a> |
| 20:46 |
pinesol_green |
[evergreen|Ben Shum] More additions to 2.7 Release Notes (part 2) - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9e67c5b> |
| 20:58 |
pinesol_green |
[evergreen|Chris Sharp] LP#1371173: Reporter: Classic Item List needs link to Item source - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=97bbbdf> |
| 20:58 |
pinesol_green |
[evergreen|Chris Sharp] LP#1234927 Reporter needs Item -> Combined Aged and Active Circulations link - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8669b1c> |
| 20:58 |
pinesol_green |
[evergreen|Chris Sharp] LP#1234927: Pluralizing link names to follow convention. - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1d18f19> |
| 21:11 |
bshum |
Okay I think that's it for now. |
| 21:11 |
eeevil |
bshum: without an appropriate index, I fear senator's patch. With one, it'd be fine. I can offer that tomorrow, or for 2.7.1 |
| 21:13 |
bshum |
eeevil: We can save it as a bug fix for 2.7.1. No rush, thanks Mike! |
| 21:21 |
bshum |
Okay, 2.7.0 milestone is now closed. |
| 21:21 |
bshum |
There is a new milestone for 2.7.1 now. |
| 21:41 |
|
b_bonner joined #evergreen |
| 21:41 |
|
mnsri_ joined #evergreen |
| 21:42 |
|
mtcarlson_away joined #evergreen |
| 22:11 |
|
sarabee_ joined #evergreen |
| 22:17 |
Dyrcona |
Good night, Evergreen! |
| 22:32 |
pinesol_green |
[evergreen|Ben Shum] Update core committer information on the staff client's About Page - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=116e9de> |
| 23:05 |
jeff |
RapidSSL SHA256 intermediate is available from here: https://knowledge.rapidssl.com/support/ssl-certificate-support/index?page=content&actp=CROSSLINK&id=SO26459 You'll likely want/need to reissue your cert from here: https://products.geotrust.com/orders/orderinformation/authentication.do |
| 23:08 |
bshum |
jeff++ # thanks |
| 23:08 |
* bshum |
is uploading 2.7.0 into place now. |
| 23:09 |
jeff |
bshum++ |
| 23:10 |
jeff |
nice that they got that out before Oct 1 |
| 23:39 |
* bshum |
will finish the blog post and email summary later tomorrow. |
| 23:39 |
bshum |
Zzzz |
