Also, given that we will also be aggregating the whole of these records , does it make sense to name these as something like itemSummary or requesterOverview?
Marc Johnson September 11, 2017 at 11:01 AM
Edited
The full name as presented in the ui-users module is in the form {{ last name, first name middle name }} in the detail view and {{ last name, first name }} in the list view.
Given that these formats are very much presentational, I believe it is worth storing these three properties separately with the request instead of a consolidated property. Thoughts?
I'm going to work on the basis that this provides us more flexibility for the future, with almost no difference to the amount of backend work, and possibly a small increase in initial UI work
In order to be able to search for/sort requests by requesting patron's name or barcode, these properties need storing with the request