User assertions: Ability to download all flagged records with reasons

[peggynewman]

1 complaint from collection managers

Currently, if an institution has a large number of flagged records, they can filter to them and download them as a CSV. However, this is meaningless functionality given one of the most critical elements of each flag, the reason, is not downloaded. This is a high priority change. If you download records that have been flagged, the reason must be included in its own column.

Need to be able to download assertion reasons and details.

cc @tmesaglio for testing

[adam-collins]

The download field "userAssertions" contains the current UserAssertion "status". It does not include the associated "comment".

The task is to alter the assertions /sync service to add the latest QualityAssertion "comment" field into SOLR so it is available for retrieval, and include it in downloads.

• This function will be updated to add QualityAssertion.comment to the indexMap with the name "userAssertionsComment".
• syncDocFieldsWithSOLR will create the SOLR schema field, should it be absent, so no manual schema changes are required
• fieldProperies requires the addition of properties for the userAssertionsComment as the SOLR field docValues="false" indexed="false" stored="true"
• Other instances of "userAssertions" need to be accompanied by the addition of "userAssertionsComment" and appropriate implementation.
• Change /index/fields description of "userAssertions" to indicate that it is a "current user assertion status code".
• Add /index/fields description for "userAssertionsComment".
• Should "userAssertions" not be included as part of the hubs custom download "Miscellaneous fields" toggle, find out how it is added and also include "userAssertionsComment".