-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
Miet edited this page Oct 19, 2022
·
40 revisions
We are going for feature parity in November 2022 – which means what was possible in the original Biblio is possible too in the new Biblio interface. It might not work in the same way, but you'll be able to accomplish what you did before.
The invisible parts that make all the visible parts possible. We're restructuring the architecture in a sustainable way, to be able to adapt better to our audiences in the future.
Feature | Category | Status | |
---|---|---|---|
💾 Snapshot database | Creating a minimal database for publications and datasets. | Development architecture | DONE(BETA) |
🏗 Nomad | Makes running different environments and roll out features for different audiences possible. | Development architecture | Learning |
🏗 Temporal workflow engine | Makes long-lasting tasks possible in the background, so you an leave the page without worrying and visible to anyone using Biblio. | Development architecture | Development |
💻 GRPC API and remote client | In the long, this interface will enable people (internal in the first place, external in the second place) to use, improve and reuse the data inside Biblio. | Development architecture | Development |
🏃🏼♀️ Data migration & clean-up 🧼 | We have to migrate the data from the old to the new architecture. Since we have a new interface with some new assumptions, the data has to be cleaned along the way. | Development architecture | Development |
🤝 Reaching feature parity for researchers & librarians 🤝
Feature | Category | Status | Audience | |
---|---|---|---|---|
📖 New publication policy | There's a new policy for publications at UGent, Biblio needs to allow and reflect this. | Policy | DONE(TESTING) |
Everyone |
💬 Setting up communication flow | Allow for primary communication between researchers and librarians with statuses & message fields. | Communication | DONE(TESTING) |
Everyone |
✍️ Adding authors, editors, creators | Restructure the way creators, editors and authors are added, in a more transparent way. | Publication and dataset details | DONE(TESTING) |
Everyone |
☕️ Filter & Sort | Enable librarians and researchers to filter and sort in Biblio in various ways so they can do their work accordingly. | Overview | Development |
Everyone |
🔭 Dashboard | Give librarians a way to get overview on all the records to be reviewed & curated, so they can do their work accordingly. | Overview | DONE(TESTING) |
Librarians |
📤 Export | Enable librarians to export data. | Overview | DONE(TESTING) |
Librarians |
🖼 First version for data curation | Make sure data curators are supported in their job. | Redesign Biblio interface | DONE(TESTING) |
Librarians |
🧪 Testing | Testing for the involved librarians during the month of October and November | Quality assurance | Progress |
Librarians |
🪲 Bug fixing | Hunting for bugs & UX crashes | Quality assurance | Progress |
Everyone |
🦮 Accessibility strategy | Make sure where we need to improve, and plan for the future. | Accessibility | Analysis |
Everyone |
💬 Improve communication | "You don't have to sound smart, you have to make them feel smart". Make copy more accessible, and the steps more manageable. | Accessibility | Progress |
Researchers |
View everything we've already done.
Starting after November, we'll focus on continuous development. This means changes will not have a big launch, but rather implemented and shared whenever they are ready.
Feature | Category | |
---|---|---|
💬 In-app messaging functionality & notifications | Make interaction with researchers and administrative manageable | Collaboration and integration |
💭 External messaging infrastructure | This infrastructure would make features possible such as data exchange through push notifications | Collaboration and integration |
📝 MutantDB database | A database thats tracks changes to a publication on a more detailed level. | Development architecture |
🆔 Importing records with other persistent identifiers | For example, we need to be able to ingest datasets with other identifiers than we already have, that are industry standard. | Data ingestion |
🆔 Use ROR ID for Collaborative research units (SVOs) | Use this standardised way to refer to Collaborative research units to be able to integrate with other organisations such as GISMO | Collaboration and integration |
🍽 Table view | View records in Biblio in a table view next to the list view | Development architecture |