Skip to content

LINDASnext

Julien A. Raemy edited this page Aug 11, 2025 · 1 revision

LINDASnext

LINDASnext represents the next generation of the LINDAS platform, featuring a migration from Stardog to GraphDB EE and a new contractual structure to support the growing demands of Swiss federal linked data services.

Migration Overview

Current Situation

  • Technology Transition: Migration from Stardog to GraphDB EE in progress
  • Service Continuity: All services remain operational during transition
  • Timeline: Full migration targeted for 2026-2027

Contract Structure

Procurement Results

Following the end of the previous general contracts in May 2025, new contracts have been awarded through public procurement in two lots:

Lot 1: Infrastructure, Migration & Operations

Role Organization Services
Prime Contractor Cognizone Lead infrastructure provider
Subcontractors Liip, Ontotext Supporting infrastructure services

Services Include:

  • GraphDB EE triplestore deployment and management
  • Migration from Stardog to GraphDB EE
  • Infrastructure operation and maintenance
  • Performance optimization and scaling
  • Security and access control management

Lot 2: Application Development

Prime Contractor Subcontractors
Liip Interactive Things, Cognizone, MetaSolutions
Zazuko Puzzle ICT, bit42
Adnovum Squirro

Services Include:

  • Cube Creator enhancement and maintenance
  • Data pipeline development and optimization
  • I14Y (Interoperability) platform development
  • opendata.swiss platform implementation (Zazuko)
  • Custom application development for federal offices

Contract Execution Model

Mini-Tender Process

For Lot 2 (Application Development), specific work packages are assigned through mini-tenders - competitive processes among the three pre-selected contractors (Liip, Zazuko, and Adnovum). This ensures:

  • Quality Competition: Ongoing competition for excellence among qualified providers
  • Cost Efficiency: Competitive pricing for individual work packages
  • Flexibility: Ability to match specific expertise to project requirements
  • Risk Distribution: Work spread across multiple proven contractors

The SuisseOffer platform will be used to manage mini-tenders.

Special Projects

  • opendata.swiss next development: Handled separately from the mini-tender process, specifically assigned to Zazuko consortium

Technical Migration

Triplestore Migration: Stardog → GraphDB EE

Migration Process

The migration from Stardog to GraphDB EE will follow a staged approach to ensure service continuity and minimize disruption to users and partner systems. The process will include infrastructure preparation, parallel system testing, gradual data migration, and coordinated endpoint transitions. Throughout the migration, close coordination with partner organizations and satellite systems will be maintained to address compatibility requirements and ensure smooth transitions for all stakeholders.

⚠️ Migration Details TBC: The migration process is currently in planning phase. Detailed timelines, technical procedures, and coordination schedules will be communicated as they are finalized.

The LINDASnext Environments have a dedicated page on this wiki.

Satellite Systems Coordination

Stakeholder Role Coordination Needs
Federal Offices Data publishers Pipeline updates, new tool training
Application Developers System integrators API changes, testing environments
End Users Data consumers Service continuity, new features
Technical Partners Infrastructure users Migration timeline, compatibility

Communication Channels

  • Regular Updates: Fortnightly meetings
  • Testing Environments: Access to LINDASnext features

Partner Coordination Requirements

For Application Developers

  1. Compatibility Testing

    • Test applications against GraphDB EE
    • Validate SPARQL query performance
    • Check authentication flows
  2. Performance Optimization

    • Optimize queries for new triplestore
    • Update caching strategies
    • Monitor resource usage
  3. Feature Updates

    • Leverage new GraphDB EE capabilities
    • Update error handling

For Data Publishers

  1. Pipeline Updates

    • Test existing pipelines with new infrastructure
    • Update metadata and validation
    • Train staff on new tools
  2. Data Quality

    • Validate data integrity post-migration
    • Update documentation and schemas
    • Implement new quality checks

For ongoing updates and specific technical questions, contact the LINDAS team at support.lindas@bar.admin.ch and join our fortnightly calls.

Clone this wiki locally