make CreateIssuePageJob more generic

[jillpe]

Summary

CreateIssuePageJob should be more generic.

class method that should take an argument of what type of class it should split it into. ie #split_pdf_into("Book")

Currently the newspaper gem doesn't give you a choice. All created children are type NewspaperPage.

ref: https://github.com/samvera-labs/newspaper_works/blob/bbe8736b0cf622d9c2577faf7a6f0a4e8dd1452c/lib/newspaper_works/ingest/newspaper_issue_ingest.rb#L41

Acceptance Criteria

• CreateIssuePageJob is more generic
• #split_pdf_into takes an argument of a work type

[ShanaLMoore]

renamed to CreatePagesJob per LaRita. Currently the functionality of this job is all commented out.

[ShanaLMoore]

maybe reference and compare it to ConvertPdftoJpg job in LV.

[laritakr]

Test comment for @ShanaLMoore

[laritakr]

Note: Per discussion at 12/14 standup, this job will be based on the Newspaper gem's job, where one or more PDFs are added to a parent work, and processing will split each PDF into individual works with multiple FileSets for each page of the PDF.

[jillpe]

#32 depends on this ticket

[ShanaLMoore]

TODO: Question about tiffs

@kirkkwang to help change tiffs to jpgs for now to unblock LaRita. We will revisit this when we have Rob's attention

We will split this off to its own ticket.

scientist-softserv/utk-hyku#310

[ShanaLMoore]

TODO: @laritakr to add QA instructions with a demo/screenshots to this ticket. We will spin off the specs for this work in a separate ticket, to unblock other iiif_print work.

[laritakr]

To test via hyku, create a Generic Work with a PDF file. This can be done via the UI or via Bulkrax. (If via bulkrax, the file name must be in the same CSV row as the work itself).

Other work types are not configured to split PDFs, and should behave normally.

You should see:

• parent work is created with the pdf in a fileset with the derivative thumbnail.
• each page of the pdf is split as a TIFF into it's own Image child work. The title will match the title of the parent, with the PDF sequence and page numbers added.
• when viewing the parent work show page, the PDF fileset will appear first, and all child works will follow in page number sequence.
• if multiple PDFs are attached to the parent, sequence should still work appropriately as long as all PDFs are added at the same time. (see note re edit below)

Note:

• editing and adding a second PDF to a work will currently result in duplicate file names because PDF sequencing when adding PDFs is not yet implemented.
• relationships are created last. Until the relationships are completed, the new works will not appear on the parent work.

[laritakr]

Blocked by deploy failure. #100

[ShanaLMoore]

@laritakr did this get QA'd? I see it moved to this column but don't see notes detailing the results (unless the previous comment got edited with them?).

[laritakr]

Kirk and I did some QA ourselves, but neither of us added notes. Jeremy merged it yesterday because it had code we needed for spec work, which is why I moved it, but you're right that additional QA with notes is probably beneficial.

[laritakr]

Note that the relationship job is delayed 10 minutes, so there can be a lag before the child works appear on the parent.

Test with one PDF
Test work with multiple PDFs