Hello Currently, facets are defined in perl code. This is not good for unimarc libraries : a recent improvement is specific to Marc21 and could not been transposed in Unimarc, because the information is not encoded in the same field in all unimarc libraries. I'm referring to http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4255 "Add item type to facet list" : there is no universal Unimarc field for "item type" :-( The solution could be a system preference for this peculiar facet. But if a development is needed I would prefer a more generic one, to make all facets fully editable, so that each library could define its own facets matching the (sub)fields of its choice, without editing perl files. Do you think it would be a good idea ? I think there is 2 way for doing this : - create a configuration file (yaml ?) - create a (big) syspref Which choice would be the best regarding performances (and other criteria I did not think of...) ? Regards, Mathieu Saby Rennes 2 University -- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
Another option would be a tool, similar to the Keywords to MARC Mapping tool in the Administration section. On Wed, Oct 31, 2012 at 11:26 AM, Mathieu Saby <mathieu.saby@univ-rennes2.fr
wrote:
Hello
Currently, facets are defined in perl code. This is not good for unimarc libraries : a recent improvement is specific to Marc21 and could not been transposed in Unimarc, because the information is not encoded in the same field in all unimarc libraries. I'm referring to http://bugs.koha-community.** org/bugzilla3/show_bug.cgi?id=**4255<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4255>"Add item type to facet list" : there is no universal Unimarc field for "item type" :-( The solution could be a system preference for this peculiar facet.
But if a development is needed I would prefer a more generic one, to make all facets fully editable, so that each library could define its own facets matching the (sub)fields of its choice, without editing perl files. Do you think it would be a good idea ? I think there is 2 way for doing this : - create a configuration file (yaml ?) - create a (big) syspref Which choice would be the best regarding performances (and other criteria I did not think of...) ?
Regards, Mathieu Saby Rennes 2 University
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
______________________________**_________________ Koha-devel mailing list Koha-devel@lists.koha-**community.org<Koha-devel@lists.koha-community.org> http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.**org/ <http://bugs.koha-community.org/>
Le 31/10/2012 18:26, Mathieu Saby a écrit :
Hello
Currently, facets are defined in perl code. This is not good for unimarc libraries : a recent improvement is specific to Marc21 and could not been transposed in Unimarc, because the information is not encoded in the same field in all unimarc libraries. I'm referring to http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4255 "Add item type to facet list" : there is no universal Unimarc field for "item type" :-( The solution could be a system preference for this peculiar facet.
But if a development is needed I would prefer a more generic one, to make all facets fully editable, so that each library could define its own facets matching the (sub)fields of its choice, without editing perl files. AFAIK, Mathieu, this feature is in the solR stuff. Irrelevant for zebra, but the best option is probably to extend what we did for solR to zebra.
Ask Claire if you want more information. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
Hello Mathieu It is already possible to configure indexes via the koha interface. But only for Solr :) You can have a look at Bug 8233. Switch your syspref SearchEngine to "Solr" and go on the search engine configuration page (admin/searchengine/solr/indexes.pl) based on a yaml file. You can configure your facetable indexes and on the result page (at opac) you see facets you had selected. Look at the module Koha/SearchEngine/Solr/Config.pm and the script opac/ search.pl (and the tmpl opac-tmpl/prog/en/modules/search/results.tt). Regards, Jonathan 2012/10/31 Mathieu Saby <mathieu.saby@univ-rennes2.fr>
Hello
Currently, facets are defined in perl code. This is not good for unimarc libraries : a recent improvement is specific to Marc21 and could not been transposed in Unimarc, because the information is not encoded in the same field in all unimarc libraries. I'm referring to http://bugs.koha-community.** org/bugzilla3/show_bug.cgi?id=**4255<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4255>"Add item type to facet list" : there is no universal Unimarc field for "item type" :-( The solution could be a system preference for this peculiar facet.
But if a development is needed I would prefer a more generic one, to make all facets fully editable, so that each library could define its own facets matching the (sub)fields of its choice, without editing perl files. Do you think it would be a good idea ? I think there is 2 way for doing this : - create a configuration file (yaml ?) - create a (big) syspref Which choice would be the best regarding performances (and other criteria I did not think of...) ?
Regards, Mathieu Saby Rennes 2 University
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
______________________________**_________________ Koha-devel mailing list Koha-devel@lists.koha-**community.org<Koha-devel@lists.koha-community.org> http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.**org/ <http://bugs.koha-community.org/>
Thank you Jonathan I will take a look next week. Maybe we could use SolR facet configuration as a model for Zebra? If I don't understand how to do that I will ask for some advice to you or Claire... Regards, Mathieu Jonathan Druart a écrit :
Hello Mathieu
It is already possible to configure indexes via the koha interface. But only for Solr :) You can have a look at Bug 8233. Switch your syspref SearchEngine to "Solr" and go on the search engine configuration page (admin/searchengine/solr/indexes.pl <http://indexes.pl>) based on a yaml file. You can configure your facetable indexes and on the result page (at opac) you see facets you had selected. Look at the module Koha/SearchEngine/Solr/Config.pm and the script opac/search.pl <http://search.pl> (and the tmpl opac-tmpl/prog/en/modules/search/results.tt <http://results.tt>).
Regards, Jonathan
2012/10/31 Mathieu Saby <mathieu.saby@univ-rennes2.fr <mailto:mathieu.saby@univ-rennes2.fr>>
Hello
Currently, facets are defined in perl code. This is not good for unimarc libraries : a recent improvement is specific to Marc21 and could not been transposed in Unimarc, because the information is not encoded in the same field in all unimarc libraries. I'm referring to http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4255 "Add item type to facet list" : there is no universal Unimarc field for "item type" :-( The solution could be a system preference for this peculiar facet.
But if a development is needed I would prefer a more generic one, to make all facets fully editable, so that each library could define its own facets matching the (sub)fields of its choice, without editing perl files. Do you think it would be a good idea ? I think there is 2 way for doing this : - create a configuration file (yaml ?) - create a (big) syspref Which choice would be the best regarding performances (and other criteria I did not think of...) ?
Regards, Mathieu Saby Rennes 2 University
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 <tel:02%2099%2014%2012%2065> Courriel : mathieu.saby@univ-rennes2.fr <mailto:mathieu.saby@univ-rennes2.fr>
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
participants (4)
-
Jonathan Druart -
Mathieu Saby -
Mike Hafen -
Paul Poulain