This monorepo contains the Dataset Portal website.
The Dataset Portal is a web-based frontend for the Dataspace Ecosystem, providing a user-friendly UI on top of the Eclipse Dataspace Connector (EDC). It enables data providers and consumers to discover, publish, and exchange datasets through a secure interface using JSON-LD standards for interoperability.
The portal manages the complete lifecycle of data sharing—from browsing federated catalogs to negotiating contracts and monitoring transfers. Built with Angular's standalone component architecture, it follows enterprise-grade practices including comprehensive testing and automated code quality checks.
The portal includes three main functional areas:
Federated Catalog
- Browse and discover datasets from multiple data providers
- Search and filter available datasets
Dataset Management
- Create and manage datasets as a data provider
- Define access policies for datasets
- Configure contract definitions for data sharing
Contract Management
- Initiate and track contract negotiations for dataset access
- Monitor contract transfers and data exchange status
- Node.js (v22+)
- Built with Angular, ng-bootstrap and Bootstrap
- Tested with Jest and Playwright
- Formatted with prettier
- Lint with eslint
The project requires npm and can be launched in local by running npm install and npm start.
By default, npm start connects to the test environment. To connect to the dev environment instead, use npm run dev.
Launch the website in different environments:
# Connect to test environment (default)
npm start
# Connect to dev environment
npm run dev
# Run without authentication (local development)
npm run start:no-auth
# Connect to local backend - provider mode
npm run start:local-backend-provider
# Connect to local backend - consumer mode
npm run start:local-backend-consumer
# Shortcut for provider mode
npm run start:localThe website will be available at http://localhost:4200
Start the backend locally by following the instructions here.
Unit and end-to-end tests are implemented to ensure code reliability. Reports can be generated to review test results and coverage.
Ensure code quality before committing:
# Lint the codebase
npm run lint
# Lint SCSS files
npm run stylelint
# Format code with Prettier
npm run format:fix
# Check formatting without modifying files
npm run format:check
# Run all validations (tests + lint + stylelint + e2e)
npm run validateBuild the application and regenerate SDK:
# Build the application (runs build:webapp-dev)
npm run build
# Build webapp for production with dev keys
npm run build:webapp-dev
# Build webapp for production
npm run build:webapp
# Watch mode for development
npm run watch
# Regenerate all SDKs
npm run generate:sdk
# Regenerate catalog API services
npm run generate:sdk:catalog
# Regenerate management API services
npm run generate:sdk:management
# Regenerate management backend API services
npm run generate:sdk:management-beBefore pushing your code, run:
npm run validateThis command runs tests, linting, stylelint, and e2e tests. Your PR won't be merged if this fails.
The badges above represent the current build status and security audit results. For the most up-to-date information, refer to the CI/CD pipelines and security scanning reports used in this project.
To use the Storage Account Browse feature (browsing containers and blobs from the UI when creating assets or initiating transfers), each Azure Storage account must have CORS (Cross-Origin Resource Sharing) configured to allow requests from the application's origin.
- Go to your Storage Account in the Azure Portal
- Navigate to Settings > Resource sharing (CORS)
- Under the Blob service tab, add a rule with:
- Allowed origins: your application origin (e.g.,
http://localhost:4200) - Allowed methods:
GET - Allowed headers:
* - Exposed headers:
* - Max age:
3600
- Allowed origins: your application origin (e.g.,
- Click Save
az storage cors add \
--services b \
--methods GET \
--origins "<YOUR_APP_ORIGIN>" \
--allowed-headers "*" \
--exposed-headers "*" \
--max-age 3600 \
--account-name <ACCOUNT_NAME>Replace <YOUR_APP_ORIGIN> with the origin where the portal is hosted (e.g., http://localhost:4200 for local development) and <ACCOUNT_NAME> with your Azure Storage account name.
This project is licensed under the terms specified in LICENSE.txt.