Closed acka47 closed 8 years ago
One title is generated as usually by taking the 331 from the superordinated resource with concatenated volume information from 090 and adding the 331 from the volume, see current morph, lines 502ff. Obviously, we don't have a rule for when there also is a 310 from the superordinated resource. I think, in this case we should just ignore the 310. Desired outcome for the example:
{
"@id" : "http://lobid.org/resource/BT000003404",
"title" : "Deutschland, 2: Nordrhein-Westfalen, Niedersachsen-Süd"
}
Fix deployed to staging.
From the comment above (removed the array for the title
filed):
Desired outcome for the example:
{ "@id" : "http://lobid.org/resource/BT000003404", "title" : "Deutschland, 2: Nordrhein-Westfalen, Niedersachsen-Süd" }
Currently on staging (snippet):
{
"@id" : "http://lobid.org/resource/BT000003404",
"title" : "Deutschland 1:300000"
Obviously, not the 331
s plus 090
were taken for the title (as requested) but the other way round, the 310
from the superordinated resource was taken and the rest was ignored. Please adjust the morph accordingly so that the 310
from the superordinated resource is ignored.
Ok, as this was just a sideeffect of dealing with #762 I will fix this when the latter is closed.
Deployed to staging.
+1
Deployed to production, closing.
Example http://lobid.org/resource/BT000003404 (snippet):
From the source:
Obviously, both the title of the resource and the superordinated resource are taken as a title. I think, these should rather be concatinated