Hi, working on frameworks translation I decided to take a look at LOC [1] searching for updates. I found that the following fields are absent in default and optional frameworks: '085','264','336','337','338','344','345','346','347','363', '377','380','381','382','383','384','542','588','751','882', '883' (the last one is brand new, September 2012) Also, the following are absent in LOC documents, many obsoleted or for OCLC/RLIN, save the third that is a mistake I known for years but failed to report. '009','011','01e','023','029','039','049','087','091','092', '096','098','099','211','212','214','241','261','262','265', '301','302','303','304','305','308','315','350','359','400', '410','411','440','503','509','512','517','523','527','537', '543','570','582','652','705','715','755','840','851','859', '870','871','872','873' Questions: 1) Is it ok to write a patch to add missing fields? 2) Is it ok to write a patch to remove non-LOC fields? Or do you think is better to keep them? 3) Most of 9XX has no use in Koha, Can it be cleaned? Regards, Bernardo [1] http://www.loc.gov/marc/bibliographic/ecbdhome.html -- Bernardo Gonzalez Kriegel bgkriegel@gmail.com
On 9 February 2013 17:51, Bernardo Gonzalez Kriegel <bgkriegel@gmail.com> wrote:
Hi, working on frameworks translation I decided to take a look at LOC [1] searching for updates.
I found that the following fields are absent in default and optional frameworks:
Hi Bernardo There is a bug open for this already, and may even have a patch, but if not adding one sounds like a fine idea to me Chris
Hi Chris, as usual, you're right :-) Bug 5858 is the one, and have one patch of yours. I'll look at it. Sorry, was too late in the night. Regards, Bernardo -- Bernardo Gonzalez Kriegel bgkriegel@gmail.com On Sat, Feb 9, 2013 at 3:26 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On 9 February 2013 17:51, Bernardo Gonzalez Kriegel <bgkriegel@gmail.com> wrote:
Hi, working on frameworks translation I decided to take a look at LOC [1] searching for updates.
I found that the following fields are absent in default and optional frameworks:
Hi Bernardo
There is a bug open for this already, and may even have a patch, but if not adding one sounds like a fine idea to me
Chris
participants (2)
-
Bernardo Gonzalez Kriegel -
Chris Cormack