CRUD Material Types

Description

Jakub, I added the for-next-sprint label to this one because it seems like it might be a candidate if we really don't have enough stories to keep the guys busy in Sprint 10. I know we don't yet have the design for where this should live or the UI scaffolding, but we might be able to just piece something together with the components we have and refine later. Worth discussing with the team, if we are looking for something extra for the sprint.

Purpose Implement basic CRUD functions for Item Material types. Material types are customer-defined and can be associated with Items.

As a library administrator
I want to be able to create, read, update and delete Material types
So I can determine the appropriate categories for use in my institution

  1. Scenario

    • Given the ?? page under Settings > Users (Need input from UX - LIBAPP-140)

    • When displayed

    • Then a Material types control should display

  2. Scenario

    • Given the material type control

    • When a new material type is created

    • Then Material type name can be specified

  3. Scenario

    • Given the Material type control

    • When a new Material type is created

    • Then:

      • It should display in the list of created Material types in Settings

  4. Scenario

    • Given the Material type control

    • When a new Material type is deleted

    • Then:

      • It should be removed from the list of created Material types in Settings

  5. Scenario

    • Given the Material type control

    • When a new Material type is edited

    • Then:

      • The edits should be reflected in the list of created Material types in Settings

NOTE: This should use the same component as the one used for Patron Group CRUD

Environment

None

Potential Workaround

None

Attachments

2
  • 28 Mar 2017, 02:05 PM
  • 28 Mar 2017, 02:05 PM

Checklist

hide

TestRail: Results

Activity

Show:

Matt Connolly March 28, 2017 at 2:06 PM

Sure! Screenshots attached.

Cate Boerema March 28, 2017 at 9:55 AM

Awesome, thanks ! Any chance you can post a screenshot? The demo site is down again and I'm curious how/where this got implemented. Thanks!

Matt Connolly March 25, 2017 at 1:32 AM

I've split the goals in this issue into two parts (as Jakub suggested doing for the patron groups CRUD issue). This issue now contains the goals for pure material type CRUD, and the material type-item interactions have been moved to https://folio-org.atlassian.net/browse/LIBAPP-169#icft=LIBAPP-169.

Jakub Skoczen March 20, 2017 at 11:42 AM

Guys, since this story is really focused on the UI/front-end handling of material types I have retroactively filed https://folio-org.atlassian.net/browse/DMOD-209#icft=DMOD-209 to track progress on the backend work (a prerequisite for this issue). This really should've been done in sprint10, sorry.

Cate Boerema March 16, 2017 at 1:20 PM

Hi guys. My understanding is there is just one material type per item and there must be one (it's required).

Done

Details

Assignee

Reporter

Priority

Sprint

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 1, 2017 at 3:39 PM
Updated February 15, 2018 at 3:32 PM
Resolved March 27, 2017 at 3:09 PM
TestRail: Cases
TestRail: Runs

Flag notifications