Bring Column Mapping into C&P

[Ben-Hodgkiss]

Background

We have the ability to map columns within the manage service. We think that this functionality would be for external users who find it difficult to provide exact field matches (possibly due to existing workflows).

The internal tool includes the ability to un-map.

Work for this ticket

We want to introduce column mapping in to check & provide. We want to approach this with some safeguards such as the following;

• Without ability to un-map global values
• Ensure drop-down only shows fields from spec

We will also need to think about language that is used as internally 'field' and 'column' (and the difference between them) makes sense to internal users, however this may have unclear to external users.

• Think about content
• Mock up design based on new content
• Design crit/co-design session
• Implement functionality in dev for UR

[paris-dp]

@Ben-Hodgkiss and I discussed this today. A summary of this is below;

• We spoke about mandated datasets and the requirements set out within legal instruments for Brownfield Land data and Plans datasets. Field names are set out as part of the requirements and therefore, we would like to implement column mapping by using the provision reason. We would like this to result in column mapping not being available for the provision reason statutory, but available for other provision reasons. In terms of future state, we can introduce tasks to let users know that their field names do not match the specification, and raise issues if a dataset becomes statutory.

• We spoke about how users can identify when they can map a non mandatory column (as this is not raised as an issue in check) one way in which this could be more obvious to users is to list the fields outlined in the data specification and pull the field headers from the user's dataset in the dropdown, however we understand this would be a more challenging dynamic tech approach and we can discuss this. We would change this in the manage service too.

• We also spoke about the generally services should offer one thing per page, and that column mapping may look different in check and provide than the manage service. I will look to wire frame how this could look along with some content to explain why the user is being shown new functionality.

[paris-dp]

I have mapped out some user flow options for check and provide here. I have suggested some initial content however when an approach is agreed I can fnalise this with Oli.

Options to be discussed in a design crit/co-design session

https://app.mural.co/t/mhclg2837/m/mhclg2837/1778839673966/506e57403bd90732cd3c78bba60ba4c78b2572ef?wid=0-1778839671558

[paris-dp]

Updates made to the mural board based on the design crit.

Explanation of implementation.

Column mapping should be introduced into the user flow conditionally. If the conditions apply, the user will see column mapping, before they see check results for the first time.

This will be introduced slightly differently to how this is in the manage service as this will be in a ‘one thing per page’ pattern for external users. There will not be the option to un-map for a user.

Conditions:

• Provision reason: if the provision reason is statutory, we do not want column mapping to be available for the user, as they are obliged to provide the fields specified. We want column mapping to be available for other provision reasons if other conditions are true
• We have been unable to map all expected fields (and there are unmapped headings available to map in the user’s data)
• There are no other blocking issues

Other amends

• Column mapping component columns have been flipped around and headings changed. Drop down will now be dynamic and based upon the headings provided in the user’s data. This will also contain a ‘not provided’ option.
• The user will need to select something for each field in the dropdown. This means column mapping will only be shown to the user once.
• We need to introduce an error message for if a user does not map a field. If one or more is not selected, an error summary should be shown at the top of the page, each error should link down to the field that has not been selected. The row in the mapping component should also show an error message. The error message would be ‘Select the [field-name] field’
• We want to introduce a summary of columns that we have mapped into the check results page (only if the user has seen column mapping)

[gibahjoe]

Currently testing with various datasets to ensure I have it all covered. I have a few meetings to get through this morning so I will have this up sometime after lunch.