Yeah - that's a good point. Right now SolrMarc and VuFind are 2 separate projects and will remain so. My first guess is that SolrMarc should not be reliant on the solr jars so that you can use SolrMarc with whichever version you happen to run. Maybe this should be a runtime param with SolrMarc.
I don't think maven will help solve this problem since solr can change drastically from one day to the next and they only release "numbered" versions every 6 months to a year at least.
I cc'd the solrmarc list - maybe Robert can chime in here. It's been a while since I have participated in the SolrMarc community - so I need to reaquaint myself with the code.
On Wed, Feb 18, 2009 at 3:03 PM, Barnett, Jeffrey <email@example.com> wrote:
I notice you making the point that *both* vufind and solrmarc now come with associated solr.jar files. Is this a temporary or permanent situation? How will we be able to assure that the versions packaged separately will be compatible at run time? Are we approaching a Maven Moment?
It's probably best to copy over the solr jars if you are running an updated solr into the solrmarc project just to make sure there are no chances for failures.
I will add this to my list to grab the latest solr for both vufind and solrmarc.
On Wed, Feb 18, 2009 at 2:44 PM, Barnett, Jeffrey <firstname.lastname@example.org> wrote:
Bill Dueber just posted a recommendation on grabbing the latest Solr build to capture a fix for the spellcheck module. Will the newest SolrMarc include this fix as well? Any dependencies in other parts of Vufind?
Thanks for the super-quick response.
I'll check with Jeff about the latest solrmarc and changing the properties file.
Daniel - its funny that you brought this up. Last week I just committed a fix for this to the SolrMarc code base. I noticed that our language logic needed to be more detailed, so I built a custom function in SolrMarc to parse the languages correctly.
If you are up to it - grab the latest solrmarc and try it out to see if this fixes your problem.
You will need to change your vufind.properties file to use the following line:
language = custom, getLanguage, language_map.properties
On Wed, Feb 18, 2009 at 2:20 PM, Lovins, Daniel <email@example.com> wrote:
We discovered something here that I was planning to report on JIRA as a bug, but thought I'd bring it up first on the list.
If we search the following book in our database: "Hoffmanns Erzählungen" http://tinyurl.com/bo5w4w, we notice a blank line in the language facet indicating 3 hits. There's no way to click open the facet directly since there's nothing there to click on, but my colleague Chuck Riley was able to determine that, because they were cataloged according to an earlier version of the MARC 21 standard, records like this have multiple 041 subfield $a language codes that are not separated by subfield delimiters. So, for example, an item that includes English, German, French, and Spanish language would have "041 $a enggerfrespa" for an. The latest version of MARC 21 specifies repeatable subfield $a delimiters (e.g., "041 $eng $a ger $a fre $a spa"), but this is a fairly recent change, which means there are many legacy records. When the delimiters are present, VuFind parses and displays the languages correctly. When not, VuFind seems to represent the undefined string of characters as blanks.
We're thinking about trying to add the subfield delimiters retroactively, but we're also wondering if others have noticed this issue, and, if so, whether anyone's found a way to represent the concatenated language codes as something other than a blank facet.
Thanks for your help.
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
VuFind-General mailing list
You received this message because you are subscribed to the Google Groups "solrmarc-tech" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to email@example.com
For more options, visit this group at http://groups.google.com/group/solrmarc-tech?hl=en