Let's say that I have a list of financial transactions that I need to read in from the file. I want to make the best guess I can at what account should be credited/debited based on the transaction memo compared to past transactions.
For example, if Wal-Mart was used with 'Shopping' then if a transaction that gets read in from the file with Wal-Mart as the description should show 'Shopping'. If there cannot be a match found, then the application should make the best guess and get feedback from the user. If there is not a best match then the user should be asked which account makes most sense.
To me, there is a lot of interaction with the user so it would make sense that this should all live in the UI layer. Once all the transactions are paired with accounts, then it should be sent to the Application Service layer to be saved.
Right now I'm just using a CLI, so I could inject an object that inherits from a 'Presenter' interface that the Application Service uses; however, this will not work when I get rid of the CLI and want to use a REST API around the Application Service layer.
Does it make sense to just include all this logic in the UI layer?