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

Settings page. Inventory > Instances > Contributor Types




      Purpose: In Inventory we use the Contributor element for all contributor types, but we'd like to be able to express the role, or the relationship between a name of a contributor, and the given instance record (=bibliographic resource).

      The MARC21 Code List for Realtors, consist of the Relator terms and their associated codes designate the relationship between a given name and a bibliographic resource. The relator codes are three-character lowercase alphabetic strings that serve as identifiers. Either the term or the code may be used as controlled values.

      As a cataloger, I want to review and manage the list of Contributor 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 > Contributor Types (displayed in 3rd pane),
        • Then the Contributor Types setting page open (displayed in 4th pane) - see comment below re. STRIPES-363
      2. Scenario
        • When the Contributor Types setting page is open,
        • Then the top bar in 4th pane display: Instances > Contributor Types
      3. Scenario
        • The Contributor Type has following elements
          • Term. The relator terms are listed alphabetically
          • 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 Contributor Type can be set as a 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
          • Term
          • Code
          • Source
          • The actions buttons now displayed are 'Save' and 'Cancel'
      7. Scenario
        • When edit of an 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
        • When click on the trash icon it's possible to delete the
          • Term
          • Code
          • Source
      10. Scenario
        • Go to a given term, which is to be deleted
        • click on the 'trash icon'
        • Then the standard modal will show, warning about:
          • Headline: Delete Contributor Type
          • Text: The Contributor 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
        • When adding a new Term to the list of Contributor 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 for Code
        • A Select box for Source, where to select 'marcrelator' or 'local'. Default setting is 'local'

      Overview: See the attached wireframes.

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

      TestRail: Results


          Issue Links



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



                  Time Tracking

                    Original Estimate - Not Specified
                    Not Specified
                    Remaining Estimate - 0 minutes
                    Time Spent - 2 hours

                    TestRail: Runs

                      TestRail: Cases