Book Solution Pack Roadmap May 2, 2012

Updates

Paul's work

• Paul has been working to keep things close together. Book solution pack is Alan's from his github, book viewer is a combination of everybody's work. Paul's been trying to add things - search, configuration for DSID, relationship to book object, and other stuff. Solr module is a dependency. Jason's changes have been merged. The only real difference between Jason's and ours is that we still do book metadata, not page metadata, but Paul things that he can make things work.

• Global namespace suggestion of Jonathan's has been used. Page relationship has replaced .

• Upgrade path for all people using book solution pack - Jason has a script, and Alan has a module. Alan's module can be modified to provide an upgrade path. Script so that we don't have time out issues (not GUI based).

Resolution

• All people who want to use the book solution pack from this point forward must upgrade to provide page numbers in relsext. Book Module will pack with an ingest script.
• Make iiv page aware.
• One book solution pack with two bookCModels and shared PageCModel - CModel chosen on ingest and defines the viewer that the book will show in (either IAViewer or iiv). Names will be IABookCmodel and BookCModel.

Action Items

• Links instead of tabs? - put out to google dev list (Alan)
• Solr dependency for book solution pack (Committers Meeting - David and Alan)
• Create the ability to change weights and labels for tabs in the interface in a configuration panel in book solution pack (Paul)
• Make iiv page aware
• Bring together script work for upgrade path

Digital Humanities Module (Advanced Book Solution Pack)

• Regular tab labels and just define a new tab called critical editing.

• Relevant datastreams and functions

• backward compatibility

• Alan's work relies on the current release of the solution pack. Digital Humanities Module is currently two modules (cwrc and shared canvas) will be amalgamated.

Datastreams

Hello: these are the datastreams that I'm proposing for the book page content model for the legislative assembly content. This is what will impact the reprocessing of the content with microservices. Feedback would be appreciated. Default datastreams

RELS-EXT
POLICY
DC

Descriptive metadata

MODS

Archival binary

TIFF

Technical metadata derived from the archival binary

TECHMD

Image-based derivatives

TN
PagePDF
JP2

Text-based derivatives

OCR
ABBYY_XML
WORDSXY

Thoughts? The derivatives may seem a little over the top ... but I'm thinking of the same set of streams for any 'paged' content we may have ... eg. newspapers.

Paul has added some new XSLTs that will facilitate the indexing/display of the content. I am thinking that we can start the reprocessing through microservices and it will reindex the content at the same time as each object is updated with the extra datastreams.

Donald

Other

• JIRA ticket #577 (Abbyy datastreams. Datastream names)
• http://support.vre.upei.ca/issues/6808
• namespace resolution for relationships - what relationships are we using?
• Internet Archives Viewer
• Page Management stuff that Alan's done
• Release schedule and tasks.