Skip to end of metadata
Go to start of metadata

Date

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


Discussion items

ItemWhoNotes
Product Council UpdateDracine Hodges
  • Prioritization of the Workflow App - State of FOLIO in terms of implementation.
  • Harry Kaplanian - Epics ranking
  • Discussion about creating a "FOLIO Futures" group to discuss future feature possibilities. The hope would be to cast a wide net for involvement, perhaps beyond FOLIO's current membership.
Face to face meeting planningLaura Wright

Meeting dates: June 17-19, Location/Hotel: DoubleTree by Hilton Hotel Washington DC - Crystal City,

300 Army Navy Drive, Arlington, VA 22202

Attendance fee: ~$100 ; Target number of attendees: ~120

Registration link:

https://www.eventbrite.com/e/folio-meeting-june-2019-tickets-59544369813

Agenda (much fuller now!)

https://docs.google.com/spreadsheets/d/1na2hOx0iHh6U1rhjut1NJnWb6qxJUcHgezK1-oVtHgo/edit#gid=1940789848


Laura asked that the group look at the current agenda. There have been some new events added.

Subgroup Updates and Other Updates

No updates.

Data Warehouse and In-App ReportingSharon Beltaine
  • Define reporting: Sharon confirmed that defining reporting is not simple. "Refine data delivery" - this has be interpreted as batch processing, script tools, generation of spreadsheets. Pulling data from transnational systems and generating report. 
  • Label of "In App Reports" has been established. They try in their SIG to keep clarity of their mission.
  • Most of their conversations with other SIGs deal with in-app reports, data warehouse reporting. 
  • The group makes a separation between in-app reports and data warehouse reports.
  • An in app report can pull from many other apps
  • Jason - How will the data warehouse facilitate queries that are run on a daily basis and institution specific? Sharon - reporting SIG follows development. A "data lake" was not a feasible option for ease of use due to its unstructured nature. The data warehouse will build an SQL friendly layer. It will use the STAR data model structure. Jason - concerned about loss of data elements. There is no need inherently to not include information. It can all be structured no matter the amount. Sharon - The reporting goals of the groups are being responded to first. The structure of the STAR schema dependent on development.
  • Jackie from Duke asked if in-app reports would be able to be exported. Sharon - It's up to the POs as to how that will be implemented.
  • The "Reporting SIG" does not touch on transformation.
  • Felix (via chat) - "Are in-app reports completely predefined (like UXPROD-887 - journal title list) or could you still narrow it down by specifying attributes?" - Sharon - For the circ related ones - yes, it is defined. 
  • Do they need to be predefined for every app? - 
  • Example: Shelf list by location:


  • Tiziana - It's difficult to imagine an example of a report that could be limited to the domain of a single app since the information from each app is interrelated. Sharon - Agreed that having a way to connect across applications is important. Charlotte - In the data flow between MARCCat and Inventory is about data maintenance. Therefore there will be in app reports relevant for MARC tags - it will be possible to pull reports like this directly from MARCCat. Title data in Inventory maintained in MARCCat is still in the Inventory app. So data sharing when it is not data gathered "on the fly", but stored, in-app reports is a reasonable expectation.
  • Charlotte and Laura agreed that we need a working group to work on in-app reports.
  • Jason - Use-cases around metadata operations is being conflated with how we manage our data and perform batch operations.
  • From Sharon via Chat: In-app vs DW reports: LDP vs. In-App Reporting


Multiple Graphical Representations

(to be continued)

working document:

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

Problems:

  • If multiple forms of the value are represented in a single JSON object, both scripts have to be included in a single value cell. This limits the search function.
  • Chicago is testing graphical representation in FOLIO. Here is an example:

  • See MARC record: https://catalog.lib.uchicago.edu/vufind/Record/8539712/Details#tabnav
  • See JSON sample: (Christie will provide)
  • Functional requirements need to be built so developers can understand the issues. What would we like to have happen in FOLIO?
  • Proposed solution:
    • Single JSON object for the property, e.g., Title, with the ability to have an array of values for display (labels).

    • Values should allow for a property that identifies the script.

    • This would allow for the ability to configure displays to include multiple representations or a selection of representations.

Functional requirement: Create an instance record and be able to have multiple graphical representations of the language, or be able to put a non-transliterated title that can be searched in other scripts.

Note: Charlotte has added following feature description (UXPROD) in Jira: 

UXPROD-1646 - Getting issue details... STATUS


Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) 

The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well?


Future meeting topics

Reporting: in-app and data warehouse (planned for May 16)

Inventory Permissions ( UXPROD-1371 - Getting issue details... STATUS )

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

Item record statuses and the apps that affect them

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

Felix (via chat) "@charlotte: I could ask a colleague (from one of the 180 network libraries) if she/he could review the beta elements from a 'musical' point of view."

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

Christie Thomas

Colin Van AlstineSmith (FC)

Damian Biagi

Dennis BridgesStacks
xDennis ChristmanDuke University
xDracine HodgesDuke University

ZBW

Filip Jakobsen
xJacquie SamplesDuke University

Jason Kovari

Jenn Colt

Jennifer EustisUMass Amherst
xJessica JaneckiDuke University

Kristen WilsonIndex Data
xLaura WrightU Colo Boulder

Lisa FurubottenTexas A&M

Lisa McCollLehigh University

Lisa Sjögren

Lynn Whittenberger

Martina Schildt

VZG

xMary AlexanderUniv. of Alabama

Nancy Lorimer

Stanford


Natascha Owens

Niels Erik Nielsen

Patty Wanninger
xSara ColglazierMHC/5C
xSarah RossCornell



xTiziana Possemato

Theodor Tolstoy



Wayne SchneiderIndex Data