Expand the ResultType enum and handle further entity types
LavMatt opened this issue · 1 comments
User Story
As a catalogue
I expect to have my searches return the results of multiple types (e.g. dataset, chart, dashboard)
So that i am aware of all available representations of the data i'm searching for
Currently we only handle data products and datasets
Value / Purpose
https://github.com/ministryofjustice/data-platform/blob/main/python-libraries/data-platform-catalogue/data_platform_catalogue/client/datahub/search.py#L159 and https://github.com/ministryofjustice/data-platform/blob/main/python-libraries/data-platform-catalogue/data_platform_catalogue/client/datahub/search.py#L95 you can see how we don;t handle all entities. Will need to add more and suitable parsers for each new enitity
Useful Contacts
No response
User Types
No response
Hypothesis
If we... [do a thing]
Then... [this will happen]
Proposal
No response
Additional Information
Could do with some more discussion and agreement of what entities to focus on
Definition of Done
- ResultType enum expanded
- add those result types to all search client methods where appropriate, along with suitable parser{type} method
- Update tests for more entity types
This is out of date -
we are now handling data product, container, dataset, chart