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: | critical, po-mvp, report-cluster, reporting, team-mvp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Reporting: LDP-based Reports | ||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Reporting | ||||||||||||||||||||||||||||||||||||||||||||||||
| Report Functional Area(s): |
Resource Access
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R5 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
This report cluster covers reports on library reserves that will be based on data from both FOLIO and the ARES (from Atlas Systems, Inc.) library reserves system. |
| Comments |
| Comment by Sharon Beltaine [ 13/Jan/20 ] |
|
WolfCon 2020: Review data sources and integrations. |
| Comment by Erin Nettifee [ 13/Jan/20 ] |
|
Is this really all related to ATLAS? How does this integrate with the course reserves module? |
| Comment by Angela Zoss [ 13/Jan/20 ] |
|
We talked about this today and realized we need to dig deeper here. Probably need RA input, since we don't know much about course reserves yet! |
| Comment by Erin Nettifee [ 13/Jan/20 ] |
|
There's a subgroup - Kelly Drake is the convener |
| Comment by Kelly Drake [ 13/Jan/20 ] |
|
The Atlas Course Reserves development and requirements are all being developed outside the Course Reserves App. We can help with Course Reserve reports but not Atlas. - Might want to check with Chicago. |
| Comment by Angela Zoss [ 24/Jan/20 ] |
|
for Ares reports, see what they need from FOLIO and at least write that report, making sure they have any required connector to Ares |
| Comment by Sharon Beltaine [ 21/Oct/20 ] |
|
Cornell: working with Course Reserves staff to check ranking |
| Comment by Sharon Beltaine [ 27/Oct/20 ] |
|
Cornell: Course Reserve statistics are the number of checkouts on the items that were on reserve. Reserve items are identified in ARES, eresources identified by click in ARES, and we get data from Voyager for physical date range. Criteria includes loan interval, such as minutely loan or regular loan. For Cornell, we will get data from FOLIO to match the data we get from Voyager. The FOLIO Course Reserves module will not be used by Cornell at this time. |
| Comment by Joanne Leary [ 29/Oct/20 ] |
|
To clarify Cornell's needs: our objective is to collect reserve usage statistics, for both physical items and e-items, every semester. We currently use Ares to input and manage course reserves. Ares records the number of uses for electronic reserves, but cannot capture usage (checkouts) for physical reserves. At the end of each semester, we extract all of the reserve data from Ares, and import the file into a Voyager Access database. From there we can link to the circ transactions tables in Voyager to get the physical usage for print items. We use criteria related to the loan type to get just the reserve usage. We will need a similar process for linking to physical usage data in Folio, since we will continue to use Ares for course reserve management. |