Uploaded image for project: 'ERM Platform'
  1. ERM Platform
  2. ERM-1799

Store "match key" information on PTI and PCI



    • ERM Sprint 120, ERM Sprint 121, ERM Sprint 129, ERM Sprint 131, ERM Sprint 132, ERM Sprint 133, ERM Sprint 134
    • Bienenvolk
    • Lotus R1 2022


      Currently when PTI and PCI information is stored it is linked to a Title Instance. In some cases, where some incoming data is subsequently found to be incorrect, it may be necessary to "fix" data in the local kb by re-linking the PTI and PCI data to a new Title Instance. In order to support this, we will start to store information on the PTI and PCI that can later be used to rematch PTIs and PCIs to title instances after the data for a title instance has been changed (e.g. one title instance split into two separate title instances).

      The proposed information to be stored as a set of "match key" information is mainly based on data in the KBART guidelines (where this maps to a KBART field, the KBART field is given in brackets for reference):

      1. title string (publication_title)
      2. issn for print version (print_identifier for serials)
      3. issn for electronic version (online_identifier for serials)
      4. zdbid
      5. ezbid
      6. doi
      7. isbn for print version (print_identifier for monographs)
      8. isbn for electronic version (online_identifier for monographs)
      9. date print version published (date_monograph_published_print)
      10. date electronic version published (date_monograph_published_online)
      11. author (first author)
      12. editor (first editor)
      13. monograph volume (monograph_volume)
      14. edition (monograph_edition)

      The first eight should be prioritised as they cover the information currently used to match incoming data to existing title instances. The remaining six could be relevant when matching monographs, but are not currently used.

      TestRail: Results


          Issue Links



                ostephens Owen Stephens
                ostephens Owen Stephens
                0 Vote for this issue
                3 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases