Partner Profile Export

[cielf]

Summary

Add the ability to export the partner profiles

Why?

Assists with making HE the 'golden copy' of information for banks, also for reporting to NDBN

Details

Add an export for the partner profiles with (almost) all the fields, except area served, which is detailed below.

• For area served, provide a field that lists the counties, semi-colon-separated

Add a button for the export to the screen reached by signing in as org_admin1@example.com, then clicking "Partner Agencies" and "All Partners" in the left-hand menu.

The banks can configure which sections of the partner profile are used (see the organization information). That configuration shall be taken into consideration for the export -- i.e. show the same sections.

Criteria for completion

• behaviour as described
• tests to support
• update user guide to support

[Benjamin-Couey]

May I work on this one?

[cielf]

Please do!

[Benjamin-Couey]

Two small questions.

The screen reached by signing in as an org admin, then clicking "Partner Agencies" and "All Partners" already has an "Export Partner Agencies" button. However, the CSV created by this button and the ExportPartnersCSVService it calls doesn't include any information from the profile aside from counties served. Should the functionality described by this issue be added on to this existing button and service(possibly with a toggle to select the current limited export vs the full export described in this issue), or should it be an entirely new and separate button and service?

Second, I'll need to create some dummy partner profile data for testing as while the db seed does create profiles for the partners, they aren't complete. Would you like me to update the seed to create complete profiles while I'm at it?

[cielf]

1/ That's actually a pretty big question g. I'm of two minds on it, but since we already are putting information from the profile in the partner export, it's not like we're making things simpler or faster by keeping them separate.

Let's put the profile information into the current one -- but put it before the counties served.

Hmmm. In that case, the Counties served should also be disappeared if they aren't including that section.

2/ Could you reasonably only do complete on ones that are ready for approval, approved or require_recertification? We wouldn't have complete ones for earlier statuses normally.

[Benjamin-Couey]

1/ Sounds good, I'll modify the existing stuff.

2/ That would be doable yes.

[Benjamin-Couey]

Another point of clarification. Partners::Profile defines a list called ignored_columns which contains the names of a bunch of fields which currently aren't implemented in the forms of any partial. There are also a handful of fields (application_data, distributor_type, status_in_diaper_base) which aren't mentioned in ignored_columns but also don't show up in any view.

Am I correct in assuming the export should also ignore these fields?

[cielf]

Yup, don't export the ignored columns. We have a "Waiting for" with a time to go ahead and remove them in the proto-issues.

[github-actions]

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

[cielf]

This is actively in the process of review-and-fix.