Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Location

  • Session Overview
  • Date: Monday 03 June
  • Time: 14:00 – 17:00
  • Location: SB3-L111
    • Chalmers Campus Johanneberg. Go to building Samhällsbyggnad III. Entrance from Sven Hultins Gata 8. Go to floor 1. Room 1302.

Agenda

  1. Welcome and Introductions
  2. Overview of the DSpace 8.0 Release
    1. New Features / Major Changes
    2. Overview of Upgrade process from v7 to v8
  3. Open Discussion / Presentations (see "Topic Sign Up" below)
    1. Attendees are encouraged to bring anything they have built or are planning to build for DSpace. Demonstrations are welcome/encouraged. This is an opportunity to receive feedback from other developers or find potential collaborators. DSpace Committers will be in attendance to answer questions or provide tips/tricks. Committers will similarly share any newfeatures they may be working on (or brainstorming) for future releases.

Topic Sign Up

In order to present an idea or request a topic be discussed, we ask that you propose your topic in this sign-up form.  Please add your name next to any topic you wish to discuss, along with a brief overview of the topic (including relevant links).  Topics may only be suggested by attendees.

  1. DSpace 8.0: New themed component and linting rules
    1. Proposed by: Art Lowel (Atmire) 
    2. Brief overview: https://github.com/DSpace/dspace-angular/pull/2865 changed how making a component themeable works, in order to lower the chance of making a mistake. I could give an overview of what's changed, what you need to know to upgrade existing themes. We can also discuss https://github.com/DSpace/dspace-angular/pull/2343 and https://github.com/DSpace/dspace-angular/pull/2750 in that regard
  2. New python library for managing dspace: dspyce
    1. Proposed by: Eike Löhden, Jörg Bieszczak (University Marburg)
    2. Brief overview: With dspyce, we are developing a library to communicate with DSpace via RestAPI (or SAF). The library is still under development. It enables you to add, retrieve, update or delete data in DSpace, to work with bitstreams, entities and statistics. We could provide a short overview about the functionalities and would discuss further needs.
  3. DSpace 8.0: The new correction & publication claim services
    1. Proposed by: Andrea Bollini (4Science) 
    2. Brief overview: DSpace 8 introduces two new major services / framework that have been used to implement some of the new features introduced with DSpace 8 such as the OpenAIRE Broker Integration, the COAR Notify and Withdrawn/Reinstate workflow (see Quality Assurance , Publication Claim). These frameworks are expected to be used to implement more features and integrations in the next dspace versions and are a good fit for many use cases.
  4. DSpace 8.0: The COAR Notify protocol
    1. Proposed by: Andrea Bollini (4Science) 
    2. Brief overview: opportunity for asynchronous interoperability between other systems and DSpace (see also https://wiki.lyrasis.org/display/DSDOC8x/COAR+Notify )
  5. Improvements to the login process when multiple provider are enabled
    1. Proposed by: Andrea Bollini (4Science) 
    2. Brief overview: Porting of the Improvements to the ORCID Login Flow made in DSpace-CRIS and future opportunities to extend it to other providers.  Goal is to have this included in DSpace 9.0
  6. Brainstorming the Future of DSpace (9.0 and beyond).
    1. Proposed by Tim Donohue 
    2. Brief Overview:  This is an opportunity for attendees to talk about what they'd like to see out of DSpace in the future. What features, functionality or improvements would you like to see in future DSpace releases?  If you were able to prioritize the DSpace Roadmap, what is the highest priority feature/improvement on your list?  Is there any other feedback you have for DSpace Committers & Governance about upcoming releases?
  7. Linking of file access rights to special metadata field
    1. Proposed by David Gerner (NTK)
    2. Brief Overview: In order to be able to search and filter items according to access right of the primary file, it would make sense to able to configure special metadata field which inherits the access right value of the primary bitstream of an item. It could be also a valuable information to pass on in case of metadata-only harvest. 
  8. Choosing contributor roles with qualdrop value input type
    1. Proposed by David Gerner (NTK)
    2. Brief overview: How to deal with a plethora of contributor roles? Is each special role supposed to have it's own relationship type? And if so, is it possible to choose the contributor type along with its relationship using qualdrop value input field type instead of having dedicated voluntary field for each contributor type?
  9. Metadata description of related items which are not in the repository
    1. Proposed by David Gerner (NTK)
    2. Brief overview: We have a special metadata schema oriented at related items (enabling us to describe items without identifiers which are not in our repository). However, for multiple related items to work correctly, we need to find a way to bundle multiple metadata filed into clusters, so that it is apparent which metadata describe which related item.
  10. Example Topic
    1. Proposed by: 
    2. Brief overview:
  • No labels