Mark for Deletion - Detecting and Resolving Conflicts Requirements

Requirements

Define requirements for behavior in Inventory - responsible @Charlotte Whitt
- Use cases

IF an instance record marked for deletion cannot have any item records attached, there is no impact on Circulation log

Architectural Requirements for the SA

Define permission solution - responsible @Raman Auramau
- The App Interaction SIG has begun spec of the use of field based permissions. This work is still in a very early phase.
  - Meeting minutes from the App Interactions discussion of field based perms: 2022-05-09 Meeting notes: Field based permissions.
- @Marc Johnson has suggested that the chosen design is by it’s very nature an example of a field level permission, in that the ability to alter the marked for deletion field is controlled by permissions separate to those which control access to the record.
Define robust dependency check across apps; - responsible @Raman Auramau
- This should both support Mark for deletion, and also support the coming work when we must be able to handle the actual deletion of instances
- Deletion of instance can either be performed by a human action or an automatically job

Use cases - Must test to validate functionality (wip)

Test	Jira	Tester	Notes	PO responsible

Test	Jira	Notes	PO responsible
Inventory
Inventory > Edit instance record. Mark instance FOLIO source = FOLIO as Marked for deletion	UIIN-1504	1st iteration	@Charlotte Whitt
Inventory > Edit instance record. Mark instance FOLIO source = MARC as Marked for deletion	UIIN-1504	1st iteration	@Charlotte Whitt
Inventory > Edit instance record. Un-check instance FOLIO source = FOLIO as Marked for deletion	UIIN-2099	2nd iteration	@Charlotte Whitt
Inventory > Edit instance record. Un-check instance source = MARC as Marked for deletion	UIIN-2099	2nd iteration	@Charlotte Whitt
Inventory > When marked for deletion. then instance with instance source = FOLIO is not editable, and all data properties (except check box for marked for deletion) is frozen/greyed out	UIIN-2105	2nd iteration	@Charlotte Whitt
Inventory > When marked for deletion. then instance with instance source = MARC is not editable, and all data properties (except check box for marked for deletion) is frozen/greyed out	UIIN-2104	2nd iteration	@Charlotte Whitt
Inventory UI > Filter and facets on. Verify default search excludes instances being marked for deletion	UIIN-1094	1st iteration	@Charlotte Whitt
Inventory Instance look up component. Verify default search excludes instances being marked for deletion	UIPFI-106	1st iteration	@Charlotte Whitt
Permissions. User has only permission to mark instance as Marked for deletion.	UIIN-1979	2nd iteration	@Charlotte Whitt
Permissions. User has only permission to mark instance as Marked for deletion.	UIIN-2098	2nd iteration	@Charlotte Whitt
Permissions. User has both permission to mark instance as Marked for deletion, and uncheck instance as Marked for deletion	UIIN-1979 UIIN-2098	2nd iteration	@Charlotte Whitt
Data import > Verify indicator set in LDR when instance is Marked for deletion	?	Ann-Marie to define requirements	@Ann-Marie Breaux (Deactivated)
Data import > Verify change of the indicator set in LDR when instance is unchecked as Marked for deletion	?	Ann-Marie to define requirements	@Ann-Marie Breaux (Deactivated)
Data import > Block Update > when instance is Mark for deletion?	?	Ann-Marie to define requirements	@Ann-Marie Breaux (Deactivated)
SRS > View source (storing mark for deletion flag)	?	Ann-Marie to define requirements	@Ann-Marie Breaux (Deactivated)
Dependency checks for when instance with Instance source = MARC is marked for deletion:
Inventory > Action menu is greyed out for quickMARC edits	?	Khalilah to define requirements	@Khalilah Gambrell
Inventory > Action menu is active for quickMARC derive	?	Khalilah to define requirements	@Khalilah Gambrell
Inventory > Action menu is greyed out for quickMARC Add holdings record	?	Khalilah to define requirements	@Khalilah Gambrell
Inventory > View Source. Verify the indication set in LDR 05.		Ann-Marie to define requirements	@Ann-Marie Breaux (Deactivated)
SRS API	?	Ann-Marie to define requirements	@Ann-Marie Breaux (Deactivated)
Authority + Bib linking		Khalilah to define requirements - When can this be tested?	@Khalilah Gambrell
Dependency checks for when instance with Instance source = FOLIO and instance source = MARC is marked for deletion:
Inventory > Search result. Mod-search	MSEARCH-321 MSEARCH-386	1st iteration	@Khalilah Gambrell @Mikhail Fokanov
Orders	?	Dennis to define requirements	@Dennis Bridges
z39.50	✓	Charlotte discussed with Mike Taylor (6/30)	@Mike Taylor
Data export > Mapping? / Export?		Magda to define requirements	@Magda Zacharska
OAI-PMH		Magda to define requirement	@Magda Zacharska or @Michelle Suranofsky
INN-Reach		Brooks to define requirement	@Brooks Travis
edge-patron		Khalilah to define requirements	@Khalilah Gambrell
edge-rtac		Khalilah to define requirements	@Khalilah Gambrell
OPAC/Discovery UX - how can a library prevent an instance record that is marked for deletion to return in results? Verify in test environment (not sure which?)		CW: The solution where setting check mark as Marked for deletion, will also automatically set the check mark in both the Suppress from discovery and Staff suppress. This functionality will prevent an instance record that is marked for deletion to be populated in OPAC/Discovery	Who?