| Who? | What? | Note | Status |
|---|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology ( Oliver Goldschmidt) | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| Improve the ORCID login flow solving the issue related to private email address in the ORCID profile and/or discrepancy among the ORCID's email and the one in the existing DSpace EPerson | This project has been funded by ORCID under their GPF program. More details here Improvements to the Login Flow | | Status |
|---|
| colour | Green |
|---|
| title | In Production |
|---|
|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology ( Oliver Goldschmidt) | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| Allow multiple Affiliations per person on publication level | In DSpace-CRIS it's possible to set an affiliation for authors or other persons on publication level. But in the current implementation it's only possible to set just one affiliation per author. As far as I know, this is the same as on DSpace-CRIS 7. Does anybody use setting affiliations for persons on publication level and how do you handle that?
----- Hi Oliver, we are handeling it with further child-fields. Currently we are supporting one further affiliation - in future we want to add 3 more. If anybody has a better idea, we are interested. Best Dirk. Fraunhofer IRB (Dirk Eisengräber-Pabst) ----- Hi Oliver, in our settings one person has one affiliation (delivered via LDAP) and can set additional affilations by choice. E.g. https://fis.uni-bamberg.de/cris/rp/rp14224. So you enter the author's name in the submission and receive a preview of the entered affiliations, from which you can select one. That fits our needs.
Best Steffen, University of Bamberg (Steffen Illig ) | |
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology ( Oliver Goldschmidt) | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| Importing items as private with bulk import | On DSpace-CRIS 7 2022.03.01 it's possible to set items as discoverable or not discoverable in the bulk import excel file. But it's not possible to create items, which are really private (no READ permission to Anonymous). For us, this is pretty bad as we are using the bulk import to import persons from our LDAP and need to restrict access to some of them. Does anybody else have the same problem? | | Status |
|---|
| colour | Blue |
|---|
| title | Planned (with 4Science) |
|---|
|
|
| Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
University of Bamberg ( Steffen Illig )
| Script Merging Entities | Our use case is: by now we regulary merge Persons (rps), which are created by mistake during the submission or by our ldap. In Dspace-Cris 5.X this could only done by our developers. In DS-CRIS 7 we would like to have a similar function operable via process to enable more colleagues to do this work. We would like to merge two entities, so that only one entity remains. The remaining one should contain all relationships and metadatafields from the deleted entity without losing its own metadatafields. It has been confirmed to us that this feature is part of the Data Quality Module, which 4Sience is currently working on. We will therefore participate in the financing of this module (to become Open Source). Help is welcome.
| | Status |
|---|
| colour | Blue |
|---|
| title | Planned (with 4Science) |
|---|
|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology ( Oliver Goldschmidt ) | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| See all languages for specific metadata fields (instead of only the values in the language, which is currently chosen on the UI) | If metadata fields with different languages are set (for instance a title in german and a title in english), the german title will only be displayed, when German is chosen as the language of the User interface. For some use cases this is a very nice feature. But for some metadata fields this could be unwanted (for instance if you have subject headings in different languages, you may want to see all of them at once, independently from the actually chosen language). | |
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology ( Oliver Goldschmidt) | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| Set user for command line operations | On command line it is not possible to set a user, who should execute the operation on DSpace end. That is a problem, because it's impossible to create new entities via bulk import on command line as the user needs to be allowed to create new entities to the collection the import is targeting. | | Status |
|---|
| colour | Green |
|---|
| title | In Production |
|---|
|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology ( Oliver Goldschmidt) | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| https://github.com/4Science/DSpace/issues/419 | Bug on the itempages (at least with the advancedattachment rendering in DSpace-CRIS): the files are sorted randomly and the sort order from bundle2bitstream.bitstream_order is ignored. Anyone having trouble with that as well? | |
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
Hamburg University of Technology (Oliver Goldschmidt)| Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
| Status |
|---|
| colour | Blue |
|---|
| title | Planned (with 4Science) |
|---|
|
| Status |
|---|
title | Working on | https://github.com/4Science/dspace-angular/issues/66 Version information not visible on DSpace-CRIS itempages | The version information with a reference to the latest version and a version history for versioned items is not displayed on DSpace-CRIS itempages (in fact, it is visible on the full item view page and on generic DSpace 7, but not on DSpace-CRIS) | | Status |
|---|
| colour | GreenYellow |
|---|
| title | In ProductionIdea |
|---|
|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
| Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
|
|
| | Status |
|---|
| colour | Blue |
|---|
| title | Planned (with 4Science) |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | In Production |
|---|
|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
| Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
|
|
| | Status |
|---|
| colour | Blue |
|---|
| title | Planned (with 4Science) |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | In Production |
|---|
|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Initiated |
|---|
|
| Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | interested |
|---|
|
|
|
| | Status |
|---|
| colour | Blue |
|---|
| title | Planned (with 4Science) |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | In Production |
|---|
|
| Status |
|---|
| |
|---|
| colour | Red |
|---|
| title | In Production |
|---|
|
|