Requests (UXPROD-790)

[UXPROD-2879] Remote storage: Reports Created: 27/Jan/21  Updated: 23/Feb/23

Status: Blocked
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Requests

Type: New Feature Priority: TBD
Reporter: Stephanie Buck Assignee: patty.wanninger
Resolution: Unresolved Votes: 0
Labels: remote_storage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UIRS-35 Report format & data fields Open
is defined by MODAUD-69 mod_audit.circulation_logs query util... Closed
Relates
relates to UXPROD-498 Remote Storage Integration Module (Ca... Closed
relates to UXPROD-2696 Remote Storage Integration (Dematic t... Closed
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front-End Confidence factor: Medium
Back End Estimate: XXXL: 30-45 days
Estimation Notes and Assumptions: Moving mod-audit module to spring is included into high-level estimation as it is a pre-requisite for this feature
Development Team: Volaris
Kiwi Planning Points (DO NOT CHANGE): 6
PO Rank: 98
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R1
Rank: U of AL (MVP Oct 2020): R3

 Description   

Current situation or problem: The first iterations of remote storage integration did not include reports

In scope: Exception reports for Dematic StagingDirector, Dematic EMS and CaiaSoft

Use case(s):

  • Status inconsistencies:
    Item was accessioned in status other than “Available” or “In transit”
    Item statuses in Remote Storage and FOLIO don’t match
    Remote Storage shows item is IN, but FOLIO status is not “Available”
    Remote Storage shows item is OUT, but FOLIO status not “Available”
  • Location inconsistencies:
    No information available to determine what the location should be
    Holding’s permanent location doesn’t match to items’ permanent locations (ignore for empty items’ locations)
    Item’s location is remote, but it is not found in the Remote Storage
    Item is available in the Remote Storage, but none of associated item locations is remote
  • Job failures:
    Accession job failures (server errors and rejected items)
    Retrieval request failures (server errors and rejected requests)
  • Other:
    Barcode is changed on the FOLIO side for the item stored remotely
    New holding was created as a result of accession
    Holding was left without items as a result of accession

Links to additional info
Vision doc https://docs.google.com/document/d/1kMTq4D6PBWsTrEOsn-GIUgFt7vbGKxA2/edit#
Reporting requirements: https://docs.google.com/document/d/1IBhLYsihk-lZ9mh9TTP2lr1sLZf-W9agu7IqLABRxmE/edit?usp=sharing

Report configuration requirements

 Configuration settings for Reports

  • Notifications
    • Notification for less frequent reports would be nice, no notifications for frequent reports
    • Configurable notifications ideal
    • Link in notification would be nice
  • Permissions for report writing?
    • Credentials (GVSU)
  • Data retention
    • 15 months (default)
    • Other
  • Optional data fields
  • Call number
  • Chronology
  • Enumeration
  • Item depository ID
  • Loan status
  • Location
  • New collection
  • New loan status
  • New location 
  • Manual/ad hoc
  • Automated
    • Daily
    • Weekly
    • Monthly
    • Annually

Notes: mod-audit should be necessarily refactored according Spring Way approach for this feature.

Interested parties: patty.wanninger



 Comments   
Comment by Tim Auger [ 23/Feb/23 ]

Stephanie Buck Howdy! Should we move forward with this or is this only for Dematic implementations?

Comment by Stephanie Buck [ 23/Feb/23 ]

This could be worked on, Tim Auger

Comment by patty.wanninger [ 23/Feb/23 ]

Tim Auger I had several meetings with a number of people with remote storage, and the people who used dematic did not have any requirements for reports. The Caiasoft people (Duke and Alabama) were very concerned about reports but neither had implemented FOLIO, so it was difficult to get specifics. I spoke to Laura Beacham of Caiasoft and she is very willing to accommodate requirements on her side.

Generated at Fri Feb 09 00:27:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.