Archived Data Import Filed Topics
Introduction
This page is meant to track archived topics. Archived topics are ideas for new or changed functionality that didn’t have any associated Jira issue added to the Data Import New Topic Spreadsheet. Once a new topic has a JIRA, this is managed through our labels expressed as dashboards of needs review or reviewed.
How to contribute to other people's new topics:
Do not add detail to closed or discussed topics as your comments may be overlooked. In this situation, it might be best to Add your details as a new topic and reference the previous topic.
To contribute to an existing topic. Add a new paragraph to the description column.
@mention yourself at the beginning of the paragraph
How to indicate you are also interested in a topic:
@mention yourself in the "Interested parties" column and add your institution name
How are topics archived:
When a topic status is set to closed by it's "Owner". The topic must also be moved to the Data Import Topic Tracker Archive.
Copy the topic and paste it at the top of the Archived topics page that is nested under this page
Delete the topic from this page
Closed Topics
Topic | Original Description/use case | Date Added | Provided By (Name/Institution) | Interested Parties | Has Been Discussed (Link to agenda/minutes) | Jira Link | |
|---|---|---|---|---|---|---|---|
| 1 | Preview import jobs before running. Select records to include/exclude from preview screen. | Review import results before committing | 5/29/2025 | @Ryan Mendenhall /Columbia |
|
| |
| 2 | Deleting old versions of records from srs |
|
|
|
|
| |
| 3 | View all logs: filters aren’t updated after logs deletion |
|
|
|
|
| |
| 4 | Incoming records tab duplicates error message from SRS tab in json |
|
|
|
|
| |
| 5 | Update MARC holdings job completes with status completed with errors |
|
|
|
|
| |
| 6 | Remove unnecessary data from SRS |
| 2023-10-09 |
|
|
| |
| 7 | Provide required field for receiving subfields in field mapping |
| 2023-09-28 |
|
|
| |
| 8 | Order data import for multiple copies always opens with quantity = 1 | When creating an order for multiple copies with a profile set to create an order, instance, holdings, and items, I would expect the quantity in the order and the number of items created to equal the number of copies. | 2025-05-22 | Christie Thomas |
|
| |
| 9 | Update Administrative Data Only | Users need to be able to update administrative data using a brief MARC record without the job updating the whole Instance and/or the underlying source record and obliterating a full cataloging record. | 2025-03-27 | Lynne Fors |
|
| |
| 10 | Order import logs | Order import log does not return job log entries in order. As a result, the log is not displayed in record order, cannot be sorted by record order, will not display more than 50 records, and breaks paging in the logs. | 2025-03-12 | @Christie Thomas / University of Chicago |
|
| |
| 11 | Allow for MARC field protection at the import profile level. | Data Import job profiles should have the option of protecting a field during import that is not protected at the system level. Currently MARC modifications allows for the override of system level field protections, but not the protection of a field during the import that is not already protected at the system level. This applies to single record import overlays as well as other data import jobs. | 2025-01-30 | Christie Thomas (University of Chicago) |
|
| |
| 12 | Ability to update instance and marc srs in same job | Users need to be able to update the administrative data and also override protected fields to update the srs bib record. Tested in lab session 10-17-2024 this didn’t work in Poppy (Chicago test environment). | 2024-10-17 | Lab session |
|
| |
| 13 | Reporting: Have the ability to download a list of errors from an import | Issue: The only way to see errors is to navigate in the log and to click on the title to see the jason. Having an export like in Bulk Edit would be helpful. | 2024-07-11 | @Jennifer Eustis |
|
| |
| 14 | Reporting: Have the ability to save a list of successfully imported records to a list in the Lists App | New Functionality. In addition to downloading a list, it would be great to be able to save the imported identifiers to a list in the Lists App | 2024-07-11 | @Jennifer Eustis |
|
| |
| 15 | Reporting: Have the ability to download a list of instance, holdings, or item record identifiers that were successfully imported | Issue: There isn't a way to retrieve a list of identifiers through the Data Import log. | 2024-07-11 | @Jennifer Eustis |
|
| |
| 16 | Additional values needed for Electronic access fields or 856 subfields | Issue: Right now, only a few subfields from the 856 are mapped. We would like to expand that ability to include the non public note (856$x), access status (856$7) and terms governing access (856$n). |
| @Jennifer Eustis |
| ||
| 17 | Ability to change the link to a profile rather than just remove it | Current situation: We are only able to link or unlink profiles (field mapping to action, action to a job, match to a job, etc). New Feature: We want to be able to change the link rather than just unlink Expected behavior: There is another option that allows the user to change the link to a different profile. Use case: The wrong profile was used and the new one needs to be added. Rather than unlinking everything, it'd be easier to just update the link to the correct one. | 2024-02-27 | @Jennifer Eustis |
| ||
| 18 | Add new subfields to Electronic access (856) | New subfields in the MARC 856 field need to be represented in Inventory data. The same elements should appear in the electronic access block in Instance, Holdings, and Item records. https://www.loc.gov/marc/bibliographic/bd856.html | 2023-09-14 |
|
|
| |
| 19 | Partial matching doesn't work | Partial matching, e.g. begins with, ends with, is required but it does not function as it should. Only exact matching seems to work. | 2021-01-25 | @Yael Hod (Stanford) |
| ||
| 20 | Review and fix Marc updates for individual fields | Currently (as of Orchid), the Data Import MARC Updates for specific fields do not handle repeatable fields properly. The logic needs updating, and UI may need updating to indicate how incoming repeatable MARC fields should be handled vis-a-vis the same repeatable field(s) in the existing SRS MARC Bib. This is similar to how the field protection logic needed updating to handle repeatable vs non-repeatable fields properly. | 2023-02-20 |
|
|
| |
| 21 | Asynchronous migration is not completed | The asynchronous migration script was run but migration has not been completed, the migration job is still IN_PROGRESS. | 2023-06-04 |
|
|
| |
| 22 | Duplicate field is added when updating $0 in linked marc bib field upon data import if field mapping profile allows $0 update | Duplicate field is added when updating "$0" in linked "MARC bib" field upon data import if field mapping profile specifically allows "$0" update | 2023-02-15 |
|
|
| |
| 23 | Fields duplicated when adding several subfields when updating marc bib upon import | Fields duplicated when adding several subfields when updating "MARC Bib" upon import when field mapping profile has rules allowing update of corresponding subfields in corresponding fields | 2023-06-01 |
|
|
| |
| 24 | Fields duplicated when adding one subfield when updating Marc bib upon import | Fields duplicated when adding one subfield when updating "MARC Bib" upon import when field mapping profile has rules allowing update of several subfields in all fields (including the subfield which is being added) | 2023-06-01 |
|
|
| |
| 25 | Subfield can't be removed when updating Marc bib upon import | Subfield cannot be removed when updating "MARC Bib" upon import when field mapping profile has rules allowing update of several subfields in all fields (including the subfield which is being added) | 2023-06-01 |
|
|
| |
| 26 | match on 035$a with qualifier fails | When updating an SRS record using a match on the 035$a with a qualifier on the incoming MARC record, the match fails. | 2023-11-15 | Yael, Corrie Hutchinson |
| https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/4670482 | |
| 27 | Field is shown after being removed via data import when field mapping profile has rule allowing updates for this field | Field is shown after being removed via data import (when field mapping profile has rule allowing updates for this field) | 2023-03-09 |
|
|
| |
| 28 | Investigate deleting old versions of records from SRS, SPIKE | When SRS records are updated, the previous version is marked as old (and the newest version is marked as actual), but the older versions are not deleted. Over time, many, many previous versions of records will build up in SRS and potentially affect performance. | 2022-08-16 |
|
|
| |
| 29 | The number of created invoices is displayed when all invoices have errors with invoice lines | Overview: ** The file has 18 invoices and 1104 invoice lines. Steps to Reproduce:
Steps to Reproduce:
Expected Results: The '0' number of created invoices is displayed in cells in the row with the 'Created' row in the 'Summary' table in logs. NOTE: Recreated on Poppy Bugfest:
| 2023-11-23 | Tetiana Paranich |
| ||
| 30 | Jobs run immediately after canceled jobs take excess time
| Overview: Jobs started immediately after canceling a job get stuck and don't progress | 2023-03-29 | Jenn Colt | ALL | https://folio-org.atlassian.net/browse/MODSOURMAN-970
| |
| 31 | Incorrect behavior of "Delete Files" button | Note: Does not always reproduce "Delete files" request deletes the file, but does not always show in the UI | 2022-06-02
|
|
|
| |
| 32 | MARC-MARC Matching Enhancements | MARC-MARC matches and MARC-Inventory matches have differing use cases. Pairing a MARC-MARC match with a more specific MARC-Instance or MARC–Holdings or MARC–Item match allows for identifying a specific record to be updated, or confirms that a new record is needed.
We want to ensure that MARC-MARC matching works properly for repeatable and non-repeatable fields, especially 0XX/9XX fields, and that they can pair well with Inventory submatches. In scope:
Out of scope:
Use case(s):
| 2020-05-13 | All | All | ||
| 33 | Data Import removes duplicate 856s in SRS | Overview: When updating an SRS record via Data Import, some MARC fields are duplicated while others are de-duped without notification or guidelines. Steps to Reproduce:
Expected Results: The SRS record contains duplicate 856 fields. Additional Information: We know that Data Import does not de-dupe the 903 field, for example, during an update but it does the 856 field. Data Import jobs which create new SRS records includes the duplicate 856 fields. This raises several questions:
From testing, there appears to be no difference between de-duping of the 856 when field protections are applied or not.
| 2023-06-13 | @Corrie Hutchinson (Unlicensed) | All | 2024-1-17 Data Import Subgroup meeting 2024-1-10 Data Import Subgroup meeting
| |
| 34 | Adding MARC modifications to imports with update actions creates broken records | Overview: Steps to Reproduce:
Expected Results: Overlaying the record works. The MARC is modified as described in the profile and the instance and SRS are updated. Actual Results: The instance is not updated. A modified SRS record is created but still has the original OCLC 001 and 003. QuickMARC will not work on the record. |