old.kete.net.nz

Hi there,

I am delighted that there is interest in integrating Kete with Koha. I envisaged from the very beginning that this would be possible and our choice of programming tools, structure and standards were all selected with this in mind. I had thought that the search results drawn from Koha would display on another tab which held the Koha results; so the tabs could be koha, images, docs, audio, video, weblinks etc.  But, there may well be better ways to do this.

I am not the technical person so can't help with programming, but Kete was my concept and I was part of the team who developed Koha so I would love to participate in discussions when I can add something (and just listen when I can't!).

Anyway - fantastic news!

Hi,

The option to configure Kete to integrate, meaning showing data from Koha 3 in Kete, with Koha 3 will be a part of the next release which is 1.3.

If configured to, in Kete search you'll be able to see Koha 3 catalog results alongside the normal Kete results.  You'll also be able to see Koha 3 results on a Kete item detail page.  The Koha 3 results will be determined by a search run against the Kete item's title.

Documentation on how to configure Kete to do this will be added to this site's documentation as a part of the 1.3 release process.

My understanding is that Koha 3, after configuration, should be able to show results in catalog searches from Kete as well. I haven't confirmed this myself yet, but will look into it and report back here.

The Kete 1.3 code is nearing completion. There is still some work to be done for right to left reading languages to have elements of the layout altered.  We would also like to have a number of translations in place for the release. The first non-English translation is almost complete, but we have at least one other that must be done before the release. If possible I would like to have five languages available before we call 1.3 done.

Tags: translation, Koha, integration

Thank Walter for your gratefully appreciated dedication to help non-English speaking users enjoy Kete features in their native languages. This is super. 

Our development team in Egypt and our colleagues here in Riyadh are so excited about the upcoming Kete ver. 1.3, particulary its mutillanguage support amd its robust integration with Koha 3.0, which we have completed its localization to Arabic recently. It would be nice thought to have a seamless access from now to Kete 1.3 (Beta) code and documentation for developers like us so that we can get the chance to test its localization features  while moving forward toward the release announcement date.

One more suggestion, is to use the term 'localization' in place of 'translation' for the whole multilingual feature process of Kete 1.3. The reason is that an application localization process invloves more than the langauge translation task of the User Interface, to include enabling screen orientations (Right-to-Left for Arabic and Hebrew) and selecting between different calndar formats. In the case of Arabic localization it is requireed to provide Hejri (Islamic calendar) support in addition to the Gregorian calendar.

Thanks, Massoud AlShareef

KnowledgeWare Technologies. 

Tags: Arabic, localization, Kete 1.3, Hejri, Right-to-Left

Hi Massoud, 

Great to hear about the excitement for the project. I'm pretty excited by the cool stuff coming with Kete 1.3, too.

It's been easy to view pre-release code and contribute to it for quite some time, but I hadn't explicitly outlined the process. I've fixed that by updated this topic that should give guidance on how to collaborate on the Kete codebase:

http://old.kete.net.nz/site/topics/show/176-using-git-and-github

I've also added a section to the homepage to highlight this topic so other new developers can easily find it.

In regards to the use of the term localization. I agree, though I think the 1.3 release will likely concentrate largely on the translation aspect of localization. Localizing Kete will be an ongoing development process as more locales are supported.

At some point we should discuss how best to implement the handling of right-to-left locales in Kete so we have a clear technical plan before work begins.

Tags: Arabic, localization, translation, contributions, Develelopment

Oh.  Just to be clear.  Kete 1.3 will be able to integrate with ANY library system (or web service) that provides an RSS feed of search results, not just Koha 3.

And it can integrate with multiple systems or web services in this way on the same page.

Hello WalterI ,

I would like to know when kete 1.3 final release will be ready

and What method of integration with Koha 3 in detail

thank you,

Tags: koha and kete integration

Hi,

The implementation for Kete 1.3 is almost done. We are working out the details of some final functionality aimed at having localization work for right-to-left languages.

Beyond that there will be time needed for translating for various languages. I'm in the midst of working out the timeline for that, too.

Hopefully things will go reasonably fast and we can have the final release of Kete 1.3 in a few months. In the meantime, those that want to use the functionality of Kete 1.3 before it's official release may use the "master" branch from the code repository.

As for documentation for how to set up Koha 3 sites to integrate with Kete 1.3. I'll write up a topic to document it soon. Here's the short version though:

1. on your Kete 1.3 site as a user that is a tech admin (default admin will do fine), visit Administrator's Toolbox > search sources
2. click create
3. Fill out the form, the main thing you need is the base URL for your Koha 3 installations catalog's search results in RSS, e.g. http://69.54.27.22/cgi-bin/koha/opac-search.pl?idx=ti&format=rss2&q= 
4. choose "All" for Source Target and submit the form

That will add Koha 3 searches to Kete search result pages along side local search results AND do a Koha 3 search for an item's title on the item detail page.

A similar technique can be used Tools for basket: basket name > basket preferences > Homepage Options > RSS or Atom Feeds, too.

Tags: Koha, koha and kete integration, Koha and Kete

the integration Works well ,
, i have another question

the rss feed show some koha results , can i show all koha results in the rss ?

Good to hear.

The amount of results shown from each external search source is determined by either user preference on the search results page, i.e. if they select 5 or 50 results to be shown, or by the limit that is set for the external search source.

The "more" link setting for the external search source is meant to provide a link to the rest of results in Koha or another external search source.  The idea being that if the user wants to see a more complete list, they can click on more.

It's meant to keep the layout from within Kete reasonable, particularly if you have more than one external search source being displayed.

Tags: Koha, External Search Sources

hello Walter ,

can i change the more URL to  go to the original  koha search page (  http://badir.maktabat-online.net/cgi-bin/koha/opac-search.pl?idx=ti&q= )

not the rss page ( http://badir.maktabat-online.net/cgi-bin/koha/opac-search.pl?idx=ti&format=rss2&q= )

?

Tags: Koha, External Search Sources

> can i change the more URL to  go to the original  koha search page
> ( 
> http://badir.maktabat-online.net/cgi-bin/koha/opac-search.pl?idx=ti&q= )

Yep, that is what you should use for the "more URL".  You should use an HTML page that presents the user with a standard search interface.

Tags: Koha, External Search Sources

hello ,

i downloaded the new kete yesterday and it running well

and i want to add my koha to the search source

but the source search link not exist

and the table searchsearch not found also

how i can add my koha to the search

thank you,

Tags: Koha

Hi,

Could you confirm that you are logged as a site administrator and have the "Administrator's Toolbox" at the bottom of each page, please?

Cheers,

Walter

Tags: Koha

yes i logged as a site administrator

and i have the "Administrator's Toolbox" at the bottom of each page

and this is

Odd.

Ok, I've just merged a decent amount of new code (speed optimizing search/browse results and some refactoring) and confirmed that the latest code has the "search sources" link in the Administrator's Toolbox.

Could you do a "git pull" and grab the latest code please and report if the issue is fixed?

Hi,

Could you also confirm that you are using the latest code base as cloned from the github repository please?

Do the following in your application's root directory:

 $ git branch
* master

If this is an upgrade, you may have the 1-2-stable branch as well, like so:

 $ git branch
  1-2-stable
* master

The important thing is that the * is in front of "master". Here's what you do if not:

 $  git checkout master
Checking out files: 100% (4555/4555), done.
Switched to branch "master"

Note that numbers the numbers in the parenthesis may vary.  My steps also assume that you are doing a public clone as outlined in the Downloads page. If you are working with Kete as a "remote" in git things will be a bit different and specific to you set up.

Also note, if you WERE NOT on master before, you WILL need to run through the upgrade steps (rake db:migrate, rake kete:update, and Rebuild Search Database) again.

The main thing is that the following should appear in app/views/layouts/application.rhtml:

  link_to_unless_current t('layouts.application.search_sources'),
                                           { :urlified_name => @site_basket.urlified_name,
                                             :controller => 'search_sources',
                                             :action => 'list'},
                                           :tabindex => '2'

I've confirmed that the latest code from Kete master with a fresh clone contains this code as it should.

If you are using a github "fork" of Kete rather than the standard git clone, you'll want to take that into account when following the above steps.

Instead of making sure you are on a local branch called "master", make sure you are "pulling" from Kete's git repository's master branch.

The details can be found here:

http://github.com/guides/keeping-a-git-fork-in-sync-with-the-forked-repo

Tags: git, fork, developer, contributions, github, branches

hello ,

i installed koha 3 on amazon ec2 instance ,

and i added koha as search source in kete

but it didn't return any result , the url i used is :  http://79.125.20.146/cgi-bin/koha/opac-search.pl?idx=ti&format=rss2&q=

and when i used any other koha demo like: http://sharedkoha.osslabs.biz/cgi-bin/koha/opac-search.pl?idx=ti&format=rss2&q=

it returned results .

is there is another information i need to add ??
thank you

Tags: Koha

hint :

when i add this rss url to basket preferences home page , it returned data

look :  http://kete.maktabat-online.com/site/

it just didn't return data in search

Tags: Koha

I've verified that what you are seeing is a real issue. I'll ask Kieran if he has any ideas what the cause may be and why it works in one place and not the other. My suspicion is that it is related to the IP address.

Thanks for pointing this out.

Tags: Koha

how is it related the ip address ?

and

can i do or try thing to resolve this problem ?

Tags: Koha

Hey Ahmad,

So it looks like this boils down to the fact that both Koha installations aren't returning results fast enough.

In order to keep page loads to a minimum, we use a timeout of 2 seconds when fetching search sources. If the search source doesn't return anything in this time, we skip the search source. The idea is that the app might then cache the results, and one the second request, return them faster (this is how Kete operates when using the search rss feeds).

However, it would appear Koha does not cache their results. So each request takes just as long.

You can resolve this issue by putting the following code into config/initializers/search_sources_configuration.rb

ExternalSearchSources[:timeout] = 10

Place it inside the 'if IS_CONFIGURED condition, underneath the line:

ExternalSearchSources[:source_targets] = %w{ all search items }

Then restart your application server and try it again. Once I did that, both search sources started returning results.

Regards
Kieran

Tags: Koha

thanks so much  Kieran ,

it works now

Tags: Koha