Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Friday, December 3rd, 2010

< Thursday, December 2nd, 2010Raw Log FileSaturday, December 4th, 2010 >
#TimeNickMessage
#00:40:19tildeequals has quit IRC
#01:20:32jamesrf has quit IRC
#02:01:10dbs has quit IRC
#02:01:25dbs has joined #evergreen
#02:06:38atz_ has quit IRC
#02:07:12atz_ has joined #evergreen
#07:28:11sfortin has joined #evergreen
#08:09:40artunit has quit IRC
#08:09:53artunit has joined #evergreen
#08:48:41rsinger has quit IRC
#09:04:04Meliss has joined #evergreen
#09:06:18eeevilcall for testing: http://svn.open-ils.org/trac/ILS/changeset/18901 on any version (note the bug link) ... TIA!
#09:09:11rsinger has joined #evergreen
#09:23:08kmlussier has joined #evergreen
#09:32:50jenny has joined #evergreen
#09:32:54cbandito has joined #evergreen
#09:51:50mrpeters-isleeevil: applying it to our migration server now and i will check it out for you
#09:52:26eeevilthanks!
#09:54:13mrpeters-isldone!
#09:54:26mrpeters-islwe get no results (maybe we don't have any items by madonna! lol)
#09:54:44mrpeters-islauthor:"Madonna" title:-sex -music was the query....whcih appears to not have the extra white spaces
#09:55:57eeevilmrpeters-isl: thanks ... you can replace Madonna with Rowling and sec and music with foo and bar to test
#09:56:04mrpeters-isl10-4
#09:56:16mrpeters-islthe key is that extra space in front of " foo" right?
#09:56:48mrpeters-islhmmm no results for author:Rowling title:-foo -bar which is hard to imagine
#09:57:09mrpeters-islhttp://mig.evergreen.lib.in.us/opac/en-US/skin/default/xml/advanced.xml if you want to confirm
#09:57:28eeevilrigth
#09:57:36eeevilany extra spaces, actually
#09:57:41mrpeters-isloh, but matches exactly "Rowling"
#09:57:46mrpeters-islthat will be why we get no results
#09:58:20mrpeters-islshoot...using "Contains" 'Rowling' gives no results
#09:59:35mrpeters-islhttp://mig.evergreen.lib.in.us/opac/skin/default/js/adv_global.js shows the patch...no need to restart services or anything right?
#10:00:16eeeviljust shift-reload, perhaps
#10:00:19dbsclear cache in your browser
#10:00:32dbs(not that I trust shift-reload to clear cache anymore)
#10:00:55mrpeters-islill use a new browser just in cas
#10:01:10eeevillooks like your harry potter records contain either (stemmed-to) foo or bar
#10:02:16mrpeters-islwell, it at least seems like the patch worked since the search string trims out the white space properly, right?
#10:05:13mrpeters-islon another subject - runing through 1.6.1-2.0-upgrade-db.sql -- SELECT SETVAL('asset.uri'::TEXT, (SELECT MAX(id) + 1 FROM asset.uri)); -- gives an error "ERROR: "uri" is not a sequence" (I've got this set to stop on error) is this something that should be ignored or an actual error
#10:08:48dbsmrpeters-isl: it should be SELECT SETVAL('asset.uri_id_seq'::TEXT...
#10:09:05dbsmrpeters-isl: this in beta4?
#10:09:10mrpeters-islbeta 3 still...
#10:09:26mrpeters-islshould i just go right from 1.6.1 to beta 4?
#10:09:38dbsyeah
#10:09:42eeevilmrpeters-isl: if you want to test b4, yes
#10:10:11mrpeters-islok. the biggest problem is we had a bunch of the triggered event stuff backported to our 1.6 database so i'm having a heck of a time making the jump to any of the 2.0's
#10:10:29mrpeters-isli had the beta 3 upgrade script trimmed down to take care of most of those
#10:10:36mrpeters-islbut i can do that again
#10:10:56eeevilmrpeters-isl: diff the original b3 and b4 scripts to show you what to /add/ to your trimmed script
#10:11:23mrpeters-islyep thats the plan after i sew them back together :)
#10:15:25dbsheh. the weirdest thing about the flexibilitylab document in that obviously errant email to the general list is that I actually understand most of what I've scanned. benefit or downfall of having a kinesiologist spouse :)
#10:21:27yboston has joined #evergreen
#10:25:33Barb has joined #evergreen
#10:31:14mrpeters-islok, even with -- Push the auri sequence in case it's out of date
#10:31:14mrpeters-isl-- Add 2 as the sequence value must be 1 or higher, and seed is -1
#10:31:14mrpeters-islSELECT SETVAL('asset.uri_id_seq'::TEXT, (SELECT MAX(id) + 2 FROM asset.uri));
#10:31:14mrpeters-isl I'm still getting the uri not a sequence error :(
#10:32:10mrpeters-islwait..ignore me
#10:32:18mrpeters-islthats an old error
#10:38:51natschil has joined #evergreen
#10:41:00phasefxa contribution to the community hive mind: errors with bib merging may be due to a disabled or mangled protect_bib_rec_delete rule on biblio.record_entry. I've seen that twice now
#10:41:33dbsphasefx++ # taking care of dangling or unanswered threads
#10:45:05Granitize1 has joined #evergreen
#10:51:41phasefxthe formats menu in the OPAC, I figure it's easy to trim stuff from it, but where should I look for adding things? In the opac xml, am I just able to specify combinations of codes from config.item_type_map?
#10:56:08eeevilphasefx: and item_form
#10:58:22phasefxah, so separate the two with a dash
#10:58:31phasefxeeevil++
#11:05:22natschil has quit IRC
#11:10:44mrpeters-islb4 upgrade craps out on CREATE INDEX metabib_author_field_entry_source_idx ON metabib.author_field_entry (source);
#11:11:09mrpeters-islERROR: relation "metabib_author_field_entry_source_idx" already exists
#11:11:14mrpeters-islthen kills the xact
#11:24:07parsr has joined #evergreen
#11:24:08b_bonner has joined #evergreen
#11:24:33b_bonner has joined #evergreen
#12:01:13parsrOpenSRF - current version is 1.6.1 but recall seeing talk of patch coming - patch is not yet available, correct?
#12:01:35parsrAlso, sample scenario say you have OpenSRF 1.6.1 & EG 1.6.1.4 - Would you ever do just an upgrade to OpenSRF (say 1.6.1 to 1.6.2) and not touch openils (or do you need to recompile your Evergreen against any new OpenSRF)?
#12:02:16parsri.e. can you just upgrade OpenSRF by itself if patch available?
#12:10:42tsbere throws some SQL thought for stuff from earlier this morning at mrpeters-isl: SELECT SETVAL('asset.uri_id_seq'::TEXT, (SELECT GREATEST(MAX(id),0)+1 FROM asset.uri));
#12:11:05eeevilparsr: it would be safest to recompile EG ... until we can find the properly shaped tuits to implement library versioning in the autotools bits
#12:13:49dbseeevil: library versioning is in OpenSRF trunk
#12:14:28dbstsbere: could do that for maximum conservation of one sequence ID, but... have you looked at the ingest logic for uris?
#12:14:38dbs1 sequence ID is nothing compared to 1000
#12:15:04tsberedbs: I saw the +2 workaround in the scrollback. That is about it. <_<
#12:15:14eeevildbs: really?!
#12:15:16eeevildbs++
#12:15:28dbseeevil: heh. two line patch or something :)
#12:16:30eeevildbs: the -version-info bit?
#12:17:01dbsyup
#12:17:36eeevilnice ... one small line for autotools, one giant leap for opensrf apps
#12:17:42tsberedbs: Also, I have never looked at any ingest logic. If anyone here has, it is Dyrcona.
#12:17:48dbsI probably should have included a comment that summarizes how -version-info works, because it's pretty much an accident that 2.0.0 matches version 2.0.0
#12:19:28b_bonner has quit IRC
#12:27:04dbscurrent 1.6 behaviour increments callnumber and asset.uri by 1000 for every record that contains a located URI, IIRC
#12:28:28dbshmm, that can't be right, we're only at 14533906 for asset.uri
#12:28:47dbsand 6293965 for acn
#12:32:30tsbereAny chance of pointing me at the SQL files that define that stuff? Or it is in the perl layer?
#12:32:57dbsIn 1.6, it's perl (OpenILS/Application/Ingest.pm)
#12:33:32dbsin trunk, the behaviour is much nicer, and defined in SQL (030.metabib I believe in the indexing_ingest_or_delete trigger)
#12:35:53tsbereLooks reasonable in the sql form, but I don't think I could do going over it justice for a week or two (assuming I started learning how that all works today, instead of doing other things that need to be done)
#12:39:20dbshmm, up to asset.uri.id = 14779396 now
#12:40:05dbsin the process of ingesting about 5,000 records with URIs. fun fun
#12:41:35tsbere finds himself wondering if he will need to re-write his receipt printer program for the legacy ils to work with evergreen in some fashion :(
#12:46:58sfortin has quit IRC
#12:47:31tsbereI just got off the phone with a library that doesn't think their receipt printers are recent enough to have windows drivers. :(
#12:47:34b_bonner has joined #evergreen
#12:49:38dbswhoa
#12:49:54dbsthey probably have linux drivers though... :)
#12:50:54tsbereJust got a correction via email: They might be able to find drivers, if the brand and model identifiers weren't all missing. The thing is so old the labels and such are all worn to nothingness.
#12:53:35mtcarlson has joined #evergreen
#13:16:54mjg_ has joined #evergreen
#13:18:53parsr has quit IRC
#13:19:53jenny has quit IRC
#13:30:45mrpeters-islany thoughts on why the 1.6.1 to 2.0 upgrade from beta 4 is dying out at ERROR: relation "metabib_author_field_entry_source_idx" already exists? I have this index in even my 1.6.0.0 server, so of course it exists?
#13:31:24mrpeters-islperhaps I need to DROP INDEX IF EXISTS in the script before it tries to create those 4 indexes?
#13:31:50eeevilperhaps. I suggest dropping it and trying again
#13:32:13mrpeters-isleeevil: ok, but it's normal that those exist prior to 2.0 right?
#13:32:25mrpeters-island this isn't some customization that i'm forgetting about?
#13:33:37mrpeters-islok now this is funky - evergreen=# DROP INDEX metabib_author_field_entry_source_idx;
#13:33:37mrpeters-islERROR: index "metabib_author_field_entry_source_idx" does not exist
#13:34:12mrpeters-islits almost like the transaction is trying to do this twice
#13:34:15mrpeters-islCREATE INDEX metabib_title_field_entry_value_idx ON metabib.title_field_entry (SUBSTRING(value,1,1024)) WHERE index_vector = ''::TSVECTOR;
#13:34:33mrpeters-islthen ... CREATE INDEX metabib_title_field_entry_source_idx ON metabib.title_field_entry (source); just a bit later
#13:34:48mrpeters-islerr...i meant
#13:34:48mrpeters-islCREATE INDEX metabib_author_field_entry_source_idx ON metabib.author_field_entry (source);
#13:35:54mrpeters-islah value != source
#13:36:00eeevilyeah
#13:37:43eeevilif we're going to do that, and I don't know that we should, we should drop them before (or inside with IF EXISTS) the transaction
#13:38:27mrpeters-islwhats puzzling me is where they got dropped in the first place
#13:38:38eeevilthey don't
#13:38:41mrpeters-islbecause if i try to drop them now, it says they aren't there
#13:39:04eeeviltrac is complaining about the file being to big to annotate, so doing that from the shell now
#13:39:22mrpeters-islheh yeah this is a monster script
#13:40:30mrpeters-islpostgresql-8.4-main.log:2010-12-03 12:09:22 EST STATEMENT: CREATE INDEX metabib_author_field_entry_source_idx ON metabib.author_field_entry (source);
#13:40:30mrpeters-islpostgresql-8.4-main.log:2010-12-03 12:50:02 EST ERROR: relation "metabib_author_field_entry_source_idx" already exists
#13:40:31mrpeters-islpostgresql-8.4-main.log:2010-12-03 12:50:02 EST STATEMENT: CREATE INDEX metabib_author_field_entry_source_idx ON metabib.author_field_entry (source);
#13:40:35mrpeters-islthose should be relevant lines from the postgres logs
#13:41:00mrpeters-isli guess it took some time to error, since this started at 12:09 and died at 12:50
#13:41:50eeevilor from two runs of your chopped up script?
#13:42:36mrpeters-islprobably more likely
#13:42:42mrpeters-isli'm using 1 single script now though
#13:42:56mrpeters-islcan't remember what time i started the most recent run...sometime before lunch
#13:43:04eeevilmrpeters-isl: you know, I bet those are not stock indexes ... they were added to your db by hand, not by default schemas
#13:43:27eeevilnot stock in 1.6 I mean
#13:43:32mrpeters-isleeevil: very possible. so i'm wondering if now that they are gone, the upgrade might just run properly
#13:43:44eeevilif you've dropped them, it should
#13:43:53mrpeters-islok. i will give it another pass
#13:44:46mrpeters-islit's vaguely familiar that gmcharlt might have added (or advised us to add) those extra indexes a while back
#13:48:10djfiander has joined #evergreen
#13:49:07afterl has joined #evergreen
#13:49:38djfianderNCIP is making my brain melt.
#13:50:01dbsdjfiander: was it the brown NCIP? I heard that stuff was bad.
#13:50:49afterl_ has joined #evergreen
#13:50:57djfianderno, this is NCIP classic.
#13:51:24afterl_dbs is funny
#13:52:12dbsfwiw, there appears to be no indexes other than the index vector created on metabib.author_field_entry in stock rel_1_6; that said, we can chalk it up as a best learning practice to DROP IF EXISTS anything droppable before creating in the future, I guess
#13:52:59dbsUnless, perhaps, somebody defines a local object "foo" with a vastly different meaning than the newly introduced one - in which case, erroring is good.
#13:53:02dbs is so conflicted
#13:53:02mrpeters-islheh all i do is cause trouble
#13:54:19bshum has joined #evergreen
#13:54:26afterl has quit IRC
#13:55:47afterl_ has quit IRC
#14:00:50afterl has joined #evergreen
#14:06:45afterl has quit IRC
#14:13:16[1]Marduk has joined #evergreen
#14:15:05mrpeters-islCURSE! ERROR: relation "metabib_author_field_entry_source_idx" already exists
#14:15:24mrpeters-islevergreen=# DROP INDEX metabib_author_field_entry_source_idx;
#14:15:24mrpeters-islERROR: index "metabib_author_field_entry_source_idx" does not exist
#14:15:29mrpeters-islso which is it! ugh!
#14:16:05phasefxprobably a path thing. may need to specify the table along with the index for the drop
#14:16:11dbsprobably DROP INDEX metabib.metabib_author...
#14:16:33dbs(needs to be schema-qualified)
#14:16:40mrpeters-islah yes that did the trick
#14:16:50phasefx wrong, dbs right. unga bunga
#14:18:11afterl has joined #evergreen
#14:18:13mrpeters-isl crosses fingers this time
#14:18:26bshummrpeters-isl++ # digging at the 1.6.1-2.0 upgrade script
#14:19:07mrpeters-islhah i'm not sure i'm doing much good!
#14:20:01mrpeters-islexcept for causing dbs to be conflicted :P
#14:20:09bshumI've been there ;)
#14:20:18bshumSpeaking of metabib stuff
#14:21:02bshumI've been poking at this blog post by dbs about adding additional indexes and weights for relevance: http://coffeecode.net/archives/218-Adjusting-relevancy-rankings-in-Evergreen-1.6,-some-explorations.html
#14:21:31bshumHave you poked at this more lately dbs? I just implemented part of this to increase title matches for general keyword searches.
#14:22:24bshumOr anyone else for that matter.
#14:22:46bshumI've been wondering if we'd need to modify triggers or whatnot to generate the additional metabib entries
#14:22:51bshumFor new bibs we import
#14:22:53bshumOr create
#14:26:05Maryll has joined #evergreen
#14:26:27dbsShould get generated automatically on ingest or reingest IIRC
#14:27:17[1]Marduk has quit IRC
#14:28:00afterl has quit IRC
#14:28:08bshumdbs: Oh really? That's awesome... wasn't sure if I needed extra steps.
#14:28:45bshumThanks :)
#14:28:56bshumI'll test it some more and see what happens.
#14:33:44eeevilbshum: anything updated or inserted after the definition is added uses the definition it sees. also, changing the weight value does /not/ require reingesting
#14:34:32eeevilbshum: only changing the xpath (or search_field/facet_field) would, for existing index defs
#14:36:21bshumeeevil: Ah alright. Neat.
#14:37:30Maryll has quit IRC
#14:37:42bshumWell, wandering out for the weekend. Have a good one everyone
#14:37:44dbs has quit IRC
#14:37:58Maryll has joined #evergreen
#14:38:09bshum has quit IRC
#14:39:49Maryll has left #evergreen
#14:54:13mrpeters-islgotta ask another one - CREATE INDEX metabib_series_field_entry_source_idx ON metabib.series_field_entry (source); is giving postgresql-8.4-main.log:2010-12-03 14:48:03 EST DETAIL: Key (source)=(5300001) is not present in table "record_entry".
#14:54:28mrpeters-islsource = bre.id correct?
#14:55:40mrpeters-islthus, if i don't have a bre.id = 5300001 why is it keying on one with that source?
#14:56:10mrpeters-islah doh you know what
#14:56:20eeevilcorrect ... there was, at one, a missing fkey there. looks like it still is missing on your db ;)
#14:56:20mrpeters-islwith those earlier DROP INDEXES i bet i need to truncate all of those tables
#14:56:30eeevilno, don't truncate those
#14:56:33mrpeters-islno? ok
#14:56:50mrpeters-islSELECT * FROM metabib.series_field_entry WHERE source=5300001; returns a row, but there is no corresponding bre
#14:56:56mrpeters-islso just delete from those tables where source NOT IN bre?
#14:57:10eeeviljust: DELETE FROM metabib.series_field_entry WHERE source NOT IN (select id from biblio.record_entry);
#14:57:14eeevilright
#14:57:17mrpeters-islawesome ok
#14:57:30jeff has quit IRC
#14:57:41mrpeters-islso, this is probably something noone else will run into?
#14:57:51eeevilunsure...
#14:58:36mrpeters-islok i dont want to cause confusion based on things that could be my fault
#15:00:54mrpeters-islnew topic - we're getting searches that hang up in our database for 15, 20... minutes at a time
#15:00:59mrpeters-islit appears to be when an & is used
#15:01:08mrpeters-isl 22430 | 00:18:03.607991 | SELECT *
#15:01:08mrpeters-isl : FROM search.staged_fts(
#15:01:08mrpeters-isl : 162::INT,
#15:01:08mrpeters-isl : 2::INT,
#15:01:08mrpeters-isl : $${"author":{"fts_query":["to_tsquery('author','debbie&macomber')"],"word":["debbie","macomber"],"fts_rank":["rank(author.index_vector, to_tsquery('author','debbie&macomber'))"],"phrase":[]},"title":{"fts_query":["to_tsquery('title','someday&soon')"],"word":["someday","soon"],"fts_rank":["rank(title.index_vector, to_tsquery('title','someday&
#15:01:09mrpeters-islsoon'))"],"phrase":[]}}$$::TEXT,
#15:01:30mrpeters-islif not checked, these just run on and on and on (and this is in our production enviornment)
#15:01:54mrpeters-isljust curious if anyone else has seen similiar behavor
#15:03:44eeevilmrpeters-isl: without the full query, and looking at it in your env, I couldn't say.
#15:04:05jenny has joined #evergreen
#15:04:25mrpeters-islok np
#15:04:51mrpeters-isli've just been killing them off with pg_cancel_backend when they get out of hand and run for over 20 min
#15:11:37jeff has joined #evergreen
#15:20:49Granitize1any more talk of indexing solr with evergreen?
#15:21:03Granitize1er… evergreen with solr
#15:24:59eeevilnothing concrete, just "it'd be neat if..."
#15:25:21eeevilGranitize1: there are Hard(tm) problems to be solved there
#15:27:41eeevilif we want to provide a true replacement indexing backend, and not just a bolt-on separate interface
#15:30:33b_bonner has quit IRC
#15:34:10mrpeters-islERROR: insert or update on table "metabib_search_alias" violates foreign key constraint "metabib_search_alias_field_fkey"
#15:34:11mrpeters-islDETAIL: Key (field)=(16) is not present in table "metabib_field".
#15:34:14mrpeters-islnot familiar with this table....
#15:34:17mrpeters-islnew in 2.0?
#15:34:40Granitize1eeevil: bolt on would go a long way to facilitating a meta-search with other indexes… for the meta-search lovers out there.
#15:35:36Granitize1eeevil: guess a schedules export/import into an existing index would be possible.
#15:36:16b_bonner has joined #evergreen
#15:36:53eeevilGranitize1: bolt-on is outside the scope of EG proper, unless the command-line export tools need work to facilitate it ... I think they're smart enough today, though
#15:36:56mrpeters-islI assume the INSERT INTO config.metabib_search_alias (alias,field_class,field) VALUES ('bib.subjectoccupation','subject',16); is where I'm failing...since my config.metabib_field only goes up to 15?
#15:37:33eeevilmrpeters-isl: possibly ... there's a whole pile of new defs you should have from earlier in the upgrade script
#15:37:57mrpeters-islhmmm i have 17, 18, 19...
#15:37:59mrpeters-islbut no 16
#15:38:18mrpeters-islcomes right after -- resolves performance issue noted by EG Indiana in the upgrade script
#15:38:52mrpeters-islis it possible #16 was left out accidentally? or should i have it from an earlier release than 1.6.1
#15:39:17eeevilI think you should have 16 already ... IIRC, that's the "all subjects" index
#15:39:35mrpeters-islhmm
#15:39:56mrpeters-islnot on production server either...
#15:40:03mrpeters-islso it must come in after 1.6.0.90
#15:40:09mrpeters-islerr 1.6.0.0
#15:42:30b_bonner has quit IRC
#15:44:46mrpeters-islINSERT INTO config.metabib_field ( id, field_class, name, label, format, xpath ) VALUES
#15:44:47mrpeters-isl (16, 'subject', 'complete', oils_i18n_gettext(16, 'All Subjects', 'cmf', 'label'), 'mods32', $$//mods32:mods/mods32:subject//text()$$ ); from 950.data.seed-values.sql perhaps solves this?
#15:48:09dbs has joined #evergreen
#15:48:48b_bonner has joined #evergreen
#15:52:54eeevilmrpeters-isl: yes, but that came before 2.0
#15:52:59mrpeters-islhmm
#15:53:13mrpeters-islof concern that we don't have it in our prodution database then...
#15:53:21eeevilmrpeters-isl: have you been upgrading to (at least) 1.6.0.4?
#15:53:30eeevilfor this test, I mean
#15:53:47mrpeters-islyes
#15:54:03mrpeters-islstarting with 1.6.0.0-1.6.0.1-upgrade-db.sql and working my way up
#15:54:20eeevilreally, you should be going through all the scripts in the 1.6.0.10 tarball, and then moving on to 1.6.0-1.6.1, if you can
#15:55:12mrpeters-isli see...ive been stopping at 1.6.1.3-1.6.1.4-upgrade-db.sql and then moving on to 1.6.1-2.0-upgrade-db.sql
#15:55:54dbsrename 1.6.1-2.0 to 1.6.1.10-2.0?
#15:55:56mrpeters-isljust using what was in the latest tarball
#15:56:20mrpeters-island then 1.6.1-2.0-upgrade-db.sql from beta4
#15:57:31mrpeters-islso 1.6.0.10 has an upgrade for .1 thru .10 while 1.6.1.4 just has 1.6.0.4-1.6.1.0-upgrade-db.sql
#15:57:39mrpeters-islwas that 1.6.0.4-1.6.1.0-upgrade-db.sql not the same as going through these 1 by one
#16:00:00mrpeters-isli'm not finding ... (16, 'subject', 'complete', oils_i18n_gettext(16, 'All Subjects', 'cmf', 'label'), ... in any of the scripts from 1.6.0.0 on up :(
#16:01:20Granitize1 has quit IRC
#16:01:34Granitize1 has joined #evergreen
#16:02:38eeevilhrm... ack says it's indeed not in rel_1_6 (no instance of the string 'All Subjects')
#16:02:46eeevilthat's lame :(
#16:03:38Meliss has quit IRC
#16:03:43dbsmrpeters-isl: hah, even I got confused by the jumps from 1.6.0.x to 1.6.1.x
#16:04:18mrpeters-isleeevil: also not in the beta 3 tar
#16:05:22mrpeters-islso ill try th upgrade again with that insert in there and hope for the best!
#16:08:48dbsPerhaps "database upgrade script maintenance strategy" should be a dev meeting agenda item
#16:08:48mrpeters-islif anyone discovers in which upgrade that *should* have occured please let me know
#16:08:58djfianderheh
#16:09:28eeevilmrpeters-isl: according to svn, it should be part of the 1.6.1-2.0 upgrade
#16:09:48mrpeters-islhmm not in beta 3 or 4 tarballs
#16:10:02b_bonner has quit IRC
#16:10:11mrpeters-isldownloading it just 1 more time to make sure....
#16:10:29eeevilmrpeters-isl: no, I'm not saying the script is correct (anywhere)
#16:10:58mrpeters-islah ok i thought if svn showed it as being updated it would have made it into the tarball
#16:11:07eeevilI'm saying that index def 16 is, in fact, new to 2.0. I thought it came in earlier because dbs invented it quite a long time ago
#16:11:15mrpeters-islok
#16:11:22eeevil(which is not pointing a finger at dbs!)
#16:11:25mrpeters-islgot it
#16:11:28dbshah
#16:11:36mrpeters-islwell now we know :)
#16:11:50mrpeters-islI'm rolling with
#16:11:50mrpeters-islINSERT INTO config.metabib_field ( id, field_class, name, label, format, xpath ) VALUES
#16:11:50mrpeters-isl (16, 'subject', 'complete', oils_i18n_gettext(16, 'All Subjects', 'cmf', 'label'), 'mods32', $$//mods32:mods/mods32:subject//text()$$ );
#16:12:09mrpeters-island placing it just before INSERT INTO config.metabib_field ( id, field_class, name, label, format, xpath, facet_field ) VALUES
#16:12:09mrpeters-isl (17, 'identifier', 'accession', oils_i18n_gettext(17, 'Accession Number', 'cmf', 'label'), 'marcxml', $$//marcxml:datafield[tag="001"]/text()$$, TRUE );
#16:12:22eeevildbs: seriously ... it's likely my fault. I just recall you building that for conifer ... and I could be wrong about that too
#16:12:38eeevilanyway, I'll put it in the upgrade script now
#16:12:42dbseeevil: version control by blog post
#16:12:45mrpeters-isleeevil++
#16:12:57dbsI'm pretty sure I blogged / mailed the list about it.
#16:13:09dbsand we definitely talked about it in IRC :)
#16:13:42b_bonner has joined #evergreen
#16:13:49dbsSo who wants to go check out that CI webinar next week? :)
#16:13:51dbs whistles
#16:14:13eeevilheh
#16:15:55b_bonner_ has joined #evergreen
#16:17:55b_bonner has quit IRC
#16:17:55b_bonner_ is now known as b_bonner
#16:20:26mrpeters-islthanks for 18919
#16:21:57mrpeters-isleeevil: dang it that won't work
#16:22:08mrpeters-islit failed on me again ERROR: insert or update on table "metabib_search_alias" violates foreign key constraint "metabib_search_alias_field_fkey"
#16:22:08mrpeters-islDETAIL: Key (field)=(16) is not present in table "metabib_field".
#16:22:13mrpeters-islmaybe it has to be there before the transaction ever runs?
#16:25:11eeevilno, just before the aliases are added
#16:25:25mrpeters-islyeah...i've got it in the same place as you
#16:26:21eeevilyeah... need to move it up, or the aliases down
#16:26:38eeevilI'm going to move the aliases down
#16:26:52mrpeters-islcool! i'll grab the new one monday
#16:26:54eeevilno I'm not ...
#16:26:56mrpeters-islhave a good weekend guys - thanks
#16:29:44b_bonner_ has joined #evergreen
#16:33:00b_bonner has quit IRC
#16:33:00b_bonner_ is now known as b_bonner
#16:34:42kmlussier has quit IRC
#16:35:46mtcarlson has quit IRC
#16:39:11dbsvandelay++ # currently simultaneously processing three batches of MARC records
#16:39:49eeevilrad :)
#16:40:17eeevilnow to clean up the UI so it matches the backend .... (with regard to item import, at least)
#16:40:20eeevil out
#16:40:52dbseeevil++ # enjoy the weekend
#16:51:04AaronZ has quit IRC
#17:08:44dbs has quit IRC
#17:08:51djfiander has left #evergreen
#17:11:05mjg_ has left #evergreen
#17:36:42brian_f has joined #evergreen
#17:47:58yboston has quit IRC
#17:55:55jenny has left #evergreen
#18:22:30b_bonner has quit IRC
#18:26:27b_bonner has joined #evergreen
#19:01:26phasefxgranitize: getfirefox.com, has a screenshot with UPEI's wikipedia entry :)
#19:01:40phasefxwell, not upei
#19:01:43phasefxbut pei
#19:07:26b_bonner has quit IRC
#19:51:40moodaepo has quit IRC
#21:57:40brian_f has quit IRC
< Thursday, December 2nd, 2010Raw Log FileSaturday, December 4th, 2010 >