On 29/11/2008, at 12:42 PM, Andrew Nagy wrote:
> Thanks Steven for sharing - are these changes available in the NLA
> branch of the VuFind SVN?
Well this change actually didn't require any change to the VuFind
codebase. I used some simple Java to extract all terms from our
Indexes I created an aspell personal word list (which is a straight
text file with an aspell header), then followed the aspell doco on
how this is compiled into a system dictionary:
http://aspell.net/man-html/Creating-an-Individual-Word-
List.html#Creating-an-Individual-Word-List
I then added this new dictionary to the aspell alias for en_US, and
it all just worked.
> What about the "fast facets" plugin?
I think I posted something about the fast facets plugin to the tech
list before:
http://sourceforge.net/mailarchive/message.php?msg_id=B195653F-
ABEA-4765-B7DB-D91706D10E65%40nla.gov.au
As this code wasn't written by Mark or myself, and conceptually lives
outside VuFind, I'm not sure it belongs in the VuFind SVN repo.
On that subject, I think that over this holiday break the NLA might
put some effort in to making some clean branches in the VuFind SVN
repo. I think we might need to discuss further (maybe off-list) what
features you would be interested in seeing, then we can work out some
way to test them out without mucking up the trunk.
----
Steven McPhillips <smcphillips@...>
IT Business Systems
National Library of Australia
Try our new catalogue - http://catalogue.nla.gov.au

Hello,
Yale is currently beta testing its own implementation of Vufind called Yufind (our main catalog interface is called Orbis). We have just completed a brief survey run in October of undergraduates who have used the Vufind beta implementation at Yale. Below is a synopsis and a link to the full survey. A System Usability Scale was included in the survey. The SUS is widely used in evaluating product usability. I would be very interested in hearing from other institutions who are implementing Vufind or other next generation type OPACs who would be interested in running the SUS. This could provide useful comparative data for libraries considering different OPAC products.
83 surveys were submitted by readers indicating they had used the Yufind search. Of those 83 responses, 79.3% found that results were what they had expected and 75.6% found what they needed. Respondents who tried facets tended to like them (85.0%), and those who didn't like facets commonly complained that results were oddly not related to their search or took too long to load. 57.8% of respondents preferred Yufind to Orbis, but when asked for the first place they would turn for a book search, slightly more respondents would turn to Orbis than to Yufind (40.2% to 35.4%). Some respondents indicated they were frustrated by the broad search in Yufind, which in some cases returned many highly irrelevant results, and by slow response times. Other respondents were unable to use Yufind to locate items they knew to be in the collection, such as the journal Nature.
Some changes could be made to Yufind to improve results, and a key area would be facets. In the short term, those facets with misleading metadata can be suppressed, including era and format. Additionally, facets can be made more relevant by narrowing the set of results to exclude those records that may only match one word in a search query. Finally, usability results indicated that facets should be presented in a list that the reader could manipulate with an alphabetical sort. This sort option should be implemented.
Survey results indicated that while Yufind is viewed as promising, it needs significant improvement. A search of the Yale collection should be more accurate so that very popular items such as Nature (as measured by holdings, circulation, or downloads) are easily located in the Yufind search. This type of customization to the Yale environment would help to improve Yufind's standing as a search interface for Yale readers. Another area where Yufind could distinguish itself would be by integrating seamlessly with other Yale services. Candidates would be easy export to Refworks/Endnote and ordering book delivery via Eli Express or interlibrary loan. The benefit of this emphasis in the Yufind implementation would be to provide a service that other search engines such as Google could not easily provide, thereby distinguishing the Yufind interface.
System Usability Scale: The System Usability Scale or SUS (developed by John Brooke) is an instrument composed of 10 statements (5 negative and 5 positive) that are scored on a 5-point Likert scale. 83 respondents answered the SUS section of this survey, returning a score of 66. In general, those systems which return a score over 70 are considered acceptable in terms of usability. Scores of less than 70 require further improvement and are considered "marginal.". A score of 66 places Yufind on the higher end of the marginal scale.
http://library.yale.edu/libepub/usability/studies/yufind_survey.doc
Sincerely ,
Katheen Bauer
Director of Usability and Assessment
Yale University Library
130 Wall Street
P.O. Box 208240
New Haven, CT 06520-8240
203-248-3359
kathleen.bauer@...<mailto:kathleen.bauer@...>

Hi all,
We rejigged our wiki extractor to use a wikitext parser instead of
all that looping / regexp work. It's by no means perfect (its image
support flaky at best), but it allowed us to deal with that extra
information seen at the front of some wiki articles (which I think is
what is used to do the info box on the right column?)
http://pear.php.net/package/Text_Wiki_Mediawiki/
Douglas Mawson:
￼
On 02/12/2008, at 1:36 AM, Lovins, Daniel wrote:
> We've noticed some parsing errors with the Wikipedia author mashup.
> Sometimes the wiki syntax/punctuation shows up. Any suggestions on
> how to fix?
>
>
>
> Sometimes it comes through fine, e.g.:
>
>
>
> <image001.png>
>
>
>
> Other time it's like this:
>
>
>
> <image002.png>
>
>
>
>
>
>
>
> I compared the wiki source of the two articles and noticed that
> the first line for Einstein was this: "{{pp-semi|small=yes}}",
> which the Mawson article didn't have. Could that be making the
> difference? If so, is there a way to tweak the VuFind code so that
> it doesn't affect display?
>
>
>
> Thanks!
>
> / Daniel
>
>
>
> <image001.png><image002.png><ATT00001.txt><ATT00002.txt>
----
Steven McPhillips <smcphillips@...>
IT Business Systems
National Library of Australia
Try our new catalogue - http://catalogue.nla.gov.au

I have this problem too... Anyone have a solution?
Thanks,
Dean
-----Original Message-----
From: Martin Longo [mailto:jmlongo@...]
Sent: Tuesday, November 25, 2008 10:31 AM
To: vufind-general@...
Subject: [VuFind-General] Facets gone after updating
Hi there !
I have updated my test copy of vufind to rev 1156 and now no facets get
displayed after any search. I tried restarting vufind, deleting and
reimporting the records, but without success...
anyone else is having the same problem ??
Best regards
--
Ing. J. Martin Longo
Depto. Gestion Informatica
SID - UNCuyo
http://sid.uncu.edu.ar
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
VuFind-General mailing list
VuFind-General@...
https://lists.sourceforge.net/lists/listinfo/vufind-general