Developers Meeting before OR13 on Mon, July 8, 2012

Who is invited?

• All Committers,
• All DSpace Community Advisory Team (DCAT) members,
• Any other interested DSpace developers or technology-savvy individuals

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).

Logistics

• Day: Monday, July 8th, 2013
• Time: 1:00pm - 5:00pm
• Where: Henry-Johnson Room (Mezzanine Level) in the Delta Prince Edward (Google Map)
  
  • Floor plan of the Delta Prince Edward (PDF)
• Attendance Limit: Likely 30-35 people maximum
• Post-Meeting: We will likely all head to a local pub (TBD) for dinner & drinks. You are also welcome to join us there if you are unable to attend the meeting.
  
  • There is a Bar Bingo Night after our meeting, which is an option.
  • Other nearby pubs with seemingly good ratings:
    
    • Gahan House Pub & Brewery (3-4 blocks away)
    • Olde Dublin Pub (3-4 blocks away)
    • Many more pubs in the same area.
      
      

General Agenda

AGENDA:

1:00pm : Introductions

•  Name, Institution, How are you using DSpace / How have you customized DSpace
• Assign a notetaker!

1:15pm : DSpace 3-5 Year Vision Initiative

• Overview of Vision Initiative
• Please read DSpace 2013 Vision Document before the meeting (At least the 5 Vision Statements, copied below – the Use Cases are still extremely rough)
  
  1. DSpace will focus on the fundamentals of the modern "Institutional Repository" use case. We are striving to meet the IR needs of the next 5-10 years
  2. DSpace will be re-architected to be "lean", with agility and flexibility as primary goals
  3. DSpace will include a "core" set of functionality that can be "extended" (think Wordpress-like plugins) or have "hooks" (integration points) to complimentary services/tools
  4. DSpace will be designed in such a way that it can be easily/quickly configured to integrate with new & future tools/services in the larger digital scholarship "ecosystem"
  5. DSpace will support low-cost, hosted solutions and deployments (by featuring an easy, "just works" setup)
• Discussion:
  
  • Opinions on the draft vision document?
  • How to get Tech folks involved. Bridging communication between "visionaries" and technology team to build a longer term technology roadmap.
  • Keeping the discussion transparent

2:15pm : Empowering Individuals / Small Teams to tackle features/bugs rapidly

• Initial Discussion at IRC Mtg dicussion on 2013-04-10 (starts around [20:32])
• Want to avoid "blockages" or slowing down progress by waiting around for "widespread approval" on any proposal/idea.  Instead, we want to let small groups move/develop rapidly, and trust that they will build something "good enough" (which we can later improve on if needed). These small groups would still need to communicate their work/progress back to broader developer community (to keep others in the loop / receive ongoing feedback / avoid duplicate projects), but need not wait for an "official vote" before moving forward with their work.
• Possible "quicker" workflow:
  
  1. someone raises an issue / feature idea
     
  2. several interested parties discuss it
     
  3. self-organized team presents an idea, hears objections and suggestions
  4. (if needed) team addresses immediate concerns and presents again
  5. (we hope) everybody is okay with amended proposal and work goes forward
     
  6. people talk about the work as it is progressing, and get more feedback
     
  7. finished work addresses all known issues and is voted in. If additional work is needed it may be voted in as a "beta" feature until it can be improved in future releases.

2:45pm : Break

3:00pm : Open Discussion Topics

• DCAT proposal to improve metadata support in DSpace. Please read: Updating the Qualified Dublin Core registry in DSpace to the latest standards of the DCMI Better yet, read the Proposal to Update QDC.
• DSpace Add-on / Plugin Modularity
  
  • What new modularity do we need to ease the creation/maintenance of add-ons?  How can we make them easier to install?
  • Some known add-on "integration" points with DSpace: 
    
    • Additional configs (In [dspace]/config/modules/)
      
    • Additional dependencies (JARs)
    • XMLUI Aspects (add and configure/enable)
    • XMLUI Themes? (add and configure/enable)
    • DB Schema (Not a prevalent use case, but possible for complex add-ons)
    • Updates to metadata & format registries
• SHARE -  http://www.arl.org/news/arl-news/2773-shared-access-research-ecosystem-proposed-by-aau-aplu-arl
  
  • What would it take to implement SHARE in DSpace? This is likely to of most interest to US repository managers and developers.
  • "Phase One" of SHARE calls for the following common metadata / protocol support (in the next 12-18 months):
    
    • ORCID or ISNI (for Principal Investigator ID)
    • Award Number (assigned by federal agencies)
    • Repository ID Number ("data field required to identify repository access location")
    • Publication ID (persistent identifier "to reference the journal article of the publication")
    • Data Set ID (persistent identifier "to location of stored data or data sets that are linked to the published article")
    • Copyright License Conditions (including embargo timelines/restrictions)
    • Preservation Rights (given to repository by author)
    • Sponsoring / Funding Agency Name
    • Reporting : "feedback loop to the federal agency and the PI's research office providing tracking of publications resulting from awards funded by the agency"
    • Core Usage Statistics : "reports to authors (and agencies, if desired) .. usage activity and downloads of their publications"
    • Metadata Exposure to Search Engines
    • SWORD support
    • OpenURL support
• Other topics (time permitting)

4:15pm : DSpace 4.0  Planning / Updates

• More detailed planning or updates around DSpace 4.0
• Are there any areas of high interest that need volunteers/support (perhaps based on earlier discussion)? I.e. can we identify areas of "high priority" or potential "low hanging fruit" that needs a person or two to just help out?
• Any topics coming out of today that could be targeted for 4.0?

5:00pm : End Meeting and Depart for Pub

Sign Up to Attend!

If you're planning to attend this meeting, please add your name to the sign up sheet. This will allow us to determine a proper headcount.

Sign Up Sheet - Will Be Attending

1. Tim Donohue
2. Mark H. Wood
3. Hardy Pottinger
4. Bram Luyten
5. Andrea Bollini (CINECA)
6. Sarah Shreeves (UIUC)
7. Ivan Masár
8. Andrea Schweer (LCoNZ)
9. Sarah Molloy (QMUL UK)
10. Ryan Scherle (will be 30 min late?)
11. Maureen Walsh (OSU)
12. Sid Byrd (Rice)
13. Sarah Potvin (Texas A&M)
14. Michael W. Bolton (Texas A&M)
15. Jonathan Markow (DuraSpace)
16. Terry Brady (Georgetown University)
17. Aaron Helton (United Nations)
18. Sarah Currier (Jorum, Mimas, University of Manchester)
19. Anja Le Blanc (Jorum, University of Manchester)
20. Richard Jones (Cottage Labs)
21. James Evans (Open Repository, BioMed Central)
22. Artur Konczak (Open Repository, BioMed Central)
23. Peter Dietz (Ohio State)

Want To Attend / May Be Attending

• (add your name here)

Will Not Be Attending

• Valorie Hollister - arriving late, will try to join everyone at the pub

Meeting Notes

• Meeting Notes: https://docs.google.com/document/d/1QzrmHDvpJlpsVo6e8tJvWk2rXZm1p_F3TaUcEKIeODU/edit?usp=sharing