Reporting: Build Misc Functionality to Support Reporting
(UXPROD-943)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q4 2019 | Parent: | Reporting: Build Misc Functionality to Support Reporting |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Holly Mistlebauer | Assignee: | Sharon Beltaine |
| Resolution: | Done | Votes: | 0 |
| Labels: | NFR, po-mvp, reporting, suppress-from-capplan, team-mvp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Epic Link: | Reporting: Build Misc Functionality to Support Reporting | ||||||||
| Analysis Estimate: | XXL < 30 days | ||||||||
| Analysis Estimator: | Holly Mistlebauer | ||||||||
| Front End Estimate: | XXL < 30 days | ||||||||
| Front End Estimator: | Holly Mistlebauer | ||||||||
| Front-End Confidence factor: | Low | ||||||||
| Back End Estimate: | XXL < 30 days | ||||||||
| Back End Estimator: | Holly Mistlebauer | ||||||||
| Development Team: | Reporting | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||
| Rank: FLO (MVP Sum 2020): | R1 | ||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||
| Rank: hbz (TBD): | R1 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||
| Rank: Leipzig (ERM Aut 2019): | R1 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||
| Description |
|
Reporting SIG members working with their institutions to identify elements. |
| Comments |
| Comment by Cate Boerema (Inactive) [ 03/Jul/18 ] |
|
Hi Holly Mistlebauer, I was just going through the list of featured targeted for the Q2 release and saw that this one still had the status of Open (as opposed to Closed). Are you expecting this to be in or out for the Q2 release? If not, can you please change the fix version accordingly? If so, the status should probably change. Thanks! |
| Comment by Holly Mistlebauer [ 03/Jul/18 ] |
|
Hi Cate Boerema. I scheduled this issue for the Q2 2018 release because, according to Sharon's data warehouse plan, it needed to be done by September 2018 in order to implement the data warehouse by July 2019. I will change the release to Q3 2018 for now. |
| Comment by Cate Boerema (Inactive) [ 03/Sep/18 ] |
|
Hi Sharon Beltaine, is this still targeted for completion in the Q3 2018 release? If not, can you please change the Fix version? Thanks much! |
| Comment by Theodor Tolstoy (One-Group.se) [ 19/Sep/18 ] |
|
Could someone elaborate a bit more on this feature? |
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Hi again! This is making sure that the data needed for reporting is actually available. Most institutions have reports that they currently create daily, weekly, monthly, quarterly, yearly, as needed, etc. With FOLIO these reports will be created using the data warehouse. We need to make sure that the data warehouse contains all of the data you need to create your reports. |
| Comment by Nassib Nassar [ 19/Sep/18 ] |
|
I think, but correct me if I have misunderstood, this issue is superseded by the work of the Reporting SIG (currently within a subgroup) to formulate specifications, called "report prototypes" by the SIG, for individual reports. That activity involves identifying needed data elements at a fine grained level. I can create an issue for that new activity. |
| Comment by Holly Mistlebauer [ 19/Sep/18 ] |
|
Nassib Nassar, this is the planning issue for the work of the Reporting SIG. The actually dev issues should be linked to this one. |
| Comment by Sharon Beltaine [ 19/Sep/18 ] |
|
Anne Highsmith and I are working with the Data Migration subgroup to map data elements in current library systems to data elements in FOLIO. I represent reporting in this subgroup. We are working on data maps for all functional areas (e.g. vendors, loans, requests, users). As Holly said in a previous comment, this is to make sure that the data elements needed for reporting are included in FOLIO so that they can also be available in the data warehouse for reporting. We are still mapping the data elements, so I believe it may be best to change this activity to Q4 2018. I would recommend creating another issue, for instance "build report prototypes," to capture the work the small workgroup is doing to capture how the data elements relate to generate a report. I see the first activity as making sure the data elements are present, and the second as putting the data elements together to form the structure of the report. |
| Comment by Anya [ 29/Mar/19 ] |
|
Comment from the March Meeting : |
| Comment by Sharon Beltaine [ 17/Jan/20 ] |
|
Done! |