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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Developers / DCAT Meeting before OR16 on Mon, June 13, 2016

Face-to-face developer's meeting on topic of the DSpace RoadMap at OR2016 in Dublin.

Who is invited?

If you don't fall into one of the above categories, you are still welcome to attend. However, be warned that discussion will likely get very technical at times (which is why we recommend you be a developer or have a technology background).

Please sign up for this "working meeting" as follows...

Logistics

Agenda

Format of Meeting

This meeting will be organized as a group discussion. Although at times one or more of us may lead discussion sections, it is meant to be a group discussion and not a series of presentations.

9:00am : Introductions

  • Name, Institution, How are you using DSpace?, How have you customized DSpace (or anything you'd be willing to contribute back)?
  • Assign a note taker!

9:15 - 11:00am :  New UI Initiative , Decision Making / Collaboration

  • DSpace New UI Initiative and Roadmap to DSpace 7
    • How we got here (DSpace UI Prototype Challenge)
    • Why Angular 2? (Risks vs opportunities)
    • Proof of concept: https://github.com/DSpace-Labs/angular2-ui-prototype
    • DSpace 7 proposed architecture (overview), including necessary REST API enhancements
    • How you can help / How would you like to help
      • How can DCAT support this initiative / provide feature suggestions/expertise?  How can other developers / institutions get involved?
  • DCAT, Committers and Steering/Leadership: How we collaborate and make decisions together
    • Streamlining the ways to get new features approved and into DSpace
      • Which features should be pushed up for DCAT or Steering approval first?
    • Moving the code through technical approval process. Are there ways to streamline?
    • Streamlining the ways we share expertise / contributions between and within our groups?

11:00 - 11:15am : Coffee Break

11:15am - 12:30pm: DSpace-CRIS (and other topics)

What would YOU like to hear about or discuss?  Please add your ideas to this list, and if we have extra time during our meeting, we will pull topics from this list to discuss.

  • Creating a community for repository managers/super users to share expertise.
    • Our developer meetings and DCAT discussions are often task-oriented and future-focused (next software release).  
    • We do not currently have a forum for exploring existing system features (facets, workflow, permissions, etc) and discussing best practices around those features.
      • Comment (from Tim): There may be direct opportunities to start some of this in the design / implementation of the new User Interface. I would love to have feedback on feature best practices and UI design. This is a great opportunity to build the UI we need/want, and not just recreate what we already have.
    • A forum such as this could be a useful way to nurture future project contributors.
  • The DSpace 6 Service API - What is now possible
    • The new service API introduced hibernate into DSpace.  What capabilities does this infrastructure enable (performance tuning, diagnostics, etc)?
  • Metadata Authority
    • The metadatavalue table contains 2 columns: authority and confidence.  
    • What is the intended behavior of these fields?  Are these fields behaving as expected? (note: the intended behaviour is documented in the Data Model section here: Authority Control of Metadata Values#DataModel)
    • There has been some recent discussion of text vs URL's in metadata.  Could these fields provide a solution to the issues being discussed?
  • Usage Statistics - how to deal with inaccuracies such as bots.
    • NOTE: For folks interested in this topic, there are a few OR16 sessions related to improving DSpace statistics:
  • Overview of the process of how new code gets into DSpace; not just the GitHub-specific process, but what discussions take place, the whole workflow, and where people can help to move code through that process.
  • GPG-Key-Signing: We sign our releases but we didn't build a chain of trust yet. Let's cross sign our keys to catch up. More info here (you'll need to print something before-hand if you actually want people to be able to sign your key).

Sign Up to Attend!

If you're planning to attend this meeting, please add your name to the sign up sheet below. This will help us better cater to content to the audience type. In addition, don't forget to officially REGISTER for this workshop from the OR2016 site (as that is the official registration form)

Sign Up Sheet - Will Be Attending  (If you are only able to attend part of the meeting, please note your approximate arrival)

  1. Tim Donohue
  2. Maureen Walsh
  3. Jonathan Markow
  4. Pascal-Nicolas Becker
  5. Mariya Maistrovskaya
  6. Terrence W Brady
  7. Susan Borda
  8. Hardy Potting
  9. Graham Triggs
  10. Roeland Dillen
  11. Andrea Schweer
  12. Ivan Masár
  13. Ignace Deroost
  14. Bram Luyten (Atmire)

Possibly Attending / Unsure

  • (add your name here)

 

Meeting Notes

Will be posted here after the meeting

 

  • No labels