Product Owners
Page tree

Versions Compared

Old Version 25

changes.mady.by.user Khalilah Gambrell

Saved on

compared with

New Version Current

changes.mady.by.user Magda Zacharska

Saved on

Key

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

...

 TopicsTimePresenterAgenda/Notes
Announcements 20 minutes


All 

  • Lotus HF #1 released
  • Lotus HF #2 - No date yet or dashboard 
  • Morning Glory 
    • Please start adding your Morning Glory Release Notes - Morning Glory (R2 2022) Release Notes
    • Please clean up your Morning Glory FOLIO features statuses
    • Bugfix period - use it to fix bugs/tests/prep for Nolana etc. Do not use for new Morning Glory development or to address a P3 bug that cannot be tested at all during bugfest (i.e. a P3 bug that will take more than half a sprint to complete). 
      • Priority: Address P1/P2, Wrap up Morning Glory development asap, Test Morning Glory development, Prepare for Bugfest do not wait... do now. 
  • Will discuss MODINVSTOR-925 tomorrow 
  • WolfCon Asia-Pacific - July 15th - there will be English translation. Please register for the program! 
Defining delete instance record requirements- next steps discussion 40 minutes[Khalilah, Charlotte Whitt 

Slack raised on 5/4 - by Charlotte Whitt

Hi @kg - could we maybe put on the agenda for an upcoming PO meeting how best to plan for a coordinated release planning for a couple of topics, we need to solve with a cross app approach.
11:53
From my point of view we have:

  1. Move of holdings and item - with dependencies with other apps
  2. Deletion of Instance - with dependencies with other apps

Not all POs need to stay on for this segment.  Just those POs that need to support what we want to initially support for Nolana:

Complete list of use cases for Deletion of instances

Deletion of instances - dependency check

Slack channels:

#app-interaction-when-deleting-instances (public)

#app-interaction-deleting-instances-dev (private)

Next step: 

  1. UXPROD-3621 Mark instance for deletion. Implement action menu in top navigation bar. Enable the user to mark an instance for deletion  (Nolana, fingers  crossed)
    1. list of corresponding feature for related work on dependent apps:
      1. UXPROD-3092 Corresponding Data Import & SRS MARC Bib work required for Instance "Mark for deletion" 
  2. UXPROD-1624 Deletion. Implement action menu in top navigation bar. Enable the user to delete an Instance (Orchid)
    1. list of all corresponding features for related work on dependent apps: 
      1. ...
      2. ...
      3. ...
      4. ...

Khalilah's notes, reviewed by Charlotte:

Mark for Deletion requirements | Catalog to Patron discovery | Source = FOLIO
1. Action: Mark for deletion (Responsible team: Prokopovych) - UXPROD-3621-- When user selects Mark for deletion what should happen to that record? (Next step: Charlotte to confirm requirements with MM SIG and post a link to requirements to wiki page dedicated to this feature, and POs tied to this requirement will  write their requirements. These requirements should include if any dependency checks (e.g. has a holdings records attach , item record attach , open loan, open requests etc.) are needed to mark a record for deletion.
-- Dedicated Inventory permission (Responsible team: Prokopovych) [Next step: Charlotte to confirm with MM SIG requirements] - UIIN-1979

2. Edit instance record UI (Responsible team: Prokopovych)  [Next step: Charlotte to confirm with MM SIG requirements]

3. Inventory search (Responsible teams: Prokopovych/Spitfire)
- Search > New filter - Mark for deletion - UIIN-1094  (Responsible teams: Prokopovych/Spitfire)[Next step: Charlotte to confirm with MM SIG requirements]
- Default search query change (Responsible teams: Prokopovych/Spitfire) [Next step: Charlotte to confirm with MM SIG requirements]
- Verify if mod-search needs update/create new permission - MSEARCH-321 (Responsible teams: Spitfire) [Next step: Khalilah will verify]

4. Find instance and Find items plug-ins (Responsible teams: BE: Spitfire; UI: Prokopovych)
- Search > New filter - Mark for deletion (Responsible teams: Prokopovych/Spitfire) [Next step: Charlotte to confirm with MM SIG requirements]
- Default search query change (Responsible teams: Prokopovych/Spitfire) [Next step: Charlotte to confirm with MM SIG requirements]
- Verify if mod-search needs update/create new permission (Responsible teams: Spitfire) [Next step: Khalilah will verify]

5. Data export and OAI-PMH? [Next step: Magda to confirm once mark for deletion requirements are confirmed.]

6. Z39.50? [Next step: Charlotte will work with Mike Taylor, and figure out if there is any work needed her]

7. Determine impact edge-rtac/edge-patron. IOW - what do users expect when an instance record is marked for deletion? Should the mark for deletion record be returned in RTAC response? Should the record display under a patron's list of loans. Can the patron renew a loan? Can the patron place request? [Next step: Circ POs Stephanie Buck Brooks Travis  and others to confirm requirements with RA-SIG]

8. OPAC/Discovery layers - what do we need to inform libraries in order to not show records marked for deletion? Or do we do nothing? A property flag is set in the record - UIIN-1504. [Next step: Charlotte to confirm with MM SIG requirements]

Mark for Deletion requirements |  Catalog to Patron discovery | Source = MARC - Next step: Khalilah will schedule a meeting for next week with Charlotte, Magda, Brooks, and Ann-Marie. Charlotte will lead discussion

Baseline Definition of Done (revisions) 40 minutes

Denis Kovtun 

Oleksii Petrenko 

Postponed to July 

...