Re: [Koha-devel] Notices and slips documentation RFC

Until 17.11, there was a Field Guide for Notices and slips in Koha documentation (https://koha-community.org/manual/17.11/en/html/17_miscellaneous.html#field-guide-for-notices-slips) but it seems to have desappeared in 18.05 Regards S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81

Re: [Koha-devel] What is biblioitemnumber for?

+1 S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 17/11/2018 à 21:24, Tomas Cohen Arazi a écrit : Or merge biblio and biblioitems ;-) El sáb., 17 nov. 2018 a las 16:41, Barton Chittenden (mailto:bar...@bywatersolutions.com>>) escribió: Jus

Re: [Koha-devel] What is biblioitemnumber for?

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 expressio

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 () escribió: > > > Koha v1.x has no MARC support. In fact, it was the first FRBR compliant > software ever, long before FRBR exist

Re: [Koha-devel] What is biblioitemnumber for?

Three levels in BIBFrame again ? Van: koha-devel-boun...@lists.koha-community.org Namens Tomas Cohen Arazi Verzonden: maandag 19 november 2018 14:02 Aan: Paul Poulain CC: koha-devel Onderwerp: Re: [Koha-devel] What is biblioitemnumber for? Great info, Paul! We now removed the marc/marcxml co

Re: [Koha-devel] What is biblioitemnumber for?

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-boun...@lists.koha-community.org *Namens *Tomas Cohen Arazi

Re: [Koha-devel] What is biblioitemnumber for?

From my side it was a joke: we will integrate the new standards, no doubts, but we'll do it more cleanly than using biblio/biblioitems/items ! Le 19/11/2018 à 14:39, Ere Maijala a écrit : If three levels are needed in the future, I'd start from a clean(er) slate and at least make sure they're n

Re: [Koha-devel] Notices and slips documentation RFC

Hi Sophie > Until 17.11, there was a Field Guide for Notices and slips in Koha > documentation > (https://koha-community.org/manual/17.11/en/html/17_miscellaneous.html#field-guide-for-notices-slips) > but it seems to have desappeared in 18.05 For Koha 18.05 you can find the field guide at h

Re: [Koha-devel] What is biblioitemnumber for?

Phew! :) Paul Poulain kirjoitti 19.11.2018 klo 15.41: From my side it was a joke: we will integrate the new standards, no doubts, but we'll do it more cleanly than using biblio/biblioitems/items ! Le 19/11/2018 à 14:39, Ere Maijala a écrit : If three levels are needed in the future, I'd start

Re: [Koha-devel] Notices and slips documentation RFC

Thanks, It's ok with the url but you can't find it (or I can't find it) directly on 18.05 documentation page Sophie -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 19/11/2018 à 14:44, Michael Kuhn a écrit : Hi Sophie > Until 17.11, there was a Field Guide fo

Re: [Koha-devel] Notices and slips documentation RFC

The field guide is based on the wiki page, which I maintained... but I think that developers should be documenting any notices they add, which is why I've added this to the agenda for Wednesday's dev meeting: *Review of coding guidelines* - Proposed coding guideline DOC2: Entries in the *lette

Re: [Koha-devel] Notices and slips documentation RFC

Hi,   I feel if we want one source of truth besides the source code, it would make sense to submit patches to the manual directly instead of adding more documentation outside of it. Adding a POD file will need another person to work on adding it to the manual regularly. Let's not make things mor

Re: [Koha-devel] Notices and slips documentation RFC

I agree with Katrin here, I have been slowly working manual submissions into my QA workflow with requests for patch authors to submit a corresponding manual submission at the same time as the Bugzilla entry. Documenting notices feels like it fits in nicely with that.. rather than requiring double

Re: [Koha-devel] What is biblioitemnumber for?

So who fancies sponsoring that cleanup... it's been on my "Wouldn't it be nice to do" list for years ;) *Martin Renvoize* Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvo...@ptfs-europe.com *Fax:* +44

Re: [Koha-devel] What is biblioitemnumber for?

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 typ

Re: [Koha-devel] Notices and slips documentation RFC

I see your point about eliminating duplication of effort... somewhat less so about failing QA for lack of documentation... undocumented features become a support issue, and that falls in my lap ;-). --Barton On Mon, Nov 19, 2018 at 10:30 AM Renvoize, Martin < martin.renvo...@ptfs-europe.com> wrot

Re: [Koha-devel] What is biblioitemnumber for?

Thanks Paul, that was interesting! I'm glad I asked :-) On Mon, Nov 19, 2018 at 10:58 AM Stefano Bargioni wrote: > 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

[Koha-devel] Hackfest in Marseille in 2019

Hello Koha, I wrote a while ago that the hackfest in Marseille will not take place in spring, because of the KohaCon in Europe (congratulation Dublin). We've chosen : sept 30th - oct 4th. It may be a little bit early to book your flight but you can already set the dates in your agenda ;) --