Milestones
List view
This milestone is setup to have a target for the multi-user repo issues.
Due by November 3, 2025•4/4 issues closed- Due by September 1, 2025•20/20 issues closed
- Due by June 30, 2025•20/20 issues closed
Potential topics: - Extra data sources / sources for harvesting ([issue](https://github.com/research-software-directory/RSD-as-a-service/issues/810)) - License consultation - Software quality indicators/assessment - enable email communication channel to users
Due by April 30, 2025•15/15 issues closedPreliminary content: - Meeting at [Open Science Conference](https://www.open-science-conference.eu/) in Berlin (21-23. October) - Support for communities ([issue](https://github.com/research-software-directory/RSD-as-a-service/issues/616))
Due by February 28, 2025•19/19 issues closedMain theme of this milestone is providing a standardized API and cleaning up technical debt: - Standardised API (CodeMeta?) (issue for SPARQL) - clean up
Due by November 30, 2024•12/12 issues closedMain theme for this milestone is to come up with a useful set of metrics, and make it easier to plug in modules into the RSD: - KPIs / metric for internal use (management...) - Define set of metrics for NLeSC and HIFIS and see what the overlap is. - plugin (p.ex. licencing wizard) - evaluate: how big of a challenge is it to send mails from RSD (existence of mail addresses)
Due by September 30, 2024•7/7 issues closedMain theme of this milestone is to start with support for communities, better explanation in the UI and links to documentation: - Start with: support for communities - First meeting about steering committee - improve self-explanatory of UI - Improve on page (links to) documentation - start with documentation howto videos - Module for automatically pushing metadata to RSD - Assess Matomo Cookie-less tracking mode - Secure authorization cookie is still used in memory client side
Due by July 31, 2024•19/19 issues closedThe main topic of this milestone is improves communication with the users (notification, search, news), improved performance (large files, logs, many citations), and making a start with improved metadata exchange. - News - Improved themability - Improve themablility of UI (p.ex. coloring) - Notify users about new features - Improve personal pages - metadata format / API - move big files (p.ex videos) to git LFS - Fix search functionality - Some database operations seem needlessly slow, e.g. backend logs
Due by February 29, 2024•3/3 issues closed- Documentation - Infrastructure issues (backups, hosting, etc.) - Connecting more organizations - SURF Research Cloud (keep the momentum going) - Personal profile pages (do this in 2023) - Dashboards + metrics (continue in 2023)
Due by January 22, 2024•13/13 issues closed- Due by October 9, 2023•16/16 issues closed
Here we collect issues that live on the `rsd-v2-release` branch to prepare for the release of version 2 of the RSD. Todo before the release: - [ ] test V2 in NLESC and HH settings - [ ] collect feedback from selected users - [ ] update documentation? - [ ] last V1 release - [ ] public announcement?
Due by October 2, 2023•34/34 issues closed- Due by April 3, 2023•8/8 issues closed
- Due by February 27, 2023•8/8 issues closed
Since the Christmas period is rapidly approaching (and many people will be away), the main goal of this milestone is to slow down and take our time to tie up several loose ends and some technical debt gathered over the last few months. Topics included in this milestone: - add more tests / testing infrastructure - think about future CI/CD and demo setup - add more technical documentation
Due by January 17, 2023•10/10 issues closed- Due by November 21, 2022•13/13 issues closed
- Accomodate logging in with an alternative to SURFconext, probably ORCID - Provide external standardised API's so that organisations can import/export data, possible standards are OAIPMH, SPARQL + JSON-LD, etc. - Make a Wordpress plugin or create an API that Wordpress can use, so we can display data on the corporate website (https://www.esciencecenter.nl/) - Keep working on existing UX issues
Due by October 31, 2022•25/25 issues closedThe goal of this milestone is to process feedback and tie up the loose ends before the public launch of the RSD. Topics to look at include: - Process the feedback / bug reports / feature requests we received from NLeSC users in M7 - Complete / update the user documentation (docs site, instructions in RSD, link between both?) - Improve the research units concept - Improve landing page, logo, branding, etc. - Ensure we have suitable REST APIs for bulk import/export of data - Ensure we have suitable REST APIs for export of data to wordpress sites - Ensure we have suitable REST APIs data exchange with other services (NARCIS?) - Complete integration with Matomo (if needed) - Prepare workshop on RSD
Due by October 3, 2022•28/28 issues closedGoal of this milestone is to open up the RSD to the NLeSC users and collect their feedback / bug reports / feature requests, etc.
Due by September 5, 2022•26/26 issues closedThe main goal of this milestone is to tie up several loose ends in the software, organization, project and profile pages. This requires the following: - properly implement the maintainer role of pages, allow maintainers to be added, removed, etc. - properly implement the profile pages, which show a logged in user which pages she maintains. - ensure the software, project, organization pages interact as expected. - come up with a proper mechanism to invite new users, maintainers such that everything is secure and GDPR compliant - finish the login provider selection mechanism - finish up the RSD house style, and a mechanism to plug in an alternative one if desired In addition it would be nice to: - make a start on a backup-restore / database migration mechanism (needed once we run in production). - further improve the landing page. - further improve the documentation (both user and developer)
Due by June 1, 2022•25/25 issues closedThe goal of this milestone is to determine the technical stack we will use to implement and run the RSD as a service. This includes (but is not limited to) choices on: - frontend frameworks - authentication mechanism - backend database - scrapers / harversters - VM hosting NOTE: this milestone was created retroactively to clean up the issue list.
Due by February 1, 2022•14/14 issues closedThe main goal of this milestone is to start preparing to move the service to production. This implies the following actions: - Legal: \- Resolve GDPR discussion \- Properly license all files \- Find hosting provider? - Front-end: \- personal page \- managing maintainers for organizations - Back-end: \- finish database structure \- limits on DB fields \- backups (specific) \- database migration (generic) - Testing: \- CI/CD pipeline \- Security test, pen testing \- more test for frontend \- Load test \- Test with NLeSC by sharing link - get feedback - Generic \- SURFConnext \- Come up with date for the big switch \- Think about domain name
Due by July 6, 2022•30/30 issues closedThe main goal of this milestone is to produce a beta version of the project and profile pages of the RSD-as-a-service. This requires the following: # Project pages - determining which info should be on the project pages (legacy RSD is a good start). - design and UX - a project page should have its own path (example: research-software.nl/esciencecenter/projects/blabla) - editing of project info - generated overview of projects in an organization - linking projects to organizations and software (and vise versa) - adding project maintainers - overview page of all projects 'officially present' on the RSD? # Profile pages (is this name clear?) This is the page a logged in users starts on. It provides an overview of the software / projects / organizations the user is a maintainer of. It may also provide notifications, such as invites to join software/projects/organizations, or the status of invites that this user has sent? - Determine what should be on a profile page - Design and UX - First beta of implementation
Due by May 1, 2022•19/19 issues closedThe main goal of this milestone is to produce a beta version of the organizational pages of the RSD-as-a-service. This requires the following: # Organizational pages - creating an public & private organization page with its own path (example: research-software.nl/esciencecenter) - editing of organizational info & logo - generated overview of software 'linked to' an organization - mechanism to create such links (software requests to organization and/or vice versa?) - adding organization maintainer login(s) to RSD - overview page of all organization 'officially present' on the RSD? # RSD admin pages - private pages for RSD maintainers to add/remove/edit official organisations - RSD admin login for RSD # Software pages - update to include links to organization (official/informal?) - improve mention pages # DCCs - discuss current RSDsaas with individual partners - start pilot with one partner?
Due by April 1, 2022•18/18 issues closedThe main goal of this milestone is to produce a beta version of the software pages of the RSD-as-a-service. This requires the following: - an initial landing page for the RSD (Done: although mostly empty) - being able to get an overview of software (Done) - viewing the (public) software pages (Mostly done) - being able to log in to the system using Surfconext (Partly done: test accounts work, real accounts not yet) - creating a new software page and editing the data related to this software (In progress) - being able to restrict editing a software page to certain users - being able to get an overview of which software a logged in user can edit ("my software"?). This also requires the design for: - the initial landing page (current one is fine, but improve if time allows) - the software pages (Done?) - the software adding / editing page (In progress) - the login page (Done?) It requires the following harvesting / migration: - github language info (Done) - github activity info - github license info - Zenodo DOI from the concept DOI - Migration of the data from the legacy RSD (Mostly done, organizations remain an issue) In addition: - an initial setup for the CI/CD would be helpful to speed up development (in progress). - an initial definition of a "house style" for the RSD-as-a-service may be useful? Community management: - plan a kickoff meeting with DCCs
Due by February 25, 2022•29/29 issues closed