Background
As part of preparing for BFL data due this year, we discussed the problems in the current approach and long term approach as a team on 09/10/25. We walked through this board.
Sticky notes of the discussion
Key actions to achieve our log term approach
- Update this ticket with any learnings from our short term approach.
- Spikes for future state (possibly using expectations) and how to add authentication to the providers web app if this is required
Connected work
We also discussed the current way we display tasks when a user has provided multiple endpoints, currently this is mainly the case for BFL data. In the data table withing the providers service, we show the amalgamated data however a task is raised against a single resource.
For example the below is raising an invalid URI against a previous resource, but it looks like it is being wrongly raised.
Background
As part of preparing for BFL data due this year, we discussed the problems in the current approach and long term approach as a team on 09/10/25. We walked through this board.
Sticky notes of the discussion
Key actions to achieve our log term approach
Connected work
We also discussed the current way we display tasks when a user has provided multiple endpoints, currently this is mainly the case for BFL data. In the data table withing the providers service, we show the amalgamated data however a task is raised against a single resource.
For example the below is raising an invalid URI against a previous resource, but it looks like it is being wrongly raised.