Jesse, In case you still needed the help. To see these entries you need to have access to your database through the command line or a visual tool to look at the schema called "config" and the table inside of it called "metabib_field"
A sample SQL query for the the tables data would be... select * from config.metabib_field order by id There should be two columns with the xpath data, one is only for facets/browsing and only a few row entries will have data in it. You want the column that I think is just called "xpath" Hope this helps, Yamil > On Jul 22, 2014, at 7:08 PM, Jesse McCarty <[email protected]> wrote: > > Thanks for the information Ben. Where would I go to look at the > config.metabib_field entries to pull out examples of the xpath entries for > review? I am still learning the in depth aspects of the Evergreen system. > > Jesse McCarty > City of Burlington > IT Technical Assistant > > From: [email protected] > [mailto:[email protected]] On Behalf Of Ben Shum > Sent: Tuesday, July 22, 2014 3:22 PM > To: Evergreen Development Discussion List > Subject: Re: [OPEN-ILS-DEV] Reingest records error, upgrading Evergreen > 2.4.4-2.5.4/2.6.1 > > Hi Jesse, > > I think the problem point seems to be: ERROR: invalid XPath expression > > I would take a look at your config.metabib_field entries and check for any > customization that have been made to the existing entries or the addition of > new metabib entries. We encountered similar errors as well during our > reingests because of bad browse_xpath entries (discussions in IRC starting > around here: http://irc.evergreen-ils.org/evergreen/2014-04-07#i_85041). > Other developers offered us suggestions, but ultimately we decided that our > custom entries did not need to be part of browse indexes and just set the > browse field for some of those custom entries to false and removed the xpath > issues. > > There are others with more experience in this area, but we would have to see > examples of your xpath entries from the config.metabib_field to know the > exact reason for the problems. > > -- Ben > > > > On Tue, Jul 22, 2014 at 5:21 PM, Jesse McCarty <[email protected]> > wrote: > Hello Everyone > > My upgrade 2.4.4 to 2.5.x/2.6.x saga continues (slowly). While I am getting > closer and have narrowed down other issues, I am now presented with the > reingest process producing errors instead of working. When running the psql > command to start the reingest process, it starts running with the following > error as output: > > psql:reingest_2.5_bib_recs.sql:1: ERROR: invalid XPath expression DETAIL: > Invalid expression CONTEXT: SQL function "oils_xpath" statement 1 PL/pgSQL > function "extract_metabib_field_entry" line 48 at assignment SQL function > "extract_metabib_field_entry" statement 1 PL/pgSQL function > "reingest_metabib_field_entries" line 33 at FOR over SELECT rows > > Running the reingest script generated with the 2.6.x upgrade script produces > similar errors: > > psql:reingest_2.6_bib_recs.sql:34167: ERROR: invalid XPath expression > DETAIL: Invalid expression CONTEXT: SQL function "oils_xpath" statement 1 > PL/pgSQL function "extract_metabib_field_entry" line 48 at assignment SQL > function "extract_metabib_field_entry" statement 1 PL/pgSQL function > "reingest_metabib_field_entries" line 33 at FOR over SELECT rows SQL > statement "SELECT metabib.reingest_metabib_field_entries(NEW.id)" PL/pgSQL > function "indexing_ingest_or_delete" line 55 at PERFORM > > This continues for the entirety of the script, not sure what is causing this > or where to look to fix. > > Jesse McCarty > City of Burlington > IT Technical Assistant > > > > > -- > Benjamin Shum > Evergreen Systems Manager > Bibliomation, Inc. > 24 Wooster Ave. > Waterbury, CT 06708 > 203-577-4070, ext. 113
