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

    • Prokopovych
    • 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

            clones

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-227 Instance Record. Accordion Descriptive data. Implement new elements and reorder data - part 1

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            New Feature - New feature requests MODINV-71 New Instance properties, 2018Q3

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests MODINV-78 Instance: Make edition repeatable, rename to 'editions'

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests MODINVSTOR-152 New Instance properties, 2018Q3

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests MODINVSTOR-171 Make Instance.edition repeatable (Instance.editions)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-166 Add accordions to the detailed view of the Instance Record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-248 Instance edit form. Look up feature when assigning Format

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-273 Add accordions to the edit view of the Instance Record

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UIIN-317 Change publication date from date to 'yyyy'

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UIIN-318 Status for additional fields as well as changes to, moving of and reformatting of fields.

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-330 Instance record (detail and edit form). Change Format field group to be repeatable

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-247 Instance edit form. Look up feature when assigning Resource type

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UIIN-299 Render repeatable `editions`

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1106 Analyse and implement 'missing' elements in the Instance Record - part 2

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases