add retirement beneficiary info to project-level credit view

[andersy005]

as of https://github.com/carbonplan/offsets-db-api/pull/118, we now have additional (beneficiary, note, account, reason) fields in the /credits/ endpoint's payload. should we go ahead and add these fields to the project-level credit view, or should we wait until we have figured out how the search on these fields is going to work?

Cc @katamartin / @badgley

[katamartin]

Practically, I think there's some design work to think through because it's not totally obvious where in the 6-column credits table this info will go, and we don't have a lot of front-end/design capacity right now.

• Straw man proposal: Could we add beneficiary info to an expander, similar to expander pattern on the landing page?
• An issue to consider when we integrate search is: how do we make it clear why a project was included in search results. Right now, we're just searching fields that are already visible in the projects table.
  • To solve this problem on the project-specific page, we could add filtering to the credits table, and pass through search as a query param to the project view (i.e. /projects/[id]?search=[beneficiary query]).
  • To solve this problem on the landing page: I think this might require some more thought! Is it possible to include a summary of beneficiaries on the project? Does database-wide beneficiary search ultimately belong on a credits-specific page?

Curious for @badgley's thoughts + your reactions @andersy005 !