Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-150

Settings page. Inventory > Instances > Resource Type



    • Prokopovych


      Purpose: In Inventory we use the Resource Type element. The Resource Type follows the Term and Code List for RDA Content Types (MARC 336) - https://www.loc.gov/standards/valuelist/rdacontent.html
      See also: List in spread sheet: https://docs.google.com/spreadsheets/d/1scRQl09jroOy-c_emITk3EQ6lkj7XPRlkupPNuL-FfM/edit#gid=2048910067.

      RDA Content Types list contains Resource Description and Access (RDA) terms and corresponding three-character lower case alphabetic codes for RDA Content types.

      As a cataloger, I want to review and manage the list of Resource Types.


      1. Scenario
        • Login to FOLIO snapshot stable, and go to Settings
        • When selecting Inventory > in the menu Instances is displayed in the 2nd pane
        • When selecting > Resource Types (displayed in 3rd pane),
        • Then the Resource Type setting page open (displayed in 4th pane)
          no 4th pane / wireframe is accomplished in 3 is this ok? Yes this is okay - the fourth pane got not to be wide enough - awaiting responsive behavior of Panes/Paneset - STCOM-274
      2. Scenario
        • When the Resource types setting page is open,
        • Then the top bar in 4th pane display: Instances > Resource types
          the top bar says Rescourse
      3. Scenario
        • The Resource types has following elements
          • Term. Here the RDA content terms are listed alphabetically (X) says resource type
          • Code: Three-character lowercase alphabetic strings, which is the code for the given term
          • Source: Which is the list identifier; a string
          • Last updated: Data from the Metadata component
      4. Scenario
      5. Scenario
        • The Resource Type can be set as locally used term
          • The Term sequence is defined locally by the tenant
          • The Code sequence is defined locally by the tenant
          • The Source is set to be 'local'
      6. Scenario
        • When click on the 'pen' it's possible to edit the (X) no pen cannot edit -but can create
          • Term
          • Code
          • Source
          • The actions buttons now displayed are 'Save' and 'Cancel'
      7. Scenario
        • When edit of a Term, Code, Source is done
        • Click on 'Save'
      8. Scenario
        • When navigation away when in the middle of edit of a Term, Code, Source
        • Then the standard modal will show, warning about: There are unsaved changes (e.g. like in the Settings > Material Types)
      9. Scenario for local works but not RDA
        • When click on the trash icon it's possible to delete the row:
          • Term
          • Code
          • Source
          • Last updated
      10. Scenario
        • Go to a given term, which is to be deleted
        • click on 'trash icon'
        • Then the standard modal will show, warning about:
          • Headline: Delete Resource Type
          • Text: The Resource Type [given term] will be deleted.
        • Select buttons: 'Cancel' or 'Delete'
        • The modal will be e.g. like in the Settings > Material Types
      11. Scenario only local not RDA Yes this is the wanted functionality. The RDA content terms, is a standard, and these terms are not to be editable
        • When adding a new Term to the list of Resource Types, click on the '+ New' icon
        • A new line in the top of the list will be added, which consist of
        • An text input box for Term
        • A three-character input box restricted to lowercase characters
        • A Select box, where to select 'rdacontent' or 'local'. Default setting is 'local'


      Out of scope for this story will be systematic check against deletion of a Resource Type with associated instance records - see: UIIN-161.

      TestRail: Results


          Issue Links



                nielserik Niels Erik Gilvad Nielsen
                charlotte Charlotte Whitt
                Charlotte Whitt Charlotte Whitt
                0 Vote for this issue
                3 Start watching this issue



                  Time Tracking

                    Original Estimate - Not Specified
                    Not Specified
                    Remaining Estimate - 0 minutes
                    Time Spent - 1 hour

                    TestRail: Runs

                      TestRail: Cases