See the Changelog audience section for info about the expected audience and content of the changelog.
• Update Datacite mapping to set resource type of RAiDs to 'project'
- Component updates and refactoring
- Test framework and dependency management (Playwright for e2e, Vitest for unit tests)
- UI/UX enhancements (especially nested components)
- General maintenance and cleanup
- Updated UI components and logic, including new mappings and service point UI logic.
- Removed unused code, such as mappings, helper functions, and Keycloak functions.
- Added new features like async/await, Postman request collection, SP switcher, CORS to user-groups endpoint, and a restore button.
- Created and refined error handling, history pages, and mapping files.
- Fixed bug that set embargoed Raids to 'draft' in Datacite. Embargoed now use the 'register' event.
- Fixed bug with missing Raid history.
- Added endpoint to allow users to switch between active service points.
- Added endpoint to expose all groups a user belongs to.
- Added BFF (Backend for Frontend) to store additional data for UI that we don't want in the API.
- Added
stageenvironment
- Added API validation error messages to the frontend
- Added service point selector
- Added additional end-to-end tests
- Removed unused legacy code
- SAML authentication with AAF
2024-05-14
- Minor bug fixes
- Bug fix to allow RAiDs to be findable in Datacite
2024-04-22
- All new UI
- Handles replaced with DOIs
- RAiD versioning and history
- Removal of auth endpoints from API
- Removal of experimental API
- Shared stack templates across environments
- Fix to validation of ORCID to allow x in checksum
2023-05-15
- Additions to mint/edit page:
- Spatial coverage field
- Traditional knowledge label field
- Option to disabled editing by service point
- PID validation
- check ORCID exists for contributor
- check ROR exists for organisation
- check DOI exists for service point
- note that the service-level-guide has been updated to allow that API requests maybe rejected if they have too many PIDs associated
- New metadata blocks:
- spatial coverages
- traditional knowledge labels
- introduced the InMemory stubs for APIDS, ORCID, ROR and DOI
- this is noted in changelog not because it changes anything, but the
deployment plan should take it into account, specifically:
- attention should be paid to env config (shouldn't need changing)
- post-deploy tests should verify that we didn't accidentally start using in-memory handles in production
- this is noted in changelog not because it changes anything, but the
deployment plan should take it into account, specifically:
- DB changes
- bumped width of
raid.handlecolumn - edit service point new column
- bumped width of
- Metrics publishing to AWS CloudWatch introduced
- must be enabled in config
- remember to add the permissions to the ECS task role (not the ASG
cluster role), see DEMO
ApiSvcEcs
2023-04-11
- Change public landing page title from "Raido" to "RAiD"
- Add sign-in warning of uBlock Origin / ORCID issue
- Add "Copy handle" button to the home page list
- Add download for "recently minted raids" report
- Default the lead organisation on the mint page to the institution associated with the service-point.
- Add item to menu for admin users to access API keys
New metadata blocks:
- subjects
- related Raids
- related objects
- alternate identifiers
2023-03-15
Initial production deployment.
The changelog has multiple audiences:
- communications team - for preparing the notification email that
will be sent for a new deployment
- mostly interested in the UI section
- but they also need to know about deprecations of stable API endpoints
- client API integrators
- mostly interested in the API section
- test team
- interested in both UI And API sections
- deployment team
- interested in the infrastructure section