Paul, very interesting the basic historic idea. What you wrote, helps me to say that with Elasticsearch, Koha has the possibility to adopt definitely the LRM [1] model, that is going to be implemented in RDA [2]. Especially important IMHO are links among authorities. Or, better, links of any type. Stefano [1] https://www.ifla.org/publications/node/11412 [2] http://www.rda-rsc.org/ImplementationLRMinRDA
On 19 Nov 2018, at 14:39, Ere Maijala <ere.maijala@helsinki.fi> wrote:
If three levels are needed in the future, I'd start from a clean(er) slate and at least make sure they're named appropriately.
--Ere
Marcel de Rooy kirjoitti 19.11.2018 klo 15.08:
Three levels in BIBFrame again ? *Van:* koha-devel-bounces@lists.koha-community.org <koha-devel-bounces@lists.koha-community.org> *Namens *Tomas Cohen Arazi *Verzonden:* maandag 19 november 2018 14:02 *Aan:* Paul Poulain <paul.poulain@biblibre.com> *CC:* koha-devel <koha-devel@lists.koha-community.org> *Onderwerp:* Re: [Koha-devel] What is biblioitemnumber for? Great info, Paul! We now removed the marc/marcxml columns from biblioitems too, so it makes more sense to merge them. El lun., 19 nov. 2018 a las 6:02, Paul Poulain (<paul.poulain@biblibre.com <mailto:paul.poulain@biblibre.com>>) escribió: <wise-old-man mode ON> Koha v1.x has no MARC support. In fact, it was the first FRBR compliant software ever, long before FRBR exist... (who says Open Source is not innovative :D ) More explanation: in Koha v1, you had to enter a minimal biblio description (title, author(s), subject(s)) THEN one or more expression of the work (one large print, one readed book, one pocket, ...), THEN the different items. Very efficient and handy. When I wrote the MARC code, I had to break this 3 level management (MARC has only 2 levels, biblio and items). In Koha 2.0, you had the option to stay "basic" of "marc" cataloguing. It has been removed in Koha ??? (2.2 or 3.0 ?), only MARC cataloguing remained. At this time biblioitems table became useless/should have been merged, but no one coded/hacked it. But yes, it can be removed (unless we want to keep it for future advanced support of FRBR :D ) <wise-old-man mode OFF> Le 17/11/2018 à 20:40, Barton Chittenden a écrit : > Just out of curiosity, why does biblioitemnumber exist? There should > be a one-to-one relationship between biblio records and biblioitem > records ... so why not use biblionumber as the primary key for > biblioitems? > > --Barton -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries _______________________________________________ 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/ -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆+54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha-devel mailing list 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/
-- Ere Maijala Kansalliskirjasto / The National Library of Finland _______________________________________________ Koha-devel mailing list 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/