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

Analyse and implement 'missing' elements in the Instance Record

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      Medium < 5 days
    • Confidence factor:
      Medium
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      76
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      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

      Q3 2018 - Plan as of 9/12/2018:
      Following fields that we can implement in detail view and/or edit form as time permits, provided that we release the related branches of mod-inventory-storage and mod-inventory now, something that's still to be decided:

      • HRID
      • Cataloged date
      • Previously held (form only I think)
      • Staff suppress (form only)
      • Suppress from discovery (form only)
      • Publisher role
      • Publication frequency
      • Publication range
      • Electronic access (group of fields)

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

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

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-228 Instance Record. Accordion Subjects. 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-229 Instance Record. Accordion Electronic access. Implement new elements and reorder data - part 1

            • 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-230 Instance Record. Accordion Classification. 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-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

            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

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Charlotte Whitt Charlotte Whitt
                Front End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Back End Estimator:
                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