Email is a compulsory field when attempting to package or publish the book to the docs stage. Let's do this: 1. Find a way to map the user ID with the API key to Author ID. 2. Use the Author info (First Name, Last Name, Email) for the Rev History entry. 3. Failing an existing and valid Author info, use the Author ID 0 record, if it exists. Failing that, use: First Name: CS Builder, Last Name: Robot, email: robot.com 4. Make the Rev History entry say: "Built from Content Specification <ID> Revision: <RevNumber>
Added. If the user who sends the build request is an author, it will use the information stored in the AuthorInformation table. Since email is compulsory and the fields in AuthorInformation allow email to be null. If the author has a null email address then the "robot.com" email shall be used. If the user isn't an author than it will attempt to use the the Database Default (AuthorID = 0). If that field is empty, then the defaults above are used. If the program has to fall back on defaults then the user's username will be added to the end of the built statement. ie: Built from Content Specification: 2, Revision: 3 by lnewson Also removed the Content Specification built message from the abstract in Book_Info.xml
Looks good. Just change the revdescription to "Build of book by CSBuilder"
Changed the output from "Initial creation of book by CSBuilder" to "Build of book by CSBuilder".
Books assembled by csprocessor now push to the stage via rhpkg with no manual intervention, as of: CSProcessor client version: 0.17.0 Web Service at http://csprocessor.cloud.lab.eng.bne.redhat.com:8080/ version: 0.21.4