Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1106

Analyse and implement 'missing' elements in the Instance Record - part 2

    XMLWordPrintable

Details

    • Medium < 5 days
    • Medium < 5 days
    • Medium
    • Medium < 5 days
    • Prokopovych
    • R1
    • R1
    • R1
    • R1
    • R2
    • R1
    • R1
    • R1
    • R4

    Description

      Analyse and implement 'missing' elements in the Instance Record - input from MM-SIG working groups

      Source: https://discuss.folio.org/t/codex-metadata-analysis-when-should-a-new-instance-be-created/1001

      https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439

      Q4 2018 - Plan as of 9/12/2018:
      The fields are:

      • Instance status (and thus 'Date status updated')
      • Mode of issuance
      • Cataloging level
      • Statistical code

      Other fields that didn't make it with the Q3 2018 release (UXPROD-122) to be UI or UI ready:

      • Index title (present in back-end but will not be UI visible and is not yet populated)
      • Succeeding title (we may have the structure for that, but could be a design decision to make) -> UIIN-426
      • Preceeding title -> UIIN-426

      TestRail: Results

        Attachments

          Issue Links

            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-92 Instance record. Add ContributorType in the Instance UI

            • 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-224 Instance Record. Accordion Title data. Implement new elements and reorder data

            • 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-226 Instance Record. Accordion Contributors. Implement new elements and reorder data

            • 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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-282 Duplicate ... Instance Record. Accordion Related Instances. Implement elements

            • 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-284 Instance Record. Accordion Descriptive data. Implement new elements and reorder data - part 2

            • 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-288 Instance Record. Accordion Administrative data. Implement new elements and reorder data - part 2

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

            New Feature - New feature requests MODINVSTOR-205 rename Piece Identifier to Copy Number in the schema

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

            Task - A task that needs to be done. UIIN-165 Analyse identified 'missing' elements in the Instance Record

            • 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-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-260 Instance Record. Accordion Notes. Implement more elements and reorder data

            • 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-287 Instance Record. Accordion Electronic access. Implement new elements and reorder data - part 2

            • 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-362 Settings page. Inventory > Instances > Alternative title types

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

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases