[kbss-cvut/record-manager-ui#71] Reduce the size of PatientRecordDto data #45
Conversation
…data. Also update code to the new OWL2Java constant naming strategy.
… build. Required updated jopa-spring-transaction.
…ing in PatientRecordDao.
…se generic record filtering to get records from institution.
…o record REST API.
…ng-sorting Record manager UI#71 filtering paging sorting
|
Note that the changes regarding kbss-cvut/record-manager-ui#71 are backwards compatible with the frontend, so the PR can be merged without waiting for frontend implementation. |
| @OWLObjectProperty(iri = Vocabulary.s_p_has_author, fetch = FetchType.EAGER) | ||
| private User author; | ||
| @OWLObjectProperty(iri = Vocabulary.s_p_has_author) | ||
| private URI author; |
There was a problem hiding this comment.
Not sure that we won't be using it to show provenance information before the record is fully loaded:
I guess we do not need to optimize PatientRecordDto too much anymore since implementing on the backend, so I was wondering if it is not useful to leave there User author instead (at least developer friendly:). I guess the most important argument to consider is that we do it somehow consistently across the application.
There was a problem hiding this comment.
I just tested it and the current frontend works well with this backend, so picture above is not the issue :)
| @OWLObjectProperty(iri = Vocabulary.s_p_has_last_editor, fetch = FetchType.EAGER) | ||
| private User lastModifiedBy; | ||
| @OWLObjectProperty(iri = Vocabulary.s_p_has_last_editor) | ||
| private URI lastModifiedBy; |
kbss-cvut/record-manager-ui#71.