Page Comparison

In April 2020, all FOLIO Zoom meetings will require a password to join.  Unless otherwise specified for a particular meeting, the password is "folio-lsp".  If this password needs to be changed, come to this page to see the new meeting password.  All FOLIO Special Interest Groups remain open to all—whether or not you are associated with an institution that is implementing FOLIO.

FOLIO Meetings with Zoom

• Over 80% of the bugfest tests passed
• Update from Mike Gorrell about supporting releases.

• Ann-Marie suggested that demos could be planned for the next week or two, based on Sprint demos. Ann-Marie may show import next Thursday or the following. She suggested that 10 minutes could be given in an MM SIG to POs to talk about their areas of development.
• Demo of export will be given by Magda.

Long term solutions - a Performance team has been established. 

See also: 

• Jira Legacy
  server System JiraJIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2369

   New feature to be ranked by the libraries

Results of Bugfest:

• Some performance issues due to new large dataset. Example: search results are not correctly numbered. Calculation of number of records at the top is incorrect. It is actually an estimate, although it looks like a precise number. It is misleading. Looking for a short-term solution. A thought for a solution is to use rounded numbers... Another solution may be to have a "hit count" button that would generate an exact count. Charlotte has a Doodle Poll she is interested in seeing the results from.
  
  Action: Please fill out this Doodle Poll: https://doodle.com/poll/tdp3fn3g9zxcy5bx
  
  
• Document how current systems handle counting results? 
  • Aleph - There are limits depending on size of search results. Important to them to know the number of records planning on being acted upon. 
  • Voyager - truncates giant searches
  • Lloyd - could this be a user setting to be turned on and off?
  • Use Case  - When reconciling ebook collections, for example, knowing the number of ebooks in the catalog within a particular collection in FOLIO and comparing that number to vendor counts of what should be in our catalog is important. 
• Query search: Would it be acceptable that CQL searches would be slower than predefined searches.
• Export result and query result should be the same. Is Inventory the right place for counts? Would MARCCat be better or another area? 
• Use Case: "the search to kick off exports happens in inventory right now so if you do an inventory search and get x records for exports, it’s jarring when the export is a different number of records"

We will postpone this until our next meeting (so those who introduced the questions can participate in the discussion)

Thinking through ramifications of how HRIDs are implemented (e.g., prefixes or not, continuation of numbering from previous ILS) & documenting implementation decisions

Does this information belong in Tips & Tricks? somewhere else?

Some background (thanks to Ann-Marie):

Here is the most recent documentation on HRIDs: https://docs.google.com/presentation/d/1D4yEPVhFbD8ZXlyKfInRafnJUfQWM8syakLu7v6_c8U/edit#slide=id.p1.

Migration is mentioned on slide 4. 001 handling is mentioned on slides 6-7. The Jiras that detail the SRS HRID handling for MARC Bibs are https://issuesfolio-org.folioatlassian.orgnet/browse/MODSOURMAN-206 https://issuesfolio-org.folioatlassian.orgnet/browse/MODSOURMAN-249

Will be happening March 27 12-4 pm Eastern Time:

Inventory (Inventory tips and tricks page)

For every app there are pages of documentation - some are placeholders.

Action: Volunteers needed to collaborate on creating documentation for Inventory pages. It does not have to be in a perfect final form. You can start to record information. If you need a wiki logon let Laura know. She will help you get a log on.

Ann-Marie suggested using this page as a model for a similar page for Inventory - Settings - Reference data decisions and load sequence for migration

>Individual Apps : - Information, Tips, and Tricks

>Inventory

Do we want to start formally splitting meetings between development and implementation discussions? Have a more organic structure? Something else entirely? What future topics would you like to discuss?

https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit

Please think about this over the next week. 

We could keep a running list of ideas on a Google Spreadsheet. 

https://issuesfolio-org.folioatlassian.orgnet/browse/REP-234

https://wiki.folio.org/pages/viewpage.action?pageId=78336464