...
- If you were to be presented with a roadmap for DSpace today, which questions or concerns would you expect to be addressed in there?
- Read Brainstorms on a Future UI, especially the section "What makes a good UI (framework)? What common "use cases" do we need to keep in mind?"
Meeting notes
Creating the roadmap
It has to be specified what DSpace's core supposed to be. e.g. which features / functionalities should be included in each of the following DSpace releases and which features can be deleted, replaced or modified. This brings us to the first conclusion of March's meeting: All of the DCAT members should list features they consider to be part of the DSpace core and which they would like to be kept in each of the following DSpace releases. Consequently we should list which features are redundant and could be modified, replaced or deleted. This is important to know for constructing the roadmap. If some institutions rely heavily on one or more features, changing those might cause serious implications.
Nowadays DSpace is not very convenient for dealing with data, except for merely storing it. This is stil an opportunity for future development and should be taken into consideration while creating the roadmap. Making DSpace more data friendly.
Some modifications that should be rather easy, for example customising facets, require a lot of work due to the fact that several files have to be modified. It would be convenient if those things could be configured in the admin UI rather than in the configuration files. We should list all things admins should be able to do in the admin UI with a 'no rebuild' criterium in mind.
Future of the UI
We cannot continue the maintenance of 2 UI’s. after the security bug that led to the release of dspace 5.1 it is made clear we should choose between one of the current UI's or opt for an entirely new one.
Call Attendees
Bram Luyten (@mire) - @mire
- Ignace Deroost - @mire
- Pauline Ward - University of Edinburgh
- ...
- ...
...