Timestamp for the creation date of projects and resources
The next live deployment will bring another new feature: a timestamp for the creation date of the project or resource will be added to the project and resource settings. This will help both Coscine users and the support team to classify problems or malfunctions in terms of time.
Account deletion
Users can now also delete their Coscine account themselves, provided they are not affiliated with a project. Explanations of this new feature can be found in the documentation.
Status message portal
All logged-in Coscine users can now access the status message portal via the “?” tab, where they can view potential fault reports relating to Coscine. This does not replace the banners on the platform that indicate restrictions but serves as an additional supplement with further information.
Access token
At the request of the community, the minimum validity period for Coscine access tokens has been reduced to one day. Previously, it was one week.
Migration Completed
We hope you had a good start to the new year. Exciting developments await us again in 2026 at Coscine. In this newsletter, we report on new features that have been developed in recent weeks. We are also very pleased that the migration from the old to the new storage system has been completed and that more universities have successfully completed onboarding for Coscine.
API Keys Available for Additional Models
Features:
- Users can now create and manage API keys for multiple models:
- For employees: In addition to OpenAI GPT OSS 120b API keys for the following models are now enabled: GPT-4o mini, GPT-4o, GPT-4.1, and GPT-5.1.
- For students: In addition to OpenAI GPT OSS 120b API keys for the following models are now enabled: API keys for Mixtral 8x22B / Mistral Small 3.2 are now enabled
Slurm Update for Claix
We updated Slurm to a newer and more stable Version: 25.05.5
This upgrade fixed issues we had with our scheduling system and internal rights-management database.
We improved how Slurm calculates priority for pending Jobs based on user feedback and internal metrics. Here is a short summary with basic details.
In short:
– Job waiting times will be more predictable and intuitive.
– Longer waiting times will increase the priority of a pending jobs.
– Jobs will still be able to access resources quickly if recent resource usage quotas are low.
Details:
– A pending job will not be delayed by any other new jobs (see its expected start time increase into the future) after 24 hours of waiting.
– Note that other software or hardware malfunctions might still cause delays in jobs, but new jobs will no longer cause this after 24 hours.
– A pending job with low fair-share factor might still be delayed by new jobs with higher fair-share factors during the first 24 hours of waiting.
– The project used for a job (default or otherwise) will determine its fair-share priority factor based on recent resource usage.
– Projects that have already used their “fair-share” of resources, will have a lower fair-share priority factor than projects with lower recent resource usage.
– Priorities and fair-share priority factors only matter for comparing jobs waiting for the same resources (e.g: partitions).
Release Notes Version 2.46.0
Improvements and bug fixes:
- Funtionality for searches has been enhanced
- Address display in the learning room list has been adjusted
- Various bug fixes
Release Notes Version 2.45.0
Improvements and bug fixes:
- Search results for courses, rooms, and persons are now highlighted
- Building names are now displayed in room details
- Various bug fixes
API Keys for Users
Features:
- Users can now create and manage their own API keys:
- Currently for the OpenAI GPT OSS 120b model
