Demian,

That worked perfectly!

I didn’t realize it would be that easy.

Thanks again!

 

Thom

 

From: Demian Katz [mailto:demian.katz@villanova.edu]
Sent: Tuesday, October 29, 2013 3:18 PM
To: Shepard, Thomas - 1150 - MITLL; Mosior, Benjamin; vufind-tech@lists.sourceforge.net
Subject: RE: Restarting and deleting records from vufind2

 

There are several lines in marc.properties which reference 099. I would recommend copying all of those lines into marc_local.properties and then removing the 099 part. You don’t need to switch to the script() version of the call number logic unless you plan on customizing the call number behavior at a deeper level.

 

Does that help?

 

- Demian

 

From: Shepard, Thomas - 1150 - MITLL [mailto:tshepard@ll.mit.edu]
Sent: Tuesday, October 29, 2013 3:16 PM
To: Demian Katz; Mosior, Benjamin; vufind-tech@lists.sourceforge.net
Cc: vufind-admin@lists.sourceforge.net
Subject: RE: Restarting and deleting records from vufind2

 

Demian, Benjamin,

 

Thank you both for weighing in on this problem.

 

This all started when I was trying to make vufind NOT map our marc tag 099 to vufind’s call numbers, as our catalogers use this marc field to simply enter the text string “JOURNALS” (or WEB RESOURCE, etc).

Vufind, however, interprets this text string as J, and so maps all our Journals to J- Political Science.

 

Hoping to fix this, I edited our local copy of marc_local.properties, uncommenting and modifying the following:

 

From this:

#callnumber = script(callnumber.bsh), getFullCallNumber(099ab:090ab:050ab)

To this:

callnumber = script(callnumber.bsh), getFullCallNumber(090ab:050ab)

 

 

I am guessing we need to configure more than this, right?

 

In any event, when we reverted back to the original setting, we had no problem stopping and restarting vufind.

 

But this leaves us with the bigger question: how do we configure our imports to ignore mapping 099 to our call numbers?

 

Thanks,

Thom Shepard

MIT Lincoln Lab

 

 

 

From: Demian Katz [mailto:demian.katz@villanova.edu]
Sent: Friday, October 25, 2013 4:39 PM
To: Mosior, Benjamin; Shepard, Thomas - 1150 - MITLL; vufind-tech@lists.sourceforge.net
Cc: vufind-admin@lists.sourceforge.net
Subject: RE: Restarting and deleting records from vufind2

 

Sometimes these things can happen if the vufind.pid file gets deleted, or if vufind.sh is run with inconsistent environment settings. In any case, Benjamin's suggestions should help!


From: Mosior, Benjamin [BEMosior@ship.edu]
Sent: Friday, October 25, 2013 3:49 PM
To: Shepard, Thomas - 1150 - MITLL; vufind-tech@lists.sourceforge.net
Cc: vufind-admin@lists.sourceforge.net
Subject: Re: [VuFind-Tech] Restarting and deleting records from vufind2

A quick “ps -f |grep java” will tell you if the Solr index is still running (you’ll see a process that has a flag similar to “-jar /usr/local/vufind2/solr/jetty/start.jar” if the index is still up).  

 

Worst case, you can kill the process by its pid, which will be one of the first pieces of information returned by the ps command above. Once you verify that nothing’s running you can start again.

 

Benjamin Mosior

 

Sent: Friday, October 25, 2013 3:22 PM
Subject: [VuFind-Tech] Restarting and deleting records from vufind2

 

Also, ./vufind.sh stop seems to have absolutely no effect: our vufind continues to be up and running, no matter how many times we try to stop it.

 

Thanks,

Thom Shepard