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

Instance Record. Accordion Descriptive data. Implement new elements and reorder data - part 2

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      Prokopovych
    • Front End Estimate:
      Medium < 5 days

      Description

      Release: Q4, 2018:

      Property In detail view In edit form Missing parts (Q4/part 2) Other comments
      Publisher role Q3 Q3 Publishers are currently formatted as a simple string but are going to be in a tabular display. This reformatting will be part 2 Formatting done
      Format category Part 2 Part 2   Reference table change, will be part 2 UIIN-151
      Block with Format fields (properties: category, term, code, source) to be set as repeatable Part 2 Part 2   Reference table change, will be part 2 UIIN-151
      Publication date change from date to yyyy Part 2 Part 2 Isn't it already yyyy ? (Yes, seems I've misunderstood, closing it, NE) UIIN-317
      Edition, to change from string to array of strings Part 2 Part 2   Breaking change, will be part 2 (UIIN-299) Done. Back-end merge pending (MODINV-78, MODINVSTOR-171)

      Purpose: To re-order and extend the metadata in Inventory Instance record, the accordion Descriptive data collected in accordance with the Metadata Management SIG discussions and the GAPS analysis done by the Data Migration Subgroup, which are captured in

      Acceptance Criteria:

      • Inventory Beta - Metadata Elements, column I (Descriptive data)
      • Fields where Jira Story UIIN-227, column B are in scope for this story
      • Elements with a check mark in column C is implemented for alpha, or later updates
      • Create, view, edit and clone mode of the instance record all need to be updated
      • The UI display should look like the attached UX wireframes
      • Metadata elements labels should be as shown in column A "Instance Metadata Elements" column (please pay attention to the label case
      • Form edit controls (and values, where applicable) are specified in the "Input Type" column
      • Repeatable fields are indicated in column G "Repeatable"
      • Required fields are indicated in column H "Required" - include asterisks where noted (these denote that the field is required)
      • Please note, some of these have input controls that will ensure they are populated (when records are created via the UI). Others will require a validation message if left blank but that is out of scope for this story
      • All other columns in the Inventory Beta - Metadata Elements (tab: Instance Metadata for Inventory) spreadsheet can be ignored

        TestRail: Results

          Attachments

          1. Edit_Instance_full_0810.png
            Edit_Instance_full_0810.png
            309 kB
          2. Instance_Full _0810_1.png
            Instance_Full _0810_1.png
            304 kB
          3. Instance_Full _0810_2.png
            Instance_Full _0810_2.png
            455 kB
          4. screenshot-1.png
            screenshot-1.png
            192 kB
          5. Skærmbillede 2018-10-26 kl. 13.56.13.png
            Skærmbillede 2018-10-26 kl. 13.56.13.png
            187 kB

            Issue Links

              Activity

                People

                Assignee:
                nielserik Niels Erik Gilvad Nielsen
                Reporter:
                charlotte Charlotte Whitt
                Tester Assignee:
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases