You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Islandora objects that have the content models islandora:pageCModel and islandora:newspaperPageCModel, i.e., book and newspaper pages, use a datastream ID of 'JPG'. MIK's CONTENTdm toolchains write out a file with the name 'JPEG.jpg' (see https://github.com/MarcusBarnes/mik/blob/master/src/writers/CdmNewspapers.php#L209 and https://github.com/MarcusBarnes/mik/blob/master/src/writers/CdmBooks.php#L220). This filename determines the DSID used in Islandora if the content was batch loaded using islandora_book_batch or islandora_newspaper_batch. Therefore, paged content generated by MIK's CONTENTdm toolchains may have DSIDs that are inconsistent with the paged content composite model, depending no how the paged content was loaded into Islandora.
This bug does not affect other toolchains.
This bug is easy enough to fix, but in the interests of consistency and portability during future migrations, Islandora instances that have paged content with the improperly named datastreams should probably replace the JPEGs with JPGs. SFU's site have had these incorrectly named datastreams for over two years with no visible side effects, but we'll be offering a solution for fixing the problem.
The text was updated successfully, but these errors were encountered:
Islandora objects that have the content models
islandora:pageCModel
andislandora:newspaperPageCModel
, i.e., book and newspaper pages, use a datastream ID of 'JPG'. MIK's CONTENTdm toolchains write out a file with the name 'JPEG.jpg' (see https://github.com/MarcusBarnes/mik/blob/master/src/writers/CdmNewspapers.php#L209 and https://github.com/MarcusBarnes/mik/blob/master/src/writers/CdmBooks.php#L220). This filename determines the DSID used in Islandora if the content was batch loaded using islandora_book_batch or islandora_newspaper_batch. Therefore, paged content generated by MIK's CONTENTdm toolchains may have DSIDs that are inconsistent with the paged content composite model, depending no how the paged content was loaded into Islandora.This bug does not affect other toolchains.
This bug is easy enough to fix, but in the interests of consistency and portability during future migrations, Islandora instances that have paged content with the improperly named datastreams should probably replace the JPEGs with JPGs. SFU's site have had these incorrectly named datastreams for over two years with no visible side effects, but we'll be offering a solution for fixing the problem.
The text was updated successfully, but these errors were encountered: