Bugs:
- Data Export new Issue: Only 1 Electronic Access type from the FOLIO Holdings records is exported.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MDEXP-480 |
|---|
|
- Data Export and Data Import flow: View Source disabled in Kiwi, concerns exported files being reimported with the 999. See workaround in issue.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODSOURMAN-634 |
|---|
|
- Data integrity issues (Kiwi bugfest): Testing encountered issues of not being able to edit an instance record via quickMARC or the MARC and last updated date/time for holdings records.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODSOURMAN-627 |
|---|
|
- Data Import sort by Record column: Testing revealed that this isn't working properly in Kiwi bugfest.
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODSOURMAN-625 |
|---|
|
Kiwi Release Notes: These are still being worked on. Ann-Marie discussed new features and updates for Data Import. Charlotte is going over Inventory today.Here are some highlights below grouped by topic or app:
- 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.
- Administration Note:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODINV-581 |
|---|
|
and | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODINV-582 |
|---|
|
are now closed. | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODINV-580 |
|---|
|
is in review. | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-2867 |
|---|
|
- These concern the holdings, items, and instance records. We are some steps closer to the administrative notes for instances, holdings, and items.
jira| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-2867 |
|---|
|
- 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)
- 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:
| 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?).