Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Please prepare the abovementioned questions in advance of the meeting. You can leave your answer to those questions in a comment below. In case you can not attend the meeting but would like to share your opinion, feel free to leave a comment as well. 

Meeting notes

Part 1: Core functionalities of DSpace

Following are non exhaustive lists based on the outcomes of our discussion. The goal of this port of the meeting was to list the main features in DSpace. The underlying idea is when we improve those features the overal admin user experience will increase.

Which admin features are used most often:

  • Editing metadata
  • Eperson management and authorization: This, however, still is a labour intensive process in most cases. Adding Epersons to certain groups is often done manually.

Which features are seldom used:

We went over this question rather quickly. It was clear that nearly all of the mentioned features are relatively new and might still need to find their way in.

One of those less used features in DSpace are curation tasks. The reason why this is not often used might be that those are not very well organised, which hampers the work.

What should be configurable in the admin UI (Without having to reboot afterwards):

  • Themes: admins should be able to select different themes for each collection or community without requiring any technical assistance from developers. They should be able to adapt the basic look and feel of the communities and collections they're in charge of. 
  • Facets: Admins should be able to conveniently add or remove sidebar facets.
  • Changing the submission forms: Admins can alter the metadata schema's, but not the fields included in the submission form itself. Also, it would be a great improvement if submission forms could be tailored to the collection one it submitting to.

Part 2: Most important UI functionalities

Call Attendees