Reporting: LDP-based Reports
(UXPROD-1319)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Reporting: LDP-based Reports |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Angela Zoss | Assignee: | Angela Zoss |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | report-cluster, reporting | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Reporting: LDP-based Reports |
| Development Team: | None |
| Report Functional Area(s): |
Resource Access
|
| Rank: Chalmers (Impl Aut 2019): | R5 |
| Rank: Chicago (MVP Sum 2020): | R4 |
| Rank: Cornell (Full Sum 2021): | R3 |
| Rank: Duke (Full Sum 2021): | R4 |
| Rank: 5Colleges (Full Jul 2021): | R4 |
| Rank: GBV (MVP Sum 2020): | R4 |
| Rank: Lehigh (MVP Summer 2020): | R4 |
| Rank: Leipzig (Full TBD): | R5 |
| Rank: TAMU (MVP Jan 2021): | R4 |
| Rank: U of AL (MVP Oct 2020): | R3 |
| Description |
|
Current LDP derived table expands the user address list into a table where each row is a user-address pair. Some libraries would also like a table where each user appears as a single row and repeated addresses are pivoted so that there is a group of address columns for each address type. (This will be a very wide table! Something like 9 address columns for each address type.) Built-in PostgreSQL pivot functions aren't necessarily sophisticated about pivots. There is a crosstab function that may or may not be built in, but it doesn't ensure that the columns are the same across users unless you know in advance what all of the column names are, so this is just trickier. |
| Comments |
| Comment by Angela Zoss [ 05/Jan/21 ] |
|
Note: one possibility for implementing crosstab automatically (requires function, I think): https://stackoverflow.com/questions/12879672/dynamically-generate-columns-for-crosstab-in-postgresql |