master_files RELS-EXT has preceding & following even when only one page.
sdm7g opened this issue · 2 comments
RELS-EXT being generated for master_files have preceding and following pages
(following unit sequence) even when the component has only one page.
This is incorrect.
<rdf:RDF xmlns:fedora-model="info:fedora/fedora-system:def/model#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:rel="info:fedora/fedora-system:def/relations-external#" xmlns:uva="http://fedora.lib.virginia.edu/relationships#">
<rdf:Description rdf:about="info:fedora/uva-lib:2345334">
<uva:isConstituentOf rdf:resource="info:fedora/uva-lib:2222000"/>
<uva:hasPreceedingPage rdf:resource="info:fedora/uva-lib:2345333"/>
<uva:isFollowingPageOf rdf:resource="info:fedora/uva-lib:2345333"/>
<uva:hasFollowingPage rdf:resource="info:fedora/uva-lib:2345335"/>
<uva:isPreceedingPageOf rdf:resource="info:fedora/uva-lib:2345335"/>
<fedora-model:hasModel rdf:resource="info:fedora/djatoka:jp2CModel"/>
</rdf:Description>
</rdf:RDF>
These RELS-EXT values are generated from master_files next & previous attributes, which I assume are being assigned on unit import. We should probably break these outside-component links when MFs are assigned to a component. I need to test whether breaking next/previous links breaks anything in the Unit or Bibl display.
OK: more complicated that I had thought: next and previous are not attributes. They are computed on the fly by sorting master_files.unit.master_files . Not breaking Unit is more of an issue.