PDF2XML vendor tagging issues tracking
Hi @lathrops1
As scoped in #17 (closed) and discussed in the walkthrough on Tuesday:
Once Sys Admins has send the PDF2XML vendor files for conversion, Apex currently works as follows:
- Package review before conversion work starts
- checks the content to make sure there is no content missing (e.g. images as reported in pre-flight checks) and the tagging instructions are clear.
- resolves queries with NCBI via email, attaching ‘exhibits’ to show the tagging queries (as comments or markups on the PDF). Usually NCBI can answer these questions. Sometimes they need to contact the Awardee who submitted the PDF content.
- PDF2XML conversion and queries prior to supplying xml
- The conversion work happens externally to NCBI current system
- If the vendor has questions about content, as he is tagging it, he contacts NCBI Sys Admin via email. Again, these relate to content tagging that is unusual in some way (e.g. what tag should be used for this content in the margin?). NCBI currently receives several of these queries a week.
The issues tab would replace the communication currently taking place via email, and would apply to book-level and chapter-level processed books in the PDF workflow for all orgs excluding those that supply the converted xml themselves.
The vendor creates a new issue from the new issue button, which opens this modal:
- He gives the issue a title, describes the issues, and opens the issue. Sys admins associated with the Org get notified.
- He has option to attach files, create a link, and basic styling for text: bold, italics, lists.
- The vendor gets notified when there is a response, and the sys admin can loop in the Awardee if necessary by @mentioning by name or role.
- When the issue is resolved, it's closed.
In the walkthrough your team asked for:
- styling icon for code so snippets of xml can be read clearly. (added to wireframes above)
- that an issue can be reopened if necessary. (added to wireframes above)