Problems with reporting Agreements API Publishing Errors
cc @deniskar
Expected behaviour
Failures for Agreements API checks should be accurately reported for component and file and errors tag
Current behaviour
Failed Agreements API check not accurate checked in all contexts
Steps to reproduce
See on NCBI deployed site: http://root.pd-bk-bcms-collection-aggrements-do-not-sweep.ocpdev-be.p2.ncbi.nlm.nih.gov/organizations/ab9a1f09-cfd7-49ab-abdb-71a9b10e9c38/bookmanager/71c080bf-82eb-4527-acf1-fb399283d8c6/ec3ae333-3c13-44f4-a6f4-6b5c948deaa3
- Go to / create book that does not have an agreement for the book / collection
- Load to PMC a file for that book
- Notice that converted file has a Publishing Failed status BUT the component does not, the error is not recorded in Errors tab, and the user received a notification the file was Published but NO notification of any Publishing Failed errors
QA Steps
This is resolved by the development as documented in #800 (closed)
Priority
Y, required for accurate processing and tracking / management