Reporting Feature Requests
(UXPROD-1910)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Reporting Feature Requests |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Holly Mistlebauer | Assignee: | Nassib Nassar |
| Resolution: | Done | Votes: | 0 |
| Labels: | ldp-platform, reporting, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Reporting Feature Requests |
| Back End Estimate: | XXL < 30 days |
| Back End Estimator: | Nassib Nassar |
| Development Team: | Reporting |
| PO Rank: | 24 |
| Rank: Chalmers (Impl Aut 2019): | R4 |
| Rank: Chicago (MVP Sum 2020): | R2 |
| Rank: Cornell (Full Sum 2021): | R4 |
| Rank: Duke (Full Sum 2021): | R1 |
| Rank: 5Colleges (Full Jul 2021): | R4 |
| Rank: FLO (MVP Sum 2020): | R4 |
| Rank: GBV (MVP Sum 2020): | R4 |
| Rank: hbz (TBD): | R4 |
| Rank: Lehigh (MVP Summer 2020): | R4 |
| Rank: TAMU (MVP Jan 2021): | R4 |
| Rank: U of AL (MVP Oct 2020): | R4 |
| Description |
|
Create a reporting application as a front end to the Library Data Platform (LDP) with a dashboard of reports as a FOLIO application. This project would require much more research, and is not envisioned for go live. |
| Comments |
| Comment by Cate Boerema (Inactive) [ 03/Sep/18 ] |
|
Sharon Beltaine, Holly Mistlebauer and Nassib Nassar, is this still targeted for completion in the Q3 2018 release? If not, can you please update the Fix version? Also, can we get this assigned to someone (who will play the role of PO for this). Perhaps Nassib? |
| Comment by Theodor Tolstoy (One-Group.se) [ 19/Sep/18 ] |
|
Could someone elaborate a bit more on this feature? It is hard to rank. |
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Hi Theodor. This will be a place where the reports are available for selecting, like a menu. You will be able to import reports that other institutions have created, organize your institution's reports, etc. Does this help? |
| Comment by Nassib Nassar [ 19/Sep/18 ] |
|
I don't think this is currently scheduled or assigned, in the sense of being an active issue, as far as I know. |
| Comment by Nassib Nassar [ 19/Sep/18 ] |
|
I have cleared the Assignee field and the Fix version based on my understanding, which is that this a contemplated feature but not currently prioritized. Please let me know if I am mistaken. |
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Nassib Nassar, the UXPROD issues are not the dev issues. These are the issues we use for planning. The Assignee would be the PO or, in some cases with reporting, Sharon. This helps planners know who to go to with questions. The Fix Version is when we are planning to have the work done or need to have the work done. |
| Comment by Nassib Nassar [ 19/Sep/18 ] |
|
Thanks. I'm happy for this feature to remain here, if you think it is useful. But in terms of development planning, the dashboard is one of many contemplated features and I don't think it is planned for the near or medium term. (Please see the LDP document linked in the "Epic".) So it might be confusing to have certain selected features like that, and not others, listed at this top level. But unless advised otherwise, I will leave the existing feature issues alone. |
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Nassib Nassar, every feature ever planned for FOLIO is a UXPROD issue. We loaded every feature from the original spreadsheet--above and below "the line," There is an expectation that a reporting dashboard will be created for FOLIO so if this isn't your understanding we need to discuss this. Thanks. |
| Comment by Nassib Nassar [ 19/Sep/18 ] |
|
Is this “Epic” a catch-all for everything related to reporting, or is it intended for the reporting database reference implementation? I had thought the latter. |
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Nassib Nassar, this issue isn't the Epic. The Epic is
|
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Nassib Nassar, I will agree that UXPROD is very confusing. Originally it was for tracking the work of the Product Owners. It has evolved to also be the place we plan releases, which means we added the results of the gap analysis results here, and the feature estimates, etc. Believe it or not, it does work. It's probably best for you to focus on the issues in the Reporting JIRA project for now. This is where the detail issues are entered and tracked. You can define the issues that need to be done as you become aware of them. I will work with JIRA to make sure each Reporting JIRA issue is linked to a UXPROD issue and that each UXPROD issue gets an estimate. This way you can focus on the data warehouse. I'll show you what I've done so you can see how it all connects up. We can leave the Fix Versions (release) blank for now and only assign those issues that have a known assignee. How does that sound? |
| Comment by Sharon Beltaine [ 15/Jul/19 ] |
|
Need to review with Reporting SIG. |
| Comment by Sharon Beltaine [ 22/Jul/19 ] |
|
Should/can this issue become an NFR? |
| Comment by Charlotte Whitt [ 07/Nov/23 ] |
|
Hi Nassib Nassar - wouldn't you say that this feature has been accomplished by now? And we can close this feature as done. |
| Comment by Nassib Nassar [ 07/Nov/23 ] |
|
This has been superseded by the Reporting app. |