Versions Compared

Key

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

...

  • Sprint Meetings (Please do your best to attend all three meetings. If you cannot attend a meeting, please touch base with Tim Donohue for any updates, etc.)
  • Daily Standups are on #dev-sprint channel in Slack. Just provide your daily updates via text chat, prior to 15:00UTC each day.
  • More information on Sprint Schedule / Meetings can be found at Sprint Schedule

Sprint Goals

(NOTE: Sprint Goals will be coming soon. Obviously, the primary goal is to create Sprint tasks for both the new Angular UI and REST API that can be claimed by our sprint participants.)

The below goals have been copied from DSpace 7 Community Sprint 1 (as a few may be carried over into this second sprint)

  1. Alphabetic jump to (specific letter) in results listing
    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. Administrative Search feature, which allows for faceted searching & browsing of "hidden" items.  This feature would replace the following two Administrative Browse use cases (by providing a way to filter items by withdrawn status and/or private status)
      1. Browse Withdrawn Items (by Title) (e.g. XMLUI: http://demo.dspace.org/xmlui/admin/withdrawn , JSPUI: http://demo.dspace.org/jspui/dspace-admin/withdrawn)
      2. Browse Private Items (by Title) (e.g. XMLUI: http://demo.dspace.org/xmlui/admin/private , JSPUI: http://demo.dspace.org/jspui/dspace-admin/privateitems)
  3. Administrative Edit Item form
    1. Build a simple edit item form that mirrors the existing XMLUI and JSPUI edit item pages (e.g. XMLUI: http://demo.dspace.org/xmlui/admin/item, JSPUI: http://demo.dspace.org/jspui/tools/edit-item)
      1. This form should allow Administrators to add/update/delete any metadata field values for this item.
      2. This form should allow Administrators to withdrawn/reinstantiate the item
      3. This form should allow Administrators to make the item discoverable/private
      4. This form should allow Administrators to add/update/delete bitstreams attached to the item.
      5. This form should allow Administrators to delete an item
  4. Improve developer documentation / getting up-to-speed documentation.


Note

July has turned out to be a difficult time to find Sprint Participants (most individuals we've reached out to are on holiday or busy with local projects).  So, the DSpace 7 Working Group has decided to use this Sprint #2 as concentrated effort towards closing out existing Pull Requests, and also working to finalize/complete in-progress "feature sets" from our Development Planning spreadsheet.


Sprint Tickets

...

Angular UI tickets

All Angular UI tickets are managed in GitHub Issues (under the DSpace/dspace-angular project). You will need developer access to claim individual GitHub tickets (contact Tim Donohue or Art Lowel (Atmire))

There are two ways to view the available tickets – either in GitHub directly, or via our dspace-angular Waffle Board.  Both views point at the same tickets, so changes in one are reflected elsewhere.

  • Sprint #2 "Milestone" (coming soon) (Start with tickets which are labeled "Ready". Other tickets may have dependencies that need to first be completed.)https://github.com/DSpace/dspace-angular/pulls
  • Waffle board (Any ticket in the "Ready" column can be claimed, though we recommend those with the "Sprint 2" label)

REST API tickets

All REST API tickets are managed in DuraSpace JIRA (as the REST API is being developed on the current "master" branch of the DSpace codebase). You will need developer access to claim individual JIRA tickets (contact Tim Donohue)

JIRA tickets (All "REST API v7" tickets with the "community-sprint2" and "ready" label)

 

Jira
serverDuraSpace JIRA
columnskey,summary,type,updated,assignee,priority,status,resolution,labels
maximumIssues10
jqlQueryproject = DS AND component = "REST API v7" AND labels = community-sprint2 AND labels = ready
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
Additional, unassigned REST API v7 tickets can be found in JIRA.  However, we recommend selecting a ticket with the "community-sprint2" label.