Bolsena 2020

Agenda for the Bolsena Code Sprint 2020

Link to the event: Bolsena Code Sprint 2020

hangout: https://meet.jit.si/BolsenaCodeSprint2020
discussion: https://gitter.im/OSGeo/Sprint
Timezone Planner

Timeslot	Melbourne	Amsterdam	Halifax	Vancouver
7:30 UTC	17:30 AEST	9:30 CEST	n/a	00:30 PDT
10:00 UTC	20:00 AEST	12:00 CEST	7:00 ADT	n/a
14:00 UTC	n/a	16:00 CEST	11:00 ADT	7:00 PDT
18:00 UTC	n/a	20:00 CEST	15:00 ADT	11:00 PDT

GeoNetwork Presentations & discussions

Venue:

video: https://meet.jit.si/GeoNetworkDeveloperSprint
discussion: https://gitter.im/geonetwork/core-geonetwork

Presentation links:

Jose: Monday 7:30 UTC GeoNetwork Kickoff
Jody: Monday 14:00 UTC Moving to Maven artifacts
Ian: Monday 18:00 UTC Record Status Change Breakout
Jeroen: Wednesday 7:30 UTC Roadmap and resources
Jose: Friday 14:00 UTC: Sprint results and Social

GeoNetwork Agenda

Day	Time	Topic	Chair	Participants
Monday
	7:30-8:00 UTC	Kick off	PSC	All
	13:00-14:00 UTC	Microservices
	14:00-15:00 UTC	Maven Build
	18:00-19:00 UTC	Record Status Change Breakout	Ian	Jody
Tuesday
	7:30-8:30 UTC	available
	10:00-10:30 UTC	available
	14:00-15:00 UTC	Java 11 Compatibility
	18:00-19:00 UTC	available		Jody
Wednesday
	7:30-8:30 UTC	Roadmap and resources	Jeroen	GeoNetwork PSC
	10:00-10:30 UTC	available
	14:00-1500 UTC	Build party	Jody	Juan, Jose, Francois
	18:00-19:00 UTC	available
Thursday
	7:30-8:30 UTC	available
	10:00-10:30 UTC	available
	13:00-14:00 UTC	Ui architecture	Florent
	18:00-19:00 UTC	available
Friday
	8:00-8:30 UTC	Documentation review	Victor Olaya
	10:00-10:30 UTC	available
	14:00-15:00 UTC	Sprint results and Social	GeoNetwork PSC	All
	18:00-19:00 UTC	available

Work items

Ideas:

Review priorities from user meeting
Date handling Improvement https://github.com/geonetwork/core-geonetwork/issues/1970
GeoNetwork Version 5 Roadmap and Financial Planning - Jeroen identified this as a priority in the user meeting, addressing the sustainability of the project with upfront planning that includes financial and resource planning.

Build using maven artifacts

A recent proposal to use osgeo nexus repository has highlighted several areas where our build system is non-standard and there are opportunities to improve.

Consistent use of maven jar and zip artifacts (rather than copying files between folders) will allow core-geonetwork artifacts and metadata101 schema plugins to be deployed to the nexus repository. See #4701.
Use of maven war overlay allows the webbapp war to be smoothly reused, rather than forked, for those maintaining a custom configuration.
A critical point of discussion in the use of 3.7 for the version number of schema, schema-core and the handling of transitive dependencies by schema plugins. See discussion.
Jody will provide a presentations on these topics on Monday.

The result of this activity should be build independence (checkout and build any directory), a faster development cycle for developers, and a better approach to managing schema plugins and custom WARs.

Evaluate Java 11 compatibility

With master now making use of GeoTools 23.x we are no-longer blocked from pursuing Java 11 compatibility.

This activity will evaluate Java 11 compatibility, with the goal of determining how much work is required
The bulk of the work will be identifying dependencies that require updating or replacing
There are a couple dependencies we use that are no longer maintained (we have our own fork of saxxon) which are a priority to review

The result of this activity is a plan of activities required, and dependencies to update, feeding into GeoNetwork Version 4 planning

Record Status Change Breakout

There are competing requirements for handling and tracking status changes events:

Ian: Picking up 4751 (from earlier 3703) allowing restore of previous changes
Jody: Change log that includes status change deletes, UUID, and indication when children change

This activity may result in a proposal.

OSGeoLive 14.0 update?

Anyone available to update the current version 3.2.1 before 2 July. See

This activity results in a recent version of GeoNetwork being included for OSGeoLive for outreach purposes.

GeoNetwork Version 4

https://github.com/geonetwork/core-geonetwork/issues/4727
Upgrade javascript platform / Generate typescript client / Use landing-page URL inside SPA
OGC API Records / Serving and Querying records as HTML, JSON and XML
Search / Boost series over member of a series / Boost matches on keyword/title
Home / Custom facet on home page (https://taskman.eionet.europa.eu/issues/118112). Requires custom translations loaded from db (https://github.com/geonetwork/core-geonetwork/pull/4756)
Finalize Spring5/JPA2 migration

This activity explores the design decisions going into GeoNetwork version 4.0 planning and results in roadmap decisions.

geonetwork-ui

debriefing of first code sprint
discussion around remaining choices to do
- css framework
- javascript framework
Work on the project architecture
- schematics for Jest ?
- better Storybook integration
  - input parameters for live components
  - accessibility
  - e2e test over storybook
- expose components as libraries ?
- routing
- lazyloading
- css customisation
Coding some components
- search input
- search results
- infinite scroll
- ...
Provide some web components (mini-apps)
Server Side Redering tests
- for metadata page (formatter)
- crawling
UI template for search page