Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Week of March 21 Highlights

  • Lotus Bugfest
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyBF-245
      • ISBN and invalid ISBN identifier types not showing properly
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIMARCAUTH-100
      • MARC Authority - When user clicks on "Heading/Reference" value at result pane, exact matches for the value aren't highlighted
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIMARCAUTH-102
      • MARC Authority - Search doesn't start after editing the advanced search query from search box.
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODINV-661
      • MARC Holdings - error appears when you save "MARC Holding" record after editing it in quickMARC
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIDATIMP-1112
      • MARC Authority - Data Import fails for import of authority record
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIIN-1962
      • When viewing Instance, identifier pair values are misaligned. See also
        Jira Legacy
        serverSystem Jira
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyUIIN-1962
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODEXPS-80
      • order export jobs showing are showing a "Currency" not found error message rather than successfully exporting orders to EDI
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODDATAIMP-659
      • Data import fails to create FOLIO Holdings
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIDEXP-270
      • Data Export: The search box do not contain searching value when User filtering result list by Record type in the Select Transformations
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODINVSTOR-149
      • Sorting contributor types ignores spaces
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODDATAIMP-656
      • Data Import: Records that were imported using DI and in that job had a MARC modification on the incoming file and where you then overlay that record using single record import result in an error
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIMARCAUTH-107
      • MARC Authority: Facet list for subjects has random value
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODINV-550
      • Bound-with parts get empty collection
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIMARCAUTH-105
      • MARC Authority - updating advanced search model query doesn't return expected results
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIIN-1971
      • The original work was implemented with the work done on ticket UIIN-1645, but now when bugfest testers test in Bugfest Lotus these searches using the search option All, does not work. This can be reproduced in FOLIO Snapshot.
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyUIIN-1934
      • Inventory App icon: Sometimes the "Something went wrong" appears when this is clicked
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODINVSTOR-889
      • Newly created tag doesn't appear in list and it's not possible to search for tag (tested on instance record)
    FOLIO Snapshot
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODQM-212
      • Unable to save MARC record in quickMARC

...

Week of March 14 Highlights

...

  • Data Export:
  • MARC Holdings records:
    • And Data Import: MARC Holdings during data import flow, we should use pre-defined MARC Holdings source (which is created in the reference data with pre-defined id = 036ee84a-6afd-4c3c-9ad3-4a12ab875f59).
    • Functionality in Kiwi: This wiki page explains how you can test MARC holdings records in snapshot.
  • Administrative Notes:
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyUXPROD-2867
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINV-581
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINV-582
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyMODINV-580
     
    • These concern the holdings, items, and instance records. We are some steps closer to the administrative notes for instances, holdings, and items.
  • Mapping rules: This only applies to institutions that have custom mapping rules. This is for the marc-bib.
    • If you have both custom and the default mapping rules, make sure to follow these steps for consistency:
        1. Send GET request to  /mapping-rules/marc-bib to retrieve the mapping rules
        2. Send PUT request to /mapping-rules/marc-bib and put in the body the result of step 1 
        3. Use the script to clear irrelevant records in the db (make sure the correct tenant name is used in the script)
  • quickMARC permissions:
    • View and edit MARC holdings record
  • OAI-PMH
    • Holdings without associated items are now included in the response
    • Harvesting times have improved. Baseline reports and release comparisons. To implement this, you will need to run the reindex (see release notes)
  • Source Record Manager/Other:
    • Jira Legacy
      serverSystem Jira
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyMODSOURMAN-468
      • This concerns creating a new API and db table that should store and represent information for the Data Import landing page. More for those using the API or accessing data via the db (such as LDP, perhaps Panorama?).
    • Identifier UUIDs as text values rather than json stream changed approved. This will help those working with the API or accessing the data via the db. This is to speed up the process of saving the UUIDs. This is for Lotus.