Monograph Chapter-Processed XML Workflow Requirements
Context
Miro ref: scoping session 3
BCMS so far only supports "database" type of chapter-processed content. However, Bookshelf receives monographs that must be chapter-processed because of funding or our submission details. For these monographs, submitters provide detailed book metadata that we want to ingest and use as provided. Thus, we need a setting or workflow adjustment in the BCMS to migrate and process this content.
User story: To migrate legacy content that must be migrated as chapter-processed for BCMS funding data model, and continue to process this type of content, BCMS needs to support reading book metadata from a chapter submission so that the rich metadata in funded submissions can be processed and preserved. This scope assumes a new settings template is not required. (Time estimate: 6 developer days)
User story: As a frequent submitter of bulk content via FTP I want to be able to submit my content without first setting up the content "container" in the BCMS so that I don't need to take multiple submission steps. (Time estimate: 3 developer days)
User story: As a frequent submitter to Collections I want my content to be automatically matched to the correct collection so that so that I don't need to take multiple submission steps. (Time estimate: 2 developer days)
Scoping outcome
- Match a FTP submission of a chapter to a collection by the
<collection-submit-id>
- Create a book from an FTP submission of a chapter package
- Send collection metadata in json file with XML WF chapter packages for conversion.
- Parse and display book metadata from a chapter converted file.
Proposal
See:
Monograph_Chapter_Processed.pptx
Design
See above
Implementation (if applicable)
[A description of the steps to implement the feature.]
Open issues (if applicable)
This has been discussed, but not sure what issues exist or are related.