Versions Compared

Key

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

...

New Zoom PolicyLaura E Daniels

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

Product Council Update
  • Over 80% of the bugfest tests passed
  • Update from Mike Gorrell about supporting releases.
Subgroup & other updates?
  • Ann-Marie suggested that demos could be planned for the next week or two, based on Sprint demoesdemos. 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.
Inventory SearchCharlotte Whitt

BugFest follow up work:

Short term solutions on following findings:

  • Inconsistencies; e.g.
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-1055
  • Performance requirements; e.g.
    Jira Legacy
    serverSystem JiraJIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUIIN-1062
  • Result counts (estimates vs. exact hits)

Long term solutions - a Performance team has been established. 

See also: 

  • Jira Legacy
    serverSystem JiraJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-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"
HRIDs in Inventory, implementation decisions

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

Future meetings format & structureLaura E Danielshttps://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit
Inventory Documentation Edit-a-Thon


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


Future MM meetings

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. 

Future meeting topics


Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyREP-234
(overlap analysis) need to collaborate with RM – Chalmers is interested as well (incorporates Inventory & e-Holdings plus ???) see also
Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyREP-92

Statistical codes: type = "Action" – create list of recommended values

Refine the result list - work planned for development Q3 2020

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1634
 and slide deck about hierarchical display of result list

Filip Jakobsen suggests to use Message banner (a new component) to display if an instance record is marked as: Suppressed from discovery, Staff suppress, or Previous held, or holdings/item is marked Suppressed for discovery. This use is intended as a MVP solution: https://ux.folio.org/docs/guidelines/components/message-banner/ Post-MVP we aim for ux consitency with MARCcat.

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keySTCOM-592

Source format (FOLIO, MARC and more) and Source of truth (SRS, LIBRIS, K10Plus and more). Review the FOLIO metadata flow based on test of the newly implementation of edit freeze of records in Inventory when having only SRS and Inventory installed. 

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2249

Inventory, MARCcat, Data Import Permissions interaction review

Search enhancements - possible also look at more general requirements for defining search, e.g. when to use: Phrase search, Truncating (left and/or right), Stemming, Nested search, Boolean search, etc. (TC and MM task)

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-140

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2180

Discovery – need to clarify sources of data for discovery vs. data needed for operations; this needs to be documented for the entire FOLIO community and direction should come from Product Council

Item statuses and the apps that affect them - https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit#gid=2006676577

Music / Maps / Media cataloging review of data elements in Inventory

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIIN-864

Texas A&M may have a music cataloger that can help.

Christie offered to load cartographic and music data from other libraries into their test FOLIO instance.

Jennifer (via chat): We should also look at video as well. Videos have other standard numbers EAN for instance and fields that people like to search and discovery them by

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

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

...

present?

Name

Organization


Aaron TrehubAuburn
      Alice Krim
xAnn-Marie BreauxEBSCO

Ann KardosUMass Amherst


Charlotte WhittIndex Data

Christie ThomasChicago
       Christin Seegerthbz

Colin Van AlstineSmith (FC)

Damian Biagi

Dennis BridgesStacks

Dennis ChristmanDuke University
     Douglas ChorpitaGoethe Uni Frankfurt
xDracine HodgesDuke University

Felix Hemme

ZBW

Filip Jakobsen
xJacquie SamplesDuke University

Jason KovariCornell

Jenn ColtCornell

Jennifer EustisUMass Amherst

Jessica JaneckiDuke University

Kristen WilsonIndex Data
xLaura WrightCornell

Lisa FurubottenTexas A&M

Lisa McCollLehigh University

Lisa SjögrenChalmers

Lynn Whittenberger
xMagda ZacharskaEBSCO

Martina Schildt

VZG


Mary AlexanderUniv. of Alabama

Nancy Lorimer

Stanford


Natascha OwensChicago

Niels Erik Nielsen

Patty WanningerEBSCO

Rita AlbrechtHeBIS-Verbundzentrale
xSara ColglazierMHC/5C

Tiziana Possemato

Theodor Tolstoy

EBSCO


Wayne Schneider

Index Data


...