About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20230110

VuFind® Community Call Minutes: January 10, 2023

Attending: Chris Hallberg, Demian Katz, Sudharma Kellampalli, Ere Maijala, Mario Trojan, Susan Turkel

Agenda

1. Development Planning

Newsletter Highlights

The December, 2022 Newsletter was discussed.

Pull Request Review (9.0 milestone)

  • #2400 / VUFIND-1533 - Wrapped link elements should not have space between the lines
    • Next step: resolve conflicts; finish testing and fixing outstanding issues - CH / DK
  • #2447 - AJAX status standardization/modernization
    • Next step: final test/review - DK
  • #2492 - Add refresh buttons to jump menu controls
    • Next step: decide when to add buttons and when to use MenuButton controls from #2378
  • #2543 - ThemeInfo: Fix getMergedConfig
    • Next steps: finish discussion, ensure full test coverage - CH / DK
  • #2624 / VUFIND-1514 - Modernize front end build environment, replace Grunt with NPM scripts
    • Next step: Discuss / finish TODO list - CH
  • #2640 / VUFIND-1563 - Blowfish encryption fails under Ubuntu 22 and Fedora 36
    • Next step: continue test/review process - CH / DK
  • #2660 / VUFIND-1529 - Configurable sort tie-breaker field
    • Next step: continue test/review process - SK / DK
  • #2668 - Avoid null pointer exception in getSubfieldOrDefault
    • Next step: final testing - DK

JIRA Ticket Review (9.0 release, without an existing pull request above)

Not Started - No Blockers
  • VUFIND-1568 - Make Solr port configurable during installation [assigned to DK]
  • VUFIND-1396 - Investigate possibility to deprecate the Context view helper [assigned to EM]
  • VUFIND-1541 - Add Mink test coverage for Markdown rendering [assigned to CH]
  • VUFIND-1547 - Normalize search event namespace [unassigned]
  • VUFIND-1535 - Make search history labeling more consistent [assigned to DK]
  • VUFIND-1566 - Clean up/standardize Javascript lib directory [assigned to CH]
Not Started - With Prerequisites
  • VUFIND-1567 - Update language translation files for release 9.0
    • Prerequisite: complete all changes that impact language files.

2. Technology Demo: Typescript Annotations

Chris mentioned that after reflecting on feedback from last month's discussion, he opened a JIRA ticket with a proposed solution to the variable management challenge he previously discussed.

Chris then demonstrated a way to add JSDoc comments to Javascript to apply Typescript types without requiring a compilation step – this allows VuFind to potentially benefit from Typescript documentation and validation tools without having to change our build process or make the addition/changing of Javascript code more complicated.

It should be easy to integrate type checking into continuous integration. It should also be possible to enforce the inclusion of typing via eslint with “no-implicit-any”.

We should be able to introduce this via a new pull request; no need to wait on other “npm scripts” work in progress before we begin. Chris suggested finishing up the AJAX modernization before introducing this to avoid duplication of effort.

There was discussion of whether we should at some point introduce a compilation step for our Javascript assets. Down sides: introducing compilation steepens learning curve; could complicate deployment process for complex sites like Finna with many views. Advantage: would make it easier to manage dependencies, and to include libraries that don't necessarily have an easy-to-include, stand-alone .js version.

Possible middle ground on compilation: a compiled.js which lumps together third-party dependencies, without making it impossible to override VuFind-specific .js code. This could follow the precedent of compiled.css and offer some benefits without all the drawbacks.

3. Open Q&A / Other Topics?

Ere is releasing RecordManager 2.0 today!

Demian mentioned the need to improve the efficiency of the web crawler tool. Ere suggested that RecordManager might be able to be customized to do web crawling and cache results so that Tika could only be called when things have actually changed upstream.

Next Call

The next call will be Tuesday, February 7, 2023 at 9am Eastern Standard Time (14:00 GMT).

community_call/minutes20230110.txt · Last modified: 2023/01/10 14:31 by demiankatz