-
Notifications
You must be signed in to change notification settings - Fork 98
Embedded fields of UNIMARC #11
Comments
Bad code, but work :) |
Sorry this has sat open for a while. Do you happen to have a record I can test with? |
01527naa2a2200217#i#450# Field 463 have subfield $1 with inner fields 001, 101, 200 etc (inner record). Lang of record - russian, encoding UTF-8. |
Thanks for the record. pymarc seems to be able to read it. For example this works:
What specifically isn't working for you? |
Yes, it's work, but now inner fields handling as plain text. In my patch, inner fields converts to Field instances. it is more easy for working with record , as it seems to me. |
I'm still confused about what is broken. Can you supply a unit test? |
I think I understand. UNIMARC allows for fields to be embedded in certain linking entry fields (4XXs), as expressed in the "1" subfields in some of the records above. @isergey - @edsu is right; we would need a unit test for the code to make sure it's working and further changes don't break the rest of the module. |
Thank you for pymarc!
But pymarc can't handle embedded fields in UNIMARC scheme. Eg:
EX 1 Embedded fields technique
200 1#$aKesteven chronicle ...
205 ##$aFosse Way ed.
430 #1$12001#$aLincolnshire chronicle$1205##$aNorth Kesteven ed.
More info: http://archive.ifla.org/VI/3/p1996-1/uni4.htm#410
The text was updated successfully, but these errors were encountered: