Versions Compared

Key

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

Attendees

Goals

...

  • October 11, 2017

Notes

Catch-up, Announcements

  • Wouter reports that it was surprisingly hot for OAI in Geneva where 20-25 DSpace workshop attendees learned more about DSpace 7 development.
  • Good contacts with http://www.who.int/en/, may be interested in using DSpace
  • OR2017 workshop was well-attended
  • Some discussion of DSpace 7 Outreach group work

Review action items

Sarah has provided a one-page DSpace 7 summary sheet (link above)

  • Useful hand-out for conferences and meetings particularly for repository managers
  • This is enough of a summary coupled with recent materials provided at conferences

Add links to current DSpace 7 use cases from make or break features wiki page--Felicity

Current development plan is already pretty ambitious—should be mindful about being too ambitious

  • Emphasis on including current features, not new ones, to keep current user base
  • Likely this will be the first of 7.–releases; there will be evolution to further releases
  • Adequate development resources would make it possible to make faster progress; capacity of the development team is key
  • Should this group develop an outreach campaign to encourage institutions to participate in hands-on DSpace 7 development?
    • Need for more people from the community to participate and work directly on DSpace 7
    • Not easy as an institution or a group to take on OS development tasks
    • Suggestion to work through national projects, networks of repositories, to get a call for participation out
    • Carol to reach out to COAR, Kathleen Shear
  • DSpace 7.0 is planned for release in 2018, taking into account the timeline and the progress
  • It was announced that at OR there would be a prototype that would include all current features
  • Early expectations too high?
  • Difficult in one year to transfer all the work that has been done over the years on DSpace
  • The "make or break" list is helpful in maintaining the view of what we want in the future

Ranking the make or break list of use cases

  • Some institutions have already done this

1.) Take use case overview sheet to DCAT2 for comment and review: https://docs.google.com/spreadsheets/d/1qUD_lU8i727n6s6pfbvJOs_hjOFFEGnXC_9VBpCgB

2.) Subsequently add columns for "nice to have", "must have", easiest for the development team to interact with

Current DSpace functionality

  • Don’t understand all current functionality that has been migrated from the 2 UIs
  • What am I going to get on top of the basic functionality—looking at it as an administrator
  • What are the  key enhancements?
  • Where is the overview of current complete functionality?
    • No overview at this time
    • "Tall order"
  • Having a full functional description is important; this group is moving towards that documentation with review of use cases
  • Suggestion to meet next week to continue discussing use cases

We will review the changes that have been made to use cases on 7/12

Action Items

  • We welcome Tim Donohue and Andrea Bollini from the DSpace 7 tech team who provided us with a greater understanding of design decisions and development process along with a status update.
    • Jose gave an overview of what this group has been working on including a review of use cases and requirements Use Cases , a collection of inspirational UI elements for reference, and external communications/messages.
    • Key discussions have been around the collection of use cases: functionality, field, title, primary actor, scope, or level, description of action
    • For each new use case, specific tag created, analysis needed



Update

  • Tim provided an overview of technical progress and process:
  • The DSpace 7 tech team meets weekly
    • They review and discuss mock-ups of key features and functionality (here): DSpace 7 UI Mockups
    • Aim is to make DSpsce 7  UI backwards compatible–config files will still be usable
    • Group agrees that collaborative development (with tech team) of a communication for the community at-large articulating features/functions of what will be included in DSpace 7 is needed
    • Users are working with many different versions of DSpace so its not enough to say that functionality from the 2 UIs will be included in the single UI, and developers are still working toward that goal.
    • This group will review current mock-ups at future meetings to provide timely feedback for developers.
    • If issues, questions from developers Tim or other will take notes, and ask for additional specific feedback
    • https://wiki.duraspace.org/display/DSPACE/UI+examples+of+inspirational+design+and+functionality
    • What this group thinks is very useful/needed for DSpace, Tim will remind developers of this resource
  • DCAT has created a spreadsheet of functionality


Action Items

1Condensed version of The DSpace 7 Project–A Simple Summary
2Add links to current DSpace 7 use cases from make or break features wiki page
1Reach out to COAR, Kathleen Shear regarding advice on how to ask for institutional participationCarol Minton Morris2Take use case overview sheet to DCAT2 for comment and review: https://docs.google.com/spreadsheets/d/1qUD_lU8i727n6s6pfbvJOs_hjOFFEGnXC_9VBpCgB
3Continue to add examples/comments to UI examples of inspirational design and functionalityAll
4Reach out to tech team and call attention to examples and comments on make or break wiki page