Use case deliverable 2: Support for XML and PDF book-processed content
As agreed (below) in DDWG meet 30 March, I'm opening this draft epic to begin mapping issues to the high level use case deliverables.
DDWG meet 30 March
- Retain Stacy's high level map of use cases
- Roll up existing issue (in the DDWG proposal) into epics - map these onto Stacy's high level items
- We write sign off criteria per (existing) issue (where possible), starting with those we need to get moving on now - and highlight technical tests and user tests.
- these (3) should be agreed to, then:
- identify gaps
- identify items that cannot not yet have sign off criteria due to ongoing research into requirements
Use case deliverable 2: Supports all in-BCMS functions required for XML and PDF submitted book-processed content, including:
-
-
Domain service (create and update domain and its settings)
- Specs from NCBI: #226
- #427 (closed): Creating a book in the bcms creates a book in PMC domain using the org's template
- #428 (closed): Collection and book settings changes
- #213 (closed): archiving books
-
-
-
Collection management and inherited templates to permit cloning of metadata / domain settings by organization / collection rules
- #265 (closed): Collection metadata proposal and queries
- #355 (closed): Collection metadata UI
- #436 (closed): collection cover in metadata
- #445 (closed): New collection: redesign to 2 steps for create domain and update domain
- #428 (closed): Collection and book settings changes
- #356 (closed): Sending collection metadata to NCBI system
- #186 (closed): Collection management: grouping and ordering books
-
-
-
Support for Manual and FTP uploads of book-processed content and correct file / component management and versioning for this content - #183: Submission via FTP
- #214 (closed): Books processed at the book-level in PDF and XML workflows
- #408 (closed): Files tab UI for all workflows
-
-
-
Ability to send and receive XML and PDF source files and key processing information about them for conversions to Bookshelf BITS - #278 (closed): XML conversion
- #404 (closed): FTP integration with Apex (PDF2XML vendor)
- #387 (closed): Wholebook load into PMC proposal
- #403 (closed): XML workflow: Renaming PDF files submitted via FTP
-
-
-
Support for all required book metadata (by UI or separate file upload) not in source files to be provided in final XML for ingest into PMC - #270 (closed): Book metadata proposal and queries
- #423 (closed): Book metadata UI
- #426 (closed): Organization metadata templates as xml files
- #315 (closed): Loading and previewing updated Book metadata to PMC
- #425 (closed): Contributor affiliations
-
-
-
Clear rules for database / release loading and implemented integration with PMC (#435 (closed))
-
-
-
Cover upload, modification, and send to PMC for display on PMC sites (#250 (closed))
-
-
-
Clear reporting of submission, conversion, Schematron, loading, release, and other processing errors / issues - Developed as documented here
- #330 (closed): Loading preview status
- #438 (closed): FTP Submission errors
- #370 (closed): Status and error detail on dashboard
- #268 (closed): Status and error detail on book manager
-
-
-
Ability for users to add grant information by API-fed award data sources for funded collections according to funder and NCBI requirements and agreements - #129 (closed): Granthub integration
- #433 (closed): Specs for granthub UI and metadata
-
-
-
Query tab for communicating with vendor and submitters about content issues with source PDF files (#216 (closed))
-