16 May 2023

from 2-4 EST (2 hour meeting)

1. Review any notes or comments on ranking
2. Wrap up preliminary ranking
3. Prepare for EMWG meeting on 23 May

9 May 2023

from 2-4 EST (2 hour meeting)

1. Review any new comments made to EMWG use Cases spreadsheet
2. Update fields based on Use Cases Framework

Note taker: Steven

The Use Case development process is helpful for the LC/Ebsco development; new Jira issues have been created for the LOC development process and many of the use cases we've defined are covered by them. Use cases that have been defined but are not in scope for LOC development work are still useful and can be worked on if/when other funding is identified.

The spreadsheet has links to the LOC-related Jira Issues. 

Still identifying a tech lead at Ebsco.

Before LOC's planned migration in October 2024, they need to have LOC requirements in releases, so that they can be tested and training developed before going live.

The entity management group had use cases from a couple years ago that may be redundant or related to the new issues that are being added for LOC/MARVA development. Our original entity management use cases didn’t know of/take into account MARVA when we were defining them years ago. MARVA will need to continue to be able to exist separately from FOLIO if desired. We should look at the older issues in the original epic, to make sure the new issues can account for any additional context/needs. Also, there may be older entity management issues that we know longer need because the circumstances have changed.

It was suggested that we are the group to rank the issues; we spend the remaining time starting this process.

TODOs

• Charlotte will add links to the spreadsheet for the original EM use cases
• Jacquie will renumber the issues in the spreadsheet.
• Everyone try to provide thoughts on rankings for the remaining issues.
• Next meeting will be on the 16th, hopefully to wrap and prep for the meeting on the 23rd.

25 April 2023

from 2-4 EST (2 hour meeting)

1. Review any comments made to EMWG use Cases spreadsheet
2. Update fields based on Use Cases Framework
3. What do we need to finish so we can wrap-up this group?

Note taker: Charlotte and Steven

Going over the spreadsheet updating FOLIO Role(s), Library/Types, and Comments/Discussion columns.

Homework: Add categories for the remaining Use Cases

Next meeting: May 9th (reserve 2 hours just in case)

18 April 2023

from 2-4 EST (2 hour meeting)

1. Review use cases #37-39 to update the spreadsheet elements.
2. Review any comments made from EMWG group
3. Update framework elements when those are lacking in spreadsheet (this activity might be iterated as we understand more from other library-types)
4. Do we need to continue meeting for 2-hour sessions?

Regrets: Steven Folsom,  Jason Kovari

Note taker: Christie

Use cases 37 and 38 need more input from the community. What is the best community for this beyond the larger Entity Management Working group? 

Use case 40: Gloria would like more examples for the types of queries for display and export for discovery and other consumption. Example of a knowledge card that was generated from a local resource from the DC Public Library and Wikidata: https://graph.library.link/panel/?domain=http://link.dclibrary.org/&id=2_8BKlrtCTI&go=true

Next meetings will be focused on completing the use case categories. Meeting will be 1 hour through the end of the month. Prioritization will happen in the larger Entity Management Working group. 

11 April 2023

from 2-4 EST (2 hour meeting)

1. MARVA demo site
2. Review use cases #26-36 to update the spreadsheet elements.

4 April 2023 from 2-4 pm EST

(2 hour meeting)

1. Review use cases #18-25? to update the spreadsheet elements
2. Schedule Marva demo with LC update
3. Any other topics?

Use cases highlighted in gray are bigger in scope than entity management and need to be addressed with the larger FOLIO community. 

Before the next meeting the participants will review use cases so far and add gap use cases.

1. Welcome Doug Loynes
2. Outcomes from today's EMWG meeting?
3. More use-case discussion. Review cases #12-17 and update the spreadsheet elements
4. Any other topics?

21 March 2023

1. Review use cases #8a-8d to update the spreadsheet elements
2. Discuss use cases #9- as time allows
3. Any other topics?

Homework for next time: to look at Dashboard https://bugfest-orchid.int.aws.folio.org/dashboard for how entity management might benefit from organizing reporting. Documentation at https://docs.folio.org/docs/dashboard/.

Jacquie will look for JIRA for workflow engine.

Gloria will bring the idea of permissions back to LOC to see how it relates to the larger question of user-based customized UI.

Gloria is working LOC to clarify use cases for deletion, deprecation, suppression in the context of entity management.

Agenda item for next meeting - introducing Doug Loynes, the new Product Owner for Missing Link, the development team for LC linked data features: https://www.linkedin.com/in/loynz/

14 March 2023

CANCELLED

1. Review use cases #7-#9 and update the spreadsheet elements
2. Any other topics?

We looked at Cases 7-8d., creating the 3 new Use Cases labeled 8b-8d.   We briefly looked at the FOLIO Linked Data Glossary (thanks to Gloria for this doc) in an attempt to refresh the Use Case documents with those vocabulary terms when needed.  (Jacquie will update current documents by mid-April)

Linked Data Import will require a separate app from the current DI app.

Christie and Steven volunteered to work on clarifying 8a-8d, adding comments and updating the language for clarity. 

We agreed that mentioning the "why" reports or information is needed will be beneficial to our work and for the developers.  What work will those data inform?

1. Review use cases #3-#6 and update the spreadsheet elements
2. Any other topics?

21 February 2023

CANCELLED

1. Any more feedback on the Use Case Document or Spreadsheet?
2. Review individual use cases and update the spreadsheet elements
3. Any other topics?

A small group met today to review use cases 1-2, we updated the description, elements, and some comments.

1. Responses/Questions about Gloria's 1/31 EMWG presentation
2. Input on Use Case Documentation

Living documents for use cases discussed today, these should be considered as "in-process" and not final documents

Use Case Document (Google Drive link)

Use case spreadsheet (Google Drive link)

1. Welcome to Jason K.
2. Updates from EMWG 1/4 meeting
3. No meeting on 1/24, reschedule meetings to more convenient time?
4. Review workflows to find granular use cases
5. Expanding beyond 2020 Use Cases – developing use cases from institution-specific workflows

Recording: https://cornell.app.box.com/s/k43cyrotwzz00e8yhpy164jn5wyod4q5

Regrets: Charlotte and Christie

Note taker: Jacquie

Adding members to this group, Jason has joined, Charlotte is inviting 2 potential members from Lehigh and National Library of Sweden.

Jacquie will write a Use Case document to replace the 2020 use cases, group will review and provide input starting in late January.

Discussion on personas, LC and Ebsco are developing them for catalogers, we could leverage that work.  BIBFRAME aspects of entity management needs to be included in use cases.

Meeting changes:  Meet later in the day (2 PM) and move to weekly on Tuesdays.

All meetings will be recorded for members unable to attend, or who wish to review the meeting.

1. Welcome to Julia Kim
2. Quick recap of 29 Nov. meeting
3. Discuss Use Case 1 edits from last week
4. Discuss Use Case 2 from the 2020 use case list

Regrets: Steven Folsom

Attendees: Jacquie Samples, GLoria Gonzalez, Charlotte Whitt, Julia, Kim, Christie Thomas

Notetaker: Christie 

Recap from 29 Nov meeting - Review of LC requirements. Does not appear to be a gap so far. Focus on a system that works for the majority of the library types. System should be flexible enough to support a range of use cases.  Also reviewed the first use case. Strikethrough means that the notes have been addressed in another use case. 

Approach - create personas for types of libraries and create use cases. Possibly use the "As a FOLIO user I want to ..." statements to define the granular use cases. Charlotte can reach out to public libraries to get their perspectives on the use cases. We should know that even within the broader categories of libraries / personas / types of users there may be multiple approaches to how they will want to manage authorities / entities and the relationships with the bibliographic data. 

Add emerging persona data in the Use case description? Add notes about institutional granularity in the 2022 review notes column. 

Can add new rows if there are use cases that do not fit into the categories present. 

Use case 1- broke this out into two areas focused on representing external datasets within FOLIO and reporting on changes that have been made / needs to be made to related entities (such as bibliographic records). 

To dos: CT will write up the UC approach and add it here: Authority Management - current practice. Others can continue to add to this page, too. 

1. Quick recap of 15 Nov. meeting
2. Recap of LOC slides use cases
3. Discuss Use Case 1 from the 2020 use case list

Regrets: Steven Folsom, Christie Thomas

From Gloria: Here is LC’s full list of requirements: https://sam.gov/api/prod/opps/v3/opportunities/resources/files/a8480cce942d4d769e6d244d3eeea3ff/download?&status=archived&token=
    (That link downloads an excel spreadsheet)

Note: The excel spreadsheet linked above is now stored as "Library_of_Congress_Requirements_Attachment+J3-Mandatory+Requirements+for+Task+Order+REVISED+AMENDMENT+0003",  where Tab 3 is most interesting to our group

1. Scope of work
2. Communication channels
3. Frequency of meeting
4. Review original Use Cases from 2020

Link to Meeting Slides

Link to Gloria's slides for LC presentation

Attendees: Jacquie, Steven, Christie

Regrets: Charlotte, Gloria

Progressed through the meeting slides above covering scope and logistics

• Meeting frequency - every other Tuesday at 11am EST, opposite the larger Entity Management meetings
• Review of the original Use Cases
• Proposal: that we record our decisions about whether there is need to update a use case
• The original use cases sometimes look like what FOLIO development calls themes or maybe even epics.
• Different libraries may have different workflows, and we might need to check assumptions, and record these situations
• Maybe we need a list of all the things we want to be able to do as an institution.
• There's some distance from the original creation of the use cases, and we need get reacquainted with them and rewrite them in some cases.
  • There's more work to connect to other UXProd work.
• TO DO: Begin to respond to the use case list, adding reactions to the right column "2022 Review Notes from Use Case Group"

Future notetaker: Christie