Validate CKAN Integration with MINT Platform

[mosoriob]

Description

We need to validate and ensure the seamless integration between CKAN and MINT for data flow and metadata synchronization. This includes documenting required metadata fields and verifying that the user interface correctly fetches and displays resources from CKAN.

Current Behavior

• The integration between CKAN and MINT may have inconsistencies or gaps
• Required metadata fields are not fully documented
• User interface interactions with CKAN resources may have undiscovered issues
• Data flow and metadata synchronization needs validation

Expected Behavior

• Complete documentation of required metadata for resources
• Verified working user interface for fetching and displaying CKAN resources
• Seamless data flow between CKAN and MINT
• Reliable metadata synchronization

Technical Details

Metadata Documentation

• Identify and document all required metadata fields for:
  • Individual resources
  • Resource collections
  • Special data types or formats
• Define metadata validation rules and constraints
• Document mapping between CKAN and MINT metadata schemas

User Interface Validation

• Test resource discovery and browsing functionality
• Verify search and filtering capabilities
• Validate resource preview and details display
• Test metadata editing and update workflows
• Verify error handling and edge cases

Acceptance Criteria

• Verification report of user interface functionality for CKAN resource fetching
• Test cases for metadata synchronization with results
• Documentation of any identified issues with proposed solutions
• Updated integration guide based on validation findings

Related

• CKAN data catalog integration
• Metadata schema management
• User interface for data discovery
• MINT data pipeline processing

Labels

• validation
• integration
• documentation
• user-interface

Priority

Medium - Important for ensuring reliable data discovery and access functionality.

[mosoriob]

Key filtering capabilities include:

1. Spatial Filtering:

• Uses spatial_coverage__intersects to find resources that overlap with a given region
• Takes a geometry object from the region parameter

2. Temporal Filtering:

• start_time__lte: Resources must start before this date
• end_time__gte: Resources must end after this date
• Handles date ranges for temporal coverage

3. Variable Filtering:

• standard_variable_names__in: Filter by specific variables/parameters
• Used when searching for datasets that contain specific types of data

4. Dataset Filtering:

• dataset_names__in: Filter by dataset names
• dataset_ids__in: Filter by specific dataset IDs

5. Pagination/Limits:

• Most queries include a limit parameter to control the number of results
• Typically set between 1000-5000 items