2023-11-29 Data Import Subgroup meeting

Recordings are posted Here (2022+) and Here (pre-2022) Slack channel for Q&A, discussion between meetings

Requirements details Here Additional discussion topics in Subgroup parking lot

Attendees: Ryan Taylor Jennifer Eustis Ann-Marie Breaux (Deactivated) Aaron Neslin Autumn Faulkner Corrie Hutchinson (Unlicensed) Ellis Butler Raegan Wiechert Robert Pleshar Sara Colglazier Taylor Smith Kim Wiljanen Yael Hod Christie Thomas Khalilah Gambrell

Links:

Agenda:

- Discuss upcoming Quesnelia feature: UXPROD-4303 - Set instance/bib record for deletion
  - Post PPT in DI Google folder and add link
  - A first iteration of deleting instances/associated SRS, to get use started - there will be future updates
  - What icon to use in the menu?
    - Flag (as used for setting item status)
    - Trashcan (used for other delete actions, but this is not a full delete yet, so maybe confusing)
    - Exclamation point (used in Instances when various checkboxes are marked)
  - Is there a block on this action if holdings/item still attached? Not in the first iteration, since all actions will be reversible (staff suppress, suppress from discovery, LDR/05)
  - If suppresses the instance from discovery, should that automatically suppress any associated holdings and items?
    - Are there any situations where an instance is suppressed, where holdings and item should not be? No one could think of any. Maybe suppress all of them?
      - Ryan will talk with devs about whether the scope could be expanded to include this; may be challenging for consortial central/member tenants
    - Before actual deletes, would need to check for any restrictions on associated holdings and items (like requests, checked out, etc.) - that would need to be a separate, future iteration
  - Is there an action to reverse this action? Not with another action, but user will be able to manually edit the Suppress from discovery, Staff suppress, and/or LDR/05 byte if an instance is accidentally marked
  - Could there be a script to clean up how instances have already been marked for deletion?
    - Might be tricky since there are so many different workarounds now - status, stat code, tags, etc.
  - Future ideas
    - Batch mark for deletion - could do now it via DI, by exporting, importing with suppressed flags, and externally updating the LDR/05
    - Batch (actual) deletes
    - When/if there is an actual "delete instance" permission and action, make sure it's separate from the "mark for deletion" permission and action, since fewer staff may be permitted to delete than to mark for deletion

Upcoming meetings/agenda topics:

Chat

Ann-Marie to Everyone 1:08 PM
Just as FYI - the current permission for viewing staff suppressed records has never worked. This change will make the permission actually work

scolglaz to Everyone 1:08 PM
How about the circle with ! in red

Christie Thomas (she/her) to Everyone 1:12 PM
I was a few minutes late, so I might have missed this. What happens to the holdings and items that are associated with an instance when you mark it for deletion?

Why do we not use the same icon for the instance that we use for delete on holdings and items?
I am assuming in the future that any removal of the records in the future will happen outside of inventory.

Robert Pleshar to Everyone 1:15 PM
The exclamation point denotes suppression (to me) which is not necessarily the same as being marked for deletion. There are cases where we want to suppress records and keep them so it seems like a different icon would help to differentiate the two.

Jennifer Eustis to Everyone 1:15 PM
I still like the flag as this is marking the instance as deleted and it mirrors the mark as in the item record

scolglaz to Everyone 1:20 PM
Right, I think this can cause problems when linking from Courses, which is to the Item, I believe

Yael to Everyone 1:21 PM
I agree with Christie

Jennifer Eustis to Everyone 1:21 PM
it might also cause problems with requests which is also linked to the item

Christie Thomas (she/her) to Everyone 1:24 PM
That does sound great. But scary! I would want the permissions for being able to automatically delete the holdings and items in batch to be separate. I don't think that everyone who can mark something for deletion should be able to delete subordinate records in batch.

You to Everyone 1:29 PM
Aah - working your way up from instance to holdings to item, Raegan - that's a cool idea as well

Jennifer Eustis to Everyone 1:29 PM
somewhat related … it would be interesting to see a mark for record retention

You to Everyone 1:29 PM
I mean up from item to holdings to instance

scolglaz to Everyone 1:30 PM
Like via Data Import?

Taylor Smith to Everyone 1:31 PM
oh right, yeah

thanks!

Jennifer Eustis to Everyone 1:32 PM
we also have a stat code for delete

Autumn Faulkner (she/her) 1:32 PM
same at Mich State

Corrie Hutchinson to Everyone 1:41 PM
Thanks!