Date & Time

  • Feb 10th 16:00 UTC/GMT - 11:00 ET 

Dial-in

We will use the international conference call dial-in. Please follow directions below.

  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free: http://www.readytalk.com/intl
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial in #
    • Once on the call, enter participant code 2257295

Agenda

As the outcome of our January 2015 call, we are dedicating this months call to a prioritization of the use cases we approached thematically in the second half of 2014.

Preparing for the call

If you want to prepare your participation to the call or if you just want to leave your opinion in the comments below please:

  1. Revisit the list of Use Cases or your own personal list of use cases.
  2. Try to decide for yourself or your stakeholders what your TOP priority (yes, a SINGLE usecase) would be
  3. If you have more time, try to think about your TOP 5 of use cases.

Discussed use cases and identified priorities

Early in the meeting, the DCAT group noticed that it would not be easy to prioritize the use cases discussed during last year's meetings. Before we can argue which use cases are most important or which are the biggest pain-points at the moment, we have to prioritize persona's. For example; usability flaws in the submission forms might be a big issue for end users, but a lesser one for repository administrators.

The DCAT group decided it would be important to keep the scope on the long term development of DSpace. Meanwhile use cases should be considered both on high (more abstract) level, as on a very specific (concrete) level. We do not want to focus on use cases that could be developed by a service provider on a short therm, or that could be included in DSpace 6. Instead we want to address use cases that give direction to DSpace's core.

We should also lay focus on use cases that we 'have to have' rather than those that are 'nice to have'. These 'have to have' use cases could be enhancements of existing features as well as the development of new ones.

During this meeting we did not decide a fixed prioritization of use cases. We did however agree that we could discuss the way we as the DCAT group could help in the development of the DSpace roadmap. This will be subject of our next meeting in March.

At the moment there is a discussion going on about the future of the user interface. Currently the angle is rather technical. Maybe we should contribute our findings so this discussion would include a mixture of technical and practical issues.

Call Attendees 

3 Comments

  1. Bram Luyten (Atmire)

    Instead of thinking about a single usecase, I think it would be worth while about which User Persona we care most. Meaning, which should require most attention in upcoming releases.

    In a recent talk, I overheard that the Drupal folks qualified their Persona priorities as follows:

    1. Content creators 
    2. Website builders
    3. Website visitors

    DSpace is not a general purpose CMS, but you can easily draw parallels between content creators & DSpace submitters, website builders & DSpace admins. Should it be our first priority to optimize for the content creators, or for administrators?

    (an answer to) this fundamental question or discussion may help us a lot when trying to prioritise individual use cases that are connected to different personas.

     

  2. Terrence W Brady

    Here are my top 5 use cases (in no particular order).  I am sorry that I will not be able to attend the discussion.

    Admin UI - Enhance the DSpace Curation System to Support a Flexible Query Tool

    Create the ability to place "dynamic collections" (pre-faceted view of a collection) within the community hierarchy.

    Stats/Metrics - Convey collection hierarchy to Google Analytics

    Admin UI - Theme management

    • Facet management would also be useful.  I debated picking the use case to update dspace.cfg instead, but I realized that the themes and facets need to be updated as new collections are added.  It is inconvenient to schedule a code deployment to be timed after the release of a collection.

    Structure - Create / manage files and metadata (as an Item)

  3. Bram Luyten (Atmire)

    Brainstorms on a Future UI

    TODO: add my notes on what was mentioned about this during the call

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.