...

1. Alphabetic jump to (specific letter) in results listing (NOTE: Below browse tasks have a dependency on this feature.  Should we do this prior to the sprint?)
   
   1. E.g. Jump to a Title / Author starting with a specific letter or string, like http://demo.dspace.org/xmlui/browse?type=title
2. Build out Administrative Search/Browse tools (each of these tools is limited to Site Administrators)
   1. Find Item by Internal Item ID/Item Handle  (e.g. XMLUI: http://demo.dspace.org/xmlui/admin/item , JSPUI: http://demo.dspace.org/jspui/tools/edit-item)
   2. Browse Withdrawn Items (by Title) (e.g. XMLUI: http://demo.dspace.org/xmlui/admin/withdrawn , JSPUI: http://demo.dspace.org/jspui/dspace-admin/withdrawn)
   3. Browse Private Items (by Title) (e.g. XMLUI: http://demo.dspace.org/xmlui/admin/private , JSPUI: http://demo.dspace.org/jspui/dspace-admin/privateitems)

Resources

• DSpace 7 Angular UI
  • Codebase (master branch): https://github.com/DSpace/dspace-angular
    
  • Demo site: https://dspace7-demo.atmire.com/
• DSpace 7 REST API
  • Codebase (master branch): https://github.com/DSpace/DSpace
  • Demo site: https://dspace7.4science.it/dspace-spring-rest/
• DSpace 7 Learning Resources
  • DSpace 7 - Angular UI Development : Getting started with DSpace 7 UI (aka dspace-angular) and how to contribute
  • DSpace 7 UI Technology Stack : Overview of technologies we are using, and links to third party resources
  • OR2017 DSpace Angular Workshop : Angular UI Training Workshop resources (slides and hands-on activities) from the OR2017 conference in Brisbane, Australia.
    • The beginning of this workshop was also presented as a tutorial at the 2017 North American User Group meeting (at Georgetown University). Video of that tutorial is available at http://youtube.com/watch?v=c4AJ8HeZzcw
• Contributing Code to DSpace
  • Code Style Guide (for Java / REST API)
    • For Angular UI we follow the official Angular.io Style Guide
  • Code Contribution Guidelines (currently more specific to Java / REST API)

...

• Weekly Kickoff Meeting (each Monday)
  • Sprint Participants (or a representative from your organization) should attend the Sprint Week Kickoff Meeting in DSpace Meeting Room.
    • Anyone unable to attend must touch base with the Sprint Coordinator (Tim Donohue) via another means (Slack, DSpace Meeting Room
    .  
    • , email, etc) for any necessary information.
  • The goal of the Kickoff meeting is to:
    • Touch base & finalize plans / goals for the Sprint week (i.e. ensure everyone is on the same page)
    • Ensure all participants have assigned tasks, and any necessary support/resources to begin their work
    • As necessary, go through expectations / protocols of the Sprint (e.g. Contributing code via PRs, Where to ask for help/support, Meeting schedule for week, etc)
    • Address or discuss any questions that sprint participants may have
• Daily Standups via Slack: On each day of the sprint (Tues-Fri), prior to 15:00 UTC, each participant should report their status update in the Slack #dev channel.  This will act as our daily "standup" meeting.

  • Template (feel free to copy and paste into Slack and fill in the details)

    Code Block
    title Standup Template
    [DSpace 7 Sprint] Tasks completed: * List ticket titles / links that you completed (since your last update) * Please include brief textual description Working on: * List ticket titles / links that you plan to work on next (or continue work on) * Please include brief textual description Blockers: * Is there anything blocking your progress today? Give a brief textual description

    
    

• Additional meetings may be scheduled as necessary (depends on the Sprint)

...