Page History

...

DSpace 7.1 and 7.2 feature prioritization

Kristi:

• The goal of the survey sent out to LG members was to have a fresh look at the backlog to help prioritizes features for 7.1 and determine which funding we need for it
• Kristi presents slides with the survey results (Link to slides)

Questions/discussion:

• Tal: URL structure changes, bitstream URLs also have a new format. This could be a problem because bitstream URLs do not redirect.
  • Tim: Please report this as a bug during testathon
  .
  • , it might simply have been overlooked
• Lieven: How was the ranking done exactly?
  • Kristi: Data have not really been ranked. Topics were only sorted according to number of votes. Mean vote is not a good indicator.
  • Lieven
  hast
  • reports he tried to do some weighted ranking, results were quite different to what Kristi has presented.
  • Kristi: Ranking is probably not so important, rather consider which features were included in the top 10.
  Survey gives some guidance on
  • Lieven: Weighted ranking does make a big difference, consider for example Sherpa/Romeo.
  • Lieven will further work on an weighted ranking analysis and share with the group
• JSPUI features did not move up in the ranking, this might be because there are only two JSPUI users in leadershipLG.

Breakout discussions: Prioritization of features for DSpace 7.1

...

• Breakout #3 notes
• Breakout #4 notes
• Breakout #5 notes
• What criteria did you use for voting and ranking features?
• Which results surprised you?
• What else should be considered when prioritizing features?

Breakout 1 (Maureen)

• Emphasis on Angular UI, pulling things into the UI that can be done via the command line
• Surprise: how high the exporting search results was in the list, batch import from ZIP file
• Bundling Consider bundling things: , e.g. entities features

Breakout 4 (Allan)

• Maybe survey results are not generablizenDiversity generizable due to diversity of organizations using DSpaceOnly DSpac, only 2 organizations using JSPUIOrganizations , some organizations waiting for 7.2 anyway
• Bundle features that make sense from dev perspective
• Prioritize features for new Dspace users (basic workflows)
• How we approached the survey: Putting user users in the center, removing thinks that are new (except for accessibility)

Breakout 2 (Pascal)

• want to look Look into weighted ranking
• take Take into account how much work a feature takes
• a A lot of highly ranked features that are not deal breakers – not sure why
• small Small group should work on interpreting the results

...

• Lack of representation of JSPUI users in survey
• Focus on submitter based features when filling in the survey
• 1 and 7.2 are arbitrary buckets, there could be more buckets to be pushed push features out more rapidly

Idea: create small group to look into this. Kristi: Steering will discuss what to do next. Maybe include discussion in Dspace 7 wgWG or build another small group as suggested.

Lieven: It would be good to know which leadres answered in the name of more users (beate, lieven)leaders answered on behalf of yarious users - Beate and Lieven himself seem to be the only ones

Lieven: what is the cut-off: How many out of the 10 features are really important to you? - LG members report numbers between 3 and 7 mostly

Any other business

Pascal:

• DSpace Anwendertreffen (Annual meeting for the German-speaking DSpace community organized and sponsored by The Library Code) will be held virtually April 15-16, 2021.

...

• Over 200 participants have signed up.
• Support from Atmire and 4Science.
• Meeting of

...

• German Consortium included.