Versions Compared

Old Version 2

changes.mady.by.user Charlotte Whitt

Saved on

compared with

New Version Current

changes.mady.by.user Tod Olson

Saved on

Key

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

Date

Attendees

Paula Sullenger

...

Tod Olson Charlotte Whitt Debra Howell Kyle Banerjee Darsi Rueda Peter Murray Robert Scheier Christie Thomas Laura Daniels Patrick Roth Hkaplanian Brooks Travis Jean Pajerek Dwayne Swigert Kara Hart @jeremy seiferth  Tracy Patton Alexis Manheim Lauren S (CU) (Unlicensed) Jenn Colt James Fuller patty.wanninger Nick Cappadona Ian Walls Martina Tumulla ranti junus Karen Newbery Natascha Owens Monica Arnold wtf Chulin Meng Martina Schildt Janet Ewing

Discussion items

TimeItemWhoNotes

Elastic Search in InventoryCharlotte Whitt, PO for Prokopovych team

Need Implementers input on a Capacity Planning proposal regarding Elastic Search and UI issues:

The CPT proposed following solution:

  • Keep ES and the Juniper look
  • Dropdown will only display what ES supports right now, limited query search can be supported to a smaller list of fields. 
  • Check with Magda about adding new indexes.
  • Date filters will be added back
  • Booleans will be supported in the query search dropdown
  • Facets will likely be a later release (Lotus)
  • Continue with the Kiwi release as planned.
  • Gives them fast and exact search counts.
  • Query fields can be added without UI changes
  • Filters with facets will require UI work

Slide deck - Search in Inventory using Elasticsearch - Kiwi

See also: 2021-10-25 Capacity Planning Meeting

  • Laura in chat: having the drop-downs will be a huge plus for us at Cornell -- the prospect of training all staff who use inventory to search without them is daunting at best; I worry that without the drop-downs not only would many searches be done incorrectly, but staff confidence in FOLIO would be severely damaged
  • need for testers; will ask in MM SIG
  • Laura in chat: I will make sure we get the searching tested, yes
  • Charlotte asks for feedback and a decision on the proposal
    • yes or no to the proposal on slide 4 from FOLIO implementers
  • Laura: excited about prospect; grave concerns to train interims functionality
    • people will not be able to search effectively
    • thinks this is a very good short term solution; Cornell could go with it
  • Karen in chat: Duke gives thumbs up to Elastic Search with Drop-Downs.
  • no other comments from the implementers 
  • so no objectins from the group
  • Patty: some short videos might be useful 
  • Charlotte: that is a good idea for Lotus, as in Kiwi there is not much changed
  • Charlotte in chat: Elasticsearch Supported Search Options, Filters, Facets and Sorting
  • Laura in chat: and I think the facets and additional new features will be fairly easy to learn (intuitive)
  • Tod: proposal seems like a good path forward
  • Thanks from the implementers group to Charlotte for the effort she has put into this proposal

Capacity Planning updateHarry Kaplanian and ??

Updates on CP team and discussion of development priorities for Lotus and beyond

  • Harry wants to clear up with a couple of things
  • capacity planning group makes no decisions on what is going to be developed
  • idea to change name of capacity planning group
  • a draft capacity planning team charge is presented
  • cap planning
    • defines and plans releases and deadlines for both full named releases and hotfixes
    • provide recommendations for go or no-go decisions
    • help support POs in deciding whether a defect has reached level of severity to make it a otfix
    • identify problem areas
    • support POs having capacity issues; suggest improvements
    • Example: Prokopovich (formerly Core: Functional)
      • Large portfolio, but down to 2 1/2 developers
      • Helped identify some tickets that could go to Vega (but that increases Vega's workload)
    • help drive community ranking process and suggest improvements to that
    • help place new developers contributed to FOLIO on teams


  • Harry presents Kiwi Dashboard as a place for everyone to look at what is in a release
  • there are different visualizations
  • dashboard includes list of dev teams and POs
  • features that teams are working on
  • areas of work within FOLIO
  • statusses of features of the release
  • list of outstanding work
  • same is there vor Lotus, which is the release after Kiwi
  • additionally, there is the Releases Home page
    • including charts with deadlines
    • those charts help in capacity planning
  • at the end of a release the release notes are displayed there as well
  • question by Karen: is the onboarding documented somewhere?
    • Harry: needs to search for it
  • Patty: the ranking in JIRA is no longer viable; some new institutions have no account to rank
    • how are libraries supposed to support needed features
  • Harry: there is the pointing process that will most probably be repeated next year
    • get involved in SIGs
  • Martina S.: there is a working group being fromed tasked by the PC to discuss and propose a new process of ranking/pointing and research on tools
  • Patty: what about the orphaned apps?
  • Harry: there a re more and more apps and code
    • there are discussions in different committees and groups at the moment (PC, TC, CC, POs)
    • FOLIO needs more development teams
  • Debra: pointing exercise - Holly used the rankings to define what goes on the pointing spreadsheet
    • as implementing institution use still the JIRA ranking and their dashboard
    • how are libraries supposed to track their needed features
  • Harry: rankings from JIRA will be exported to a spreadsheet
    • there are tools designed for ranking; that is not JIRA
  • Tod: the roadmap is supposed to be used for defining  priorities and informing on those
  • Harry: a while ago Harry sent out surveys to prioritize epics
    • the community has little or almost no developers to take on development items
    • if there is no development team, no work can happen
  • Tod: that toches back on Karen's earlier question on devs and onboarding
  • Kara in chat: Has the community thought about creating a user group that collects dues and then hires extra developers?  Like ArchivesSpace does?
    • Tod in chat: CC is working on funding/sustainability
    • Harry: this is a topic that CC has a look at
    • today: every organisation that becomes memeber pays an amount of money that goes into the project; what comes out of the dues is paying for a developer
  • Jenn: is hoping debts will be taken into consideration 
  • Karen: the documentation of dev onboardig comes into play here again
  • Ian: as a support vendor without full development team in FOLIO it is diffcult e.g. to fix bugs
    • there are a lot of barriers (e.g. if no expert in Java)
  • Harry: if any library have a developer, please reach out to anyone in capacity planning





Future agenda itemsAll

Next meeting Nov 2 - Anya Arnold and Sharon Wyles Young (PC), Getting started on two Strategic Initiatives for 2021:

  • Measure implementers satisfaction
  • Develop an Implementers SWOT Analysis


Need new demos, they are helpful

Tod: should we coordinate with the Support SIG or documentation group?

Bob: Does the official documentation include videos or demos?  They are useful

Patti: could the demos be farmed out to the SIGs

Tod: seeing others' workarounds in the demos is also useful

Patti: some of the vended libraries are active in the SIGs, others are a little more shy.  Should we bring them here for introductions?  CalTech is going live now, for instance, and nobody seems to know that.

The group liked this idea and asked the vendors to invite new implementers to future meetings?







Future meeting ideas:


Hosting/migration service providers - lessons learned, not sales pitch (smile)

Update from Capacity Planning Team on post-Kiwi development

SysOps will want to ask about integrations with external systems, how are they going for implemented libraries?  How do you get your vouchers to university payment office? IS NCIP working?

...