Welcome to OSCAR Hub, a repository of ready-to-deploy services for the OSCAR platform. Each service is defined using the RO-Crate standard, including structured metadata, deployment scripts, and FDL definitions.
- 📂 Inside the
cratesfolder, a collection of directories, each representing a deployable OSCAR service. - 📄 Inside each directory:
ro-crate-metadata.json: Service description using the RO-Crate format.fdl.yml: Service definition using the Functions Definition Language (FDL).script.sh: Script to be executed upon service invocation.
- Create a new directory named after your service.
- Copy the contents of
crates/templateinto the new directory and adjust the placeholders. - Ensure the directory includes:
ro-crate-metadata.jsonfdl.ymlscript.sh
- Validate your RO-Crate before submitting a pull request.
To validate the services defined via RO-Crate:
pip install roc-validatorThen run:
rocrate-validator validate -p ro-crate-1.1 --verbose --no-paging ./<service>A GitHub action has been configured to automatically validate new entries submitted via PRs.
-
Install dependencies:
npm install
If you plan to work on the documentation site, also run
npm installinsidedocs/. -
Start the development server:
npm run dev
The script builds the site, serves the
distoutput, and watches for changes. By default it listens on http://localhost:4173; set thePORTenvironment variable to use a different port. -
Edit the contributor & RO-Crate documentation under
docs/with:npm run docs:dev
The documentation is built with Astro Starlight and published under
/guide.
To produce a static bundle without the dev server, run npm run build to regenerate dist/. This command now builds both the catalog landing page and the /guide documentation bundle.
The catalog and service detail pages are generated from every directory under crates/ containing valid ro-crate-metadata.json with a ./ dataset node. The catalog offers table and summary-card views with shared search and filters; the selected view is retained in the URL. The header includes the same moon/sun theme toggle and GitHub icon as OSCAR Landing. Theme selection is saved locally and defaults to the system preference. Each build discovers new services and derives the service-type filter from their metadata; no manual catalog or filter registration is required. Details are published at /services/<slug>/, together with an unchanged copy of the original RO-Crate JSON. The existing Pages workflow runs on pushes to main and publishes the complete dist/ bundle, including /guide.
Run npm test to check automatic crate discovery, metadata preservation, generated links, and search/filter behavior. The generation regression test adds a new crate in a temporary workspace and verifies that a rebuild includes its catalog entry, detail page, and new service type. Tests also run before the Pages build.
“Files & artifacts” offers on-demand previews of local UTF-8 text files up to 256 KiB and PNG, JPEG, GIF and WebP images up to 5 MiB. YAML and shell scripts use syntax highlighting in both themes. File contents and the YAML/shell highlighter are downloaded only when a preview is opened; successful previews are reused for the current page. Other text formats, including Markdown and notebooks, show their source as plain text. Directories, unavailable artifacts, binaries and larger files keep their existing repository links. RO-Crate metadata also loads on demand.
The canonical reference for onboarding, workflow expectations, and field-by-field RO-Crate documentation now lives inside this repository at docs/. It is published together with the catalog at https://hub.oscar.grycap.net/guide/ and includes:
- Contributor prerequisites and local setup instructions.
- Branching and review workflow checklists.
- Detailed explanations for each RO-Crate section we rely on, with examples pulled from the in-repo services.
- Validation tips, troubleshooting tables, and templates.
Each service can define its own license. Make sure to include it in the RO-Crate metadata when applicable.
Contributions are welcome! Please open an issue or a pull request to suggest improvements or add new services.
📬 Contact: GRyCAP - Universitat Politècnica de València