-
JIRA issue created by: rcook
Originally opened: 2010-09-30 07:36 PM
Issue body:
(nt)
-
When the MARC 700 field contains a name plus a title, it may be a contained work or a related work. When the second indicator is 2, it is a contained work. The converter is treating all 700s+title a…
-
Field 740 (Added Entry-Uncontrolled Related/Analytical Title) with 2nd indicator 2 (analytical entry) lists a related work contained in the main work. The conversion uses the wrong relationship prope…
-
Currently, titles from an enhanced 505 contents note (subfield $t) are being mapped to `bf:contains/bf:Work`. Subfield $g is being mapped to `bf:note`.
I have a record for a book set that has six vol…
-
The current function to produce annotations from 520 fields only seems to work when linking to external summaries (when subfields $u/$c are present). Plain 520 $a summaries are mapped to bf:note. Does…
-
MARC 5XX fields with $5 for local notes are being mapped to bf:Work and bf:Instance. However, since these are local notes that apply to a particular institution's holdings, wouldn't it be better to ma…
-
When Byte 29 (Form) of field 008 equals "q" (direct electronic), the type Electronic is incorrectly not assigned to the Instance. When Form equals "o" (online), Electronic is assigned.
008 950809s19…
-
As part of aligning with emerging standards and simplifying our support for newer Python versions, I'd like us to consider dropping support for Python 3.9 and moving towards adopting the SPEC0 standar…
-
As mentioned in my comment to #7349 MARC 100$q subfields aren't being imported:
> Actually, the problem is worse than described for this specific example because the MARC record actually includes the…
-
Following spec documentation, the following:
```
880-04
2016- :
```
should result in:
```
2016- :
…