Page History

...

• Time gives an update on the current status of DSpace 7 development and the forthcoming beta versions
  • Dev team currently working on release of beta 5, should be released tomorrow, testathon starts next week
  • Beta 5 is feature-complete. Timing for final release (7.0) depends on feedback/bug reports from testathon. Maybe one or two month after the testathon.
  • Still looking for volunteers for security testing. Looking for 1-2 institutions to do an external audit to give a different perspective to what the dev team has already done in this area. See Security Testing
  • Third party (deque) will do an accessibility audit during the testathon. Co-funded by Lyrasis and TDL
  • Kristi: Congratulations to the dev team on the progress.
• Maureen gives an introduction to the testathon:
  • Testathon begins Monday. Everyone is encouraged to participate.
  • Please watch the videos on the information page. People can also add test definitions. See test plan. There are instructions on how to use the different test status on the “Summary” tab of the test plan. User personas are also described in the summary. Every feature needs to be tested, even those that have already been tested by Bram in March/April.
  • Maureen does a demo of doing a test: Open demo repository via link, do the testing, report the result.
  • If a test has already been done, the next tester should overwrite the last test result, no matter what the status of the previous test was. There will be small improvements during the testathon, so it makes sense to retest tests that had reported bugs previously.
• Lieven ask whether there is deadline/date for the release of 7.0? Community members have mentioned to him that it is a problem that there is not even a target date. What does the rest of the group think?
  • Tim: I No target date because it depends on output of testathon
  • Susanna: The date depends more on the number of bugs that are found, than on the dev resources. Prefers to wait after the testathon before communicating a date for DSpace 7.0.

  • Pascal: Of course everybody is waiting for a date. But is should Should be ok to wait until after the testathon before communicating a date. Date should be before OR 2021.Tal: A target date could help institutions in budget planning. Pascal: It could happen that we find a major bug when testing, it is not a good idea to communicate a date now.

  • Tal: A target date could help institutions in budget planning

  • Lieven: Typically, you classify but reports. We need a target date to push work forward.

  • Kristi: Move this discussion to breakout groups, DSpace 7 wg and stearing groupWG and Stearing Group.

Working and Interest Group Reports

Marketing Interest Group (Jennifer)

• Welcome letter created, Google doc on how to share your DSpace story, working on testathon messaging, work on website starting soon

Product Visioning Working Group (Scott)

• In the “getting started” phase, good initial conversations, get a high level sense of things beyond DSpace 7

Governance Working Group (Kristi)

• Apart from MOU topic (see below), questions re. timing of governance year were discussed, will be discussed with stearing and brought to leadership group

Questions:

• Robert: Are there any targets for how to migrate users to DSpace 7?
• Kristi: There is no plan, but it is an important topic. Need to help users migrate has been discussed, including getting support and funding.
• Jyrki: Next Leadership meeting is in July, which group will meet?
• Kristi; In practice, it’s never the new group that meets in July, but the one from the previous governance year. We should probably move the governance year to start in late September / early October.

Quarterly financial report

Laurie comments on the financial report:

• distributed via listserv.
• Reflects info as of 3/31/21

Variances

• Positive: membership, salaries/benefits, contract (dev) labor, travel, IDC, other
• Negative: fundraising, consultants

Overall: better than on track

3/31 report does not include 7.0 beta 5 development costs as those are not yet invoiced. Approximately $74,000 to be billed soon.

7.0 Development Costs

• Estimated: $ 300,000
• Raised: $ 153,227
• Allocated: $ 284,000 (includes pending invoices for Beta 5)
• Not yet using line of credit

Discussion:

• Kristi: Stearing authorized funded development through 7.1. Have to make decisions on how to manage that.
• Jyrki: Will there be another round of fundraising this year? There might be institutions willing to contribute again.
• Kristi: End of fiscal year is coming in US, if there are funds that could go to DSpace 7.1 development, please consider doing so.
• Robert: Are people more optimistic going into the next budget cycle? Mixed answers from the group.

DSpace-LYRASIS MOU

Kristi: The goals of the MOU update were

• to streamline the content of the MOU
• to make it more “evergreen” so that we don’t need to revise it too often

Changes:

• Most changes are the result of combining responsibilities (streamlining and cleaning up)
• Changes to how we work as Governance
• No end date, but recommendation to revise every 3 years
• Fees moved to appendix

DSpace Steering recommends adoption of a revised MOU developed by the Governance Working Group.

Vote: The MOU passes with no objections.

DSpace 7.1 and 7.2 feature prioritization

• Goal was to have fresh look at 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):

Survey results:

• Excel format: DSpace7.1-7.2-prioritization-survey-results.xlsx
• PDF format: DSpace7.1-7.2-prioritization-survey-results.pdf

Questions:

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 as a bug during testathon.

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 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.

JSPUI features did not move up in the ranking, this might be because there are only two JSPUI users in leadership.

Breakout discussions: Prioritization of features for DSpace 7.1

• Breakout #1 notes
• Breakout #2 notes
• 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?

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 things: e.g. entities features

Breakout 4 (Allan)

• Maybe results are not generablizen
• Diversity of organizations using DSpace
• Only 2 organizations using JSPUI
• 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 in the center

Breakout 2 (Pascal)

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

Breakout 3 (Tim)

• 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, could be more buckets to be pushed out more rapidly

Idea: create small group to look into this. Steering will discuss what to do next. Maybe include in Dspace 7 wg.

Lieven: would be good to know which leadres answered in the name of more users (beate, lieven)

Lieven: what is the cut-off: How many out of the 10 features are really important to you?

Any other business

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. Free registration at https://www.dspace-anwendertreffen.de/.

Over 200 participants. Support from Atmire and 4Science. Meeting of Germano Consortium included.