[Koha-bugs] [Bug 16245] RIS export file type incorrect

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16245

--- Comment #8 from Héctor Eduardo Castro Avalos <hector.hecaxmmx at gmail.com> ---
(In reply to Jonathan Druart from comment #7)
> What is 'MANSCPT'?

Hi Jonathan

MANSCPT is "manuscript" according with official documentation
<http://referencemanager.com/sites/rm/files/m/direct_export_ris.pdf>

This exist in UNIMARC and MARC21. This was coded as BOOK/GEN and is a wrong
reference type.

For example in UNIMARC you can find in Record label in position 6 (type of
record) the value (b = language materials, manuscript) you can see more about
it at <http://archive.ifla.org/VI/3/p1996-1/uni.htm>

MARC21 in Leader position 06 (type of record) is coded "t - Manuscript language
material" and textually cite "Examples include marked or corrected galley and
page proofs, manuscript books, legal papers, and unpublished theses and
dissertations. " <http://www.loc.gov/marc/bibliographic/bdleader.html>

If librarian coded in MARC21 Leader/06 "t" or UNIMARC 000/6 "b" he or she is
coding a manuscript and unplublished book rather than a published book.

> Are the changes related to MANSCPT expected?
Not was the expected but I think this is wrong coded as BOOK in UNIMARC and GEN
in MARC21. So if we started comparing at this point this is wrong anyway.

The expected was as Hugo pointed out in Description
>Catalogue a record with LDR 6 and 7 'ab' --> this is an article
>check the record type is article in koha leader

But for this we need to see more subfields than leader 06 and leader 07. See
"In Analytics" at
<https://www.oclc.org/bibformats/en/specialcataloging.html#CHDBIIAF>

MARC21
Journal article  JOUR
Leader/06 a
Leader/07 a  not b see examples at
<https://www.oclc.org/bibformats/en/fixedfield/blvl.html>
773$7/02  a
773$7/03  s

UNIMARC
Journal article  JOUR
Leader/06 a
Leader/07 a
461

But this needs more work, and if we include journal article we can include more
reference types as annotated in comment 4 and I think (IMHO) this could be
treat it in another bug.


Regards

-- 
You are receiving this mail because:
You are watching all bug changes.