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.
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
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".