Versions Compared

Key

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

...

  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.

...

  • Add/Remove/reorder metadata
    • Effort: 24h
    • To do:
      • write the contract (it must be based on PATCH)
      • implement the patch method in the Item repository using a support class so to be reusable for each DSpaceObject (Collection, Community, EPerson, ...)
      • write tests
  • Withdrawn, Reinstatiate, make private or discoverable an item
    • Effort: 8h
    • To do:
      • write the contract (it must be based on PATCH)
      • implement the patch method in the Item repository
      • write tests
Delete an item
  • Effort: 8hr
  • To do:
    • write the contract (it must be a DELETE on the item endpoint)
    • implement the method in the item repository, it should consider where the item is used (it could be a template of a community/collection or wrapped in a workspace/workflow)
    • write tests
Manage bitstreams
  • Add bitstreams to an existent item
    • Effort: 8hr
    • To do:
      • write the contract (it should be based on POST multipart)
      • implement the method in the Item repository, it should be possible to specify the Bundle where the bitstream will be created
      • write tests
  • Delete bitstreams in an item
    • Effort: 8hr
    • To do:
      • write the contract (it must be a DELETE on the bitstreams endpoint)
      • implement the method in the bitstream repository, it should consider where the bitstream is used (it could be a logo of a community/collection)
      • write tests
  • Reorder the bitstreams of an item (out-of-scope?)
    • Effort: ???
    • To do:
      • write the contract (it should be based on PATCH... is the current item representation good enough?)
      • implement the method
      • write tests