Versions Compared

Old Version 4

changes.mady.by.user Ann-Marie Breaux (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Ryan Taylor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 linkLink to overview slide deck
      • 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

...