Requests (UXPROD-790)

[UXPROD-2880] Remote storage: automatically split holdings Created: 27/Jan/21  Updated: 27/Jan/23  Resolved: 21/Jun/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R2 2021
Parent: Requests

Type: New Feature Priority: TBD
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Done Votes: 0
Labels: r2-2021-at-risk, remote_storage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODRS-50 CaiaSoft Accession Table Closed
is defined by MODRS-52 Accession Flow (Cornell) Closed
is defined by MODRS-45 Remove accession workflow preference ... Closed
is defined by MODRS-51 Accession Flow (Duke) Closed
is defined by MODRS-54 Extend RS configuration to support ac... Closed
is defined by UITEN-165 Add details to settings > tenant > lo... Closed
is defined by MODRS-53 Accession Table (Duke) Closed
is defined by STSMACOM-510 Update "remote-storage-mappings" inte... Closed
is defined by UIIN-1512 Update "remote-storage-mappings" inte... Closed
is defined by UIRS-32 Remove CaiaSoft accession workflow pr... Closed
is defined by UIRS-36 Configure accession table Closed
is defined by UIRS-38 Update remote storage permissions Closed
is defined by UIRS-39 Edit remote storage accession table Closed
is defined by UIRS-41 Configuration: Accession holdings wor... Closed
is defined by UIRS-42 Update "remote-storage-mappings" inte... Closed
is defined by UITEN-174 Update "remote-storage-mappings" inte... 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
Back End Estimate: XL < 15 days
Development Team: Volaris
PO Rank: 96
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: Grand Valley (Full Sum 2021): R5
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or problem: within CaiaSoft configuration, institutions need the ability to have holdings records duplicated and split as part of the accession process

In scope: Automatically split/duplicate holdings record in accession process for CaiaSoft users

Use cases: Libraries frequently add a large number of items to a location

Proposed solution/stories:

  1. Accession flow is initiated from the remote storage system by creating the accession job.
  2. Remote storage system calls into Folio Edge API to retrieve bibliographic metadata related to item. The item will be identified by barcode. (title, primary contributor, ISBN, call number, enumeration [volume and year], ISSN, identifier, holdings record)
  3. FOLIO responds with item’s (item and holding, but only the item that was accessioned) bibliographic information and automatically changes the item’s permanent location to a remote location (as per accession table). FOLIO checks the permanent location of the current holdings record. The holding needs to be changed to the remote location when the item is changed to the remote location. It is fine to have items with a different location from the holding. If one item has a remote location, the holding must have the same remote location. 
    • If a holding's permanent location matches the new item’s permanent location, the accession process successfully ends here. 
    • If a holding's permanent location doesn’t match the new item’s permanent location, then the accession flow continues.
  4. FOLIO checks the items in the current holding and compares them with items from the remote storage request.
    • If all other items from the current holding have the same permanent location, as the accessioned item, or should have the same permanent location according to the barcodes in the request, then the current holding's permanent location is changed to the new remote location of the item. Accession process successfully ends here.
    • If not all items from the current holding have or will have the same remote permanent location, then the accession flow continues.
  5. FOLIO checks the current instance for the existence of a holdings record with a location which matches the new item’s permanent location.
    • If such a holdings record is in place, the accessioned item is automatically moved to this holding
    • If there isn’t such a holdings record, 
      • current holdings record is automatically duplicated,
      • holdings permanent location is changed to new item’s permanent location
      • item is automatically moved to created holdings record

Links to additional info

Caiasoft MVP workflows & requirements doc: https://drive.google.com/file/d/1iS8nKYkIP4Q7BA0i8tU6csLqvgEiYRta/view?usp=sharing

Cornell Caiasoft workflows: https://docs.google.com/document/d/1TP4nSNtEkvOnT-tE2yhwqElVtf2aW–EefW9OKhBLjc/edit?usp=sharing

Duke Caiasoft workflows: https://docs.google.com/document/d/1e3vSoerJgYoZpCWW7mDUTaMdfPjVIwCoJdSdOPdMOQU/edit?usp=sharing 

Vision document: https://docs.google.com/document/d/1kMTq4D6PBWsTrEOsn-GIUgFt7vbGKxA2/edit#


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