Users App
(UXPROD-784)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Ramsons (R2 2024) | Parent: | Users App |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Anne Ekblad | Assignee: | Tim Auger |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | LC-priority2, SolutionArchitecture, loc, patronreg | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Release: | Ramsons (R2 2024) | ||||||||||||||||||||||||||||||||
| Epic Link: | Users App | ||||||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 20% | ||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 20% | ||||||||||||||||||||||||||||||||
| Development Team: | Volaris | ||||||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||
| Description |
|
Context: Library of Congress need this feature but it may be useful for other libraries. The solution should be designed in such a way that it would be useful to any library with this need Current situation or problem: The Library of Congress has ~25 reading rooms. Patron access to these rooms isn't contingent on whether or not they have requested something to read there - some rooms are open to most patrons while others can be accessed only by patrons with special permissions. FOLIO needs to have a mechanism for recording which reading rooms patrons are allowed to access so that staff know who to allow/disallow from the room. In scope
Out of scope
Use case(s) Proposed solution/stories
Links to additional info Questions
|
| Comments |
| Comment by Erin Nettifee [ 21/Feb/23 ] |
|
Cate Boerema how does this relate (potentially) to
|
| Comment by Cate Boerema (Inactive) [ 28/Feb/23 ] |
|
Hi Erin Nettifee! I see
This feature is narrowly focused on tracking and controlling whether or not a patron is allowed into a reading room. At the LC, patron access to reading rooms isn't contingent on whether or not they have requested something to read there - they are given blanket access. Some rooms (like the main reading room) are open to anyone with a library card. Access to other reading rooms is determined by librarians based on interview with the patron. This feature is not an alternative to something like
Hope that makes sense! |
| Comment by Thomas Trutt [ 09/Mar/23 ] |
|
Cate Boerema Question. So your desired behavior would be that this could almost be like a circulation rule in that all patrons with the user type of X would have access to a reading room. But also that staff could give access to a reading room ad hock. This is an interesting request. Cornell does have some reading rooms in one of our units and currently we use SPEC cards and other list to manage them. This may be an interesting alternative to that system. I feel
I would argue though that these spaces should not be service points. Service points are an oddity as they are not really tied to a locations they just kind of float out there in FOLIO space. Because of this i feel rooms may make more sense as an extension of locations. Locations are used to hold materials as then are tied to service points that receive the materials for those belonging to those locations. I feel an expansion of the location object to include a 'restricted use' flag and then a usage list would actually meet your needs. I can also see this being a feature that would be used by other libraries that have similar reading rooms. Also since Locations are already in circulation rules it may be possible to add a rule to allow a patron group access.. again this means added a flag in one of the policies somewhere but i feel its more in line with the current FOLIO architecture. |
| Comment by Erin Nettifee [ 15/Mar/23 ] |
|
Just to mention with Thomas's comment, there is a feature out there -
I'm not sure I agree with leveraging locations for this instead of service points, but I think it's worth also considering whether a new data object is needed for "reading room" instead of trying to extend an existing object. I'm thinking of that in light of knowing that both service points and locations are embedded in Inventory, so if you continue extending those models, you are assuming libraries will use the Inventory modules. Makes total sense for LoC, but if you had a library that wanted to use FOLIO but integrate with another system for inventory management, or even just a different version of Inventory, you introduce a lot of complexity. IMO it's better to not build in an additional dependency there. |
| Comment by Thomas Trutt [ 15/Mar/23 ] |
|
Erin Nettifee Thanks. I was looking at this form Cornell's use case as well. We have Carrels in one of our units that house research and study materials selected by faculty members. Our current solution is to check out all the items to a SPEC card and have a physical list at the desk that is checked when the key is requested. In my mind extending the locations object to include this as well as
That said and taking in consideration you point you made, of what if a library uses a different inventory system i can see where breaking this aport from inventory/service points makes sense. However I would purpose this. Add a flag to locations to allow the indication that its restricted; this could just be an indicator as suggested in
|
| Comment by Erin Nettifee [ 15/Mar/23 ] |
|
I think you're talking about good needs but they are potentially separate features and should go to the SIG for discussion, rather than try to expand this feature. In the context of the reading room, they don't need to do things like manage material type access, they need to manage access to a specific space. |
| Comment by Charlotte Whitt [ 02/May/23 ] |
|
Hi Andreas Mace - I added you as watcher on this feature |