...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Week of March
...
14 Highlights
...
Bugfest
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-567 - Script to refresh instances when MARC to Instance mapping as changed, from the work of I. Wells.
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIIN-1927 - For Lotus R1 2022. Fix the box to select which holdings to move to another instance to make sure it is more visible.
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDATAIMP-649 - For Lotus R1 2022. Sometimes in the first import of the day for a small number of the records in the import duplicates are created.
...
Week of March 8 Highlights
- Bulk Edit pilot for users has been pushed to Morning Glory.
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-592 Unresolved: Holdings records only shows first 100itemsitemsA very old bug from 2020, which has been solved long ago:- https://bugfest-kiwi.folio.ebsco.com/inventory/view/2e93db10-f5ce-4e64-8ae5-4a8ac489e5dd?qindex=hrid&query=ho126544&segment=holdings&sort=title
-
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-496 - You can save an instance with a statistical code of "Select Code" which isn't a code.
- Library Data Platform Project
- Bugfest: Seeking testers for the FOLIO LDP Query App
- Metadb derived table query development: Metadb is still in development and being tested at the Univ. of Chicago. If you are interested in the next version of LDP 1, many of the derived tables from LDP 1 are being ported over to metadb.
- LDLight: For users of LDLight, the schema naming is slightly ahead of Metadb schema naming convention. The tables without the t are the original ones from JSON including the JSON arrays. The tables with the underscore underscore t are the transformed JSON arrays.
- Tech Council Documentation: Changes proposed to the evaluation process for new development and roles of those involved in the evaluation.
...
- Data Export:
- Through the support of MinIO data export is now hosting agnostic.
- Recommended threshold on number of records to export is 300,000. Data export performance report for the Kiwi release.
- 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 server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-2867 Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-581 Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-582 Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINV-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:
- Send GET request to /mapping-rules/marc-bib to retrieve the mapping rules
- Send PUT request to /mapping-rules/marc-bib and put in the body the result of step 1
- Use the script to clear irrelevant records in the db (make sure the correct tenant name is used in the script)
- If you have both custom and the default mapping rules, make sure to follow these steps for consistency:
- 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 server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-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.