Versions Compared

Key

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

...

please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!

Discussion items

.
Product Council Update
  • There was a discussion about WOLFcon - brainstorming of topics. Dracine thought we could  take time at WOLFcon to consider how these working groups will function as schools start working on implementation.
  • A security flaw in development was reported. 
  • Some formalization of how we're managing the AWS environment by Peter Murray.
  • Tech - debt
  • Chalmers discussed some bug fixes to the tenant. Some issues between their union catalog, EDS, and FOLIO. 
  • Colleagues in Germany are planning FOLIO days in March of 2020 to be held in Mainz.
  • The hotel for WOLFcon has confirmed a block of rooms. Registration should be available by the end of the week. Meetings are expected to take place all day Wednesday, Thursday, and half a day FridayFeature ranking/new features?Revisit MARC 655 mapping into Instance

    Results of the Doodle poll?

    Concerns?

    Can all concerns be addressed through individual institutions changing their default mapping?

    Future meeting topics

    Ingolf Kuss presented the Report of the Reporting Data Privacy Working Group

    Report of the Reporting Data Privacy Working Group - Maintaining privacy in the LDP. Sensitive reports were recommended to be "in app". "In app" reports are not restricted to one app, unfortunately. More accurate: "In FOLIO" report. 

    Discussion around WolfCon Planning - In addition to Resource Management proposals there will be a discussion of "Item States" or "Item Statuses". 

    Subgroup Updates and Other Updates

    Data Import: The last subgroup meeting on 11/6/2019 dealt with import functions at the item level.  Filipe was present to assist in design. There has been analysis on all of the fields. 

    Peter Murray will be sending a message announcing the 11/20/2019 FOLIO Forum. Data Import and Data Export Register: https://zoom.us/webinar/register/WN_u_dAhUOAQIOIClZ698R92g

    Mapping genres issue - This is a short term decision. Consider it the final "MVP" decision.  Jacquie questioned why we are not currently focusing on the appropriateness of  the fields that are or are not in Inventory at the moment. Jason added that he would like to see us coming up with guiding principles with what is displayed in Inventory.  Laura wondered if this is something we would like to discuss at WOLFcon? Christie thinks it's important to begin to shift from theory to real-life practical examples. At Chicago they are trying to shift workflows away from MARC. Christie thinks it is important to make a case for data elements. She would prefer that we not be prescriptive since different institutions will develop different workflows. Agreed that WOLFcon is a good opportunity to start talking about workflows and sharing what we have planned.

    Data Export:  Last week the group had a very good meeting about mapping.

    Felix (via chat): "During the creation of our mapping we often noticed that we don't necessarily want to display an element, but want to search for it. Maybe it would be possible to talk some logic like index = yes, store = no."

    WOLFcon proposals
    • Charlotte: Reaction of FOLIO with union catalogs Charlotte Whitt  - please elaborate - sorry I lost the thread of what you said. Example: Chalmers will need different metadata sources. How is the FOLIO metadata data flow and is the flexibility sufficient, or do things need to be redone?
    • Ann-Marie (via chat): "Is there value in a general (non-SIG) session on how various parties use Inventory? Catalogers, Circ staff, Acq staff, including E or only physical? WOLFcon seems like a good opportunity to get folks from the various areas together to hear each other and understand each other's use cases more."
    • Christie Thomas (via chat) "I think it is also important to revisit the requirement to make inventory a flexible display. There are a number of elements that we don't require at Chicago so would like to suppress from display. In that way we have the ability to customize our use of inventory. I am sure that is also true of others. "

    Please contribute ideas: https://docs.google.com/spreadsheets/d/1VEVZT4U8IO9Wztx72xR2zmuLz5A-dlhvgARmdA7DvUU/edit#gid=0


    • MARCCat group has not been meeting. Laura notes progress in the testing environment.
    • Export subgroup continues defining requirements.  During last meeting we concentrated on creating Export mapping and job profiles and discussed importance of consistency in the behavior between import and export apps.  Today we plan review and prioritize features currently associated with Metadata Export epic.  Notes from last week meetings: https://drive.google.com/drive/folders/1_HlVrD4gWyBPWWjnqS_dcvb4u2pNlL8Q
    WOLFcon proposals update (Nov. 18 deadline to submit)

    Please add notes stating your opinions on the worthiness of these proposals.

    Feature ranking/new features?

    If your institution has not ranked

    Jira Legacy
    serverSystem JIRA
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-2002
    (Implement Normalized Call Number for Sorting), please do so. This helps with capacity planning prioritization.

    MARC 655 mapping into Instance
    Resolved for now, based on the Doodle poll results:
    1. Form/Genre: default map will lump the 655 field with Instance subject headings. Libraries who do not want that behavior can adjust the default mapping. And we can revisit whether there should be a separate Form/Genre field in the Instance at a later date.
    Command Line MARC to Instance Editing Demo

    https://github.com/folio-org/mod-source-record-manager/blob/master/RuleProcessorApi.md

    Tool: Postman (freely available, downloadable app)

    Connect to a version of FOLIO on a server

    Only API options needed are POST, GET, and PUT

    POST to get a token; GET the mapping rules

    Mapping rules (in Body) are displayed in JSON:

    copy entire JSON and paste it into the edit window

    Then can change MARC fields, delete, or can add MARC fields if they aren't part of the default

    PUT command to send the changes – need to be aware of which version of FOLIO the changes are being sent to

    Can use GET to retrieve new rules and verify if changes were made

    Cheat Sheets for the Beginners Among Us:

    Quick way to get a token (much quicker than the cheat sheet method): https://folio-testing.aws.indexdata.com/settings/developer/token (Thank you Jenn Colt)

    Future meeting topics

    External integrations (e.g., Caiasoft for off-site storage management) and updates to FOLIO. Where/what is the "source of truth"? --possibly to be addressed at WOLFCon

    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

    Jira

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

    Source of truth (SRS). 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.

    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)

    Authority Data and Inventory Vision (small group work first)

    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 record statuses and the apps that affect them

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

    Jira Legacy
    serverSystem JIRA
    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://wiki.folio.org/pages/viewpage.action?pageId=78336464


    present?

    Name

    Organization


    Aaron TrehubAuburn
          Alice Krim

    Ann-Marie BreauxEBSCO

    Ann KardosUMass Amherst

    x

    Charlotte WhittIndex Data
    xChristie ThomasChicago

    Colin Van AlstineSmith (FC)

    Damian Biagi

    Dennis BridgesStacks

    Dennis ChristmanDuke University
           XDouglas ChorpitaGoethe Uni Frankfurt

    Dracine HodgesDuke University
    x

    Felix Hemme

    ZBW

    Filip Jakobsen

    Jacquie 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
    RegretsMartina Schildt

    VZG

    xMary AlexanderUniv. of Alabama

    Nancy Lorimer

    Stanford

    xNatascha OwensChicago

    Niels Erik Nielsen

    Patty WanningerEBSCO
    XRita AlbrechtHeBIS-Verbundzentrale

    Sara ColglazierMHC/5C

    Sarah SchmidtDuke University

    Tiziana Possemato

    Theodor Tolstoy

    EBSCO

    Wayne Schneider

    Index Data


    ...