...
| App | Description | Should we allow the deletion to proceed (Yes/No) - If Yes, what should happen? | UXPROD or Jira issues | Product owner | Development team | Planned release | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Data Import | Currently, Data Import does not support deletion of Instances or SRS MARC Bibs, so that would need to be implemented. | Foljet | None | |||||||||||||||
| Orders | Direct links from Orders to Inventory Instance UUID Consequence being that an order can potentially no longer be received. Also we are still working on an ability to change the instance connection. This would be necessary to correct order with references to deleted instances |
| Thunderjet | None | ||||||||||||||
| Invoices | Should not be able to delete an instance if an unpaid invoice is associated | Thunderjet | None | |||||||||||||||
| Receiving | Should not be able to delete an instance if an item is in process (to be received) | Thunderjet | None | |||||||||||||||
| Agreements/Licenses/ERM | No direct links from Agreements or Licenses to Inventory right now, BUT do have direct links to POLs and if a linked POL has an Inventory Instance UUID stored with it, then that will be display as a link to the instance in Inventory. | Bienenvolk | None | |||||||||||||||
quickMARC / SRS | Instance record with Source = MARC has record stored in source-record-storage (srs). So deletion of instance record mean this record will be removed from srs and thus should not be available to edit. | Yes - Spitfire can work with Prokopovych to determine what needs to be passed to Spitfire to delete the record stored in SRS. | Spitfire | Nolana? | ||||||||||||||
| MARC Authority app | Once Authority records are linked to related MARC Bibs or Instances (work planned for Nolana) Q: Charlotte What happens with all the instances and MARC records in SRS which have been associated with the deleted authority record? A: Khalilah "We will work on that when we support linking between MARC bib and authority records. For Nolana, we will probably just not allow for deletion once we detect links. | Yes - unlink records. Do not change data in Instance. | Spitfire | Orchid? | ||||||||||||||
| mod-search | Update indexes to be kept in sync when the instance is deleted from inventory-storage | Spitfire | None | |||||||||||||||
| mod-inventory-update | Aligned with general FOLIO solution for check on dependencies |
| Sif | Orchid | ||||||||||||||
| mod-oai-pmh |
| Firebird | None | |||||||||||||||
| Courses | Should not be able to delete an instance if one or more associate item(s) is(are) part of a Course | No | Thor? | None | ||||||||||||||
| Circulation log | Need the RA-SIG input here | Yes - unlink records. Do not change data in Circulation log. | Firebird | None | ||||||||||||||
| Requests | Delete an instance record based on status? | Stephanie Buck (title level requests) | Vega | None | ||||||||||||||
| Check out | Should not be able to delete an instance if one or more associate item(s) is(are) checked out to a patron | No | Vega | None | ||||||||||||||
| Check in | Should not be able to delete an instance if an associate item does not have the item the appropriate item status (available, lost and paid etc.) | No | Vega | None | ||||||||||||||
| Fees/fines | Should not delete an instance tied to an item based on fee payment status? | Vega | None | |||||||||||||||
| Remote storage | (no description) | Firebird | None | |||||||||||||||
| LTI | ? |
...