Thanks for facbackopac

4 views
Skip to first unread message

zebil

unread,
Apr 3, 2008, 2:52:01 AM4/3/08
to FacBackOPAC
I want to thank for Dan and Mike creating this great project. The
installation capture video was great, i did all steps without any
problem. Thanks again who made this camtasia installation video.
I am a librarian. But not a system librarian :( I dont have any
programming language skill, but i am very interested open source
library projects like evergreen, koha, scriblio, and the my favorite
facbackopac. Do you think making "how to pages " like how add a mark
field for details page (520 etc), or like how to change design of
page? And which files must edited for this? Is it difficult make a
page like Paul Smith's library catalog page?
Regards,

Gabriel Sean Farrell

unread,
Apr 3, 2008, 8:31:40 AM4/3/08
to facba...@googlegroups.com

Glad you're liking FBO, and thanks for writing to the list.

The best place to start learning how to customize the FBO interface is
at the Django documentation [1], since the display side of FBO is
built with the Django framework. You shouldn't have to understand
*all* of Django to do anything, but I imagine a little introductory
knowledge (gained by going through the tutorial there, for example)
will help you make sense of the structure of this project.

The more specific answer to your question is that the design is
handled by templates. General templates can be found in the
/helios/templates/ directory. Templates for the discovery layer (the
initial searchbox screen, called "index.html", and the results page,
paradoxically called "search.html") are in
/helios/discovery/templates/. The template for the individual item
pages is at /helios/catalog/templates/item.html because it's part of
the catalog application. Note that all of the templates "extend" from
/helios/templates/base.html.

If you're interested in adding documentation for FBO, just let me
know. I'll add you as a project member so you can contribute to the
wiki.

[1] http://www.djangoproject.com/documentation/

Dan Scott

unread,
Apr 3, 2008, 9:18:58 AM4/3/08
to facba...@googlegroups.com

I should note that Casey Durfee really deserves the bulk of the credit
for the original code that made the bulk of Fac-Back-OPAC, and that
Gabriel and Mark Matienzo deserve all of the credit for the ongoing
work that's really helping FBO mature. Oh, and Mike also made the
Camtasia video.

Group hug!

--
Dan Scott
Laurentian University

zebil

unread,
Apr 3, 2008, 9:40:41 AM4/3/08
to FacBackOPAC
Thanks your answer Gabriel. I will try to learn about Django. As i say
i have no programming skill. I dont know which document could i add
for FBO. But i can translate the FBO to Turkish. Actually FBO has a
little English terms. But if you tell me which file must be translated
i can do it.

Secondly,
When i trying the FBO i used Marc records from
http://remainingrelevant.net/remainingrelevant/wp-content/uploads/10132007mrc.zip
There aout 360 records in this file but FBO shows only 22 records.
ThenI've tried to add about ten marc records from our catalog to FBO
but i got errors. If you want i can send you the marc records. I dont
know which version is our marc record USMARC, UNI or MARCC21. I know
only that it has turkish characters.

Here the error codes while i try to batch our Marc records.

C:\cat\indexer>java -classpath ".;jython.jar;marc4j.jar"
org.python.util.jython
indexerDriver.py "C:\Documents and Settings\Zeki\Desktop\cyber
\cyber.mrc"
processing file <<C:\Documents and Settings\Zeki\Desktop\cyber
\cyber.mrc>>
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
. could not parse isbn from <<['']>> for isbn
field bib_num was None!
committing...
done indexing, now optimizing
done optimizing, now warming facets
Traceback (innermost last):
File "indexerDriver.py", line 192, in ?
File "C:\cat\indexer\facetWarmer.py", line 35, in warmFacets
File "C:\cat\indexer\.\Lib\urllib.py", line 71, in urlopen
File "C:\cat\indexer\.\Lib\urllib.py", line 149, in open
File "C:\cat\indexer\.\Lib\urllib.py", line 896, in toBytes
LookupError: unknown encoding asc²²

Gabriel Sean Farrell

unread,
Apr 3, 2008, 10:01:09 AM4/3/08
to facba...@googlegroups.com
On Thu, Apr 3, 2008 at 9:40 AM, zebil <zekikem...@gmail.com> wrote:
> Thanks your answer Gabriel. I will try to learn about Django. As i say
> i have no programming skill. I dont know which document could i add
> for FBO. But i can translate the FBO to Turkish. Actually FBO has a
> little English terms. But if you tell me which file must be translated
> i can do it.

Dan Scott can speak more to the translations, but as I understand it
you can look at /helios/conf/locale/fr/LC_MESSAGES/django.po to get an
idea of how Dan did the French translation.

> Secondly,
> When i trying the FBO i used Marc records from
> http://remainingrelevant.net/remainingrelevant/wp-content/uploads/10132007mrc.zip
> There aout 360 records in this file but FBO shows only 22 records.
> ThenI've tried to add about ten marc records from our catalog to FBO
> but i got errors. If you want i can send you the marc records. I dont
> know which version is our marc record USMARC, UNI or MARCC21. I know
> only that it has turkish characters.

Encoding issues are the devil, but I'm trying to fix some of these
indexing problems in the pymarc-indexer branch of the code. Once it's
been merged into trunk some of those problems might be solved, and
others can be worked on.

As for the missing records, it's likely related to the "field bib_num
was none!" messages you're seeing. The indexer uses the MARC 001
field as a unique identifier for each record (that's the bib_num). If
there isn't an 001 field, the record isn't included in the index. If
your records have another field that can serve as a unique identifier
(possibly 035a, 907a, or 999a), you can change that in
/indexer/config/indexes.properties where it says "bib_num.marcMap".

Systemfreak

unread,
Apr 3, 2008, 2:12:31 PM4/3/08
to FacBackOPAC
I can also translate the FBO to Arabic, since I was a volunteer in the
Google translation project 10 years back!

On Apr 3, 9:40 am, zebil <zekikemalbil...@gmail.com> wrote:
> Thanks your answer Gabriel. I will try to learn about Django. As i say
> i have no programming skill. I dont know which document could i add
> for FBO. But i can translate the FBO to Turkish. Actually FBO has a
> little English terms. But if you tell me which file must be translated
> i can do it.
>
> Secondly,
> When i trying the FBO i used Marc records fromhttp://remainingrelevant.net/remainingrelevant/wp-content/uploads/101...
Reply all
Reply to author
Forward
0 new messages