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

Track changes to eresources

    XMLWordPrintable

Details

    • XXL < 30 days
    • XXL < 30 days
    • Bienenvolk
    • 82
    • Hide
      This feature relates to UXPROD-1791. Once it is possible for users to import and update e-resource data describing packages into the internal KB, there needs to be some level of change management and reporting alongside this to enable institutions to manage their lists of e-resources effectively.

      This feature will also ensure that data updates coming from GOKb are handled correctly and users can easily see what changes have happened
      Show
      This feature relates to UXPROD-1791 . Once it is possible for users to import and update e-resource data describing packages into the internal KB, there needs to be some level of change management and reporting alongside this to enable institutions to manage their lists of e-resources effectively. This feature will also ensure that data updates coming from GOKb are handled correctly and users can easily see what changes have happened
    • R4
    • R4
    • R4
    • R4
    • R4
    • R4
    • R1
    • R1
    • R1
    • R4
    • R1
    • R4
    • R3
    • R4

    Description

      This feature was significantly updated on 5th August 2019 to focus on the 'tracking' aspects. A new, related, feature has been created to manage changes on Agreement lines

      Where information about the content/coverage of a eresource is tracked by an external knowledgebase, use this information to update data about resources in Folio and provide information and functionality to those managing the resource on behalf of the library.

      Will include:

      • Tracking broad changes to a package as the result of a job (e.g. number of titles updated/added/removed)
      • Ability to see dates resources joined/will join and left/will leave packages
      • Ensure the current list of resources in a package/agreement is accurate based on the current date
      • Offer the ability for a user to see upcoming joining/leaving titles

      Discussion Jag/Owen 22nd July 2019:
      First steps

      • Rules for populating package join/leave dates
      • Rules for changes to coverage (does it extend or replace existing coverage?)
      • Ensure data model handles these
      • Ensure we have adequate logging on package import that user can see what has changed
      • Ensure UI is updated so it:
        • displays relevant information about dates resources joined/left a package
        • allows user to easily see current package content and upcoming joiners/leavers
        • only current resources in package are shown when user views "E-resources covered by this Agreement"

      Deliverable scenarios:

      1. ERM-395 Populate access start and access end dates
      2. ERM-397 Reporting change to the coverage dates on a resource (need to decide when this gets reported)
      3. ERM-392 Reporting change in title count in a package (maybe percentage)
      4. ERM-394 Viewing current content of package in UI
      5. ERM-393 Reporting change to the date a resource joined/date left package (access_from, access_to dates on resource)
      6. ERM-396 Viewing upcoming joiners/leavers for a package in UI

      NB any reporting required is about the job logging that it is making a change, not a subsequent diff between before and after states of a resource/package

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                ostephens Owen Stephens
                ostephens Owen Stephens
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases